On Sun, 24 Aug 2003, Dirk Meyer wrote:

> Aubin Paul wrote:
> >
> > They're not chkconfig compliant, because they're distro-neutral, which
> > means they have to be lowest common denominator. When I added them, my
> > goal was to have people make them into distro-specific versions, and
> > it's happened in some cases.
> 

I see. Well, adding chkconfig support is easy, it's just a bunch of
commented lines at the top of the script file. 

>From the chkconfig man page:

RUNLEVEL FILES
       Each service which should be manageable by chkconfig needs
       two or more commented lines added to  its  init.d  script.
       The  first line tells chkconfig what runlevels the service
       should be started in by default, as well as the start  and
       stop  priority  levels.  If  the  service  should  not, by
       default, be started in any runlevels, a - should  be  used
       in  place of the runlevels list.  The second line contains
       a description for the service, and may be extended  across
       multiple lines with backslash continuation.

       For example, random.init has these three lines:
       # chkconfig: 2345 20 80
       # description: Saves and restores system entropy pool for \
       #              higher quality random number generation.
       This says that the random script should be started in lev-
       els 2, 3, 4, and 5, that its start priority should be  20,
       and  that  its  stop priority should be 80.  You should be
       able to figure out what the description says; the \ causes
       the line to be continued.  The extra space in front of the
       line is ignored.


> There are also gentoo specific boot scripts. If someone has redhat or
> suse specific ones, please send them to the list.

It's easy to add, but I haven't done so since I'm not currently using
them, and haven't tested them. My guess is to add the following:
(- means don't automatically invoke (need to specify via ntsysv, 99 means
last to startup, 00 means first to shutdown)

# chkconfig: - 99 00
# description: Freevo boot script .....

> 
> > The system-wide Python really should be used I think; Python 2.3 is
> > available for every distro from rpmfind, debian, gentoo, slack, etc.

I just checked RPMfind, so far only Mandrake has released 2.3 RPMs.
Usually Mandrake RPMs don't coexist well with RedHat ones due to different
dependcy naming and packaging, and especially since they named it 'python'
which will have to replace the RH supplied python 2.2. At this moment, my
suggestion is to use the runtime supplied version for freevo if needed.

> 
> Yes. It would be great if someone could provide us with a list where
> to download _all_ needed RPMs for the current version of all distros. 
> 

That'll be needed if we do the python module release approach.

Let's do this:
1. Dischi, can you come up with a list of module dependencies (*tar.gz)
   and especially for non-standard python modules
2. I'll try and see how they track with RedHat and post the findings.

T.C.
----
Wan Tat Chee (Lecturer)
School of Computer Science, Univ. of Science Malaysia,
11800 USM, Penang, Malaysia.      Rm.625 Ofc Ph: +604 653-3888 x 3617
NRG Lab Admin: +604 659-4757           Rm.601-E Ofc Ph: +604 653-4396
Internet: [EMAIL PROTECTED]            Web: http://nrg.cs.usm.my/~tcwan
GPG Key : http://nrg.cs.usm.my/~tcwan/tcw_gpg-20030322.asc
F'print : DCF2 B9B2 FA4D 1208 AD59  14CA 9A8F F54D B2C4 63C7



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to