2.4 kernel & lilo
tom at cashmans.screaming.net
Wed Nov 22 13:13:15 PST 2000
Yeah - that was it :]. I was thinking that I'd need to let programs get to
the old kernel include files, but I suppose I want them to look at the 2.4
header files now, anyway. So bad idea all round!
Now the kernel's working, I was thinking of getting some usable network
facility going for the 2-computer LAN I have at home. The other machine is
(apologies) Windows 95, and I wondered if anybody had any suggestions for
how to make the ethernet usable. I can ping the other machine from either,
but I can't figure out how to do much else. I suppose Linux won't ever show
in Windows' 'Network Neighbourhood', will it? Ideally, I'd want to share
files, the printer and the dial-up connection (when I *finally* get round to
sorting that out in LFS). I know I'll need a proxy server for the latter. Is
printing over an ethernet easy in linux? And is the best way to share files
to set up an FTP server on one of the machines, or is there a better way?
----- Original Message -----
From: "Sergey Ostrovsky" <sostrovsky at snip.net>
To: <lfs-apps at linuxfromscratch.org>
Sent: Wednesday, November 22, 2000 4:14 AM
Subject: Re: 2.4 kernel & lilo
> > uncompressed the 2.4 sources into a directory linux_2.4 and created a
> > symlink 'linux' to the old sources. Then I did everything the lfs book
> Everything above and below this snippet seems fine. I have such a
> on Linux partitions on 3 hard drives. And I just chose from LILO menu
> to load. And I assume you are friends with LILO. The only thing that looks
> is your symlink "linux" to old sources. You know, headers are included in
> sources by constructs like
> #include <linux/blah.h> or #<asm/blah/scsi/xyzzy.h>, etc.
> Angle braces <> mean that a relative path from include's default path
> Default paths are /usr/include, /usr/local/include, and couple not so
> That's why you earlier created "asm" and "linux" symlinks - in order to
> find headers of your kernel. I suspect you compiled your 2.4.0 with 2.2.x
> Try to change your "linux" link to the new kernel source tree and rebuild.
> Sergey Ostrovsky.
> Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
> and put unsubscribe in the subject header of the message
Unsubscribe: send email to lfs-apps-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
More information about the blfs-support