Re: systemd waisted 5 hours of my work time today
On Thu, 24 Jul 2014 15:00:05 +0200
Slavko <linux@slavino.sk> wrote:
> Ahoj,
>
> Dňa Thu, 24 Jul 2014 13:00:24 +0100 Tom Furie <tom@furie.org.uk>
> napísal:
>
> > On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:
> >
> > > I know systemd is not an option any more, but if this is the way
> > > it is going to waste my time, I will have to look at a
> > > reinstallation of my system and then use something that is less
> > > buggy than Debian Testing/Sid.
> >
> > You are, of course, aware that testing and unstable are test
> > platforms where breakage is to be expected? They shouldn't be used
> > for anything "mission critical", that's what stable is for.
>
> No, i will not comply with this.
>
> The testing must be in state, where it must to boot (except some boot
> options tweaks) by default. I think, that nobody here will complain if
> some of software/services on testing doesn't work, but computer must
> to boot!
>
> If it will not boot, then it is not appropriate to "mission critical"
> only, but then it is not appropriate to nothing. And because the NFS
> is installed by default, then it can be considered as "is used" by
> default too, then system doesn't boot for default and IMO this is a
> problem.
>
I don't think this is intentional. It's not the first non-booting issue
I've had with sid, and each time it seems that not many other people
have the problem.
I'm sure a lot of testing has been done, but unfortunately the switch
to systemd from a mature sysvinit installation ('drop-in replacement')
seems to be quite stressful, and a few systems have broken badly,
including one of mine. (I still have two unmigrated sids...)
A new systemd installation is likely to be much more stable, and while
my main workstation is mostly working, there are far too many error
messages for my liking, as well as crashes during most shutdowns. It
may be worth rebuilding to get a more reliable system, when I get the
time, as I have the feeling it will be a less frustrating experience
than trying to fix the existing system.
--
Joe
Reply to: