To be clear, with grub4dos it's not possible to boot live-debian located within a full ext puppy installation, right? This is what I mean.saintless wrote:Hi, Anikin,anikin wrote:How do I boot it via grub4dos alongside with my other puppies?
extract live folder on top of a partition.
Here is my boot code (live folder is on /sda1):Code: Select all
title Light-Debian-Core-Test root=(hd0,0) kernel /live/vmlinuz boot=live config persistent swapon quickreboot noprompt autologin initrd /live/initrd.img boot
DebianDog - Squeeze
Booting Light-Debian-Core with grub4dos
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
Hi, Sunburnt,
The name sfs does not exist in any other distro as far as I know and sfs file is 100% squashfs type file like debian one.
I have renamed sfs to squashfs in your script for the test only.
live-rw save file is the same as pup_save.2.fs,3.fs,4.fs so we can use your script choosing live-rw as a name (without ext). One more thing in puppy which is 100% the same as in debian live. Just the name of the save file is different.
Create puppy empty save file in puppy linux, rename it to live-rw and use it with debian live. Or the opposite. No problem at all.
It was chosen as a smsllest file sized file manager and it has much more useful functions from the others.
You can install deb files from it with right mouse button click and unzip zip archives the same way for example without any special configuration.
Cheers, Toni
Yes. Gtkdialog dependencies. What I don't like is the size the add. But for the version with more apps I might have to install them anyway. Time will show.1) I assume by "Then fix the missing dependencies", they are GtkDialog & etc.?
Yes, debian uses squashs instead sfs. This is the same file type and I think renaming to sfs is Barry's idea. Just my thougths.2) I modded my make image file app. as Musher suggested.
...... But I don`t think we want to use it for Deb-Live ( don`t need Puppy extensions ).
...... It looks like Deb-Live uses file extension: "squashfs", but none for "ext2,3,4"
The name sfs does not exist in any other distro as far as I know and sfs file is 100% squashfs type file like debian one.
I have renamed sfs to squashfs in your script for the test only.
live-rw save file is the same as pup_save.2.fs,3.fs,4.fs so we can use your script choosing live-rw as a name (without ext). One more thing in puppy which is 100% the same as in debian live. Just the name of the save file is different.
Create puppy empty save file in puppy linux, rename it to live-rw and use it with debian live. Or the opposite. No problem at all.
It is part yours filemnt script taken from Turbopup Extreme. Maybe barry's name was also there. I'm not sure. Appolgies if I this is the situation and gratitude to him also.3) I haven`t looked at: /script/mount-sfs
...... I assume you`re saying that it`s the old filemnt script that you`ve modded.
...... filemnt is maintained by Barry who decided to use it for Puppy.
Even this one works fine as far as I see.### Recently I thought about making a new one.
The real problem is from this core debian pcman and rox will add much more dependencies to the image than xfe.### OR... Just add mounting to the image file gui ( a gui button, & Rox mime click ).?
...... I didn`t check, but Xfe mime mount should be made to work also probably.I just renamed rox to xfe in your script and it worked. Xfe window opens with the content of the file.
..... Also Xfe is pretty heavy weight, PcManFM is smaller, and SpaceFM I don`t like.
...... Size isn`t that important, and Xfe is very "feature rich", and there`s a calculator too...
.
It was chosen as a smsllest file sized file manager and it has much more useful functions from the others.
You can install deb files from it with right mouse button click and unzip zip archives the same way for example without any special configuration.
Cheers, Toni
Last edited by saintless on Mon 09 Dec 2013, 07:26, edited 7 times in total.
Re: Booting Light-Debian-Core with grub4dos
Never tested this but you can try this:session wrote:saintless wrote:Hi, Anikin,anikin wrote:How do I boot it via grub4dos alongside with my other puppies?
extract live folder on top of a partition.
Here is my boot code (live folder is on /sda1):To be clear, with grub4dos it's not possible to boot live-debian located within a full ext puppy installation, right? This is what I mean.Code: Select all
title Light-Debian-Core-Test root=(hd0,0) kernel /live/vmlinuz boot=live config persistent swapon quickreboot noprompt autologin initrd /live/initrd.img boot
Copy live folder from the CD on the top of your system like this /live
if you have /vmlinuz and /initrd.img from your full installed system, rename /live/initrd.img and /live/vmlinuz to /live/initrd1.img and /live/vmlinuz1 and try this code:
Code: Select all
title Light-Debian-Core-Test
root=(hd0,0)
kernel /live/vmlinuz1 boot=live config persistent swapon quickreboot noprompt autologin
initrd /live/initrd1.img
Code: Select all
title Light-Debian-Core-Test
root=(hd0,0)
kernel /vmlinuz1 boot=live config persistent swapon quickreboot noprompt autologin
initrd /initrd1.img
Last edited by saintless on Mon 09 Dec 2013, 09:28, edited 1 time in total.
Testing Light-Debian-Wheezy.iso 147 Mb version with pae and non pae kernel included here:nooby wrote:...could you do the same for Wheezy?
http://murga-linux.com/puppy/viewtopic.php?t=90660
It is only base to continue removing apps. Need quick tests to see if I didn't break something important so far. No use to continue without confirmation it works on your hardware and apt-get is working.
Cheers, Toni
What I mean is, grub4dos loads vmlinuz and initrd.img just fine, and then debian is unable to find a medium containing a live filesystem. I am aware of workarounds such as ISObooter, I was just wondering if I could test live-debian with the same simple grub4dos stanza I've been using to try out other linuxes.
The fact that Ubuntu boots just fine this way threw me for a loop... Ubuntu can do it (using iso-scan), so why can't Debian? (rhetorical question)
The fact that Ubuntu boots just fine this way threw me for a loop... Ubuntu can do it (using iso-scan), so why can't Debian? (rhetorical question)
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
Toni much appreciated but don't count too much on me testingsaintless wrote:Testing Light-Debian-Wheezy.iso 147 Mb version with pae and non pae kernel included here:nooby wrote:...could you do the same for Wheezy?
http://murga-linux.com/puppy/viewtopic.php?t=90660
It is only base to continue removing apps. Need quick tests to see if I didn't break something important so far. No use to continue without confirmation it works on your hardware and apt-get is working.
Cheers, Toni
Sure I will do my best but asI have already asked
and you or others may have answered already.
I have now three live directories in the /mnt/home directory.
This means that each live compete on which one gets booted
and there are other OS based on Debian that also use live so
they don't want others to use same partition something ...
So I temporarily "ditched" Pussy linux and renamed live to pussylive
so now if I install you new version I would have to rename your old one.
Is there some better solution than all debian wanting to be live directory.
What do you suggest? No hurry my illness makes me very tired
and lazy so will be slow to respond but today monday I do have
some time to dedicate to test so hope for some suggestions from all of you.
Can I name it wheezylive and do that in the menu.lst too?
would that load the right live directory? Sickgut longtime ago
most likely suggested something like that but my poor memory fails me.
No criticism I love that you are so at it and on the go!
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
I used grub4dos on this SDHC card install:session wrote:What I mean is, grub4dos loads vmlinuz and initrd.img just fine, and then debian is unable to find a medium containing a live filesystem. I am aware of workarounds such as ISObooter, I was just wondering if I could test live-debian with the same simple grub4dos stanza I've been using to try out other linuxes.
The fact that Ubuntu boots just fine this way threw me for a loop... Ubuntu can do it (using iso-scan), so why can't Debian? (rhetorical question)
# menu.lst produced by grub4dosconfig-v1.8.0
color blue/cyan yellow/blue white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
#Debian
title Light-Debian-Core-Test
root=(hd0,0)
kernel /live/vmlinuz boot=live config persistent swapon quickreboot noprompt autologin
initrd /live/initrd.img
boot
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# Advanced Menu
title Advanced menu
configfile /menu-advanced.lst
commandline
Hi, Nooby
Take care of your health and test what takes your interest most.
I don't expect you to test this. I already have an answer there. Just the question came from you and I use it to quote.
Anyway this is the way to use debian live in different folder (/debian-wheezy for example). Move live folder in /debian-wheezy and use this boot code:
swapon option is removed from this example. It creates me some issues with light-debian-wheezy when I change the path to it.. I will check out way.
Cheers, Toni
Take care of your health and test what takes your interest most.
I don't expect you to test this. I already have an answer there. Just the question came from you and I use it to quote.
Anyway this is the way to use debian live in different folder (/debian-wheezy for example). Move live folder in /debian-wheezy and use this boot code:
Code: Select all
title Wheezy 1
rootnoverify (hd0,0)
kernel /debian-wheezy/live/vmlinuz1 boot=live config persistence live-media-path=/debian-wheezy/live/ quickreboot noautologin noeject
initrd /debian-wheezy/live/initrd1.img
boot
Cheers, Toni
I think the first one was Squeeze and now Wheezy.
1) Toni; Can you out line the differences for us.? New kernel I assume, so maybe USB-3.?
2) So a dir. change is possible by putting /live in a sub dir.: /mnt/(Part)/(WhatEver)/live
# There`s a revised mk-save that has a checkbox for Puppy extensions.
Otherwise there`s none added, so it`s what the user types into the /path/file textbox.
I`m thinking that finding another GUI app other than GtkDialog would be very nice...
.
1) Toni; Can you out line the differences for us.? New kernel I assume, so maybe USB-3.?
2) So a dir. change is possible by putting /live in a sub dir.: /mnt/(Part)/(WhatEver)/live
# There`s a revised mk-save that has a checkbox for Puppy extensions.
Otherwise there`s none added, so it`s what the user types into the /path/file textbox.
I`m thinking that finding another GUI app other than GtkDialog would be very nice...
.
Hi, Sunburnt,sunburnt wrote:I think the first one was Squeeze and now Wheezy.
1) Toni; Can you out line the differences for us.? New kernel I assume, so maybe USB-3.?
2) So a dir. change is possible by putting /live in a sub dir.: /mnt/(Part)/(WhatEver)/live
# There`s a revised mk-save that has a checkbox for Puppy extensions.
Otherwise there`s none added, so it`s what the user types into the /path/file textbox.
I`m thinking that finding another GUI app other than GtkDialog would be very nice...
.
The kernel is almost the same. Original Squeeze uses 2.6.32-5-686 and 2.6.32-5-486 but I upgraded them to 3.2.0-0.bpo.4-686-pae and 3.2.0-0.bpo.4-486.
Wheezy uses as default 3.2.0-4-686-pae and 3.2.0-4-486. They supposed to be stable and long term supported from what I read.
So there is almost no difference between Light-Debian-Squeeze and light-Debian-Wheezy about hardware support.
The big difference is in the repositories. Wheezy uses and will continue to use the last versions of the programs.
Squeeze uses older versions and installing newer on it can cause problems with dpkg database.
Moving /live inside other folder with different name is what I found as an option to change the top folder name and it works with Grub Legacy. I'm not sure if there is a way to simply rename live folder.
Cheers, Toni
No, because my primary computers lack the horsepower to adequately test the guest system's snappiness.smokey01 wrote:Session, have you considered using Virtual Box?
Thanks everyone; testing from a usb drive will have to do.
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
Thanks Toni and thanks sunburnt.
I have also heard or read that the big diff is the updated files
in the repo Firefox a later version and so on.
then debian is unable to find a medium containing a live filesystem.
I should not ry to help I know too little but often
when I tell those who knows they tell me to make the
partition defragged. Which is not easy in linux.
Propietary defrag programs only
I have also heard or read that the big diff is the updated files
in the repo Firefox a later version and so on.
then debian is unable to find a medium containing a live filesystem.
I should not ry to help I know too little but often
when I tell those who knows they tell me to make the
partition defragged. Which is not easy in linux.
Propietary defrag programs only
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Very good Toni; I thank you for your answers and your efforts with all of this.
# This is a great deal of effort... Tell us of any help you might need.
I just dnlded Wheezy and I`ll let you know.
I realized what you ment about PcManFM, the Python deps. I forgot about them...
Xfe only has the Fox lib. at 6 MB size. And it does lots as we say.
I`m surprised Xfe ran filemnt by clicking an image file. Rox has it`s own mime, Xfe too I think.
.
# This is a great deal of effort... Tell us of any help you might need.
I just dnlded Wheezy and I`ll let you know.
I realized what you ment about PcManFM, the Python deps. I forgot about them...
Xfe only has the Fox lib. at 6 MB size. And it does lots as we say.
I`m surprised Xfe ran filemnt by clicking an image file. Rox has it`s own mime, Xfe too I think.
.
It really wasn't at first, but I use only small part from filemnt and it does the job in Light-Debiansunburnt wrote:I`m surprised Xfe ran filemnt by clicking an image file. Rox has it`s own mime, Xfe too I think.
Code: Select all
#!/bin/bash
set -x
# mount-sfs.sh
#This script is small edited part from original script "ROX app.: Click image files to mount & unmount." Created for Puppy linux by: Terry Becker aka: SunBurnt
imgFile="$1"
if [ -z "$imgFile" ] ;then exit 1 ;fi
if [ "`dirname $imgFile`" = '\.' ] ;then
imgFile="`pwd``echo $imgFile |sed 's/^\.//'`"
fi
MntPt='/media/'`echo "$imgFile" |sed "s#^\.##g" |sed "s#/#+#g"`
Ext=`echo "$imgFile" |sed 's/^.*\.//'` # get file type from extention
if [ "$Ext" = '2fs' ] ;then
Type='ext2'
elif [ "$Ext" = '3fs' ] ;then
Type='ext3'
elif [ "$Ext" = '4fs' ] ;then
Type='ext4'
elif [ "$Ext" = 'sfs' ] ;then
Type='squashfs'
elif [ "$Ext" = 'squashfs' ] ;then
Type='squashfs'
elif [ "$Ext" = 'iso' ] ;then
Type='iso9660'
fi
mkdir -p $MntPt
mount -t $Type -o loop $imgFile $MntPt
xfe -d $MntPt
Hi again Toni; I tested Wheezy, I`ll post that in it`s thread.
Where is your modded script.? I`m trying to get Deb Live`s layout.
Try out these code improvements if you have time:
Where is your modded script.? I`m trying to get Deb Live`s layout.
Try out these code improvements if you have time:
Code: Select all
#!/bin/bash
########### mount-sfs.sh ### From filemnt by Terry B. & Barry K.
set -x
[ "$1" ]|| exit 1
imgFile=$1
[ "${imgFile##/*}" = '\.' ]&& imgFile="`pwd`${imgFile#.}"
Mnt=/media/`echo $imgFile |sed 's#^\.##g;s#/#+#g'`
Ext=${imgFile##*.} # get file type from extension
case $Ext in
2fs) Type=ext2
3fs) Type=ext3
4fs) Type=ext4
ext2) Type=ext2
ext3) Type=ext3
ext4) Type=ext4
sfs) Type=squashfs
squashfs) Type=squashfs
sq) Type=squashfs
iso) Type=iso9660
img) Type=ext2
esac
mkdir -p $Mnt
mount -t $Type -o loop $imgFile $Mnt
xfe -d $Mnt
UUID problem using Grub4dos
i All,
Interesting project. Thought I'd see what it could do. My apologies if this problem was discussed before, but I can't get off page one of this thread and so posted without reading the following pages.
I downloaded and unpacked the ISO (non-pae) to my previously blank sdb4 partition. Opened a terminal and typed the following:
blkid > /root/my-documents/UUID.txt
which produced a text file showing, bolding added for clarity:
/dev/sda3: LABEL="LData" UUID="d3b27ca1-950c-4833-b8ef-d51a2792497d" TYPE="ext4"
/dev/loop5: TYPE="squashfs"
/dev/sdb4: LABEL="AData3L" UUID="ca0a3cca-2ead-42b6-a630-0a0047841eb7" TYPE="ext4"
/dev/sdb1: LABEL="AData1F" UUID="F1AB-D178" TYPE="vfat"
/dev/loop7: TYPE="squashfs"
/dev/sda4: LABEL="MData" UUID="3D52-D47B" TYPE="vfat"
/dev/sdb3: LABEL="AData2L" UUID="1f431a25-ca26-40fa-aa8e-c05af958ecd7" TYPE="ext4"
/dev/sda1: UUID="3A4CDDD24CDD8951" TYPE="ntfs"
/dev/loop6: TYPE="squashfs"
/dev/sda2: LABEL="Linux1" UUID="bf2b0f37-69b6-4c47-be62-ffb16dad149f" TYPE="ext4"
/dev/sdb2: LABEL="AData1L" UUID="1f531665-1026-449f-b413-dd9654a3e145" TYPE="ext4"
/dev/loop1: UUID="241699fa-e5ce-438d-8c21-a2ef3cbaaf76" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
Then I added the following to my Grub4Dos' menu.lst
title Light Debian Core
uuid ca0a3cca-2ead-42b6-a630-0a0047841eb7
kernel /live/vmlinuz boot=live
initrd /live/initrd.img
Attempting to boot into it produces something like "Partition not found".
Running blkid after the files were copied, adding a boot flag to sdb1 or sbd4, even copying a folder with a Pup, installing Grub4dos, and checking what UUID was generated for the PUP file produces the same uuid.
Ran into the same problem when trying to boot from a USB-Key which, of course, had a different UUID that was reflected in its Grub4dos menu.lst.
Any ideas?
mikesLr
Interesting project. Thought I'd see what it could do. My apologies if this problem was discussed before, but I can't get off page one of this thread and so posted without reading the following pages.
I downloaded and unpacked the ISO (non-pae) to my previously blank sdb4 partition. Opened a terminal and typed the following:
blkid > /root/my-documents/UUID.txt
which produced a text file showing, bolding added for clarity:
/dev/sda3: LABEL="LData" UUID="d3b27ca1-950c-4833-b8ef-d51a2792497d" TYPE="ext4"
/dev/loop5: TYPE="squashfs"
/dev/sdb4: LABEL="AData3L" UUID="ca0a3cca-2ead-42b6-a630-0a0047841eb7" TYPE="ext4"
/dev/sdb1: LABEL="AData1F" UUID="F1AB-D178" TYPE="vfat"
/dev/loop7: TYPE="squashfs"
/dev/sda4: LABEL="MData" UUID="3D52-D47B" TYPE="vfat"
/dev/sdb3: LABEL="AData2L" UUID="1f431a25-ca26-40fa-aa8e-c05af958ecd7" TYPE="ext4"
/dev/sda1: UUID="3A4CDDD24CDD8951" TYPE="ntfs"
/dev/loop6: TYPE="squashfs"
/dev/sda2: LABEL="Linux1" UUID="bf2b0f37-69b6-4c47-be62-ffb16dad149f" TYPE="ext4"
/dev/sdb2: LABEL="AData1L" UUID="1f531665-1026-449f-b413-dd9654a3e145" TYPE="ext4"
/dev/loop1: UUID="241699fa-e5ce-438d-8c21-a2ef3cbaaf76" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
Then I added the following to my Grub4Dos' menu.lst
title Light Debian Core
uuid ca0a3cca-2ead-42b6-a630-0a0047841eb7
kernel /live/vmlinuz boot=live
initrd /live/initrd.img
Attempting to boot into it produces something like "Partition not found".
Running blkid after the files were copied, adding a boot flag to sdb1 or sbd4, even copying a folder with a Pup, installing Grub4dos, and checking what UUID was generated for the PUP file produces the same uuid.
Ran into the same problem when trying to boot from a USB-Key which, of course, had a different UUID that was reflected in its Grub4dos menu.lst.
Any ideas?
mikesLr
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Re: UUID problem using Grub4dos
(I snipped some)
So maybe you could use sdb4 ?
I don't understand Debian, but this seems to work:mikeslr wrote: Then I added the following to my Grub4Dos' menu.lst
title Light Debian Core
uuid ca0a3cca-2ead-42b6-a630-0a0047841eb7
kernel /live/vmlinuz boot=live
initrd /live/initrd.img
Code: Select all
title Light-Debian-Core
root (hd0,0)
kernel /live/vmlinuz boot=live config persistent quickreboot noprompt autologin
initrd /live/initrd.img
boot
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Hi Toni and all of you.
Haha finally I did test your Wheezy version too.
I renamed the Squeezy live file to something else
and it booted with the code just above my post
I did not have to do anything to get out through
my Router and Modem I did not test to see if it
does wifiI have forgotten where I have my password
for the router so may need to reset it and choose a new PSW
Haha finally I did test your Wheezy version too.
I renamed the Squeezy live file to something else
and it booted with the code just above my post
I did not have to do anything to get out through
my Router and Modem I did not test to see if it
does wifiI have forgotten where I have my password
for the router so may need to reset it and choose a new PSW
Re: UUID problem using Grub4dos
Hi, Mikeslr,
I never use uuid to boot but Keef reported with similar boot code that it works.
Sheldonisaac posted this code in the post above mine. Would you mind to try the pae version the same way.
I don't think I made something wrong to the nonpae but who knows.
If I'm not wrong sdb is your second hdd. See what is your partition in Gparted. If it is hdd 1 and part 4 try this code:
Cheers, Toni
I never use uuid to boot but Keef reported with similar boot code that it works.
Sheldonisaac posted this code in the post above mine. Would you mind to try the pae version the same way.
I don't think I made something wrong to the nonpae but who knows.
If I'm not wrong sdb is your second hdd. See what is your partition in Gparted. If it is hdd 1 and part 4 try this code:
Code: Select all
title Light-Debian-Core
root (hd1,3)
kernel /live/vmlinuz boot=live config persistent quickreboot noprompt autologin
initrd /live/initrd.img
boot