DebianDog - Wheezy

[saintless]

please give me the list

I already copied the above list from a different forum to my system

please give me the jessie list

Thanks a lot.

You still have the original Jessie repository list in 01-filesystem.squashfs.

/etc/apt/sources.list for DebianDog-Wheezy:

Code: Select all

#DebianDog repository:
deb http://www.smokey01.com/saintless/DebianDog/Packages/ ./ 

deb http://ftp.us.debian.org/debian wheezy main contrib non-free
#deb-src http://ftp.us.debian.org/debian wheezy main contrib non-free

deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
#deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib non-free

deb http://security.debian.org/ wheezy/updates main contrib non-free
#deb-src http://security.debian.org/ wheezy/updates main contrib non-free

#Debian Multimedia
deb ftp://ftp.deb-multimedia.org wheezy main non-free

#Default-Original-Sources:
#deb http://http.debian.net/debian/ wheezy main
#deb-src http://http.debian.net/debian/ wheezy main
#deb http://security.debian.org/ wheezy/updates main
#deb-src http://security.debian.org/ wheezy/updates main
#deb http://http.debian.net/debian/ wheezy-updates main
#deb-src http://http.debian.net/debian/ wheezy-updates main

/etc/apt/sources.list for DebianDog-Jessie:

Code: Select all

deb http://kazzascorner.com.au/saintless/DebianDog/DebianDog-Jessie/Packages/ ./ 

deb http://ftp.de.debian.org/debian jessie main contrib non-free
#deb-src http://ftp.de.debian.org/debian jessie main contrib non-free
#deb http://ftp.de.debian.org/debian jessie-backports main
deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free


#Debian Multimedia
deb ftp://ftp.deb-multimedia.org jessie main non-free

# US mirrors:
#deb http://ftp.us.debian.org/debian jessie main contrib non-free
#deb-src http://ftp.us.debian.org/debian jessie main contrib non-free
#deb http://ftp.us.debian.org/debian jessie-backports main

Toni

[way12go]

Done. Thanks

[fredx181]

Hi William,

Fred,

I set up a copy of your DebianDog-openbox wheezy for a friend but noticed that gmail was complaining that the Firefox provided was too old. So on FIrefox Help-About notice I pressed the Update button and that seemed to work since then had Firefox 38.0.5, which seemed fine. However, I later discovered that Firefox 38.0.5 crashed everytime I visited Youtube page... There seems to be similar reports on the Internet though no fix that I've noticed. I consequently used apt-get to install iceweasel instead, since that works fine on Youtube. Is there some particular reason why you prefer FIrefox to using Debian provided iceweazel Fred?

By the way, I don't know if that Firefox crash issue is a general problem since as yet I've only tested it on one computer (where the crash always occurs as soon as Youtube page visited). Googling brought up a couple of posts which suggested the crash only occurred on Intel graphics based systems - but I haven't tested further as yet.

William

I could reproduce the crashing of Firefox 38.0.5, but only when flashplayer is installed.
If not, then HTML5 is used on YouTube, and works for me without problems.
I'm not sure, the crashing problem seems to be a combination of upgrading and flash.
BTW, When I completely removed the contents of the 'profile' directory /opt/bin/Firefox/profile I had no crashes anymore.

Is there some particular reason why you prefer FIrefox to using Debian provided iceweazel Fred?

Not really anymore except that new Iceweasel takes up much more space than the somewhat older included firefox 27.0 (to keep the iso size smaller).
Initially I choose for Firefox because it's more well known and the easy upgrading to latest version.

Fred

[way12go]

You can install flash using pipelight, the windows version flash plugin in linux

http://pipelight.net/cms/install/instal ... ebian.html

[mcewanw]

Hi Toni and Fred!

