Linked by Thom Holwerda on Mon 18th Aug 2008 23:33 UTC, submitted by Charles Wilson
Thread beginning with comment 327301
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-07-06
yep, i still love the dos day when every app or driver was contained in its own dir that one could move virtually anywhere as long as one entered the right path into either config.sys or autoexec.bat.
say what you will about its userfriendlyness but it was simple. and the same level of simple is what gobolinux is aiming for imo. that it appears to be user friendly is just a side effect.
note for instance that rather then having init.d and friends in etc (or /System/Settings in gobolinux) there is a BootOptions file (setting stuff like how the ascii-art for the boot process should look like) and a BootScripts dir.
in that dir one find:
BootUp: a list of things to start on all boots.
Console: what to start if the machine is to boot into a command line login.
Graphic: what to start if its a X based login.
Shutdown: generic tasks for dealing with all kinds of correct shutdowns.
Halt: what to do when shutting down.
Reboot: what to do on a reboot.
some daemons are packaged with Task scripts that minic init.d ones, so that they can be started and stopped with StartTask and StopTask. both of those can be used in bootup and shutdown.