puppy cd/dvd ideas
Posted: Wed 15 Sep 2010, 11:09
re the above cd/dvd ideas you could also use the dvd and put the sfs files onto a usb drive to boot with right.
READ-ONLY Archive
https://oldforum.puppylinux.com/
Interesting, I will try it when I have a chance.its-me-again wrote:Macpup opera 2 uses enlightnment its a 431 baised os try it out and see what you think.
Thank you gcmartin. I'm glad to hear that jrb has tested the new SFS Linker with Lighthouse. I'm busy with final testing and debugging of the next release LHP 5.00 F, but when I have some time I will try it myself. Here is jrb's post:gcmartin wrote:Theres a PM to @tazoc from the SFS Utility author.
Please see the notes at http://murga-linux.com/puppy/viewtopic.php?t=47976 before using it, and post questions or bugs there also.jrb wrote:gcmartin,
Have modified and tested SFS-TCZ_Linker-1.6.pet in Lighthouse 5D both Live CD and regular. Seems to work very well. Had to make a few small changes but I'm quite sure they won't be incompatible with other pups.
Try it out! J
You're welcome! All the SFS I have tested are posted at http://www.lhpup.org/download500.htm#SFS I received a PM about CairoDock but have not tested it yet. Requests for other apps are welcome.Tommylee567 wrote:dropped in to say that it is super this time. running kde 4.4 and some how figured out by the help here to boot using the intel driver.
Thanks and keep up the good work.
can i get some sfs modules somewhere?
Tim
BootManager won't see SFS files until they are copied to /mnt/home on the drive (not CD/DVD) that has the pupsave. So even if /sr0/mnt/home has them, they still need to be copied to a hard drive or flash drive, whichever was used for the pupsave. Remastering on the other hand, includes the SFS files within a newer, much larger the main file. IIRC the main file is loaded at boot before the pupsave.[Edit: the pupsave is mounted before the main file.]gcmartin wrote:...please help me understand what's wrong with this logic. I know the Mariner ISO places its SFSs in the root of the LIveDVD. I also know that Puppy BootManager Utility expects to find its SFSs in /mnt/home on the running system. Let say I:
- Open you Mariner ISO
- Leave the base system SFS, BUT move all other SFSs into /mnt/home folder
- Burn this "new" ISO as a Multi-Session.
- Boot this "new" ISO
- Run BootManager and select the SFSs I want
- When complete, Reboot the system allowing the system to '"save" the session
Except maybe SFS-TCZ_Linker, remastering--merging the SFS files into the main file (see CLAM01's post above) is the only way I know of.Do you know if there is some way to copy Frugal to a LiveDVD so that it supports LH with the "installed" SFSs?
Does this comment imply that I should copy the /mnt/home folder from the LiveDVD to the running (ram based) system's root before running BootManager, then run BootManager so that it finds the files and builds the correct boot measure and tables....Once Bootmanager is completed, should I Then to Reboot the running system allowing the system to '"save" the session to the LiveDVD/LiveCD? Is this what would work. Would the Lighthouse boot process then find the appropriate folders properly?tazoc wrote:....BootManager won't see SFS files until they are copied to /mnt/home on the drive (not CD/DVD) that has the pupsave. So even if /sr0/mnt/home has them, they still need to be copied to a hard drive or flash drive, whichever was used for the pupsave. Remastering on the other hand, includes the SFS files within a newer, much larger the main file. IIRC the main file is loaded at boot before the pupsave.... -TazOCgcmartin wrote:...please help me understand what's wrong with this logic. I know the Mariner ISO places its SFSs in the root of the LIveDVD. I also know that Puppy BootManager Utility expects to find its SFSs in /mnt/home on the running system. Let say I:
- Open you Mariner ISO
- Leave the base system SFS, BUT move all other SFSs into /mnt/home folder
- Burn this "new" ISO as a Multi-Session.
- Boot this "new" ISO
- Run BootManager and select the SFSs I want
- When complete, Reboot the system allowing the system to '"save" the session
The only way I know of to save your session directly to CD/DVD is with the experimental Multi-session LiveDVD (PUPMODE=77), probably quite slow, especially with KDE and I don't know how it handles SFS files. This is at line 115 of /usr/sbin/bootmanager:gcmartin wrote:Does this comment imply that I should copy the /mnt/home folder from the LiveDVD to the running (ram based) system's root before running BootManager, then run BootManager so that it finds the files and builds the correct boot measure and tables....Once Bootmanager is completed, should I Then to Reboot the running system allowing the system to '"save" the session to the LiveDVD/LiveCD? Is this what would work. Would the Lighthouse boot process then find the appropriate folders properly?tazoc wrote:....BootManager won't see SFS files until they are copied to /mnt/home on the drive (not CD/DVD) that has the pupsave. So even if /sr0/mnt/home has them, they still need to be copied to a hard drive or flash drive, whichever was used for the pupsave. Remastering on the other hand, includes the SFS files within a newer, much larger the main file. IIRC the main file is loaded at boot before the pupsave.... -TazOC
Code: Select all
#for multisession cd, extra sfs files have to be on the cd...
#v3.97 sfs files are at '/', saved with a session...
if [ "$PUPMODE" = "77" ];then
# MPATTERN="/dev/${PDEV1} "
# EXTRASFSMNTPT="`mount | grep "$MPATTERN" | cut -f 3 -d ' '`"
# #...it may not be mounted, then gets mounted below.
# MSGx="Note2: These files are on the Puppy boot CD"
MSGz='/'
# if [ "$EXTRASFSMNTPT" = "" ];then
EXTRASFSMNTPT='/'
xEXTRASFSMNTPTx="" #100711
MSGx="Note2: All SFS files have to get loaded into RAM from CD"
# fi
fi
BootManager can't be run in first boot / LiveCD/DVD mode (PUPMODE=5), only after saving your session and rebooting. So I think for incorporating SFS files into PUPMODE=5, either remastering or the new SFS-TCZ_Linker are the best options.You have booted off a live-CD or DVD, and you can now save your personal settings and files to a USB Flash drive, Zip drive, floppy disk, or any hard drive partition (including NTFS). The session will be saved as a single file, named spupsave.3fs, which has an ext3 filesystem inside it.
However, if you have burnt the CD/DVD as multisession (not closed), then sessions can be saved as additional tracks to the CD/DVD -- each saved session will appear on the CD/DVD as a directory with all the saved files in it, not as a single file. THIS IS STILL EXPERIMENTAL
Select <SAVE> (just type S) to choose a partition to save this session as file spupsave.3fs...
Select <SAVE TO CD> (TAB then ENTER) to save session to CD/DVD (multisession) (EXPERIMENTAL)...
You should never leave the DVD open in general use. if you save and use the same save file from cd/dvd all the time as it gets bigger or full it will break and you will get a big error runing slow and nothing can be done.gcmartin wrote:Does this comment imply that I should copy the /mnt/home folder from the LiveDVD to the running (ram based) system's root before running BootManager, then run BootManager so that it finds the files and builds the correct boot measure and tables....Once Bootmanager is completed, should I Then to Reboot the running system allowing the system to '"save" the session to the LiveDVD/LiveCD? Is this what would work. Would the Lighthouse boot process then find the appropriate folders properly?
Thanks in advance
No, that feature is new for Lighthouse 5.00 F and the latest Woof, and only works if the pupsave is in a subdirectory. When booting from GRUB use psubdir parameter e.g., psubdir=lhp5F on the kernel line. So for now, keep SFS files for other versions at /mnt/home.Barburo wrote:I think the ability to keep .sfs files in the sub-dir makes good sense, so I used it for the mariner and kde .sfs files. I found that it works fine but bootmanager does not distinguish between .sfs files in /mnt/home from those in /mnt/home/lhp5F so I need to move those other .sfs files to their appropriate sub-dirs so they do not appear in the .sfs list unless common to several versions. (... but does this feature work for previous versions?)
Hmm, strange. What is the o/p ofRebooted into LXDE (that had been my 5D default). Keeps the background through reboots, and has the new network interface system tray app.
Tried KDE4 but it quits before the desktop - falls out to the selection menu. Tried dropping out of X and back again - same. Tried rebooting - same.
Code: Select all
plasma-desktop --version
kdeinit4 --version
If Xfce misses the background, edit /etc/xfce/xdg/xfce4/xinitrc, inserting 2 lines at the beginning like this:Tried Xfce which worked OK but lost the background on reboot.
I am using the same C-F .sfs file as before.
B.
Code: Select all
#!/bin/sh
. /etc/profile #100907 TazOC (for wallpaper bug reported by Barburo)
sleep .5 #100907 TazOC
... so I guess I'm missing a library. I had noticed something amiss in 5D KDE desktop but it still functioned OK.bash-4.1# kdeinit4 --version
Qt: 4.6.2
KDE: 4.4.4 (KDE 4.4.4)
bash-4.1# plasma-desktop --version
plasma-desktop: error while loading shared libraries: libQtScript.so.4: cannot open shared object file: No such file or directory