I have discovered that DebianDog (all versions as far as I know) is not booting directly from laptop dedicated SD card slot as it stands. I need this facility because I have a laptop which has no harddrive. Of course, it is well known that if an SD card is plugged into a usb card reader it can be used as a normal usb flash stick for booting the system (assuming your system BIOS allows booting from usb). However, I don't want to use up a precious usb port through booting from usb flash stick. Also, it is nice to boot from SD slot since SD card doesn't stick out and thus in less danger of being accidentally knocked out. Anyway, I've found what the problem is and how to fix it so that DebianDog can be booted from dedicated SD slot:

Nowadays, many laptops provide such a dedicated SD card slot, which is often connected internally directly to the pci bus rather than to usb host controller (which is the problem...). The BIOS of some laptops (e.g. an HP elitebook I have) are able to boot from that pci-connected SD slot, but I have discovered that, as it stands DebianDog initrd (neither jwm or openbox versions I believe) doesn't load the required sdhci-pci module (even though the module itself is included in the initrd...). If, however, DebianDog is booted from say a hard drive or a normal usb flash stick, the SD card when plugged into its dedicated SD slot on the laptop does correctly appear as /dev/mmcblk0p1.

Here is how I managed to boot DebianDog from this SD card in the SD slot (after the following outlined changes). In these tests I was using DebianDog-openbox-wheezy with kernel version 3.16.0...:

1. First I have to install the bootable system onto the SD card. I thus tried plugging the SD card into the laptops dedicated SD slot and started DebianDog-installer (debdog-install). However the /dev/mmcblk0p1 was not detected by debdog-install (though it is detected ok as a desktop icon).

The FIX for that is: in /opt/bin/drive-info, change line 9 from:

Code: Select all

Parts=`cat /proc/partitions |sed '/sd/!d;s,^.* ,,'`

to:

Parts=`cat /proc/partitions |sed '/sd\|mmc/!d;s,^.* ,,'`

Then the mmc device will also be detected.

The alternative to actually thus fixing the drive-info script is to temporarily put the SD card into a usb card reader, allowing it to be detected as a usb flash stick (/dev/sd...) which debdog-install recognises without that otherwise necessary modification to the drive-info script.

I then used debdog-install to complete the DebianDog-openbox-wheezy installation to the SD card, putting grub4dos into the SD card Master Boot Record.

2. I then tried booting this DebianDog installed SD card from my HP elitebook dedicated SD card slot. On this boot attempt, it indeed found grub4dos and grldr and thus menu.lst, but then, though it did find and booted vmlinuz and initrd1, it refused to complete the boot process, though did allow me to drop down to a console whilst telling me to check the cheatcodes. Oops, what was the problem I wondered since I at least had now confirmed that the BIOS supported SD booting from the dedicated card slot and could find grub and loaded vmlinuz and initrd fine...?

The FIX is that the linuxrc script in initrc1.xz (once expanded and checked) did not have code to load the module sdhci-pci.ko (even though that module was in fact already included in initrd1). I therefore added that module in the loading code at line 146 of that linuxrc script (original being by porteus guy fanthom) immediately after existing load module sdhci as in linuxrc code extract below:

Code: Select all

for MODULE in mbcache aufs exportfs ext4 fat ... sdhci sdhci-pci sdhci-acpi...; do
      modprobe $MODULE 2>/dev/null
done

I didn't actually include above sdhci-acpi in my successful test, though I imagine that will be useful too.

Note that I have also checked initrc1.img and initrc2.img and the sdhci-pci module is not being loaded in them either, so the same fix would be required to boot directly from SD for debiandog-jwm version too in above important SD slot booting scenario.

