[arch-general] Upgraded kmod, but --ignored linux & glibc, modules still in /lib - can I reboot safely?
Tom, All, I see the glibc /lib move is out of testing. I updated with --ignore linux,glibc and received an install warning from kmod stating: ==> Kernel modules are now only read from /usr/lib/modules... My modules are still shown in /lib. Does this mean I cannot reboot safely and expect it to work? Since I wanted to delay install of the new kernel and glibc, should I also have excluded kmod? -- David C. Rankin, J.D.,P.E.
Op zondag 15 juli 2012 00:35:58 schreef David C. Rankin:
Tom, All,
I see the glibc /lib move is out of testing. I updated with --ignore linux,glibc and received an install warning from kmod stating:
==> Kernel modules are now only read from /usr/lib/modules...
My modules are still shown in /lib. Does this mean I cannot reboot safely and expect it to work? Since I wanted to delay install of the new kernel and glibc, should I also have excluded kmod?
Now is not the time for doing partial updates, my personal idea about this is: you should have waited with your update or just updated everything. To answer your real question: you can no longer safely reboot. You could indeed try by downgrading kmod below 'kmod 9-2' but there is no guarantee that anything will work. If you have any other extra kernel modules installed, you also should have ignored them until you are willing to do a complete upgrade. --Ike
Am Sun, 15 Jul 2012 00:35:58 -0500 schrieb "David C. Rankin" <drankinatty@suddenlinkmail.com>:
Tom, All,
I see the glibc /lib move is out of testing. I updated with --ignore linux,glibc and received an install warning from kmod stating:
==> Kernel modules are now only read from /usr/lib/modules...
My modules are still shown in /lib. Does this mean I cannot reboot safely and expect it to work? Since I wanted to delay install of the new kernel and glibc, should I also have excluded kmod?
If you ignore (don't update) linux then the modules are, of course, still in /lib. Maybe you should update your system following the News on the homepage. Heiko
On 07/15/2012 06:07 AM, Heiko Baums wrote:
If you ignore (don't update) linux then the modules are, of course, still in /lib.
Maybe you should update your system following the News on the homepage.
Heiko
Hmm, I did, but I usually put off kernel updates for a week to insure there are not gotchas. I understand now that this update is an "all or nothing" update. Would have been nice to have that note as part of the announcement. We will get through it, it will just be a bit more fun... -- David C. Rankin, J.D.,P.E.
On Sun, Jul 15, 2012 at 12:35:58AM -0500, David C. Rankin wrote:
Tom, All,
I see the glibc /lib move is out of testing. I updated with --ignore linux,glibc and received an install warning from kmod stating:
==> Kernel modules are now only read from /usr/lib/modules...
My modules are still shown in /lib. Does this mean I cannot reboot safely and expect it to work? Since I wanted to delay install of the new kernel and glibc, should I also have excluded kmod?
-- David C. Rankin, J.D.,P.E.
it is possible to still have /lib/modules, but have your modules in /usr/lib/modules. Follow issue 2 from the wiki page mentioned in the news. There is a find command to tell you what is in /lib that is not owned. The grep command will tell you what pacman thinks should be in /lib, if you have something that is in there that isn't glibc, either pacman -R it or rebuild it with a fixed pkgbuild that puts them in /usr/lib
On Sun, 15 Jul 2012 00:35:58 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
Tom, All,
I see the glibc /lib move is out of testing. I updated with --ignore linux,glibc and received an install warning from kmod stating:
==> Kernel modules are now only read from /usr/lib/modules...
My modules are still shown in /lib. Does this mean I cannot reboot safely and expect it to work? Since I wanted to delay install of the new kernel and glibc, should I also have excluded kmod?
The kernel is not new, but the same with a changed location of the modules. Why would you ever want to mask linux? Just run "pacman -Syu" and reboot... -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/15/12 08:07, Leonid Isaev wrote:
The kernel is not new, but the same with a changed location of the modules. Why would you ever want to mask linux?
Those of us who are running Linodes may well all share this issue, because Linode supplies the kernel. But isn't this what kmod is for (I hope, I hope!)? - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQAxlHAAoJELT202JKF+xpsvQP+wYdUHNmTldIrPHPzGHCanq3 ufIzaw4GhOuYrIf9TT8/boR07NOOpdEpJUfsbIyYEJaw/dKhTeNaWD115H6q7UCv +MlmPAasg/2y20HOeZIrXeiq4vp53n3Jy8q7u/8lrjL3I/jBpAYSSpRg0IaodEp1 lh5AvIPs4kxegSd+90Pug5MiR23PsCr5vBL4v+vJxsFruN2p71MI0LHeMhy0Jxqc hlNQIoNSklXNkWKkXfVe2ensED3bjtv3R0vjwpzlUvvWKFa3uZqwAwU5XgMCYQ1n 6LjjXfRrpt+apOfKMjJ2rFQw7zU/NUvgGizMG5BpodoSKFjyTa4aNcRBWEs1NS/n r9lMyBzu6JcU/F0fRZAxiV+la6B3G3GUmVIHyESZe6S9PkJWs9XbI98a+KIc5zyJ T3TYK0IblM+9ba2jIOQDFoKaOvB9HTTbZEuSc2lBnNxkHTzb77tgGgyRh4ITm2A4 +uK2M+pwZJhv3fQFd5HFN9JCO2pMfgfYME+MiXvGzqMB5xf37emSa8o0ecSAYe4x iW7Rb+CwO1LPrVJgTWWe6ghrGE5tJDXTzNfm2lZGSF1bWeklgSaJYkvuEEGDtAEW 7+maAPayhb4gpHRBf3r1m0zgMpQREENneiAvCAeKNe7CXlRe9uxjoORBDahbnNlf Johmxsba1RjWczytuYEW =vOw5 -----END PGP SIGNATURE-----
On Sun, Jul 15, 2012 at 2:25 PM, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/15/12 08:07, Leonid Isaev wrote:
The kernel is not new, but the same with a changed location of the modules. Why would you ever want to mask linux?
Those of us who are running Linodes may well all share this issue, because Linode supplies the kernel. But isn't this what kmod is for (I hope, I hope!)?
it's pretty easy to run a custom kernel on Linode -- that's what i do with mine at least. ... prob not really an answer in your mind :-) but a possibility. personally i'm curious why it's an issue at all -- if /lib/ is a symlink, why can't modules in /usr/lib/ be found? doesn't kmod follow symlinks? ... all my stuff is working fine, but now i'm compelled to seek the answer. -- C Anthony
On 7/15/2012 3:55 PM, C Anthony Risinger wrote:
On Sun, Jul 15, 2012 at 2:25 PM, David Benfell <benfell@parts-unknown.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/15/12 08:07, Leonid Isaev wrote:
The kernel is not new, but the same with a changed location of the modules. Why would you ever want to mask linux?
Those of us who are running Linodes may well all share this issue, because Linode supplies the kernel. But isn't this what kmod is for (I hope, I hope!)? it's pretty easy to run a custom kernel on Linode -- that's what i do with mine at least.
... prob not really an answer in your mind :-) but a possibility.
personally i'm curious why it's an issue at all -- if /lib/ is a symlink, why can't modules in /usr/lib/ be found? doesn't kmod follow symlinks? ... all my stuff is working fine, but now i'm compelled to seek the answer.
I am having no troubles at all using 3.4.2-linode44 on an i686 instance.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/15/12 13:01, Ariel Popper wrote:
I am having no troubles at all using 3.4.2-linode44 on an i686 instance.
Yeah, it's working for me, too. But I haven't tried rebooting. ;-) I'd have to look into using a not-so-custom kernel (presumably from the Arch package). Ten years ago, I used to build kernels routinely. But it's not trivial anymore. - -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQAzKrAAoJELT202JKF+xp3C0P/j2jIq0SKD9vXDPX7wrujAXc WtgwkvOOqypXUlMQtHQxwI2j53psGzjcB/jAz2XVbcdSxbqRF6H7I1I4eRuF7gPV 7Axvz3P1K0gzGlb8WWuKOMp03PKS3TtfuXRYwSEQiSHBPoMcYMz8KeFhIM4dr2OY 1n6f4gKavBTdMyItaci4M6b4L1Ne4ERrPG+vkBXeGmprwgZMiyrWzjkCpqTF4Uul ZNBOXHi0GqnXBazgZaSKEpb7aC4fUaHK9tmKUzERIphYNKS+UKcYnHQik9nbwtW7 OHt39F4I8maalse+2F2ErrejV1ZxlZ3GeQJbjP50/hpDEcpJxCU0RrADZT/zwKyp AQ7mM9N97G/JrYV9Dd47gED5AdphEI4lfRc8EO3q2H0w+Jfl6xGAMt+ayKGy0KnO 6+iFyUA8iffi1Xk84YjTvuOrtIzRzp7kiMoxAO33+i/+IAcej1KMPr/lx2aiVeDZ CUgYwsakNZYaCk3yuS7MsIvALbibutMpVgYhZlG4X/6JiiPO+Pe6ZdTVJHbGN8Qj sW8TU8HqXAGphh2qc8yueb6MLwC1e7toI1CF7cOdaW/suXzJz7xQuAtEbLEmTmay nSDDkK/SJNkmdSBsGaLxZe9IcSeXRj/G67f5vUhRY3LbMJsIZLrV8hlyM4GHiQ5A T+0Ey44bNAoXzs3TXkNT =4FFg -----END PGP SIGNATURE-----
On Sun, Jul 15, 2012 at 4:14 PM, David Benfell <benfell@parts-unknown.org> wrote:
I'd have to look into using a not-so-custom kernel (presumably from the Arch package). Ten years ago, I used to build kernels routinely. But it's not trivial anymore.
nah none of that :-) i detest compiling things. i run the standard Arch kernel, same as any other machine -- you just have to configure your instance to use pv-grub. ... basically, you just need to make a grub-legacy menu.lst file, put it in the normal place on an ext3 partition, and go from there. no real work in the end. the arch kernel has all the necessary CONFIG_* bits to run unmodified in the Linode XEN environment. -- C Anthony
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/15/12 18:09, C Anthony Risinger wrote:
On Sun, Jul 15, 2012 at 4:14 PM, David Benfell <benfell@parts-unknown.org> wrote:
I'd have to look into using a not-so-custom kernel (presumably from the Arch package). Ten years ago, I used to build kernels routinely. But it's not trivial anymore.
nah none of that :-) i detest compiling things.
Whew! I mean it used to be fun. And I don't mind much when it's the ./configure-make-make install sequence. But kernel building never was quite that simple and I'd have to say it's become a lot more complicated now.
i run the standard Arch kernel, same as any other machine -- you just have to configure your instance to use pv-grub.
... basically, you just need to make a grub-legacy menu.lst file, put it in the normal place on an ext3 partition, and go from there. no real work in the end.
I went to the Arch Wiki (or, more precisely, my copy of it, since the original one often fails to answer), went to the Linode wiki (which doesn't talk about Arch Linux), and came up with the following (comments elided) /boot/grub/menu.1st: timeout 5 default 0 color light-blue/black light-cyan/blue title Arch Linux root (hd0) kernel /vmlinuz-linux root=/dev/xvda ro initrd /initramfs-linux.img groot=(hd0) But I missed something because when I went to boot, it still thought it was supposed to boot from (hd0,0).
the arch kernel has all the necessary CONFIG_* bits to run unmodified in the Linode XEN environment.
- -- David Benfell benfell@parts-unknown.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQA531AAoJELT202JKF+xp3e8P/36OaNv+Aa/8pEpuwfPwZ1rY sTjhQaIJM2RF50LMfOLZUqnIz9bae2simjfv2MUi6OgmeDjvDeSKMuDY//HXQlpE mtWlgoQyYFi0SJNnUS/t36wVT5SqKZUDEIfgxqRHy6stbNJd7aaJswkupZitpiT7 z3isrUe3pitGAmLvicpbqmbx2NIDJA6ZBOECdiOQ6FVsvrWrox0bt1p38u5267J0 9hv1AdovkJ74JkmYXZILQHSUNsToW5izzVqXsQXBCM+3OEMuSYfDgb40g/jNT0yV 6oZYnkSIEyKabLrMupEbIYiLFmm1nJ0sMo239C8d2BkyJLdJT1oecc548wvN3Yed K13uKbQGVzjQdoxXWbecBvzSgZAjyFTZ3NZqvF0Rw8ICryc1zAjBkWmIvb/7B9C/ pKnI6BcQaZAZ/SJWaguFiY4xeXgKBx+TUtnshgQTa9UegyYedcp21Uyw/pGrurTF W764dWxqTw/zu9HsBnJ1UEiI03ypaaVfRmSwY+7qZWBpbOD/Orp426/gxq7+zaGs y6X4Pny9fsOw1rmCp80yRvk9MkZSJ09rgHusO6LInCZDki2yyRPBEXYH751hCdF9 3s9COuTf2O8/cQraMX/cEGBWf66ZZkeHc738v26brcuhhQYJmg/Iw+euGvwog1mT TJaLJA83orUL0XRaSZtf =zQgR -----END PGP SIGNATURE-----
participants (8)
-
Ariel Popper
-
C Anthony Risinger
-
Daniel Wallace
-
David Benfell
-
David C. Rankin
-
Heiko Baums
-
Ike Devolder
-
Leonid Isaev