Custom Query (4881 matches)
Results (235 - 237 of 4881)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #471 | invalid | modutils doesn't build kerneld by default | ||
| Description |
This isn't exactly a show stopper, but mosutils doesn't build/install kerneld by default, it must be enabled with ./configure --enable-kerneld Modutils has always behaved this way and its not "necessary" but kerneld is the daemon you want runnig if you want automatic module insertion and removal. I jsut started messing with modules (for a slower laptop) and I "discovered" this. kerneld isn't even mentioned in the book at all, and if its not something we want to use by default, we should at least mention it as an alternative ./configure option the same way we do for FHS compliance notes. If you want to automatically insert and remove modules when they are needed, you need to build modutils thusly: ./configure --enable-kerneld && make && make install And don't forget to make a startup script that loadproc /sbin/kerneld and ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rcsysinit/S05kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc0.d/K98kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc1.d/K98kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc6.d/K98kerneld I personally think it should be at least built in the default LFS modutils build, and if the user wants to enable it themselves, that's fine...I can't understand why you wouldn't want it started at boot time sometimes. But it should be built. |
|||
| #472 | duplicate | modutils doesn't build kerneld by default | ||
| Description |
This isn't exactly a show stopper, but mosutils doesn't build/install kerneld by default, it must be enabled with ./configure --enable-kerneld Modutils has always behaved this way and its not "necessary" but kerneld is the daemon you want runnig if you want automatic module insertion and removal. I jsut started messing with modules (for a slower laptop) and I "discovered" this. kerneld isn't even mentioned in the book at all, and if its not something we want to use by default, we should at least mention it as an alternative ./configure option the same way we do for FHS compliance notes. If you want to automatically insert and remove modules when they are needed, you need to build modutils thusly: ./configure --enable-kerneld && make && make install And don't forget to make a startup script that loadproc /sbin/kerneld and ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rcsysinit/S05kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc0.d/K98kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc1.d/K98kerneld && ln -s /etc/rc.d/init.d/kerneld /etc/rc.d/rc6.d/K98kerneld I personally think it should be at least built in the default LFS modutils build, and if the user wants to enable it themselves, that's fine...I can't understand why you wouldn't want it started at boot time sometimes. But it should be built. |
|||
| #473 | invalid | Chapter 5: Textutils, Findutils, Gawk, Patch, Sed, Textutils Configure Command | ||
| Description |
In chapter 5 Textutils, Findutils, Gawk, Patch, Textutils and Sed produce the error LDFLAGS="-static": Unknown Command, when using the configure command provided in the latest online cvs (www.linuxfromscratch.org/view/cvs) instead of using this method to get it to compile you have to include the LDFLAGS in the make command as in version 4 of the book or rewrite the configure command. Minor but would be annoying for a linux newbie who might not know how to fix it. |
|||
