Manoj Srivastava <sriva...@debian.org> writes:
> On Fri, Oct 23 2009, Bernd Eckenfels wrote:
>
>> In article <87r5sudn0p.fsf...@anzu.internal.golden-gryphon.com> you wrote:
>>> [ "$(stat -c %d/%i /sbin/init)" = "$(stat -Lc %d/%i /proc/1/exe
>>> 2>/dev/null)" ] ; then
>>> # So, init exists, and there is a linuxy /proc, and the inode of
>>> # the executable of the process with uid 1 is the same as
>>> # /sbin/init (ok, no init=/bin/sh going on)
>>
>> Maybe another check besides inode idendity is better, otherwise it will not
>> be able to be used afer an upgrade (and before reboot), or?
>
> Not needed. If init has been just upgraded, it has been already
> told to init -u itself. So, what are the cases?
What about setups with unionfs? Inodes might change (which one might
call a bug of the respective unionfs implementation).
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
