2006/11/14, Hisham Muhammad <[EMAIL PROTECTED]>: > On 11/14/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > On 11/14/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > > > There should be an easy way to make apps enable tasks at bootup by > > > default. I'm starting to think that rc.d directory isn't that bad after > > > all. :) > > > > Maybe only issue a message to the user if a task if found after a > > given package/recipe is installed? I think it's better than allowing > > automagical inclusion of tasks in BootUp, as sometimes one might want > > to put it in a special order based on what already exists. > > Agreed, I'm not keen on fiddling with the user's BootUp either. BootUp > should be simple enough so that the user can edit it. For tasks that > are not as simple as adding a line, then create a Task. > Do we only want to create tasks for "advanced" apps? I think it would be nicer to have tasks for everything that could be called at bootup, like the task Alsactl or SSHD. The action can be called with one line (alsactl restore (or restore) and /System/Links/Executables/sshd (or killall sshd)) but I think it's nicer to have Alsactl start/stop and SSHD start/stop.
-- /Jonas _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
