To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-08-18
"Sorry, but i see that you have no idea what linux is. "
Yes, I really have no idea. At all. I've only used it since 1996 (RH 4.0 Colgate).
"First, "* Goal description via dependencies" means that you set a goal, like "i want to use kde". then upstart looks what applications are needed for this, and then starts them in the best and fastest order."
Ok, now I get what you mean.
"You realy missed the point of multithread."
Not at all but multithreading isn't the only solution to your problem. Applications can be started simultaneously without the launching process being multithreaded. Using multithreading is in itself not a goal and it's not necessarily the best solution to the problem.
"Again, your perhaps a linux desktop user (well, i doupt that you use linux anyway), so you migth not know."
I do know and I do use Linux, both on servers and workstations (along with a much larger number of OpenBSD boxes).
"You can have a linux box, and want it to do different things, like server, and desktop (perhaps desktop when you want to condfigure it)."
Sorry, I don't see the point in using different runlevels for this. It's a marginal use-case, imo.
"Or you have a runlevel for different server types. there are so many possibilities, sure, there is no use for a desktop machine, but for servers it can be very usefull."
Do you boot into different server types a lot? I really don't see the point of this. It's a marginal use-case, imo.
"there is no use for a desktop machine, but for servers it can be very usefull."
Either a server mostly works and you just want it to run or there's a serious problem and you need single-user. I've never seen the point in any other "runlevels".
Edited 2006-08-28 11:16
Member since:2005-07-11
then, "I completely fail to see the point of runlevels other than normal and single-user/"safe-mode". "
Again, your perhaps a linux desktop user (well, i doupt that you use linux anyway), so you migth not know. You can have a linux box, and want it to do different things, like server, and desktop (perhaps desktop when you want to condfigure it). Or you have a runlevel for different server types. there are so many possibilities, sure, there is no use for a desktop machine, but for servers it can be very usefull.
Not counting single-user mode, name a situation where you have ever used more than 1 runlevel. Name a situation where you know someone who has used more than 1 runlevel.
Why do I need two separate runlevels to decide if I want to run a GUI or not? Why not just have a simple config file that has, oh I don't know, xdm_enable="{YES|NO}" in it.
I've never understood the whole SysV init process with 15 runlevels (Linux only uses the first 9, although nobody knows about the ones above 6). How often do you reboot your servers? How often do you reconfigure your servers?
There's really only two modes that a system can run in: single-user mode for doing repairs, installs, configs, etc, and multi-user mode for everything else. What more do you need?
The BSD world got it right. A single, simple config file with *_enable lines, a single directory with RC scripts, and a tool parses the scripts to generate a dependency tree. The only thing missing is a method to do parallel tasks at boot/shutdown.
Member since:2005-08-18
"The only thing missing is a method to do parallel tasks at boot/shutdown."
It's possible to replace the BSD (OpenBSD at least) init process with runit. I did that once just to try it and it worked fine. It's also a great way to end up with a total frankensystem that's a nightmare to keep up to date and support. ;P
Edited 2006-08-29 09:49
Member since:
2006-04-04
Sorry, but i see that you have no idea what linux is.
First, "* Goal description via dependencies" means that you set a goal, like "i want to use kde". then upstart looks what applications are needed for this, and then starts them in the best and fastest order.
then, * Multithreaded launch whenever deps allow it, to speed up boot-up and shutdown"
This is very usefull. When you wake up your lan connection, most of the time a dhcp request is sent out. during the waiting, nothing else happens. Anyway, a big part of the booting process is spent with waiting (dhcp answer, dns answer, reading config files), during this time other applications can start. You realy missed the point of multithread.
then, "I completely fail to see the point of runlevels other than normal and single-user/"safe-mode". "
Again, your perhaps a linux desktop user (well, i doupt that you use linux anyway), so you migth not know. You can have a linux box, and want it to do different things, like server, and desktop (perhaps desktop when you want to condfigure it). Or you have a runlevel for different server types. there are so many possibilities, sure, there is no use for a desktop machine, but for servers it can be very usefull.