Okay, the good news is that using these changes I am now able to boot DD openbox wheezy from the SD card in its dedicated slot. However, there is one remaining annoying issue, which I expect Fred will know the solution for (I don't know where to look for the solution myself): 

 [b]After booting from the SD card, I can't read the partition itself[/b] (via, for example, clicking on /mnt/home) and I note that both /lib/live/mount/medium and also /live/image are empty, which might be a clue since these are referred to in script /opt/bin/remount-rw. I do remember this kind of situation being fixed before, but I can't remember how - something to do with remounting the card rw I think. The system thus booted from SD slot otherwise seems to work fine. [b]Any ideas on how to fix this remaining issue?[/b]

Finally, I realise Toni doesn't want to modify initrd1.img or initrd2.img since they are pretty much pure Debian as is. (I expect therefore that official Debian live itself cannot thus boot from SD slots either...). However, I hope Fred could make these small fixed in the porteus boot initrd1.xz files to thus allow booting from SD card slot. :-)

William

NOTE: For machines whose BIOS cannot read directly from the SD card slot, a workaround is to put grub4dos onto the MBR of a device that can be booted from (e.g. a harddrive or usb stick) and have the menu.lst thereafter pointing to uuid of the otherwise bootable SD card. But that isn't very useful if your machine doesn't have a harddrive and you don't want to waste a usb slot, which I don't... And for machines which are incapable of even booting from usb sticks, a workaround for that issue is to use something like plop in the mbr of a harddrive (or cdrom), but that alone still does not fix the pci-connected SD slot booting issue, which does require the suggested modification to initrd linuxrc (and the modification to drive-info such that debdog-install will work with SD reader slot).

[mcewanw]

Per my above post, I still haven't found why /mnt/home doesn't point to the partition when booting from SD card slot. However, I have found a couple of other scripts that need fixed to account for SD cards:

Like my change to /opt/bin/drive-info, /opt/bin/lspart, line 9 should include mmc as follows (I've tested this):

Code: Select all

blkid |egrep '(ext[2-4]|fat|ntfs)' |sed '/sd\|mmc/!d;s,^.*/,,;s," $,,;s,:.*", ,'

and /opt/bin/mnt-all line 10 should include mmc as follows (I've not tested this cos I don't know where this script is used or for what):

Code: Select all

INFO=`blkid |egrep '(ext|fat|ntfs)' |sed '/sd\|mmc/!d;s,^.*/,,;s," $,,;s,:.*", ,'`

[saintless]

Hi, William.
Thanks for investigating and sharing this solution for SD card boot!
The only initrd I like to keep untouched in Wheezy and Jessie is initrd.img for live-boot-3 (created with update-initramfs command).
We have some modifications in live-boot-2 initrd1.img like remounting the boot partition in rw mode and adding .wh. support inside /scripts/live
I'm sure Fred will be happy to improve porteus-boot initrd1.xz

But still I think every change in initrd files should be tested well before we accept it as official replacement inside the iso. Maybe uploading testing initrd1.img-sdcard and initrd1.xz-sdcard for one kernel of your choice is the way to go for now. If you have them ready I will upload them on the site for testing.

Unfortunately the only way I can test sd card boot is from my camera plugged in usb slot (if it works and this makes the test unusable).

About the scripts drive-info, lspart, mnt-all (it is Terry's script for mounting/unmounting all available devices with menu entry in Jwm version) - if it is possible it is better to create one deb package with all scripts without changes and upload it. Then we can make higher version deb with the same scripts modded as you suggest. It will be easy to upgrade and downgrade to previous version if we find problems later. Again it should be well tested before we accept official replacement inside the iso. Sometimes small change (considered as safe) could lead to troubles we don't want to get.

Toni

[fredx181]

Hi William,

Thanks from me also for investigating SD card boot.
These days I have little time to look at it and at the moment I don't have SD card to test (and I'm not sure if my SD slot works) but here some hints to make possibly work creating correct symlink to /mnt/home:
In linuxrc on line 198:

Code: Select all

echo  $PTH > /etc/homedrv

creates file in the booted system '/mnt/live/etc/homedrv' with the path 'where booted from'
The script (started from /etc/rc.local) /usr/local/bin//mountlink creates the required link to /mnt/home reading '/mnt/live/etc/homedrv' (and more)
In case you're wondering, there's on Openbox version also /usr/local/bin/mountlink-new, meant as improvement but not fully tested yet.

I'd be happy to update initrd1.xz with the addition of sdhci sdhci-pci sdhci-acpi later and we will probably modify scripts such as drive-info and lspart and create .deb from it as Toni suggested after more testing.

Edit:

After booting from the SD card, I can't read the partition itself (via, for example, clicking on /mnt/home)

You can't read the partition itself at all? (besides /mnt/home symlink)

Edit2:
Reading your post better:

the SD card when plugged into its dedicated SD slot on the laptop does correctly appear as /dev/mmcblk0p1

Just a guess: the fact that the device name contains more than 3 characters could cause it.
The way mountlink script parses it expects e.g. sda or sdb


Fred

[mcewanw]

Hi Toni and Fred,

Thanks for the suggestions towards getting /mnt/home to show the SD card partitions contents. I'll take a look at the details and see if I can then fix the issue.

Once I have it all polished, I'll upload the initrd1.xz I'm working on to my gdrive, Toni, along with my suggested SDcard-related alterations to Terry's scripts. Shouldn't be too long because I am installing this on another similar laptop of a friend, which also doesn't have a harddrive and only two available usb ports plus the SD card slot, so we want to boot from that SD slot.

Yes, it will all need thorough testing, so my friend's machine and mine will help in that, though the simple additional loading of sdhci-pci and sdhci-acpi is hopefully unlikely to cause any issues I feel. The alterations to Terry's scripts might be another matter, since I doubt I'll have time to completely work out the complete details of what these scripts do - fortunately the mmc alteration there is minimal.

Okay, back to the /mnt/home SD boot issue, any fix to which will definitely need well tested.

William

[mcewanw]

Just a guess: the fact that the device name contains more than 3 characters could cause it.
The way mountlink script parses it expects e.g. sda or sdb


Fred

Yes, that's exactly what is causing the issue. Temporarily changing cut -c6-9 throughout /usr/local/bin/mountlink script to cut -c6-14 gets rid of the problem (but wouldn't work for sd case of course!). After that /mnt/home correctly reveals contents of the partition used for booting.

It is always risky to rely on cut (range of chars) for parsing, but will probably be an easy proper fix just to parse out the required second field of the string being parsed (using cut <field>, awk, sed, or whatever) based on the field delimiter used, which is '/'. I'll experiment with a few alternative universal 'solutions' and report back later.

Cheers, William

[mcewanw]

Fred,

I think, instead of cut -c6-9, in mountlink script, simply piping to:

Code: Select all

cut -d'/' -f3 | cut -d' ' -f1

The '/' as field delimiter to cut identifies the start of the required partition name and the ' ' (single space) as delimiter identifies the end of that name.

What do you think? Maybe you can suggest a simpler or more foolproof way?

William

EDIT: Sorry, I mean a combination of such uses of cut. For example:

hdrv=$(cat /mnt/live/etc/homedrv | cut -d'/' -f3)
BACKDRVEXIT="$(df -h | grep -P '/mnt/live/memory/images/changes-exit' | cut -d'/' -f3 | cut -d' ' -f1)"
and something the same or similar for BACKDRVCH (line 16 of mountlink).

That cut -d -f scheme will also work should you be using more sdx type partitions than 9, which cut -c6-9 wouldn't.

[mcewanw]

Hi Fred, Toni,

The current method of using cut -c6-9 is proving a bit of a headache, since that will not work with partitions > 9 nor with mmc SD devices. It is used in some other scripts, such as /opt/bin/mnt-backing and /opt/bin/mount-wizard and probably other scripts I don't know about.

I don't know the appropriate cut -d -f alternative should be for mnt-backing, since the way my openbox_wheezy_porteus_boots doesn't give any result for its, for example, line 5 code (there is no live-rw in my df -h output at commandline):

Code: Select all

df -h | grep -P '(?=.*live-rw)(?=.*backing)' 2> /dev/null | cut -c6-9

However, I do expect that in all scripts using df -h like the above, replacing

Code: Select all

| cut -c6-9 

with :

| cut -d'/' -f3 | cut -d' ' -f1

may be correct.

More definitely, however, I do believe that for the /opt/bin/mount-wizard script the cut -c6-9 lines should be changed, like the similar lines in /usr/local/bin/mountlink script, as follows:

Code: Select all

from: HDRV=`cat /mnt/live/etc/homedrv | cut -c6-9`
to: HDRV=`cat /mnt/live/etc/homedrv | cut -d'/' -f3

from: BACKDRVEXIT="$(df -h | grep -P '/mnt/live/memory/images/changes-exit' | cut -c6-9)"
to: BACKDRVEXIT="$(df -h | grep -P '/mnt/live/memory/images/changes-exit' | cut -d'/' -f3 | cut -d' ' -f1)"

and probably also:

from: BACKDRVCH="$(df -h | grep -P '/mnt/live/memory/changes' | cut -c6-9)"
to: BACKDRVCH="$(df -h | grep -P '/mnt/live/memory/changes' | cut -d'/' -f3 | cut -d' ' -f1)"

[mcewanw]

NOTE WELL: The following are only concerned with special case uses of DebianDog - users using very large numbers of partitions (9 or more) or booting from SD in dedicated SD slot. Other than these special use cases DebianDog works well as it is.

The attached files are only uploaded for testing purposes. They may or may not work so are intended only for testing by Toni or Fred. I'll be doing furthing testing of these too, but I don't know where and how some of these scripts are actually used by the system - I just recognise they have a problem. I made the suggested changes quickly, so I may also have made errors though hopefully not...

They address the cut -c6-9 issue I discuss in above posts, and additionally address the possibility of an pci-bus-slot SD card being booted from (sd\|mmc) rather than a usb flash stick.

The cut -c6-9 issue is a problem with sd partitions too, as far as I see it, since that stanza won't work for partitions >9. Note that I've only really tested mountlink and lspart thus far, and drive-info to a certain extent. The other suggested mods are based on these other tests, but need additional thorough evaluation. Also, there may well be other scripts that would require similar fixes to remove the cut -c6-9 limitation, but I don't know which scripts, if any more.

As far as the SD booting fixes, I have still to upload the modified initrd that provides for that possibility. EDIT: Note also, that these are only attempted partial 'fixes' - there is definitely more work needing done on debdog-install and drive-info to make these work on SD booted system. Main thing for me is to get them altered to the extent that debdog-install will work in this scenario (as I said, current debdog-install works fine aside from with this relatively rare SD boot scenario so the priority of that fix is low.

EDIT2: Fredx181 has since posted further updated versions of mountlink and mount-wizard, which should also be used for SD.

William

[saintless]

Thanks, William!

mount-wizard and mnt-backing give error "invalid option -d" compared to the included in the iso scripts:
New:

Code: Select all

root@debian:/new# ./mnt-backing
cat: invalid option -- 'd'
Try `cat --help' for more information.
cat: invalid option -- 'd'
Try `cat --help' for more information.
mount: /dev is not a block device

root@debian:/new# ./mount-wizard
cat: invalid option -- 'd'
Try `cat --help' for more information.

Included in the iso:

Code: Select all

root@debian:~# mount-wizard
root@debian:~# mnt-backing
mount: /dev/sda1 already mounted or /media/sda1 busy
mount: according to mtab, /dev/sda1 is already mounted on /media/sda1

Toni

[saintless]

Grub4DosConfig from Shinobar available for download in dd-wheezy and dd-jessie repository after running apt-get update first:

Code: Select all

apt-get update
apt-get install grub4dosconfig

More information read here.

Toni

[mcewanw]

Thanks, William!

mount-wizard and mnt-backing give error "invalid option -d" compared to the included in the iso scripts:

Toni

Yes, lots of problems trying to modify these scripts. These were just quick mods but alas needs lots of work on them as I now realise. I'll aim for a compromise mod to the scripts which works as before outside SD boot environment but works to a large extent after SD booting albeit not perfect for now (too hard..!).

William

EDIT: Mind you, me typing cat instead of cut here and there didn't help.

[mcewanw]

Thanks, William!

mount-wizard and mnt-backing give error "invalid option -d" compared to the included in the iso scripts:

Toni

I've re-uploaded these scripts to my previous upload post above with some fixes. Also added # mcewanw at the end of the lines I altered from the original. And have also uploaded there a modified version of debdog-install which I am about to test with an SD booted system. Debdog-install wouldn't work with SD install previously - it didn't give the SD mmcblk0p1 device as a partition option (needed change in drive-info to bring that up) and there were other alterations needed in debdog-install itself to deal with the different naming used for mmc devices. But like I say, I have still to see if it will work - I'd be astounded if it did at this stage because the code was a bit tricky - especially concerning setting the boot flag. Oh well, I'll see how it goes, if at all, now..

EDIT: you can find my new restructured debdog-install for testing here:

http://www.murga-linux.com/puppy/viewto ... 055#851055.

Cheers, William

[fredx181]

Thanks William,

cut -d'/' -f3 | cut -d' ' -f1

The '/' as field delimiter to cut identifies the start of the required partition name and the ' ' (single space) as delimiter identifies the end of that name.

What do you think? Maybe you can suggest a simpler or more foolproof way?

I think it's perfect way and I regret not having searched for something like that in the first place. You've found a lot of bugs at the same time

Quck tested your mountlink and mount-wizard and found no problems, will do some more testing in the next days.

And have also uploaded there a modified version of debdog-install which I am about to test with an SD booted system.

I can't see debdog-install itself in one of your posts.

Thanks again, good improvements!

Fred

[saintless]

Thanks, William!

No problems from quick testing the new scripts in terminal. I will test them more in the next days.

Toni

[bmark109]

Thanks for the good news hope it works out.
Being able to install grub4dos bootloader without reinstalling puppy is ideal.

Can you, please, test this properly when you have time? I think it works well but I don't have much experience with grub4dos. If it works well I will make separate deb packages for DebianDog from the included scripts and needed dependencies and upload them in dd-repository.

This is only testing sfs module (download with right click -> Save link as):
Module removed. Use apt-get or synaptic to install grub4dosconfig.

Edit: testing deb package uploaded:
The script searches only Puppy linux files. It is not changed to search for DebianDog files. We have DebianDog-frugal and full installers instead. You will have to edit the menu.list for DebianDog after installing grub4dos with grub4dosconfig.

Code: Select all

apt-get update
apt-get install grub4dosconfig

Edit2: Reminder to myself mostly - the deb packge has official dc as dependency instead dc link to /bin/busybox, but grub4dosconfig script doesn't work well with official dc from Debian. I will have to restore dc link to busybox (as in the squashfs module) or change the dc lines in the script to give correct partition size information using official dc package.

Edit3: OK, the dc version problem solved by using /opt/bin/special/dc link to /bin/busybox inside the script. Added gsu lines. I forgot to change defaulthtmlviewer to default_web-browser. I will do it later updating the repository for Wheezy and Jessie. guess_fstype script is uploaded as separate deb package. It is better to keep it separated in case other scripts from Puppy need guess_fstype as dependency (as we did with probepart deb). Seems the script works well in DebianDog now.

Edit4: All done now. I will not update the deb package anymore (unless someone finds something for fixing later). The testing module is removed. Anyone interested, please, use apt-get or synaptic to install and test grub4dosconfig.

Toni

Hi Toni
Tested on live,frugal and full install .
Works as stated, install can not find Debiandog must edit menu.lst
Thanks for your work happy to have grub4dos working