Re: Summary: Using the LSB Bootscripts

Bryan Kadzban wrote: > DJ Lucas wrote: >> * the path for the setclock script in 55-lfs.rules needs to be >> changed > > So... yeah. > > Why was this whole tree moved in the LSB scripts, again? :-) > > I really really hate systems where I can't reasonably tab-complete > the bootscript filenames

Re: Summary: Using the LSB Bootscripts

On 5/15/11 3:25 AM, DJ Lucas wrote: > wanted anyway). Problem with dhclient is that the value of DHCP_STOP > will always be empty...all interfaces using dhclient will go. If you do > 'service network stop' then no big deal. OTOH, if you execute ifdown > ethn, and you have dhclient configured on mul

Re: Summary: Using the LSB Bootscripts

On 5/18/11 12:28 AM, Bryan Kadzban wrote: > Anybody know how other distros do it? I can't figure out what Debian's > ifdown binary is supposed to do (its source is *extremely* obfuscated, > being built from a texinfo file, and containing a file parser)... Fedora does a much more elaborate version

Re: Summary: Using the LSB Bootscripts

On 05/17/2011 11:34 PM, Bryan Kadzban wrote: > Few nits related to the shell. In the network script: > >> # Process individual configuration files >> for file in `ls "${dir}"`; do > Ew. :-) How about: > > for file in "${dir}"/* ; do > ONBOOT=`grep "ONBOOT" "${file}

Re: Summary: Using the LSB Bootscripts

Few nits related to the shell. In the network script: > # Process individual configuration files > for file in `ls "${dir}"`; do Ew. :-) How about: for file in "${dir}"/* ; do ONBOOT=`grep "ONBOOT" "${file}" | sed ... ... (since it always does a ${dir}/${file} as

Re: Summary: Using the LSB Bootscripts

Jeremy Huntwork wrote: > On 5/16/11 1:49 AM, Bryan Kadzban wrote: >> I'm not sure what the goal *should* be. :-) Does it make sense to >> try to clean up completely in this kind of setup? Maybe or maybe >> not. >> >> I do think it's least *surprising* to only undo the effects of the >> start sc

Re: Summary: Using the LSB Bootscripts

On 05/17/2011 08:54 AM, Jeremy Huntwork wrote: > > I do think we're getting a little overcomplicated here. Let's try to > simplify expectations. Here's what I expect (and I *think* this is > reasonable - you tell me :-) ) > > When I run the equivalent of /etc/init.d/network stop: > > All devices co

Re: Summary: Using the LSB Bootscripts

On 05/17/2011 08:54 AM, Jeremy Huntwork wrote: On 5/16/11 1:49 AM, Bryan Kadzban wrote: I'm not sure what the goal *should* be. :-) Does it make sense to try to clean up completely in this kind of setup? Maybe or maybe not. I do think it's least *surprising* to only undo the effects of the s

Re: Summary: Using the LSB Bootscripts

On 5/16/11 1:49 AM, Bryan Kadzban wrote: > I'm not sure what the goal *should* be. :-) Does it make sense to try > to clean up completely in this kind of setup? Maybe or maybe not. > > I do think it's least *surprising* to only undo the effects of the start > script, though. For whatever that's

Re: Summary: Using the LSB Bootscripts

Zachary Kotlarek wrote: > A compromise might be to provide an `ifreset` script, that does a > full ipflush, walks the services dir calling a `reset` target, etc., > but *not* integrate that script into ifdown. That seems like a pretty good idea. :-) signature.asc Description: OpenPGP digital s

Re: Summary: Using the LSB Bootscripts

Bruce Dubbs wrote: >Zachary Kotlarek wrote: >> On May 16, 2011, at 12:49 AM, Bryan Kadzban wrote: >> >>> I also *think* the only way the cached config might not match the >>> running config is if root mucked with the running config manually. >> >> >> Or when /run is not writable at the time th

Re: Summary: Using the LSB Bootscripts

Zachary Kotlarek wrote: > On May 16, 2011, at 12:49 AM, Bryan Kadzban wrote: > >> I also *think* the only way the cached config might not match the >> running config is if root mucked with the running config manually. > > > Or when /run is not writable at the time the network scripts execute. T

Re: Summary: Using the LSB Bootscripts

