[Lunar-bugs] [Lunar Linux 0000293]: /etc/init.d/mount from lunar-init does not check filesystems with fsck at boot

[Lunar bug reports list]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.lunar-linux.org/view.php?id=293 
====================================================================== 
Reported By:                gb
Assigned To:                
====================================================================== 
Project:                    Lunar Linux
Issue ID:                   293
Category:                   module
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Moonbase Version:           20070929.17 
Core Tools:                 Lunar 
Core Tools Version:         20070623 
====================================================================== 
Date Submitted:             09-30-2007 15:41 CEST
Last Modified:              11-09-2007 01:58 CET
====================================================================== 
Summary:                    /etc/init.d/mount from lunar-init does not check
filesystems with fsck at boot
Description: 
(arch: x86_64)

lunar-init: 20070926

At boot, I get this error from /etc/init.d/mount:

/etc/rcS.d/S10mount: line221: uniq: command not found

Attached please find my "mount" script.
Is it corrupt or an outdated version? I relined lunar-init many times,
but I always get the same files.

I also opened a topic on the Forum here:
http://forums.lunar-linux.org/viewtopic.php?t=496

BTW, running line 221 from the CLI after boot produces the right results.

Some time ago, I remember that a manual procedure for updating the init.d
files
was posted on the Lunar Linux Site homepage ("requires manual
intervention").
At the time I followed those instructions and everything seemed to work
fine.
I wonder if that could be the cause of my current problem.

====================================================================== 

---------------------------------------------------------------------- 
 adriandelatabla - 09-30-07 17:18  
---------------------------------------------------------------------- 
I had the same problem. This is because the uniq command is located in
/usr/bin, so if you have /usr in another partition than / the mount script
can't find it.
A simply workaround is to replace line 221 with this

FSCKLEVELS=$(sed 's/#.*$//g' /etc/fstab | awk '($6>0){print$6}' | sort
-nu) 

but this is not optimal because you will have to be careful everytime you
update lunar-init module. 

---------------------------------------------------------------------- 
 engelsman - 09-30-07 18:14  
---------------------------------------------------------------------- 
http://wiki.lunar-linux.org/index.php/Lunar_Linux:Installation says:

"It is important to note that you can not mount the directories /etc,
/bin, /sbin, /dev, /lib and /proc on separate partitions. These
directories need to be contained within the root ("/") directory. The
installation program should block you from doing this, but it's best not
to try."

Doesn't say anything about /usr though.

 

---------------------------------------------------------------------- 
 gb - 09-30-07 20:57  
---------------------------------------------------------------------- 
adriandelatabla - Thank you for your suggestion. It's a nice work-around.

engelsman - You pinpointed the issue.
But, possibly the problem is that the coreutils module installs "uniq" in
/usr/bin by default,
instead of placing it in /bin (which is actually on my "root" / partition,
and even includes "sort").
Maybe the coreutils module could be updated/tweaked. That would fix this
issue for the time being. :)

Thanks for your help.
Please let me know if you want me to open a new bug report for the
coreutils module. 

---------------------------------------------------------------------- 
 dveatch - 11-09-07 01:58  
---------------------------------------------------------------------- 
AFAIK based on the File Hierarchy Standard 2.3, "uniq" does not belong in
/bin. That's not to say we follow FHS to the letter, just letting you
know. The real question that needs answering is; is how much of FHS do we
want to follow and given that, is "uniq"  essential enough to place in
/bin. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-30-07 15:41  gb             New Issue                                    
09-30-07 15:41  gb             File Added: mount                            
09-30-07 15:41  gb             Moonbase Version          => 20070929.17     
09-30-07 15:41  gb             Core Tools                => Lunar           
09-30-07 15:41  gb             Core Tools Version        => 20070623        
09-30-07 15:42  gb             Issue Monitored: gb                          
09-30-07 17:18  adriandelatablaNote Added: 0000652                          
09-30-07 18:12  engelsman      Note Added: 0000653                          
09-30-07 18:14  engelsman      Note Edited: 0000653                         
09-30-07 20:57  gb             Note Added: 0000654                          
11-09-07 01:58  dveatch        Note Added: 0000692                          
======================================================================