Remove upstart

**pksings** · April 27th, 2010

How does one remove upstart and go back to sysV init?

Can it be done?

PK

**Skaperen** · April 27th, 2010

I feel your pain.

It can be done. But it is a pain all its own because an increasing number of things expect upstart. Such dependencies exist in the packages which want to put in an upstart style script.

**sisco311** · April 27th, 2010

May I ask you why?

Ubuntu uses Upstart since 6.10. Upstart is backwards compatible with sysvinit scripts.

While in theory is possible, there is no easy way... I don't see any benefits...

**pksings** · April 27th, 2010

Why?

Because I cannot find what to edit or change to make my machine boot all the way, stops when it cannot mount my SATA disks, which then required me to drop to the command prompt, type mount -a, then exit, and then it would finish booting. I no longer could reboot remotely if I updated it while not at home, which I have done during business trips. And it in fact made rebooting a pain. Not needed often,but painful when it was.

Just to close the thread, I decided to try 10.04, the new LTS release and upgraded yesterday, it's still Beta, but seems to solve this problem, boots just fine.

**keybuk** · April 28th, 2010

Originally Posted by pksings

Why?

Because I cannot find what to edit or change to make my machine boot all the way, stops when it cannot mount my SATA disks, which then required me to drop to the command prompt, type mount -a, then exit, and then it would finish booting. I no longer could reboot remotely if I updated it while not at home, which I have done during business trips. And it in fact made rebooting a pain. Not needed often,but painful when it was.

Just to close the thread, I decided to try 10.04, the new LTS release and upgraded yesterday, it's still Beta, but seems to solve this problem, boots just fine.

Did you file a bug? We could have probably solved it.

Though from the sounds of it, we fixed the problem you were having if it's all working in 10.04?

**3rdalbum** · April 28th, 2010

Originally Posted by pksings

Why?

Because I cannot find what to edit or change to make my machine boot all the way, stops when it cannot mount my SATA disks, which then required me to drop to the command prompt, type mount -a, then exit, and then it would finish booting. I no longer could reboot remotely if I updated it while not at home, which I have done during business trips. And it in fact made rebooting a pain. Not needed often,but painful when it was.

Just to close the thread, I decided to try 10.04, the new LTS release and upgraded yesterday, it's still Beta, but seems to solve this problem, boots just fine.

Yeah I was going to say that the "mountall" package in Ubuntu 10.04 has had many bugfixes, and that I remembered reading the changelogs for one version saying something about fixing this problem.

**Skaperen** · April 28th, 2010

Desktops environments tend to work on a more careful basis in terms of not messing things up when something unexpected happens. If a permanent drive cannot be mounted, that's unexpected. Dropping to a command prompt right then lets the user determine the issue and deal with it (despite often requiring guru level knowledge to do it). I'm not sure I'd want it to be any other way for a desktop.

For a server, that can be different. They can be remote. I want a server to make every effort to come up, no matter what. I have built a whole init system just for that purpose (it wasn't BSD style or SYSV style or UPSTART style ... it was a whole different scheme ... and it was built on top of Slackware). I now run some Ubuntu servers, and have a few times had a problem where they fail to come up and so I run into the computer room to see what's wrong (in many cases various bugs with other things, such as ifup/ifdown, and I deploy workarounds to deal with it). For distant remote servers, I would not run Ubuntu Server at all, unless someone would always be on site there to deal with it.