Slackware :: Attempting To "speed Up Boot Time" By Using The "dash" Shell Instead Of "bash"?
Apr 23, 2010
i was attempting to "speed up boot time" by using the "dash" shell instead of "bash"there is a post on here which describes this.i installed the scripts and uhhhh....rebootednow it seems that i kinda sorta forgot to install "dash" before reboot and now ihave no system shell.no root user accessonly my regular user works, kinda...it seems that i cannot edit anything eitherit won't do any temp dataso with mc i cannot save any edited files.....prompt looks like thismichael@(none):i am hoping i just need to install dash....but with limited power at the command prompt this may be interesting.
I am trying to fix a perl script, and I really suck at perl. But I think this problem will be easy for people who know it.
The problem is, I have an old setup script someone wrote many years ago. It fails if the standard shell is dash and not bash. The only way I've gotten it to work is to point /bin/sh to bash. I looked thru the script and it uses "system" many places, and I think that's the problem.
I searched for it and found this link:url
My plan is to include this function:
Code: sub system_bash { my @args = ( "bash", "-c", shift ); system(@args); } Then I could simply change all calls to system into system_bash and it should work?
The parameter to the system calls is usually some variable. What if the parameter is a list already? Do I need to test for it somehow, and if it's a list, prepend "bash" and "-c" to the list? How do I do that?
In the script there are lots of places like this:
my $error = system($cmd); if ($error) { die/warn "some error message"; }
Shouldn't there be a return in the system_bash function?
This on a Vostro 1220 Laptop w/ Intel 5300 wireless:
A.I have long boot up time.I think it's because of the eth0 network search which I don't use.I have an intel wireless 5300 card running.How can I speed up the boot time, i.e. disable or change the eth0 at boot, the searching?
B:When I restart or shutdown, the screen flashes repeatedly and gets some garbled colors along the top before finally rebooting looks like windows ME or something).This vostro has an intel x4500HD vid chipset in it.
C.How do I get into gnome configuration editor to turn on Metacity compositing? Alt-F2 and run gconf-editor doesn't do it. I don't do compiz, but need compositing.
D.I need to install Chromium Browser as it sync my bookmarks.I have RPMforge enabled btw also...how can I do that? I.e. rpm repo for chromium?
This will help me get off to a running start so I can get up to speed on CentOS..
I'm on a Dell Inspiron 6000. I installed i8kutils and it works. Fan speed reduces CPU temp from 50C to 44C. A start-up script invokes the i8k module: $ udo /usr/sbin/modprobe i8k force=1 which creates /proc/i8k. The man page for i8kctl is straightforward: a few simple commands to read info from the aforementioned file.So. I know nothing about writing even basic bash scripts. I gave it a go here but I know this is way wrong. Would anyone like to help a guy out? This is my starting point (don't laugh):
Code: #!/bin/bash # script to toggle fan speed low/high
when I try to enter an escape sequence in the interactive mode of dash, it keeps on spewing out the <ESC> character as ^[ displayed in plain text instead of catching it as a control character. I vaguely remember encountering this on some UNIX shell but for the life of me I can't find anything on it. So how do I properly enter escape sequences in dash's interactive mode? (it supposedly supports vi line edit mode but I can't access it at all because of the ESC situation)It's not a make-or-break thing.
Despite the fact that Ubuntu 9.10 boots up faster than its predecessors (I didn't time the boot up myself, so I can't say for sure), my Ubuntu laptop still takes around 50 seconds to boot up fully. Now I'm not happy with that, and I want it to boot up even faster.
"When first starting, the shell inspects argument 0, and if it begins with a dash '-', the shell is also considered a login shell" - from the dash man page. Could someone please explain this to me in a way that I actually understand?
Are there any easy special tricks to speed up the boot time?Coming from Linux Mint (GNOME), I could get to the Desktop from cold in less than 25 secs.Now in openSuse 11.3 (KDE4.5) it takes more than twice that.Is this a function of KDE or have Ubuntu done something that openSuse hasn't to speed up the boot?
I'm curious if there are any tools that can help speed up the time it takes for my computer to boot up. I've used different utilities to help my Vista boot up time, so I'm curious if the same sort of things are available for Ubuntu.
I upgraded from Slackware 64 13.1 to Slackware 64 13.37 a week or so ago. I am now having a perceptible delay of a few seconds when launching commands from the command line, say for example: screen -R.
Is there some type of functional way to read things in the Python shell interpreter similar to less or more in the bash (and other) command line shells?
Example:
Code:
>>> import subprocess >>> help(subprocess) ... [pages of stuff to read] ...
I'm hoping so as I hate scrolling and love how less works with simple keystrokes for page-up/page-down/searching etc.
I just installed slack 13.37. I was poking around a little and I noticed that I have all these modules loaded... yet when I open up /etc/rc.d/rc.modules almost everything is commented out. how are these modules being loaded at boot time?
I have just recently installed Linux Lime along with windows 7 Home Premium. Before, there would be a menu asking me which operating system I would like to use. When I click linux it goes to linux and windows 7 goes to windows 7. Now when I click Linux, the black screen you get at the beginning shows a - (dash) constantly flashing on a black screen and won't boot to linux. This is normal as it does that for a second then boots. Now its stuck on that flashing dash on a black screen and won't boot.
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it.
I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect.
I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try?
I have Ubuntu 9.10. The batter drained several days ago, and now when I attempt to boot I simply get a string of indecipherable error messages which last for about 5 minutes, and the screen then goes completely black. I am not able to even get to the login screen. Windows 7 Starter boots fine, so it's definitely a software issue. Any solutions short of completely reinstalling? I really don't want to lose all of my data.
I downloaded the DVD release of Kubuntu 10.04, from Kubuntu.org. The file is: Kubuntu-10.04-dvd-amd64.rar . I burned it to a DVD, as image, with ImgBurn application. See any problems so far? I want to dual-boot, leaving my Win7 in tact. I am confident that I can handle this with some patient instruction.
I'm a newb and have ambitions for a triple boot with MAC/W2K/#! 9.04. I first installed Ubuntu on C600 laptop and then switched to Crunchbang 9.04 since the Dell is lacking any ooomph. Now I'm trying to triple boot an HP Pavilion a330n (AMD Athlon, non-SATA board which has created problems getting Leopard to play nice, but that's another story). I removed the HD from the C600 (W2K) and replaced it with another running only #!. I installed the W2K laptop drive as master on the HP desktop with a 120GB IDE drive as slave. The 120GB drive has been partitioned for 4: MAC (35GB, ext3), W2K (35GB, NTFS), #! (40GB, ext3) and Linux-Swap (remainder, ext3).
Now to the question: I was planning on using the DD command to "xcopy" the W2K drive to the W2K partition. Sounds simple. I am trying to use the following: dd if=/dev/sda2 of=/dev/sdb3 bs=4096 conv=notrunc,noerror
To back up a step, I saw somewhere else suggesting to boot live and run off the CD to facilitate this since I'm manipulating both hard drives. Since I'm working live, I've had some trouble sorting out password issues with root. I managed to change the root password (I know - dangerous, but only for this session anyway). Each time I try to execute the dd command, I get nada. No activity. The cursor drops below the root@crunchband:~$ prompt and just blinks. There is no important information to be lost on either drive per se, but have lost the W2K install CD long ago which is why I need to use DD anyway.
Today I attempted to install Win 7 on my Ubuntu 11.04 machine so I could dual boot. The Win 7b install went smoothly, but when I tried to fix grub everything went to hell.
I initially tried to reinstall grub using this walk though [URL] However, when I start the computer I get:
"GNU GRUB version 1.99~rc1-13ubuntu3
Minimal BASH-like line editing is supported....
grub> "
I tried to use the technique in [URL] to solve the problems, but when I try to run chroot I get a bin/bash error (I don't have the full error handy, but can rerun the steps if needed). The only potential cause that I can find doesn't apply to me since I am using a 11.04 64 bit live usb on a 11.04 64 bit install.
I'm running 10.04 on Wubi in XP and want to partition to dual boot properly. I've done the permanent grub-update issue fix for Wubi so I've got the time to figure this out, I'm just at an impasse right now.
I've tried both GParted and PartitionMagic Live CDs and have been unable to shrink my main partition down. It's currently at 45 or so GB with about 22 GB empty. I've turned off my virtual memory in XP as well and no dice. I keep getting the error in GParted during the shrinking process. It doesn't really explain why, though.
