Puppy Linux Discussion Forum :: View topic - patches to time boot messages to help to speed up boot

Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

FAQ

Memberlist

Usergroups

Profile

The time now is Tue 21 May 2013, 22:19
All times are UTC - 4

Forum index » Advanced Topics » Cutting edge

patches to time boot messages to help to speed up boot
Moderators: Flash, Ian, JohnMurga

View previous topic :: View next topic

Page 2 of 2 [19 Posts]

Goto page: Previous 1, 2

Author

Message

manelapb

Joined: 11 Mar 2011
Posts: 9

Posted: Wed 16 Mar 2011, 14:38 Post subject:

Dougal wrote:

(I added to my init script a usb_delay= parameter to control how many seconds to use).

Yes, this is the way...

usb_delay=0 failed to me until I hacked an ugly waitdev=sdb1 boot parameter to wait directly the drive I want.

That and after fixing a 2 seconds delay because there is no floppy in my PC and I arrive to "Performing a 'switch_root'" in 3.00 seconds

From 29.06 to 3.00 seconds is a quite great improvement! Cool

jemimah

Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

Posted: Wed 16 Mar 2011, 16:07 Post subject:

technosaurus wrote:

The one thing you _can_ do is run Xvesa and jwm (vesa support is built in by default), I probably need to step through the boot process somehow to figure out what part(s) make(s) the terminal emulator usable b/c jwm will not restart unless the command is issued from within the session however "rxvt -e ..." will automagically attach itself to work around that limitation

I wonder if that's how the "splashtop" OSes are doing it - just basic VESA graphics and not much else.

technosaurus

Joined: 18 May 2008
Posts: 3843

Posted: Wed 16 Mar 2011, 16:22 Post subject:

jemimah wrote:

I wonder if that's how the "splashtop" OSes are doing it - just basic VESA graphics and not much else.

thats how most of the "big boys" do it - they pretend to have a functional desktop while in fact things are still loading in the background.... but no, actually you can run a lot of apps from the framebuffer (gtk2 has a directfb port and a linuxfb port up until 2.14) most everything is in the initial ramdisk so they don't need to wait on drive module loading and mounting to get OS files (Which is what I did on my attempt) You could probably get a static uclibc Midori up in ~1 sec... Minimizing the size helps too (for load/decompression time) Which reminds me, I have been meaning to ask you what you thought would be the minimal set tools of tools for internet connection (I am already porting iwlist and iwconfig to busybox) maybe wpa_supplicant_cli? (I think iwconfig in wireless tools dev may handle it ok now though?)
_________________
Puppy Web Desktop Now with pet packages - Pet Packaging 100 & 101

jemimah

Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

Posted: Wed 16 Mar 2011, 16:50 Post subject:

AFAIK wpa_supplicant is still needed to make wpa connections.

Frisbee also needs dhcpcd - it could probably be fixed to deal with busybox dhcp client though IMO, dhcpcd at 75k is worth it.

Page 2 of 2 [19 Posts]

Goto page: Previous 1, 2

View previous topic :: View next topic

Forum index » Advanced Topics » Cutting edge

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

[ Time: 0.0469s ][ Queries: 13 (0.0047s) ][ GZIP on ]