On May 16, 2011, at 12:49 AM, Bryan Kadzban wrote: > I also *think* the only way the cached config might not match the > running config is if root mucked with the running config manually. Or when /run is not writable at the time the network scripts execute. Or if the cached config were lost fo

Re: Summary: Using the LSB Bootscripts

On 05/16/2011 12:49 AM, Bryan Kadzban wrote: > Zachary Kotlarek wrote: >> On May 15, 2011, at 12:31 PM, Bryan Kadzban wrote: >> >>> I'm trying to figure out why it'd be necessary to do this. We >>> already have the previous configuration of every interface stuffed >>> away in /run, and we use that

Re: Summary: Using the LSB Bootscripts

Zachary Kotlarek wrote: > On May 15, 2011, at 12:31 PM, Bryan Kadzban wrote: > >> I'm trying to figure out why it'd be necessary to do this. We >> already have the previous configuration of every interface stuffed >> away in /run, and we use that when deciding which service scripts >> to call

Re: Summary: Using the LSB Bootscripts

On May 15, 2011, at 12:31 PM, Bryan Kadzban wrote: > I'm trying to figure out why it'd be necessary to do this. We already > have the previous configuration of every interface stuffed away in /run, > and we use that when deciding which service scripts to call when > bringing down networking. Do

Re: Summary: Using the LSB Bootscripts

Zachary Kotlarek wrote: > On May 15, 2011, at 2:25 AM, DJ Lucas wrote: >> might actually be easier to provide a default IFCONFIG values in >> each service script, and walk /lib/network-services. > > This make sense to me -- then it's easy to extend the same approach > for arbitrary service types

Re: Summary: Using the LSB Bootscripts

DJ Lucas wrote: > * the path for the setclock script in 55-lfs.rules needs to be > changed So... yeah. Why was this whole tree moved in the LSB scripts, again? :-) I really really hate systems where I can't reasonably tab-complete the bootscript filenames. And there's way too much junk in /etc

Re: Summary: Using the LSB Bootscripts

On May 15, 2011, at 2:25 AM, DJ Lucas wrote: > might actually be easier to provide a default IFCONFIG values > in each service script, and walk /lib/network-services. This make sense to me -- then it's easy to extend the same approach for arbitrary service types -- say pppoe -- which might wa

Re: Summary: Using the LSB Bootscripts

On 05/15/2011 01:39 AM, Nathan Coulson wrote: On Sat, May 14, 2011 at 9:36 PM, DJ Lucas > wrote: On 05/14/2011 04:37 PM, DJ Lucas wrote: > Everything is covered per this conversation in SVN with the exception of > accounting for missing /run i

Re: Summary: Using the LSB Bootscripts

On 05/15/2011 01:22 AM, DJ Lucas wrote: > On 05/15/2011 12:11 AM, Zachary Kotlarek wrote: >> Could we just do this in ifdown: >> >> if [ -x /lib/network-services/dhcp ]; then >> /lib/network-services/dhcp $interface down >> fi >> >> and assume that whatever DHCP client is ins

Re: Summary: Using the LSB Bootscripts

On Sat, May 14, 2011 at 9:36 PM, DJ Lucas wrote: > On 05/14/2011 04:37 PM, DJ Lucas wrote: > > Everything is covered per this conversation in SVN with the exception of > > accounting for missing /run in LightCube OS, but I think it was decided > > that it would be added. Also no ip flush (I forgo

Re: Summary: Using the LSB Bootscripts

On 05/15/2011 12:11 AM, Zachary Kotlarek wrote: > Could we just do this in ifdown: > > if [ -x /lib/network-services/dhcp ]; then > /lib/network-services/dhcp $interface down > fi > > and assume that whatever DHCP client is installed (if any) provides a script > appropria

Re: Summary: Using the LSB Bootscripts

On May 14, 2011, at 11:36 PM, DJ Lucas wrote: > I'll need to setup both DHCP clients to test functionality for this, > which is why I didn't just do it tonight. The problem I want to avoid is > if we do a flush, but the client daemon is still running, come > expiration, the client daemon might

Re: Summary: Using the LSB Bootscripts

On 05/14/2011 04:37 PM, DJ Lucas wrote: > Everything is covered per this conversation in SVN with the exception of > accounting for missing /run in LightCube OS, but I think it was decided > that it would be added. Also no ip flush (I forgot, but will get it in a > day or two) on down interface, an

Summary: Using the LSB Bootscripts

for the new file layout), diff -Naur lsb-bootscripts-20110514/etc/default/rc.site lsb-bootscripts-20110514-LCOS/etc/default/rc.site --- lsb-bootscripts-20110514/etc/default/rc.site2011-05-14 16:00:31.0 -0500 +++ lsb-bootscripts-20110514-LCOS/etc/default/rc.site2011-05-14 16:30

