1 |
local res="$(cat /proc/modules | egrep 'serial' | cut -f1 -d" ")" |
2 |
|
3 |
remaining="$(cat /proc/mounts | awk `( print $3 " " $2 )'| \ |
4 |
grep -E ^'code|nfs|ncpfs|smbfs' | awk '( print $2 | '| sort -r)" |
5 |
|
6 |
human readable, i see... hmmmm |
7 |
|
8 |
how can you test something like this ? it will break very easily. |
9 |
|
10 |
and writing a init script for a daemon is very simple with my system. Not |
11 |
all daemons have an ready to run gentoo init script you know. |
12 |
|
13 |
|
14 |
On 2 May 2003, Terje Kvernes wrote: |
15 |
|
16 |
> Wouter van Kleunen <kleunen@××××××××××.nl> writes: |
17 |
> |
18 |
> > I wrote a new init system that has numerous advantages over the old script |
19 |
> > based init system. Please have a look at: |
20 |
> > |
21 |
> > pinit.sf.net |
22 |
> > |
23 |
> > I am a gentoo user, and i converted my scripts -> services for my |
24 |
> > system. I would like to have feedback on this system. Please try it |
25 |
> > out on your system (safely from your home directory). |
26 |
> |
27 |
> converting init-scripts to XML is a scary process. init-scripts |
28 |
> should IMHO be human readable, as atomic as possible, and testable |
29 |
> without depending on much more than having a generic shell. in |
30 |
> addition to verboseness and lack of readability, XML makes it |
31 |
> "interesting" to integrate more complex scripts, like autofs. |
32 |
> |
33 |
> yes, XML is easier to generate for a machine, but you generally |
34 |
> don't generate init-scripts, if you do you probably build them from |
35 |
> templates, which aren't XML friendly either. |
36 |
> |
37 |
> -- |
38 |
> Terje |
39 |
> |
40 |
> -- |
41 |
> gentoo-dev@g.o mailing list |
42 |
> |
43 |
|
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |