Gilbert are the scripts that you, tuxdev and Sasha available somewhere. Also have you collated them into a package, then we could have a "speed boost" package that is easy to install/remove, somewhat akin to the multi-lib packages.

samac

Here's the link to Sasha's original thread:
http://www.linuxquestions.org/questi...ght=sasha+dash

Latest versions of here scripts here:
http://www.linuxquestions.org/questi...2&d=1261773877

tuxdevs versions here:
http://github.com/tuxdev/slackware-scripts

You can get my versions of the scripts here:
http://distro.ibiblio.org/pub/linux/...ipts-dash-1.0/
I've created a src2pkg build script for the scripts themselves, and there are sources, patches and build script for dash there as well. Just download the whole directory to get it all. Then use src2pkg to build the dash package first (src2pkg -X), and then install it. Then build the sysvinit-scripts-dash package with src2pkg using the same command as above.
Please, create a backup of your /etc/rc.d directory before installing the resulting sysvinit-scripts-dash package! I have written the doinst.sh so that it should re-name any existing scripts to NAME.bash before renaming the scripts in the package from NAME.dash to NAME.
If you do not install dash first, the scripts package will create a link from /bin/sh to /bin/dash -the scripts should work fine using /bin/sh as well.

Please note that I have changed the shebang in the scripts to use /bin/dash explicitly -to avoid using dash as the system /bin/sh (as that would cause all kinds of follow-on problems from other scripts).

The scripts package will contain a handfull of extra scripts which are not included in the official sysvinit-scripts package -I have added modified versions of the main ones which create bottlenecks during bootup, including rc.udev, rc.inet1 and rc.wireless. The package will also include a dashified version of rescan-scsi-bus with corresponding rc.scanluns, but the program is installed with the '.dash' suffix, so it will not overwrite any existing one.

Please, have a good look at the package before you install it so you won't be surprised at what happens. If you have modified rc.inet1 or any of the other official scripts, you'll want to have a hard look at the new versions before renaming them. The scripts should all be installed with the '.dash' suffix so you can easily identify them -they should not overwrite existing scripts -you'll have to rename them your self. You could also simply unpack the source tarball for the scripts and install them manually. But remember, they have the /bin/dash shebang, so they will not work if dash is not installed -or unless you create a link from /bin/sh to /bin/dash:
cd /bin ; ln -sf sh dash

2 members found this post helpful.

I should point out that the latest version of that archive linked at link#2 above, *was* current for Slack 13.0 but has not been touched for some time, particularly not WRT the recent move towards Slack -current. Anyone using -current or the next release (13.1??) will find problems with some scripts in that archive, because some system binaries now accept different arguments than they used to.

The #1 example of this that I have discovered, is DHCPCD (called by rc.inet1). Some of its arguments have changed, so I now have a fresh new rc.inet1 that works with the new DHCPCD.

In the next couple days (maybe by tonight; depends how pre-occupied I am with other things, like giving my snake a bath) I'll post a new archive for anyone interested in having a look; I'll post or link it in THIS thread, as well as linked to my initial thread (linked as link#1 in Gilbert's post); and between mine, tuxdev's, and gnashley's scripts, anybody should be able to figure out which mods they may want in their own system, and decide what way is best for them.

Sasha

My version already includes the updated syntax for dhcpcd. I went along comparing with current as of a couple of weeks ago, so there might still be some new changes with the latest round of upgrades in current.

I have built dash and the sysvinit-scripts-dash using src2pkg. By the way love how the src2pkg script makes it so simple to compile, saves me having to figure out all the options. Now I just have to figure out how brave I am.

samac

Gilbert

Whoa! that was exciting. There is something wrong with the way inittab is handled in your doinst.sh, basically it doesn't rename from inittab.new to inittab. After I had got my computer going and rename it the machine booted to runlevel3 pretty well, but runlevel 4 was a complete wash out. Anyway to cut a long story short. 90 minutes later I have repaired my system, but it was fun

samac

Okay, guess I missed a line in the doinst for the inittab -it's unaltered anyway. Were you able to startx manually?

Alright, lets see what I missed there -you know the routine now so you should be able to repair it again if need be. I seem to have missed installing the 'services' file. That's a list of the 'minor' deamons which get started at the end of rc.M, so that's the main reason it hasn't owrked for you, I'll guess. Just copying it into /etc/rc.d should do the trick. You might want to skip using my rc.4 file as well as it is pretty non-standard.

I really should redo the whole group of files using the latest current ones and only make the necessary changes. As it is, I've used some from Sasha and mostly those from tuxdev. Both of them have supplied versions which include extra changes which most people might not want.

Thanks for trying -you are a brave soul -I know you are no 'greenhand' or I wouldn't have encouraged you...

When I used startx the desktop loaded but it was essentially frozen as I had no access to mouse or keyboard. Also when pidgin popped up it did not connect to the internet. I believe that the x-server was actually running but because I could not access the computer I could not test this.

I would agree that it should be, up to date, necessary changes only at this stage. If you redo the files let me know and I will give them another go, but this time I will install a breakable version on a spare partition.

samac

Ha ha, sorry I caused you so much excitement. You were probably using kde ritght? Since the services file was not in there, you'd have missed messagebus and hald for that...

I'll have a fresh look at those files and make a more conservative package -still it's a bit difficult to implement cleanly because of the need to replace existing files which you may have customized, but you will have noticed that the originals were all renamed instead of removed/overwritten.

Yes I use KDE, but I don't tend to customize the basic configuration files too much so they are easy to modify on an ad-lib basis. Keeping the originals re-named as original.bash is a very good way of handling this very invasive modification. Just post if you want an update tested.

samac

I think I've gotten them reworked in a better way, but I'm gonna sleep on them before uploading and posting.

The version you have would probably have worked except for the missing /etc/rc.d/services file. That was a mod by tuxdev which shortens the rc.M file considerably by simply listing the last minor services explicitly started by rc.M -rc.M cats the file to get the list. For the new version I have eliminated that mod to reduce the changes from the originals -even though I like the idea and suspect it may speed things up a bit.

I'll try the new versions out on my system I am testing to make sure the basic functionality is there -but it doesn't have most of those services installed and no kde or xfce, so the scope of the test will be limited...

I'd rather know that before starting a new thread. So if there is one, please post it. Otherwise, I'll create a thread simply for questions and requests about features in src2pkg.

Xavian-Anderson Macpherson
Shingoshi

@ Shingoshi,

one in particular does not come to mind for me. However, some choices:

-- you might want to ask on (one of) the most recent "[announce] new src2pkg release" threads, such as this one: http://www.linuxquestions.org/questi...leased-781261/

-- or contact gnashley by email and inquire/present your ideas.

-- or, create a thread specifically for src2pkg feature requests, if none exists.

just some ideas

Xavian, you know my email address perfectly well.

Email sent!

Xavian-Anderson Macpherson
Shingoshi