Happy spring, all! I've celebrated by doing my first kernel upgrade. Now, I have gone through all the make stuff, and ended up at make bzimage, with the intention of sticking the image on a floppy for testing. However I've come up with the message "warning: kernel is too large for standalone boot from floppy".
How advisable is it to just go ahead and "make install" at this stage? I have copied vmlinz-2.2.18 and config-2.2.18 to vmlinuxOLD and configOLD.
Also, is "make bzlilo" like "make install" but also tells lilo about the new kernel image?
Thanks! Jen.
Hi Jenny
The bzlilo places vmlinuz an System.map in root unless you go into the makefile and change the default. One thing I haven't tried is appending INSTALL_PATH=/boot to the make bzlilo stage - It might work.....
And yes, lilo is run after the vmlinuz is written - So make sure you have added your new kernel to lilo.conf first.
Do you want to try compiling a 2.4.18 kernel ???
Regards, Paul.
P.S. Can I pick your brains on Samba sometime ?
On Thursday 28 March 2002 12:12, Jenny_Hopkins@toby-churchill.com wrote:
Happy spring, all! I've celebrated by doing my first kernel upgrade. Now, I have gone through all the make stuff, and ended up at make bzimage, with the intention of sticking the image on a floppy for testing. However I've come up with the message "warning: kernel is too large for standalone boot from floppy".
How advisable is it to just go ahead and "make install" at this stage? I have copied vmlinz-2.2.18 and config-2.2.18 to vmlinuxOLD and configOLD.
Also, is "make bzlilo" like "make install" but also tells lilo about the new kernel image?
Thanks! Jen.
Jenny wrote:
Happy spring, all! I've celebrated by doing my first kernel upgrade. Now, I have gone
through
all the make stuff, and ended up at make bzimage, with the intention
of
sticking the image on a floppy for testing. However I've come up
with the
message "warning: kernel is too large for standalone boot from
floppy".
How advisable is it to just go ahead and "make install" at this
stage?
I have copied vmlinz-2.2.18 and config-2.2.18 to vmlinuxOLD and
configOLD.
Also, is "make bzlilo" like "make install" but also tells lilo about
the
new kernel image?
Hi Jenny,
Dunno if you want to know this now, but if you install the "kernel-package" you only have to run
cd /usr/src/linux make menuconfig make-kpkg --revision mine.1 kernel_image"
then install the created deb in /usr/src. This is the Debian way of doing it, but at least when you do it manually you know get to know what it's doing.
Paul wrote:
Do you want to try compiling a 2.4.18 kernel ???
I wouldn't install 2.4.18 on Debian stable (sid) tho - requires a lot of package updates! Upgrade to Unstable been running on mine for weeks with NO problems! :-)))
Cheers
David.
On Thu, 28 Mar 2002 21:04:15 David Fairey wrote:
I wouldn't install 2.4.18 on Debian stable (sid) tho - requires a lot of package updates! Upgrade to Unstable been running on mine for weeks with NO problems! :-)))
I thought stable was called potato and that sid was the codename for unstable. 2.4.18 seems to work OK on testing too (aka. woody).
Steve.
Hi David
I need to set up samba to allow sharing of two directories - One with admin privileges, the other for read/write by anyone. Both these directories need to be available from boot time, so presumably, a couple of samba commands need to to added to one of the startup scripts. Just to add to the fun - I also need to burn a CD tnat sets this all up automatically on some, as yet unspecified, hardware.
I need to read the Samba HOWTO, plus any other docs I can find before asking the dummies questions.
Regards, Paul.
On Thursday 28 March 2002 21:03, David Fairey wrote:
Hi Paul,
What's your problem with Samba? Sure one or two of us can help.
David.
Hi Jen
Just for the fun of it, I tried - make bzlilo INSTALL_PATH=/tmp
And when it finished, a new vmlinuz was found in /tmp - So it does work <g>
Regards, Paul.
-
David Fairey -
Jenny_Hopkins＠toby-churchill.com -
Paul -
Steve Fosdick