Re: implicit linkage (was: Re: Effectively criticizing decisions you disagree with in Debian)
On Sun, Oct 12, 2014 at 03:30:49PM +0300, Andrei POPESCU wrote:
> > > > > This is the same reason we are using shared libraries and the Debian
> > > > > Security Team is doing it's best to track code copies.
> > > >
> > > > Consider /etc/init.d/skeleton a library then. It's sources to
> > > > any /etc/init.d script anyway.
> > >
> > > No, it doesn't.
> >
> > Again, simple 'no' is beautiful, but hardly contributes to the
> > discussion.
>
> $ grep skeleton /etc/init.d/*
> /etc/init.d/dictd:# based on /etc/init.d/skeleton v1.7 05-May-1997 by miquels@cistron.nl
> /etc/init.d/README:# Provides: skeleton
> /etc/init.d/skeleton:# Provides: skeleton
>
> It seems like you misunderstood the purpose of /etc/init.d/skeleton.
> It's not a library, but something to use as a base to write your own
> script.
>
> As of Jessie most of 'skeleton' has been turned into 'init-d-script'
> though.
It was my mistake indeed. Thanks for the correction.
Somehow I mistook /lib/lsb/init-functions for /etc/init.d/skeleton.
> > > > > True, but sysv-rc still can't deal with them correctly.
> > > >
> > > > It does not have to deal with the hardware, as it not its' job.
> > >
> > > It has to mount filesystems.
> >
> > No, it does not have to. In Debian, there's /etc/init.d/mountall.sh to
> > do this job, in case initrd didn't care for it already. init(8) does
> > not mount anything.
>
> $ dpkg -S /etc/init.d/mountall.sh
> initscripts: /etc/init.d/mountall.sh
>
> I never said init(8) would mount anything, but sysv-rc. By sysv-rc I
> mean /etc/init.d/rc and all other scripts required to boot your system.
> Apparently most of these are split out in the initscripts package.
Ok, correction taken.
> > And, to spice things up, [1]. Beautiful link telling everyone that it's
> > not the init job to mount /usr as there's initrd for that.
>
> But sysv-rc still has to take care your / and /usr is remounted
> according to your fstab and also for mounting everything else defined in
> /etc/fstab and how this interacts with the rest of the boot / daemons.
No objections here.
> > Please enlighten me what exactly is systemd-specific here. Basically
> > they tell "yadda-yadda-yadda, fix your applications, and if you don't -
> > we have this 90-second hack for you".
>
> Systemd makes it possible for me to adjust mpd's .service file to
> *require* a specific mount. This is not possible with sysv-rc's own
> mechanisms, I'd have to script it myself.
But that's filesystem dependency, not a network one.
Reco
Reply to: