What is the best way to shorten the boot process?
My application does not need graphic. Which packages are for graphic? Or is there a description for each packages available?
bye
Ronald Wiplinger
How to speed up the boot process?
do you boot from usb?
http://www.murga.org/~puppy/viewtopic.p ... light=ehci
But I don't know, if that still is valid in Puppy 108.
To stop the Xserver from starting, rename
/usr/X11R6/bin/xwin to xwin-old.
Mark
http://www.murga.org/~puppy/viewtopic.p ... light=ehci
But I don't know, if that still is valid in Puppy 108.
To stop the Xserver from starting, rename
/usr/X11R6/bin/xwin to xwin-old.
Mark
Re: How to speed up the boot process?
Since you explain that your application does not need graphics or a monitor, Why did you decide to use puppy? wouldn't it be better to use another minimalist distribution that only has console?ELMIT wrote:My application does not need graphic.
Any way, to answer your question. Am I correct assuming that what you want to do is to remaster puppy to create a smaller usr_cram.fs that would boot faster?
If you follow the remaster process you will have a very good idea of what you want to remove by looking at the size of the unleashed packages, the names are quite descriptive.
For example, Mozilla uses 9 MB and Xorg components almost 8 MB too. There with two packages you will be cutting almost 20 MB
You can get a list of packages currently included in the liveCD by executing the following
Code: Select all
grep " on " /root/.packages/unleashedpackages.txt > /root/installed.txt
We cannot tell you what packages to remove because we don't know what you want to use puppy for.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
I am still doing something wrong!
I used createpuppy. The last time now with a new extracted /mnt/home/puppy
Not added nor deleted any packages.
Near the end of createpuppy I see:
What does it mean? How to solve?
bye
Ronald Wiplinger
I used createpuppy. The last time now with a new extracted /mnt/home/puppy
Not added nor deleted any packages.
Near the end of createpuppy I see:
Code: Select all
The size in bytes of usr_cram.fs is saved in /root0/.etc/sizeusrcram.
This is used during bootup to verify correct version of usr_cram.fs found.
...note, size is 32321536 bytes.
Now extracting usr_cram.fs as a separate file, not inside image.gz...
...done
Making ext2 filesystem on rootfs-tmp2/, size 13824 Kbytes...
13824+0 records in
13824+0 records out
mke2fs 1.34 (25-Jul-2003)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
3456 inodes, 13824 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
2 block groups
8192 blocks per group, 8192 fragments per group
1728 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Copying everything from rootfs-tmp1/ to rootfs-tmp2/...
(I hope the partition still has enough space!)
...Errors here mean the size 13824 Kbytes allocated to rootfs-tmp2/,
which will become file image then image.gz, is not big enough.
You will need to remove files or use UPX.
Note the kernel is compiled with ramdisk size of 12288K, but can be
overridden by the boot parameter "ramdisk_size="
If error msgs above, press "e" key then ENTER key for diagnostics.
If no errors, Press ENTER to continue script: e
Error diagnostic:
Partition mounted on /mnt/home has 23063992
986 Kbytes free space.
12288K ext2 filesystem "image" mounted via /dev/loop2 on ./rootfs-tmp2
has 986 Kbytes free.
Either of these being full is the cause of the trouble.
Deleting rootfs-tmp2 directory...
Exiting script...
What does it mean? How to solve?
bye
Ronald Wiplinger
I changed rootfs-complete/etc/ramdiskfssize to 15724 Kbytes.
Still I get:
...Errors here mean the size 15724 Kbytes allocated to rootfs-tmp2/,
which will become file image then image.gz, is not big enough.
You will need to remove files or use UPX.
Note the kernel is compiled with ramdisk size of 12288K, but can be
overridden by the boot parameter "ramdisk_size="
Still I get:
...Errors here mean the size 15724 Kbytes allocated to rootfs-tmp2/,
which will become file image then image.gz, is not big enough.
You will need to remove files or use UPX.
Note the kernel is compiled with ramdisk size of 12288K, but can be
overridden by the boot parameter "ramdisk_size="