Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Everything is pretty much working fine, save some net problems:
On bootup, I get the following errors:
Bringing up the loopback interface...modprobe: modprobe: Can't locate module net-pf-4
modprobe: modprobe: Can't locate module net-pf-5
modprobe: modprobe: Can't locate module net-pf-9
..[a few lines late]..
Brining up the eth0 interface...SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device
ifconfig shows only the loopback
However, after logging in, if I 'insmod tulip' and then '/etc/init.d/ethnet restart', ifconfig loopback and eth0
First, what is up with the 'net-pf' modules and loopback?
Second, how can I get tulip to load properly?
And you could add the line insmod tulip to one of your bootscripts. Or you could add it to the ethnet script. When it brings the network interface up you could do a insmod and when it brings it down do a rmmod.
Originally posted by notsoevil The FAQ! Duh! Sorry.
I tried adding it to ethnet, I must have just done it a bit wrong -- hey, it was late in the night (actually, morning by then). I'll do it again.
If you want to use modules, you may want to check into the kernel auto module loading feature. Whenever you try to do something that requires a module loaded, the kernel will attempt to load the module(s) automatically. You can setup cron to periodically scan the loaded modules list and unload modules that haven't been used in a certain amount of time.
I thought I had set up the kernel for auto-loading modules. I'll look into it again tonight.
I am going to be setting up another LFS system today, for a work workstation. I was so impressed with performance last night mucking around that I am convinced of the benefits of LFS over distributions.
Tonight I am going to put X and blackbox on that machine, see how they run -- I am sure it will be slick.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.