DebianDog64 - 64 bit DebianDog-Jessie

[Rocket]

zagreb999:

Unetbootin and DD64 works for me using an ext2 formatted memory stick. Try the following extlinux.conf entry.

label unetbootindefault
menu label Default
kernel /live/vmlinuz1
append initrd=/live/initrd.img boot=live config toram=01-filesystem.squashfs noauto

[zagreb999]

thanks to all

i do not use windows,
and linux file system,
jus fat32
no save file

only remastered iso

I POSTED THIS TO SEE IF IT IS A BUG?

REGARDS!

[zagreb999]

regards


unetbootin_647-1~yakkety1_i386.deb

works perfectly in DD32 bit.
i hope that works also in xenialdog.

thanks.

[trister]

For 32 and 64 bit versions (fork of DebianDog) based on Debian 9 (Stretch), see here:

http://murga-linux.com/puppy/viewtopic. ... 770#959770

Fred

Hello,
I've tried your DebianDog64Stretch and have some feedback porteus boot method (perhaps I or you could start a new thread)

I know you said you will not support it but I believe that DebianDog will be a BIG part of the future of Puppy.
Note 1:
The main problem I have is that "activate" from filemanager does not work. it will just create an empty folder inside /mnt/live/memory/images/ and report that mounting was successful. If I dismount the file it will remove the empty folder and report success again.

Maybe there is a problem in the mounting script?
Note 2:
If I try mounting a changes.dat file (from the older DebianDog64 Jessie) it reports "FAILED Mounting"


Very good work

[fredx181]

For 32 and 64 bit versions (fork of DebianDog) based on Debian 9 (Stretch), see here:

http://murga-linux.com/puppy/viewtopic. ... 770#959770

Fred

Hello,
I've tried your DebianDog64Stretch and have some feedback porteus boot method (perhaps I or you could start a new thread)

I know you said you will not support it but I believe that DebianDog will be a BIG part of the future of Puppy.
Note 1:
The main problem I have is that "activate" from filemanager does not work. it will just create an empty folder inside /mnt/live/memory/images/ and report that mounting was successful. If I dismount the file it will remove the empty folder and report success again.

Maybe there is a problem in the mounting script?
Note 2:
If I try mounting a changes.dat file (from the older DebianDog64 Jessie) it reports "FAILED Mounting"


Very good work

Hi trister,

For Note 1: Very strange, I just tested that and works fine for me.
You do mean 'Activate module', (SFS-load) ?

For Note 2: didn't test that yet, but do you mean a changes.dat file created in Stretch and trying to mount in Jessie ?

There will probably come a new thread sooner or later for a Stretch Dog, Stretch has just became the new stable, so better wait a while.

Best Regards,

EDIT: Maybe I understand, after some further thoughts, not sure, you boot with "live-boot" ?
If that's the case, it's required to add to kernel boot command line:

Code: Select all

union=aufs

EDIT2: Ah, no, just see now, you wrote porteus-boot method.

Fred

[RickGT351]

What about printing? I have looked through the menus and found nothing about setting up a printer. What's the secret?

[dancytron]

What about printing? I have looked through the menus and found nothing about setting up a printer. What's the secret?

None of the printer stuff is installed. That's one of the ways that Debian Dog stays small.

So. . . set it up the way you would in any other Debian installation.

Install cups from synaptic or with apt-get. Then google for "debian jessie cups setup". Here is one to start with. Let us know if you have any trouble.

https://wiki.debian.org/SystemPrinting

https://debian-handbook.info/browse/sta ... nting.html

[trister]

Hi trister,

For Note 1: Very strange, I just tested that and works fine for me.
You do mean 'Activate module', (SFS-load) ?

For Note 2: didn't test that yet, but do you mean a changes.dat file created in Stretch and trying to mount in Jessie ?

There will probably come a new thread sooner or later for a Stretch Dog, Stretch has just became the new stable, so better wait a while.

Best Regards,

EDIT: Maybe I understand, after some further thoughts, not sure, you boot with "live-boot" ?
If that's the case, it's required to add to kernel boot command line:

Code: Select all

union=aufs

EDIT2: Ah, no, just see now, you wrote porteus-boot method.

Fred

Note 1: Yes I cannot activate any Squashfs module after boot up (PCFile man-> right click->"Activate Module"). All the squashfs files that I put inside LIVE folder load ok though.

Note 2: Yes. But from DD64Jessie I can load/open ok the changes.dat files that are created from Jessie and Stretch

I boot with porteus boot and I have tried the union-ausfs .

Could it be my current PC? I only have a 2GBram PC with an old Intel CPU.

