Am Freitag, 25. August 2006 21:58 schrieb Eric Spakman:
Hi Nathan,
Thank you very much!
Hi Eric,
I just posted the source and binary versions of webconf.lrp and
webconf.lwp. Your changes to lrcfg.back.cgi were heroic.
:)))
:
I decided to
shortcut the whole thing and make
Hi Kp,
Hi;
thx - I'm running latest from cvs and see:
grep: /etc/init.d/init.d: No such file or directory grep: /etc/init.d/init.d:
No such file or directory
At the end of various (each?) daemon description - e.g. dnsmasq.
I don't think this is intended.
Did you also used the latest
Hi Paul,
Hmmm, not sure. I find it a bit of a clutch. What happens if an user
edit the inittab for other changes like mgetty?
I prefer specific configdb/sylinux.cfg for different hardware where
also other changes can be done.
Eric
--Apple-Mail-3-25159442
Content-Type: multipart/mixed;
Hi Paul,
A real /etc/inittab is always present, it's part of the etc.lrp
package...
Eric
Look at the script. If a real /etc/inittab is present, it doesn't do
its magic.
It only does it if the proto is present and /etc/inittab is not.
This is one of the most annoying things for a new user
Hi Paul,
Not if it's not. You're the software developer, you make the
distribution etc.lrp. The whole point of this thing is to get people
running with a working console. Once they're on their feet, i.e. if
they edit the /etc/inittab or do a backup after the real inittab is
working,
Eric Spakman wrote:
Hi Paul,
Not if it's not. You're the software developer, you make the
distribution etc.lrp. The whole point of this thing is to get people
running with a working console. Once they're on their feet, i.e. if
they edit the /etc/inittab or do a backup after the
