Mailinglist Archive: opensuse (2700 mails)

[Adrian <adrian@xxxxxxxxxxxxxxx>]

El vie, 22-07-2005 a las 11:15 +0200, Carlos E. R. escribió:

> All "X-UnitedLinux*" entries are vendor extensions and not guaranteed to 
> work in all SuSE systems. In fact, some of them are docuemented as 
> ignored.
> 
> Maybe "Required-Start: $all", as Anderson mentions, works, but I haven't 
> checked.
> 

The "$all" pseudo name seems to be an UnitedLinux extension too: ( from
http://www.chemie.uni-hamburg.de/tmc/stribeck/pv-wave/index_e.html )

------------------------------
 When specifying hard dependencies or ordering requirements, you can
   use names of services (contents of their Provides: section)
   or pseudo names starting with a $. The following ones are available
   according to LSB (1.1):
       $local_fs               all local file systems are mounted
                               (most services should need this!)
       $remote_fs              all remote file systems are mounted
                               (note that /usr may be remote, so
                                many services should Require this!)
       $syslog                 system logging facility up
       $network                low level networking (eth card, ...)
       $named                  hostname resolution available
       $netdaemons             all network daemons are running
  The $netdaemons pseudo service has been removed in LSB 1.2.
   For now, we still offer it for backward compatibility.
   These are new (LSB 1.2):
       $time                   the system time has been set correctly
       $portmap                SunRPC portmapping service available
   UnitedLinux extensions:
       $ALL                    indicates that a script should be inserted
                               at the end
------------------------------


It would be interesting to know when did suse start to accept the
Unitedlinux extensions, in particular the "$all" pseudo name.

I've done a quick search, and the Unitedlinux faq
( http://www.unitedlinux.com/en/info/faqs.html ) tell about a roadmap
for 2002. Maybe Suse started to support Unitedlinux extensions in 2002.
In this case, the script would work correctly in Suse versions later
than 2002.

For older versions, the script will be launched after basic services
($local_fs $remote_fs $network). Well, at least for versions that
support LSB 1.1 (any idea of which ones are they?).

I'm thinking that, to ensure even more, we could add all LSB 1.1 pseudo
names to the "Required-Start:" entry:

  $local_fs $remote_fs $syslog $network $named $netdaemons

Any more ideas?