You're right. On Feb 26, 2015 5:30 PM, "Jason Adams" <[email protected]> wrote:
> On 02/26/2015 01:19 PM, Ted Unangst wrote: > > Naim, Halim. wrote: > >> Alexander Hall <[email protected]> writes: > >> > >>> On February 26, 2015 7:36:08 PM CET, [email protected] wrote: > >>>> I was upgrading my system today to the most recent snapshot (from a > >>>> previous snapshot). The Upgrade process failed (After booting bsd.rd), > >>>> with error 'uid 0 on /: file system full' > >>>> I finally found out that the problem was that my /bsd was a symlink to > >>>> /bsd.sp (I had modified it to test if the ehci error was present with > >>>> the sp kernel). After deleting the symlink. and cp'ing /bsd.mp to > /bsd > >>>> everything worked as expected. I didn't find anyting in the archives > >>>> about this, so I thought I'd share the experience. > >>> Indeed. As you just found out, absolute symlinks can cause oddities > in the upgrade process. > >>> > >>> /Alexander > >> Is this documented anywhere? If not, should it? > > No. The number of ways you can break things is infinite. There's no way > we > > could make a list of them all. > > > > Funniest and most insightful thing I've seen all week. > > -- > Those who do not understand Unix are condemned to reinvent it, poorly.