I have some other minor issues (eg conky display appears messed up in first load- but if I toggle it problem is fixed)


My current repository for stretchdog64 with custom .squashfs files is here : https://1fichier.com/dir/hw5uWJMs
So far I have added gxkb , firefox, chromium and flash 26


(EDIT): I tried from the terminal running loadsfs myfile.squashfs
and here is the result (I don't know if this Helps)

Code: Select all

root@stretch64:/mnt/sda5/puppy_debiandog64/live# loadsfs dosbox_captive_.squashfs 
aufs             1224972      5456   1219516   1% /
dosbox_captive_.squashfs
/mnt/live/memory/images
mount: /mnt/sda5/puppy_debiandog64/live/dosbox_captive_.squashfs: failed to setup loop device: No such device or address
SUCCESS: Module 'dosbox_captive_.squashfs' activated
cp: cannot stat '/mnt/live/memory/images/dosbox_captive_.squashfs/usr/share/applications/*.desktop': No such file or directory
ls: cannot access '/.unionfs/*.desktop': No such file or directory
grep: : No such file or directory
sed: couldn't edit /.unionfs/: not a regular file

umount: /mnt/live/memory/images/dosbox_captive_.squashfs: not mounted
SUCCESS: Module 'dosbox_captive_.squashfs' deactivated

(/EDIT)[/code]

[RickGT351]

What about printing? I have looked through the menus and found nothing about setting up a printer. What's the secret?

None of the printer stuff is installed. That's one of the ways that Debian Dog stays small.

So. . . set it up the way you would in any other Debian installation.

Install cups from synaptic or with apt-get. Then google for "debian jessie cups setup". Here is one to start with. Let us know if you have any trouble.

Thanks dancytron. I got it working. My first debian install btw

[fredx181]

Note 1: Yes I cannot activate any Squashfs module after boot up (PCFile man-> right click->"Activate Module"). All the squashfs files that I put inside LIVE folder load ok though.

Note 2: Yes. But from DD64Jessie I can load/open ok the changes.dat files that are created from Jessie and Stretch

I boot with porteus boot and I have tried the union-ausfs .

Could it be my current PC? I only have a 2GBram PC with an old Intel CPU.

I have some other minor issues (eg conky display appears messed up in first load- but if I toggle it problem is fixed)

(EDIT): I tried from the terminal running loadsfs myfile.squashfs
and here is the result (I don't know if this Helps)

About note 1: It's mystery to me, tested again and works well.
The script that is called for activating (by right-click) is "loadmodule", so can you do in terminal e.g. :

Code: Select all

loadmodule -a /path/to/yourmodule.squashfs

And post the output ?
(and loadmodule -d /path/to/yourmodule.squashfs is for deactivating)
Forget about the "loadsfs" script, it's meant for something similar but not important right now.
For note 2, again very strange, just works fine for me mounting changes.dat or any squashfs or .iso.
Please post also the output of e.g.:

Code: Select all

filemnt /path/to/changes.dat

filemnt is the script that does the mounting

I have also old computer with 2GB RAM

@dancytron or anyone, can you try and see if you can reproduce the problems trister has ?

Fred

[belham2]

Hi Fred,

[ignore everything I just wrote]

...let me try something here, about ready to hit myself between the eyes for possibly confusing the partitions.....


[edit #2 update]

yes, we have liftoff NASA...all is good, Fred, both of my builds are now booting! Will post from one in a second, with a DE pic. (don't ask me what I was doing wrong...I am ashamed, lol, I swear I've been drinking from the dumb-bottle tonight)!!

[trister]

...
About note 1: It's mystery to me, tested again and works well.
The script that is called for activating (by right-click) is "loadmodule", so can you do in terminal e.g. :

Code: Select all

loadmodule -a /path/to/yourmodule.squashfs

And post the output ?
(and loadmodule -d /path/to/yourmodule.squashfs is for deactivating)
Forget about the "loadsfs" script, it's meant for something similar but not important right now.
For note 2, again very strange, just works fine for me mounting changes.dat or any squashfs or .iso.
Please post also the output of e.g.:

Code: Select all

filemnt /path/to/changes.dat

filemnt is the script that does the mounting

...

About note 1:

Code: Select all

root@stretch64:/mnt/sda5/puppy_debiandog64/live# loadmodule -a /mnt/sda5/puppy_debiandog64/live/dosbox_captive_.squashfs
squashfs
mount: /mnt/sda5/puppy_debiandog64/live/dosbox_captive_.squashfs: failed to setup loop device: No such device or address
SUCCESS: Module 'dosbox_captive_.squashfs' activated
find: '/mnt/live/memory/images/dosbox_captive_.squashfs/usr/share/icons': No such file or directory

A window opens and says mounting was successful

About note 2:
tried mounting my jessie changes.dat file

Code: Select all

root@stretch64:/mnt/sda5/puppy_debiandog64/live# filemnt /mnt/sda5/puppy_debiandog64/changes3.dat
stat: cannot stat '/mnt/sda5/puppy_StretchDog64/live/atom-amd64_1.1.12_': No such file or directory

 ### Mount: /mnt/sda5/puppy_debiandog64/changes3.dat

mount: /mnt/sda5/puppy_debiandog64/changes3.dat: failed to setup loop device: No such device or address

A RED window opens and says failed mounting.

In general no mounting work after booting up and I have been doing the same things in DD64 jessie for almost 1 year.
I do not have access to any other 64bit PC at this time to test Stretch there. Anyway DDJessie runs without any problems here.


I tried mounting the file from my ext2 USB stick (in case It was an NTFS problem -since sda1,sda5 are NTFS) but it wasn't this

During boot I see an ERROR about proc/stat and cpufreq (in case any of this is related)

(EDIT)
I tried your older StretchDog64TEST.iso (https://github.com/fredx181/StretchDog/ ... 4-TEST.iso)
and mounting WORKS!!!
So, the problem should be in something that got an upgrade.
I hope this helps.

(I also tried StretchDog32 and it also works ok)
(/EDIT)

[fredx181]

Thanks trister, your latest info can probably bring us further to a solution.

Can it be that when booting newest Stetchdog64 you have multiple (7 or more maybe?) modules loaded at boot (in live folder) and not when you tested older version ?
I'm thinking in the direction that the cause of your problem has to do with no more free loop devices available.
Not sure if it solves it but worth a try to do in terminal:

Code: Select all

for i in {8..63}; do if [ -e /dev/loop$i ]; then continue; fi; \
mknod /dev/loop$i b 7 $i; chown --reference=/dev/loop0 /dev/loop$i; \
chmod --reference=/dev/loop0 /dev/loop$i; done

It should give 63 loop devices in /dev.
And try if mounting or activating works then.
Don't think this will survive a reboot, but anyway we can know more about the cause if this works.

P.S. One thing I don't understand from one of your output:

Code: Select all

root@stretch64:/mnt/sda5/puppy_debiandog64/live# filemnt /mnt/sda5/puppy_debiandog64/changes3.dat
stat: cannot stat '/mnt/sda5/puppy_StretchDog64/live/atom-amd64_1.1.12_': No such file or directory

Any idea where does the "puppy_StretchDog64/live/atom-amd64_1.1.12" come from ?

Fred

[trister]

Thanks trister, your latest info can probably bring us further to a solution.

Can it be that when booting newest Stetchdog64 you have multiple (7 or more maybe?) modules loaded at boot (in live folder) and not when you tested older version ?
I'm thinking in the direction that the cause of your problem has to do with no more free loop devices available.
Not sure if it solves it but worth a try to do in terminal:

Code: Select all

for i in {8..63}; do if [ -e /dev/loop$i ]; then continue; fi; \
mknod /dev/loop$i b 7 $i; chown --reference=/dev/loop0 /dev/loop$i; \
chmod --reference=/dev/loop0 /dev/loop$i; done

It should give 63 loop devices in /dev.
And try if mounting or activating works then.
Don't think this will survive a reboot, but anyway we can know more about the cause if this works.

P.S. One thing I don't understand from one of your output:

Code: Select all

root@stretch64:/mnt/sda5/puppy_debiandog64/live# filemnt /mnt/sda5/puppy_debiandog64/changes3.dat
stat: cannot stat '/mnt/sda5/puppy_StretchDog64/live/atom-amd64_1.1.12_': No such file or directory

Any idea where does the "puppy_StretchDog64/live/atom-amd64_1.1.12" come from ?

Fred

---
I don't think it is cause of multiple squashfs in live folder.
I always keep a "vanilla" frugal install folder which contains only 01-filesystem.squashfs.
Even the "vanilla" version can't mount anything after bootup.

I have already tested both of your github ISOs v01 and v02. Older v01 mounts normal but v02 has the same problems.
In this pastebin you can see the squashfs I have in both v01 and v02. They are identical but onl;y v01 mounts after boot : https://pastebin.com/NquRw1aG

Just for information this is an example of My current debiandog64 JESSIE live folder : https://pastebin.com/8pPK24ub

---

I have runned your script.
After running doing ls -l in the /dev folder I have this : https://pastebin.com/gA3kHHVA
Before running it I had this : https://pastebin.com/FdFLRQTi

Still mounting does not work

----
atom-amd64_1.1.12.squashfs is a squashfs file that I was using (and was working ok in DebianStretch64 v02 -from live folder) I don't know why it showed as an error so I have removed it -just-in-case.

---------------

I think the error is created in
script loadmodule in line 163
mount -o loop $BUNDLE $CHNGS/$BUNDLE
this line produces the error " failed to setup loop device: No such device or address".
Somehow during upgrade something messed this up ( I tried downgrading versions by installing mount_2.26.2-6_amd64.deb , sfsload_1.0.1_all.deb , portablesfs-loadsfs-fuse_1.0.4_all.deb but nothing changed)

[trister]

I did a modification to loadmodule and it worked (kind of)

I replaced line 162 :

Code: Select all

mount -o loop $BUNDLE $CHNGS/$BUNDLE

(which produced the error "failed to setup loop device: No such device or address")

With this :

Code: Select all

  losetup /dev/loop62 $BUNDLE
  mount /dev/loop62 $CHNGS/$BUNDLE

=I did the mount static to loop62 and it worked (for 1 file at least)

I don't know what that means and how to fix this but it might mean something to you.

My whole loadmodule is here : https://pastebin.com/c6tEtpHm

[fredx181]

Hi trister,

I still think it has to do with limited amount of (free) loop devices, and need to be set with the right permissions.
Can you try booting with the initrd1.xz from here (I modified the init script inside):
https://fredx181.github.io/StretchDog/a ... ges/Fixes/

Good chance it will work because of creating 64 loop devices (with the right permissions) at early (init) stage. I tested successfully mounting 15 .squashfs files (didn't go up to 64, but should be possible in theory, I think).
EDIT: Forgot to mention, with the default included initrd1.xz, I was only able to mount 7 squashfs's, the 8th gave an error.

Fred

[trister]

Hi trister,

I still think it has to do with limited amount of (free) loop devices, and need to be set with the right permissions.
Can you try booting with the initrd1.xz from here (I modified the init script inside):
https://fredx181.github.io/StretchDog/a ... ges/Fixes/

Good chance it will work because of creating 64 loop devices (with the right permissions) at early (init) stage. I tested successfully mounting 15 .squashfs files (didn't go up to 64, but should be possible in theory, I think).
EDIT: Forgot to mention, with the default included initrd1.xz, I was only able to mount 7 squashfs's, the 8th gave an error.

Fred

ok I will try this.
If you checked https://pastebin.com/NquRw1aG in your previous v01 release of DD I had mounted during bootup (from live folder) about 40 squashfs without problems. In Jessie I have even more loaded at bootup.
_______--
(..deleted..)
_____
(EDIT)I tried it and mounting WORKED!!! Thanks for your time. I'll do some more tests with more squashfs and I will report feedback here (/EDIT)
(edit2)
I manually activated from PCfileman 20squashfs and I reached 53 mounted squashfs files in total. I can mount changes.dat files with any problems with the new initrd1
(/edit2)

Thanks for your quick fixes

[fredx181]

Ha ! Great !
Can't explain why you had no such problems on Jessie and why newest Stretch needs this workaround, but ok, it works as it should now, I guess.

Before you edited, I read that you wonder about what's the limit of loop devices.
I read somewhere that the limit is 256, so I just remade and uploaded new initrd1.xz (replaced here: https://fredx181.github.io/StretchDog/a ... ges/Fixes/ ) creating 255 loop devices (/dev gets very full this way).
Hope that's enough? (don't know if loop-mounting all is really possible,btw)

Fred

[trister]

Ha ! Great !
Can't explain why you had no such problems on Jessie and why newest Stretch needs this workaround, but ok, it works as it should now, I guess.

Before you edited, I read that you wonder about what's the limit of loop devices.
I read somewhere that the limit is 256, so I just remade and uploaded new initrd1.xz (replaced here: https://fredx181.github.io/StretchDog/a ... ges/Fixes/ ) creating 255 loop devices (/dev gets very full this way).
Hope that's enough? (don't know if loop-mounting all is really possible,btw)

Fred

Ok Thanks.

I am using now the latest initrd1.xz with the 255 loop devices. It works ok - I have reached 60 mounted files.

[trister]

So far testing for StretchDog64-2017-07-04 with the new initrd1.gz goes ok.
I have begun my transition from DD64 Jessie to DD64Stretch and making/re-creating squashfs files.

I have some minor issues (like conky transparency) but they are not that important.

Do you have anywhere the locale files?

I think I'm posting too much in the JessieDog Thread about StretchDog...