iB::Topic::Lamer friendly DSL

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » DSL Ideas and Suggestions » Lamer friendly DSL

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (4) </ 1 2 3 [4] >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Lamer friendly DSL, modularity of MyDSL and DSL unified

< Next Oldest | Next Newest >

doobit

Group: Members
Posts: 912
Joined: July 2005

Posted: Mar. 14 2006,03:13

OK Robert, I had a chance to test this, and I definately need to put mydsl=sda1 to get them to load automatically, and toram works for me in the HDD install script for the pendrive in dsl-2.3rc1. Also, I wasn't sure if you saw it, but the wireless save script writes a new /opt/myprism.sh line in the /opt/bootlocal.sh everytime I make a change. These multiple entries results in the wireless connecting and disconnecting several times. Still I think these scripts wil make things easier and solve a couple of the big questions that many newcomers to DSL have.

--------------
"Help stop internet piracy...use Linux!"

roberts

Group: Members
Posts: 4983
Joined: Oct. 2003

Posted: Mar. 14 2006,06:09

Yep, using toram does require the mydsl=xxx option.
I am currently working on further automation of mydsl loading. It will be in RC2.

The multiple copies of the wirless does not happen within a single session. It is added to the save scripts only upon exit and with a yes answer to the prompt question. Also, this only needs to be done once for it is not the individual parameters that is added, it the the script names. Therefore, should you decide to re-setup your wireless, do would not want to save the scripts again. A no answer would be appropriate. Maybe, I am trying to do too much automation? I suppose I could scan for it already, but like I said it is not the parameters, instead it is the name of the script that contains the paramters. Like a link or pointer to the file that contains the parameters. But, then too, field testing and feedback provides further insight as to how it is used.