[Lunar-bugs] [Lunar Linux 0000450]: udev has no functions.

Wed Mar 3 00:07:31 GMT 2004

A BUGNOTE has been added to this bug.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000450
=======================================================================
Reporter:                   dlveatch
Handler:                    nestu
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000450
Category:                   initscripts (boot system)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
=======================================================================
Date Submitted:             2004-03-02 04:29 GMT
Last Modified:              2004-03-03 00:07 GMT
=======================================================================
Summary:                    udev has no functions.
Description: 
On boot when udev tries to start it says;

/etc/init.d/udev: line 8: /etc/rc.d/init.d/functions: No such file or
directory.

Which it should because there is nothing there.
=======================================================================

-----------------------------------------------------------------------
 nestu - 2004-03-02 19:07 GMT 
-----------------------------------------------------------------------
dlveatch,
Can you please try the bzipped module?
TIA,
nestu

-----------------------------------------------------------------------
 nestu - 2004-03-02 19:11 GMT 
-----------------------------------------------------------------------
http://bugs.lunar-linux.org/file_download.php?f_id=0000040&f_type=bug
^^ Should be able to DL the module from here ;)
nestu.

-----------------------------------------------------------------------
 dlveatch - 2004-03-02 19:14 GMT 
-----------------------------------------------------------------------
Ok gave the new module a whirl and got further. i now see this when doing a
/etc/init.d/udev restart;

/etc/init.d/udev restart
/etc/init.d/udev: line 8: /etc/rc.d/init.d/functions: No such file or
directory
/etc/init.d/udev: line 8: /etc/rc.d/init.d/functions: No such file or
directory
Removing udev device nodes: rm: cannot remove `/udev/fd': No such file or
directory
rm: cannot remove `/udev/stdin': No such file or directory
rm: cannot remove `/udev/stdout': No such file or directory
rm: cannot remove `/udev/stderr': No such file or directory
rm: cannot remove `/udev/core': No such file or directory
/etc/init.d/udev: line 108: success: command not found

/etc/init.d/udev: line 8: /etc/rc.d/init.d/functions: No such file or
directory

-----------------------------------------------------------------------
 nestu - 2004-03-02 20:54 GMT 
-----------------------------------------------------------------------
Can you change POST_INSTALL to this, and retry, please?

if ! module_installed initscripts ; then
    cp -a ${SCRIPT_DIRECTORY}/functions /etc/init.d/
    sed -i 's:rc\.d/::g' /etc/init.d/udev
    sed -i 's:subsys/::g' /etc/init.d/udev
fi

-----------------------------------------------------------------------
 dlveatch - 2004-03-02 21:00 GMT 
-----------------------------------------------------------------------
That gives me;

reating /var/cache/lunar/udev-019-i686-pc-linux-gnu.tar.bz2
+ updating lunar state files after module installation
+ module size is 396KB
/sbin/lin: line 12:  : command not found
/sbin/lin: line 14:  : command not found
/sbin/lin: line 16:  : command not found
+ removing installwatch file
! Problem detected during POST_INSTALL

-----------------------------------------------------------------------
 nestu - 2004-03-02 22:01 GMT 
-----------------------------------------------------------------------
I have relined with -d flawlessly here (twice to make sure), so I cannot
confirm your problem. Can anybody else *w/o* initscripts installed confirm
this problem? Strange enough line 12,14 and 16 are comments... Please
check your install before any further bugreport, please, and after reach
back. 
Thanks,
nestu.

-----------------------------------------------------------------------
 dlveatch - 2004-03-03 00:07 GMT 
-----------------------------------------------------------------------
Think I found the issue. Running it again with -d, I saw just before the
!Problem part a line that said "+[sound] error", or something to that
effect. So relined the kernel and changed the top level of the sound
section from M to "*".

A relin of udev gives me this;

Creating /var/log/lunar/compile/udev-019.bz2
++ temp_destroy (/var/tmp/lunar.lin.30622.udev.compile-log.fOhiT30821)
++ temp_destroy (/var/tmp/lunar.lin.30622.udev.compile-fifo.ihUbR30829)
++ boost ()
++ create_install_log ()
++ temp_create (install-log)
Creating /var/log/lunar/install/udev-019
++ parse_iw ()
++ filter (/var/lib/lunar/excluded)
++ filter (/etc/lunar/local/excluded)
++ exists ()
++ syms_not_owned (/var/tmp/lunar.lin.30622.install-log.JdGux31546)
++ temp_destroy (/var/tmp/lunar.lin.30622.install-log.JdGux31546)
++ create_md5sum_log ()
Creating /var/log/lunar/md5sum/udev-019
++ files ()
++ create_install_cache()
Creating /var/cache/lunar/udev-019-i686-pc-linux-gnu.tar.bz2
++ add_module (udev installed 019 396KB)
+ updating lunar state files after module installation
++ lock_file (/var/state/lunar/packages)
++ lock_file (/var/state/lunar/packages.backup)
++ unlock_file (/var/state/lunar/packages.backup)
++ unlock_file (/var/state/lunar/packages)
+ module size is 396KB
++ run_post_install ()
+ removing installwatch file
++ temp_destroy (/var/tmp/lunar.lin.30622.udev.installwatch.shoqe30774)
++ rm_source_dir ()
+ destroying building dir "/usr/src/udev-019"
++ report (/var/log/lunar/install/udev-019 install log udev 019)
++ sound (SUCCESS)
++ activity_log (lin udev 019 success)
++ lock_file (/var/log/lunar/activity)
++ unlock_file (/var/log/lunar/activity)
++ temp_destroy (/var/tmp/lunar.lin.30622.prepared-depends.WKdOV30637)

See the line that says ++sound (SUCCESS)? That's where it was blowing up
when I had all the sound stuff in the kernel as a module (well by all , I
mean the stuff I want). 

Now heres the deal. What if I don't want sound because the box will be a
server?