Release Candidates :: DSL v4.4RC1

Quote (roberts @ May 24 2008,09:06)

Quote (curaga @ May 24 2008,15:11)

As alih posted in here, his second point is something that ought to be already in DSL.
The use of exec startx instead of startx saves ram by chopping one bash process, and comes with no negative effects since when X dies bash is restarted by init.

Except instead of putting it into an alias I'd just change it in /etc/skel/.bash_profile to not have manually using startx crap someones work out unexpectedly.

Posting here in case Robert's busy and doesn't read all the threads.

You are right in that I am not able to read all threads. You may need to "ping me" to get my attention.

In regards to this suggestion...

While we gain memory from one less bash shell, we lose the option to "exit to prompt". This was something I had suggested when I first joined this project, however, I was told that "exit to prompt" was needed for properly setting up video (X) parameters and/or changing keyboard parameters. Maybe such is no longer the case? I am all for reducing memory demands.

This may have been the case when the boot options were either to level 2 (root user console) or X as user DSL. Now that there is an option to boot to level 3 (DSL user console) perhaps having the level 5 boot option go straight to X withe 'exec startx' is a viable option. For the first run, or the xsetup boot code obviously booting to console first would need to be retained to run xsetup prior to staring X.

X always tries to start with the default runlevel 5.
Using boot option xsetup or any vga= code other than 791 causes the Dialog Setup scripts to run prior to starting X. So no change needed.

We could require those who wish to have the capability to exit from X to get to a command line only use the currently supported boot code of 3. This means that for those using runlevel 3 they would have to also issue the startx command.

For the default, there would be little noticeable change except for the following:

1. If you need to boot with framebuffer or other non-standard video code AND then mess up during the dialog setup scripts you will need to reboot to correct. Many do this now anyway.

2. The "Exit to prompt" would not appear as an Exit option.

Sorry to repeat, but I asked:

Quote

There's one redundant shell though, the root one that spawns the dsl one on boot. Do you think using exec there would be beneficial?

Any opinions?
This refers to the .bash_profile in the root of the image, which IMO leaves a root bash hanging without any purpose or use..

Yes. This is the place that can make a difference. Will implement.

Quote (roberts @ May 25 2008,16:02)

I don't want to be a hard head on smooth ansi font. I felt a change with possibly an improved appearance would be nice and to also showcase the .luafltkrc that mikshaw brought to our attention. Perhaps other, already included, fonts that work well with Dialog/Whiptail can be suggested.

Would still like comments or suggestions of alternate fonts or recommendation to go back to the original font so as to accomodate both X and Dialog/Whiptail.
I would like a nice clean next release candidate in preparation for 4.4 final.

Next Page...
original here.