Linux From Scratch This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
08-19-2006, 06:15 PM
|
#1
|
Member
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507
Rep:
|
no loopback device
Hello,
I recently installed LFS 6.2 from a LiveCD onto a Sony Vaio VGN-B1XP.
All went well, I learned plenty, and was able to iron out a few wrinkles, but am stuck on one thing.
At the end of the boot process, when the services are starting up, I get the following error message:
Bringing up the loopback interface...
Cannot find device "lo"
SIOCGIFFLAGS: No such device [FAIL]
I tried modifying the instructions at section 7.13 and making an
/etc/sysconfig/network-device/ifconfig.lo/ipv4 file but that just changed the error message to "Interface lo doesn't exist"
Other, possibly pertinent, details: I have installed net-tools from BLFS, and have recompiled the kernel several times - but this is the only error message I see.
Can anyone tell me how to create the loopback interface?
Thanks,
John
Last edited by jkobrien; 08-19-2006 at 06:36 PM.
|
|
|
08-22-2006, 02:32 AM
|
#2
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,638
Rep: 
|
Seeing that no one answers here I'll share some thoughts, but please keep in mind that I am by no way any sort of expert here and in linux in general  .
The loopback is a special device in /dev/lo*, right? It can be created by "mknod" -- so why don't you write a script which creates a loopback as needed before the services are started and have that script called by e.g. "init"?
Anyway, good luck  .
|
|
|
08-30-2006, 01:14 PM
|
#3
|
Member
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507
Original Poster
Rep:
|
Thanks for your reply. Your caveats (1,444 posts though?) and my lack of experience with mknod made me hesitate to try your suggestion.
Anyway, I managed to fix it. My network rules file had an entry SYSFS(address) instead of SYSFS{address}.
The moral of the story? Sit real close to the screen  !
John
|
|
|
08-31-2006, 01:59 AM
|
#4
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,638
Rep: 
|
Quote:
Originally Posted by jkobrien
...1,444 posts though?...
|
Oh well, I'm mostly here to learn and I do that best by asking questions  .
Quote:
Originally Posted by jkobrien
...The moral of the story? Sit real close to the screen  !
|
Relax, I'm myopic, too  .
|
|
|
01-12-2009, 10:37 PM
|
#5
|
LQ Newbie
Registered: Jan 2009
Posts: 2
Rep:
|
Quote:
Originally Posted by jkobrien
Thanks for your reply. Your caveats (1,444 posts though?) and my lack of experience with mknod made me hesitate to try your suggestion.
Anyway, I managed to fix it. My network rules file had an entry SYSFS(address) instead of SYSFS{address}.
The moral of the story? Sit real close to the screen  !
John
|
I have the same problem. Would you provide the entire line of SYSFS{address} that you added in the ../rule.d/26-modprobe.rules for "lo" loopback device?
Thanks.
|
|
|
01-13-2009, 12:03 PM
|
#6
|
Member
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507
Original Poster
Rep:
|
Hi,
I'm sorry, that was two years and a couple of laptops ago! I don't have the file anymore. All I remember about it now is that I'd used () where I should have used {}.
John
|
|
|
All times are GMT -5. The time now is 08:37 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|