Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!news2.arglkargh.de!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Tim Watts Newsgroups: comp.os.linux.misc Subject: Re: How do home users of linux protect themselves against ill-advised changes? Date: Sun, 04 Jan 2015 18:25:15 +0000 Lines: 26 Message-ID: References: <4h1onb-kih.ln1@squidward.dionic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Lwnwdd9fna+GPtbPIAsGKgzP6WAwWmgUv8wBgmAoGEfiGd7G/5 X-Orig-Path: squidward.dionic.net!not-for-mail Cancel-Lock: sha1:iAO48wSJbvwrhyzMFaYN6qfuLn0= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 In-Reply-To: Xref: csiph.com comp.os.linux.misc:13223 On 04/01/15 15:31, Robert Heller wrote: >> True about ZFS - it is an option. > > And thus something for expert use. > I will take the honourable gentleman back in time to around 2002 ish - when SuSe 7.2 had ReiserFS as an option for / And one of my colleagues thought it was a Good Idea (TM) to enable it. A few months later there was some considerable swearing from me as a moderate and increasing number of lab PCs failed to boot as /sbin/init was fucked - containing fragments of /etc/passwd and other occasionally recognisable files. So another case where boot failure was possible without the kernel failing. We are not arguing probabilities - I am merely providing a number of singular examples to disprove the statement that "only kernel failure will break the boot sequence". I've seen as many userland failures break booting as I have kernel failures.