Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 07 Aug 2009 16:18:31 -0700
From:      Drew Tomlinson <drew@mykitchentable.net>
To:        Ed Schouten <ed@80386.nl>
Cc:        Chris Ruiz <yr.retarded@gmail.com>, freebsd-current@freebsd.org
Subject:   Re: [Fwd: How To Recover From Missing /lib/libc.so.7?]
Message-ID:  <4A7CB647.80201@mykitchentable.net>
In-Reply-To: <20090807191454.GP1292@hoeg.nl>
References:  <4A7C7220.2090309@mykitchentable.net>	<4A7C72E0.8080303@acm.poly.edu>	<4A7C77B6.8000209@mykitchentable.net>	<58c737d70908071156l2f5f2deds526a996ef9f386b@mail.gmail.com>	<20090807190350.GO1292@hoeg.nl> <20090807191454.GP1292@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Ed Schouten wrote:
> * Ed Schouten <ed@80386.nl> wrote:
>   
>> * Chris Ruiz <yr.retarded@gmail.com> wrote:
>>     
>>> You must specify NO_FSCHG= when you installworld on an unupgraded ZFS
>>> filesystem, otherwise you will lose libc.so.7!  I'll spare you the
>>> details on why this happens.
>>>       
>> Which is because our install(1) is stupid enough to delete the resulting
>> binary if it can't add the schg flag. We should really change this
>> behaviour.
>>     
>
> It looks like there are actually two bugs:
>
> - install(1) does check for EOPNOTSUPP, while ZFS seems to return
>   EINVAL. This is probably a ZFS bug.
> - Inside jails, (un)setting schg is not permitted and returns EPERM. We
>   should change the VFS to return EOPNOTSUPP or install(1) to allow
>   EPERM as well.
>
> It's a bit late, but I think it would be nice to have this fixed before
> 8.0.
>   

I guess this answers my previous question regarding if the NO_FSCHG= is
documented...

Thanks,

Drew

-- 
Be a Great Magician!
Visit The Alchemist's Warehouse

http://www.alchemistswarehouse.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A7CB647.80201>