Linux from Scratch support

[willimm]

Can you please support LFS in time for 0.7? (What I mean by that is that there needs to be LFS bootscripts packaged in Avahi. An example bootscript for sysklogd, attached here, will give you a base for making the bootscripts.)

I have made a ticket for including Avahi in BLFS. (#2606)

[willimm]

LFS's sysklogd bootscript. Will become the base for making the Avahi bootscripts.

[lennart]

Please provide a proper patch. We are happy to merge patches that add another type of init script to the Avahi tarball, but please don't expect us to write an init script for every niche distribution there might be.

Please reopen if you can provide a patch.

[willimm]

If I do this, I will have to bone up on shell scripting.

But I know of the LFS-bootscripts maintainer, he is called Nathan Coulson. His email address is nathan@…. Why don't you email him about an Avahi bootscript for BLFS?

[lennart]

Dude, that's not how Free Software works. I am not your distro monkey. Why don't *you* email him about an Avahi bootscript?

Sorry, mate, but my personal interest in LFS is minimal. I am happy to merge patches but I am not going sit down and prepare an init script for some niche distro just because some random guy asked for it. Sorry.

Feel free to reopen when you can provide a patch.

[willimm]

LFS IS NOT A NICHE DISTRO! You just angered people who wanted to build this package from scratch, by not making a bootscript for them!!!!!!!

[lennart]

This is not the place to discuss whether LFS is a niche distro. As mentioned Free Software doesn't work the way you apparently think it works. I am not a fairy that fullfils every wish you might have. I only work on stuff I myself or my employer are interested in and take patches for everything else.

So please, don't reopen this bug unless you can provide a sane patch.

Free Software is about contributing, not about demanding.

[willimm]

JUST ASK YOUR FREAKIN' INTSCRIPT MAKER TO MAKE A LFS BOOTSCRIPT FOR AVAHI!!!!!!!!!

[lathiat]

You are all caught up in being angry, or too forward.. and the 'niche' as an insult.

Whether it's niche or not is irrelevant, we don't make any init scripts for any distro, 'niche' or not.. basically unless it's in our interest because we use that distro or are employed by them, etc.

If someone wants to send a patch/init script for their distro, thats fine, we will merge it.

Whether it's niche or not is irrelevant. If your upstream creates an init script let us know and we will merge it.

Thanks for your time.

Best Regards, - Trent

[willimm]

Reopening this for 0.6.25. I have now got a intscript for avahi-daemon ready.

I think this intscript will work for you.

[willimm]

Avahi daemon bootscript for LFS.

[lennart]

Please make this a proper patch including configure checks to identify this distro.

[willimm]

Avahi patch for adding LFS bootscript.

[willimm]

Got patch, now will you put this into 0.6.25?

[lennart]

Thanks for your patch.

 http://git.0pointer.de/?p=avahi.git;a=commit;h=c19ece348e308b47bd99aad2f4e98c691e78d15d

[willimm]

Whoops, forgot to mention something. In LFS, the init scripts are installed in /etc/rc.d/init.d, and symbolic links are created to the init scripts in the rc{0,1,2,3,4,5,6,sysinit}.d directories. a

They basicaly look like this:

{S or K}{a two digit number that is for when the script will excuite in the boot up, eg: 20.}{init script name}

As a example of what one looks like, I'll show you:

S20dbus

The number matters, it is for the order of when the script will start up.

As for the Avahi bootscript, these are the symlinks to the Avahi bootscript I used:

For rc0.d, rc1.d, and rc6.d: K28avahi

For rc2.d: K49avahi (because Avahi is dependent on networking [and it is stoped in this runlevel], even through dbus is started in this runlevel.)

For rc3.d, rc4.d, and rc5.d: S21avahi.

I did not put this script in the rcsysinit.d dir, because it is for before-runlevel stuff.

And also, if you forgot, all of these links were linked to the avahi bootscript in /etc/rc.d/init.d.

I mentoned this because it would be a hassle trying to make those symlinks by yourself, and that Avahi should do it when installing the package.

And also, this is one step closer to Avahi in LFS.