I attach some patches for Puppy 5.20 to time boot messages (in screen and to log) and to have a single boot log with uptimed messages.
Is this the right place for this?
The idea is to locate wasted time to help to speed up boot.
I boot from usbstick with "pmedia=usbflash pfix=ram,nocopy pkeys=es"
Update 13.3.11: I add attachment with v2
here a grep "^\[" /tmp/bootsysinit.log
Code: Select all
[ 1.37 ] Loading 'es' keyboard layout...
[ 1.38 ] Loading drivers needed to access disk drives
[ 4.55 ] - Waiting for USB device to register
[ 11.56 ] - Waiting for usb partitions
[ 28.59 ] Searching for Puppy files in computer disk drives...
[ 28.77 ] Loading the 'lupu_520.sfs' main file...
[ 28.90 ] Setting up the layered filesystem...
[ 28.90 ] Overlaying preconfig files...
[ 29.06 ] Performing a 'switch_root' to the layered filesystem:
[ 29.07 ] - Copying files and sync...
[ 30.52 ] - switch_root... (End of init in initrd.gz)
[ 31.00 ] Making the filesystem usable...
[ 34.56 ] Updating...
[ 41.51 ] Loading kernel modules...
[ 46.50 ] Loading swap partition /dev/sda3...
[ 46.59 ] Waiting for modules to complete loading...
[ 48.64 ] Setting up services (network, printing, etc.)...
[ 48.69 ] Recognising media devices...
[ 49.82 ] End of rc.sysinit, next /etc/profile (after root login)
[ 50.15 ] Starting xwin script to run X windows
[ 50.77 ] Starting X, specs in /etc/X11/xorg.conf, startup apps /root/.xinitrc...
[ 53.29 ] X server started, running /root/.xinitrc
[ 54.38 ] Starting Window Manager
[ 56.64 ] X desktop started, running /root/Startup scripts
Code: Select all
#!/bin/sh
# Use: bootmsg2csv bootsysinit-copy.log, or just bootmsg2csv
# parse log, get bootmsg messages and convert to CSV for spreadsheet processing
FILE=$1
[ ! "$FILE" ] && FILE="/tmp/bootsysinit.log"
grep "^\[" $FILE | tr "[]," " , " >$FILE.csv
grep "^\[" $FILE # Also show
17.03 - Waiting for usb partitions
7.01 - Waiting for USB device to register
6.95 Updating...
4.99 Loading kernel modules...
3.56 Making the filesystem usable...
3.17 Loading drivers needed to access disk drives
I think first one is a bug (I will report it), and at least Updating... can be avoid or speed up greatly...