Re: Re Root symlink to /boot/vmlinuz
Brooks == Brooks R Robinson [EMAIL PROTECTED] writes: me thinks you would like make-kpkg (kernel-package) IIRC, kernel-package asks if you want the symlinks. I may be wrong, it's been a while since I've needed a new kernel :) Brooks Last I ran it (a couple of days ago) out of woody, it didn't Brooks ask about symlinks. It just does them as if the kernel you Brooks are installing is the new default kernel. I always have to Brooks go back and update my symlinks, but tehn again I typically Brooks have at least three different kernels ready to go at a given Brooks moment. Why do you have to manually update the symlinks? (incidentally, I have 6 entries in my lilo.conf, and only two of them are automatically changed on kernel image installation). There are a numbe of ways you can manipulate the symlinks. From man kernel-img.conf: == image_in_boot do_symlinks minimal_swap no_symlinks reverse_symlinks image_dest move_image relative_links use_hard_links == If you have ideas on additional customization, I would e interested in hearing what it is that you are doing. And then, of course, there are the hooks -- postinst_hook, preinst_hook, postrm_hook, prerm_hook that you can attach scripts to, and they shall be run at appropriate times. Indeed, there should be no reason to manipulate the symlinks manually. manoj -- The so-called lessons of history are for the most part the rationalizations of the victors. History is written by the survivors. Max Lerner Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
RE: Re Root symlink to /boot/vmlinuz
| me thinks you would like make-kpkg (kernel-package) | | | IIRC, kernel-package asks if you want the symlinks. I may be wrong, it's | been a while since I've needed a new kernel :) | Last I ran it (a couple of days ago) out of woody, it didn't ask about symlinks. It just does them as if the kernel you are installing is the new default kernel. I always have to go back and update my symlinks, but tehn again I typically have at least three different kernels ready to go at a given moment. HTH, Brooks
Re Root symlink to /boot/vmlinuz
On Mon, 03 Mar 2002 at 23:25:30, k l u r t wrote: On Fri, 2002-03-01 at 23:29, Craig Dickson wrote: Dumb question: why does Debian like to have a symlink, /vmlinuz, pointing to the kernel image in /boot? Does some program depend on being able to find the kernel at /vmlinuz? Would something break if I simply deleted this symlink? I ask because I install kernels by hand, and I use a naming scheme for my kernels that tells me what they are and when they were built, e.g. vmlinuz-2.4.18-ac2-020226 is a 26 Feb 2002 build of 2.4.18-ac2. This means I have to go change the /vmlinuz symlink every time I install a new kernel, and I'm wondering if I can safely just delete the link and never bother with it again. Thanks, Craig me thinks you would like make-kpkg (kernel-package) IIRC, kernel-package asks if you want the symlinks. I may be wrong, it's been a while since I've needed a new kernel :) -- Paul T Wright [EMAIL PROTECTED] And, strange to tell, among the Earthen Lot Some could articulate, while others not: And suddenly one more impatient cried -- Who is the Potter, pray, and who the Pot? -- The Rubaiyat of Omar Khayyam --
Re: Root symlink to /boot/vmlinuz
On Sat, Mar 02, 2002 at 09:50:02PM +0200, Shaul Karl wrote: Dumb question: why does Debian like to have a symlink, /vmlinuz, pointing to the kernel image in /boot? Does some program depend on being able to find the kernel at /vmlinuz? Would something break if I simply deleted this symlink? I believe one reason is because that is how the kernel-package uses to manage things. IIRC you can tell the kernel-package to behave differently. You might want to read the kernel-package documentation for more information about those links. Not sure but another reason might be to let people who need it have a small /boot partition. Ahh, but if you use grub, you need the same path to point to the same files from within the linux environment and when booting just loading /boot. (/vmlinuz is on / from linux, but grub reads /boot and finds no or even *old* vmlinuz (in /boot!) and fails or boots wrong kernel) As things are now, you have to change the kernel package to putting that symlink into /boot. This is one of the first things I have to do on each new system installation... :( Are there any valid requirements to put the /vmlinuz symlink in / instead of /boot?
Re: Root symlink to /boot/vmlinuz
Mike == Mike Fedyk [EMAIL PROTECTED] writes: Mike As things are now, you have to change the kernel package to Mike putting that symlink into /boot. This is one of the first Mike things I have to do on each new system installation... :( Well, it is reasonably easy to do that, is it not? Mike Are there any valid requirements to put the /vmlinuz symlink in Mike / instead of /boot? historical reasons, mostly. (I still remember /vmunix from way back when). manoj KERNEL-IMG.CONF(5) Debian GNU/Linux manual KERNEL-IMG.CONF(5) image_in_boot Set to Yes if you want the kernel image vmlinuz in /boot rather than the default /. Defaults to No. -- Life may have no meaning, or, even worse, it may have a meaning of which you disapprove. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Root symlink to /boot/vmlinuz
On Fri, 2002-03-01 at 23:29, Craig Dickson wrote: Dumb question: why does Debian like to have a symlink, /vmlinuz, pointing to the kernel image in /boot? Does some program depend on being able to find the kernel at /vmlinuz? Would something break if I simply deleted this symlink? I ask because I install kernels by hand, and I use a naming scheme for my kernels that tells me what they are and when they were built, e.g. vmlinuz-2.4.18-ac2-020226 is a 26 Feb 2002 build of 2.4.18-ac2. This means I have to go change the /vmlinuz symlink every time I install a new kernel, and I'm wondering if I can safely just delete the link and never bother with it again. Thanks, Craig me thinks you would like make-kpkg (kernel-package)
Re: Root symlink to /boot/vmlinuz
Craig Dickson wrote (on 1 Mar 2002 at 20:29): of 2.4.18-ac2. This means I have to go change the /vmlinuz symlink every time I install a new kernel, and I'm wondering if I can safely just delete the link and never bother with it again. Yes, you can. Just make sure lilo.conf or whatever boot loader you're using can find the kernel without it. T. -- -- Tony Crawford -- [EMAIL PROTECTED] -- +49-3341-30 99 99 --
Re: Root symlink to /boot/vmlinuz
On Fri, Mar 01, 2002 at 08:29:47PM -0800, Craig Dickson wrote: | Dumb question: why does Debian like to have a symlink, /vmlinuz, | pointing to the kernel image in /boot? Does some program depend on being | able to find the kernel at /vmlinuz? Would something break if I simply | deleted this symlink? For people who aren't like you, that keeps it simple to tell them the name of the kernel. It also means the boot loader's config doesn't need to change when a new kernel is installed (assuming, of course, the new one works). | I ask because I install kernels by hand, and I use a naming scheme for | my kernels that tells me what they are and when they were built, e.g. | vmlinuz-2.4.18-ac2-020226 is a 26 Feb 2002 build of 2.4.18-ac2. This | means I have to go change the /vmlinuz symlink every time I install a | new kernel, and I'm wondering if I can safely just delete the link and | never bother with it again. Remove the existing symlink and create /etc/kernel-img.conf with the following contents : ~ # create symbolic links in / ? do_symlinks = No ~ to prevent kernel-image packages from (re)creating that symlink every time. -D -- One man gives freely, yet gains even more; another withholds unduly, but comes to poverty. Proverbs 11:24
Re: Root symlink to /boot/vmlinuz
On Sat, Mar 02, 2002 at 10:50:46AM +0100, Tony Crawford wrote: Craig Dickson wrote (on 1 Mar 2002 at 20:29): of 2.4.18-ac2. This means I have to go change the /vmlinuz symlink every time I install a new kernel, and I'm wondering if I can safely just delete the link and never bother with it again. Yes, you can. Just make sure lilo.conf or whatever boot loader you're using can find the kernel without it. I leave the symlink there, but change it to point to my default kernel, that way the 'default' section of my lilo.conf is always the same ... only what it points to gets replaced by updating the sysmlink. aloha, dave pgpgLx9ZmOOc0.pgp Description: PGP signature
Re: Root symlink to /boot/vmlinuz
Dumb question: why does Debian like to have a symlink, /vmlinuz, pointing to the kernel image in /boot? Does some program depend on being able to find the kernel at /vmlinuz? Would something break if I simply deleted this symlink? I believe one reason is because that is how the kernel-package uses to manage things. IIRC you can tell the kernel-package to behave differently. You might want to read the kernel-package documentation for more information about those links. Not sure but another reason might be to let people who need it have a small /boot partition. I ask because I install kernels by hand, and I use a naming scheme for my kernels that tells me what they are and when they were built, e.g. vmlinuz-2.4.18-ac2-020226 is a 26 Feb 2002 build of 2.4.18-ac2. This means I have to go change the /vmlinuz symlink every time I install a new kernel, and I'm wondering if I can safely just delete the link and never bother with it again. Thanks, Craig -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please substitute (at-no-spam) with an at - @ - character. (at-no-spam) is meant for unsolicitate mail senders only.
Re: Root symlink to /boot/vmlinuz
Craig == Craig Dickson [EMAIL PROTECTED] writes: Craig Dumb question: why does Debian like to have a symlink, Craig /vmlinuz, pointing to the kernel image in /boot? Does some Craig program depend on being able to find the kernel at /vmlinuz? One may set up a boot loader (like lilo or grub) to have a latest kernel and previous kernel selections, and point them to the symlinks. Craig Would something break if I simply deleted this symlink? Not unless you have set up lilo/grub to look at those links. Craig I ask because I install kernels by hand, and I use a naming Craig scheme for my kernels that tells me what they are and when Craig they were built, e.g. vmlinuz-2.4.18-ac2-020226 is a 26 Feb Craig 2002 build of 2.4.18-ac2. This means I have to go change the Craig /vmlinuz symlink every time I install a new kernel, and I'm Craig wondering if I can safely just delete the link and never Craig bother with it again. Look into your boot loader config. If it does not look at /vmlinuz, you can delete it. Or else you need to fix your boot loader config. No other progrtam should look at this link. manoj -- In the war of wits, he's unarmed. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