Re: Using the LSB Bootscripts

On Tue, May 10, 2011 at 6:39 AM, Jeremy Huntwork wrote: > On 5/10/11 8:25 AM, DJ Lucas wrote: >>       * Most important, pull as much as possible of the items below from >> LightCube OS's files to ease merging and keep the diffs to a minimum so >> that they are easily shared across distributions.

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > On 5/9/11 11:36 PM, Bryan Kadzban wrote: >> Right, but the former /etc/sysconfig/network* was also default >> configuration for how the bootscripts run. Well, the network script >> anyway. :-) > > Just ifup/ifdown (which are now in /sbin) and network-services/* which >

Re: Using the LSB Bootscripts

On 05/10/2011 08:11 PM, Bruce Dubbs wrote: > Archaic wrote: > >> Why MIT? These aren't book instructions. > They are published in the appendices. > > -- Bruce Yeah, but it is not in the tarball. The tarball can (and most likely will) be distributed outside of LFS. We are not discussing a chang

Re: Using the LSB Bootscripts

On 5/10/11 9:06 PM, Bruce Dubbs wrote: > A date gives the user additional information. How long since the last > change? Do I really need to update? Using mmdd gives a > monotonically increasing number and an idea of how long it has been > since changes were made. That is my preference. *s

Re: Using the LSB Bootscripts

On 5/10/11 9:11 PM, Bruce Dubbs wrote: > Unnecessary. The book copyright already covers it. Except, if I am understanding it correctly, if LightCube OS uses and distributes it, we are bound by that license to keep the it with the code and we have no other tie to the book. So putting the license

Re: Using the LSB Bootscripts

Archaic wrote: > On Tue, May 10, 2011 at 07:25:50AM -0500, DJ Lucas wrote: >> * ifup - copy configuration file from /etc/network/$int/$file to >> /run/network/$int/$file upon successful initialization of the interface. > > I believe /var/run is a more suitable place for this. > http://www.pa

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > On May 10, 2011, at 3:26 PM, Matthew Burgess > wrote: >> I don't mind changing the version numbering to whatever suits >> people best, but I'm just interested as to why this is an issue? >> If I had to pick any numbering scheme at all, I'd choose something >> simple like U

Re: Using the LSB Bootscripts

On Tue, May 10, 2011 at 1:09 PM, Archaic wrote: > On Tue, May 10, 2011 at 11:56:23AM -0400, Jeremy Huntwork wrote: > > > > http://www.linuxfromscratch.org/lfs/view/development/append > >> >> >> -- >> http://linuxfromscratch.

Re: Using the LSB Bootscripts

On May 10, 2011, at 3:26 PM, Matthew Burgess wrote: >>> >> > I don't mind changing the version numbering to whatever suits people best, > but I'm just interested as to why this is an issue? If I had to pick any > numbering scheme at all, I'd choose something simple like Udev's; I wouldn't say

Re: Using the LSB Bootscripts

On Tue, May 10, 2011 at 11:56:23AM -0400, Jeremy Huntwork wrote: > > http://www.linuxfromscratch.org/lfs/view/development/appendices/mit.html > > This license is fine with me. I have no objections, either. Just wondering why. -- Archaic -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev

Re: Using the LSB Bootscripts

On Tue, 10 May 2011 10:47:34 -0500, DJ Lucas wrote: > Jeremy Huntwork wrote: >> >>Can we do something more explicit about versioning? > > Need Bruce or Matt to chime in here, but I don't see that it's a big deal > to something about a more common versioning scheme. I don't mind changing the ver

Re: Using the LSB Bootscripts

On 5/10/11 11:13 AM, DJ Lucas wrote: >> Why MIT? These aren't book instructions. > > Hmm, to change licenses, or rather define one outside the scope of the book, > we'd need approval from all contributors. That is currently AFAIK Alexander, > Archaic, Bruce, Dan, Jeremy, Matt, Michael Tremmor (IP

Re: Using the LSB Bootscripts

On Tue, May 10, 2011 at 10:13:57AM -0500, DJ Lucas wrote: > > /var/run will be /run in FHS 3.0, LFS has already moved to the new > layout, but I'd imagine that the compatibility symlink will be > required for at least 3 years of not longer, so we could use /var/run > to be compatible for a while..

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: >On 5/10/11 8:25 AM, DJ Lucas wrote: >> * Most important, pull as much as possible of the items below >from >> LightCube OS's files to ease merging and keep the diffs to a minimum >so >> that they are easily shared across distributions. >> * Move ifup and ifdown

Re: Using the LSB Bootscripts

Archaic wrote: >On Tue, May 10, 2011 at 07:25:50AM -0500, DJ Lucas wrote: >> >> * ifup - copy configuration file from /etc/network/$int/$file to > >> /run/network/$int/$file upon successful initialization of the >interface. > >I believe /var/run is a more suitable place for this. >http://ww

Re: Using the LSB Bootscripts

On May 10, 2011, at 7:25 AM, DJ Lucas wrote: > * The three items above are the best I think we can do with it and > should cover > 99% of all cases, the known exceptions being starting the > dhcp client or ppp client manually, and possibly manual configuration of > wireless interfaces (I'v

Re: Using the LSB Bootscripts

On Tue, May 10, 2011 at 07:25:50AM -0500, DJ Lucas wrote: > > * ifup - copy configuration file from /etc/network/$int/$file to > /run/network/$int/$file upon successful initialization of the interface. I believe /var/run is a more suitable place for this. http://www.pathname.com/fhs/pub/fhs

Re: Using the LSB Bootscripts

On 5/9/11 11:36 PM, Bryan Kadzban wrote: > Right, but the former /etc/sysconfig/network* was also default > configuration for how the bootscripts run. Well, the network script > anyway. :-) Just ifup/ifdown (which are now in /sbin) and network-services/* which is now in /lib/{network-}services

Re: Using the LSB Bootscripts

On 5/10/11 8:25 AM, DJ Lucas wrote: > * Move network service scripts to /lib/services (there was one > minor objection here, should that be /lib/network-services or > /lib/network? I don't really have any preference here, /lib/services is > fine by me). Forgot to mention that I vote for /lib

Re: Using the LSB Bootscripts

On 5/10/11 8:25 AM, DJ Lucas wrote: > * Most important, pull as much as possible of the items below from > LightCube OS's files to ease merging and keep the diffs to a minimum so > that they are easily shared across distributions. > * Move ifup and ifdown scripts to /sbin. > * Mov

Re: Using the LSB Bootscripts

On 05/10/2011 07:25 AM, DJ Lucas wrote: > I'm just about done with the DESTDIR POC (still need to add instructions > to account for lib64 -> lib since I did this on multilib first) but that > can use some time to mature a bit anyway, so should have time on Wed if > one of y'all don't get there fir

Re: Using the LSB Bootscripts

nt manually, and possibly manual configuration of wireless interfaces (I've never configured wireless in LFS - also what about VPN tools started manually?). I believe Bryan is already on board with these changes, Bruce, Jeremy, Zach? * svn mv BOOK/bootscripts/contrib/lsb-v3 BOOK/LSB-Boots

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > On 5/9/11 1:57 AM, Bryan Kadzban wrote: >> Right, but you have no way to know (in the static config, or the >> DHCP config, for instance) whether a pppd was running and needs to >> be killed, or whether DNS needs to be unregistered (unlikely, but >> not impossible), or whet

Re: Using the LSB Bootscripts

DJ Lucas wrote: > Jeremy Huntwork wrote: >> On 5/9/11 2:53 AM, DJ Lucas wrote: >>> The simple solution is to stop networking before applying >>> changes. >> When >> >> Yes, I know. :) But in practice that becomes an annoyance. Admins >> used to working Fedora/Debian/Ubuntu or others assume that c

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: >On 5/9/11 2:53 AM, DJ Lucas wrote: >> The simple solution is to stop networking before applying changes. >When > >Yes, I know. :) But in practice that becomes an annoyance. Admins used >to working Fedora/Debian/Ubuntu or others assume that changing the >config and runnin

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > Just as an FYI, the plans for most of these changes come from myself and > Archaic who has been assisting with LightCube. The proposed > /etc/default/rc.local file was a last minute addition by myself, but > after this discussion, and some more with Archaic, I think per

Re: Using the LSB Bootscripts

On 5/9/11 2:53 AM, DJ Lucas wrote: > The simple solution is to stop networking before applying changes. When Yes, I know. :) But in practice that becomes an annoyance. Admins used to working Fedora/Debian/Ubuntu or others assume that changing the config and running 'service network restart' is s

Re: Using the LSB Bootscripts

On 5/9/11 1:57 AM, Bryan Kadzban wrote: > I believe the book has static IP addressing, and DHCP. There's also > both PPP (for both dial-up modems and cell-phone-network access) and > PPPoE, and I've added WoL to this system, as noted above. (Obviously > that only works for wired network cards tho

Re: Using the LSB Bootscripts

On 05/08/2011 06:25 PM, Jeremy Huntwork wrote: > Hello, > > So we've been using the LSB bootscripts for some time now on LightCube > OS, with very little modification (we added dhclient service and the > random bootscript to the default install), and it's behaved wonderful

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > On 5/8/11 8:46 PM, Bryan Kadzban wrote: >> I don't think there's any way to make all potential service scripts >> able to handle switching to and from all the other potential >> service scripts, just by starting them. I don't think that means >> it's not worth trying to do

Re: Using the LSB Bootscripts

unreleased as yet): http://dev.lightcube.us/sources/lsb-bootscripts/lsb-bootscripts-test.tar.bz2 And here's the sshd script, which is kept with the openssh sources: http://dev.lightcube.us/sources/openssh/sshd.init I forgot to mention that I removed DJ's interactive boot stuff, just to keep it simpler

Re: Using the LSB Bootscripts

On May 8, 2011, at 7:46 PM, Bryan Kadzban wrote: > I do think putting the service scripts under a subdirectory /lib is > good, but maybe /lib/network-services or something (to be more explicit) > would be better than plain "services". As long as the scripts are 100% parameterized so that any "no

Re: Using the LSB Bootscripts

On 5/8/11 8:46 PM, Bryan Kadzban wrote: > This seems like it might be starting to get complicated. The scripts > may set up more than just IP addresses. (I have one to set up WoL bits > via ethtool, for instance.) > > I don't think there's any way to make all potential service scripts able > to h

Re: Using the LSB Bootscripts

Bruce Dubbs wrote: > Jeremy Huntwork wrote: > >> * Add a param to release any dhclient addresses from a device if it is >> running in the ipv4-static service > > Wouldn't this be a BLFS issue? It's a good idea, but I don't use dhcp > myself. It makes it hard to ssh into the system. Unless yo

Re: Using the LSB Bootscripts

On 5/8/11 8:03 PM, Bruce Dubbs wrote: > Wouldn't this be a BLFS issue? It's a good idea, but I don't use dhcp > myself. It makes it hard to ssh into the system. :) yep, necessary for a packaged distro though. And invaluable for network booting. > I'm not sure about the name rc.local, but I lik

Re: Using the LSB Bootscripts

Jeremy Huntwork wrote: > * Add a param to release any dhclient addresses from a device if it is > running in the ipv4-static service Wouldn't this be a BLFS issue? It's a good idea, but I don't use dhcp myself. It makes it hard to ssh into the system. > * In the ipv4-static service, instead

Using the LSB Bootscripts

Hello, So we've been using the LSB bootscripts for some time now on LightCube OS, with very little modification (we added dhclient service and the random bootscript to the default install), and it's behaved wonderfully. There have been a few things that we noticed that we felt

Re: LSB Bootscripts are up to date

DJ Lucas wrote: > Got some free time tonight. If anyone in interested, the LSB style > bootscripts are up to date and working as expected. They require Dan > Nicholson's initd-tools-1.3 which gets us one step closer to LSB > compliance. Existing bootscripts will work, but all scripts (LFS and >

LSB Bootscripts are up to date

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Got some free time tonight. If anyone in interested, the LSB style bootscripts are up to date and working as expected. They require Dan Nicholson's initd-tools-1.3 which gets us one step closer to LSB compliance. Existing bootscripts will work, but

Re: lsb-bootscripts maintained?

On 03/10/2010 05:11 PM, Robert Xu wrote: > Hi all, > I've been wondering if the lfs LSB bootscripts are being maintained, > since I want to use them and integrate them with plymouth for a > bootsplash. (I have no idea how to do this, any tips would be great). > Are t

lsb-bootscripts maintained?

Hi all, I've been wondering if the lfs LSB bootscripts are being maintained, since I want to use them and integrate them with plymouth for a bootsplash. (I have no idea how to do this, any tips would be great). Are the bootscripts being maintained? -- Cya Later, Robert Xu Ever tried

Re: LSB bootscripts

Edwin van Vliet wrote: $ cat /etc/rc.d/rc.sysinit start mountkernfs start udev start swap start $local_fs ... $ cat /etc/rc.d/rc.1 stop$network ... $ This might be a nice solution, since it will be quite easy to add some lines in the right places once a script is installed, it is easy

Re: LSB bootscripts

On Fre, 2005-03-25 at 15:31 +0100, Edwin van Vliet wrote: > The directories with symbolic links look like a plan to me, but I have > also been thinking of a set of configuration files, e.g.: > > $ cat /etc/rc.d/rc.sysinit > start mountkernfs > start udev > start swap > start $local_fs > .

Re: LSB bootscripts

JÃrg Billeter wrote: I think it's great to get LSB compatible bootscripts into LFS. BTW: system init scripts don't need to follow LSB conventions, but I also like to be consistent throughout the whole system. That's right, so my goal would be to provide LSB compliant scripts for every *LFS package

Re: LSB bootscripts

On Don, 2005-03-24 at 16:44 -0700, Nathan Coulson wrote: > On Thu, 24 Mar 2005 19:53:02 +0100, Edwin van Vliet <[EMAIL PROTECTED]> wrote: > > More questions: the LSB specifications mention "facilities" like > > $local_fs and $network, but is not very clear on the implementation of > > it all. I hav

Re: LSB bootscripts

On Don, 2005-03-24 at 19:53 +0100, Edwin van Vliet wrote: > While installing LFS (development version) I have been reading the > mailing lists, and repeatedly bumped into remarks which imply that LFS > should be guided toward being an LSB compliant installation. > > Since I have recently install

Re: LSB bootscripts

Stef Bon wrote: And what's wrong with my quoting? There's rarely any reason to have to quote an entire email. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page

Re: LSB bootscripts

Matthew Burgess wrote: > Stef Bon wrote: > >> Just a question, what means LSB? > > Linux Standard Base (http://www.linuxbase.org/). Please be careful with > your quoting in the future! Oh, and google is typically much quicker > than a mailing list :) > > Regards, > > Matt. Thanks, I've al

Re: LSB bootscripts

Stef Bon wrote in <[EMAIL PROTECTED]> > > Just a question, what means LSB? http://www.linuxbase.org/ -- Regards Alex The email address above is a spamtrap. alex@ the same domain will reach me -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Uns

Re: LSB bootscripts

Stef Bon wrote: Just a question, what means LSB? Linux Standard Base (http://www.linuxbase.org/). Please be careful with your quoting in the future! Oh, and google is typically much quicker than a mailing list :) Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http:

Re: LSB bootscripts

Edwin van Vliet wrote: > While installing LFS (development version) I have been reading the > mailing lists, and repeatedly bumped into remarks which imply that LFS > should be guided toward being an LSB compliant installation. > > Since I have recently installed a second LFS server (for testing

Re: LSB bootscripts

Am Freitag, 25. März 2005 00:44 schrieb Nathan Coulson: > On Thu, 24 Mar 2005 19:53:02 +0100, Edwin van Vliet <[EMAIL PROTECTED]> wrote: > > While installing LFS (development version) I have been reading the > > mailing lists, and repeatedly bumped into remarks which imply that LFS > > should be g

Re: LSB bootscripts

On Thu, 24 Mar 2005 19:53:02 +0100, Edwin van Vliet <[EMAIL PROTECTED]> wrote: > While installing LFS (development version) I have been reading the > mailing lists, and repeatedly bumped into remarks which imply that LFS > should be guided toward being an LSB compliant installation. I have been su

Re: LSB bootscripts

Am Donnerstag, 24. März 2005 19:53 schrieb Edwin van Vliet: > More questions: the LSB specifications mention "facilities" like > $local_fs and $network, but is not very clear on the implementation of > it all. I have therefore just created /etc/init.d/local_fs and > /etc/init.d/network as I think t

LSB bootscripts

While installing LFS (development version) I have been reading the mailing lists, and repeatedly bumped into remarks which imply that LFS should be guided toward being an LSB compliant installation. Since I have recently installed a second LFS server (for testing and development), I just though