Create Debian 9 (Stretch) minimal ISO similar to DebianDog

[fredx181]

@zagreb999

BUT I CAN NOT CREATE GCONF-EDITOR...

Why not ?

@backi
The easiest is if you create vlc.squashfs with apt2sfs or repo2sfs, that just before actually creating the squashfs with mksquashfs you open terminal in the "vlc" directory (which was just created) and then:

Code: Select all

sed -i 's/geteuid/getppid/' usr/bin/vlc

And after that let it finish by creating vlc.squashfs
Note that the above is without "/" in front of usr

Fred

[backi]

Hi Zagreb !
5 Minutes ago........( iam posting from Bionic Dog )
i ran AptToSfs -----typed in gconf-editor
Choosed sda9 on my Drive to save it ----choosed gzip compression ....
and voila ....gconf-editor.squashfs was created .
Right-click menu in Pcmanfm> on gconf-editor.squashfs i activated it .
Found it in /usr/share/applications ----gconf-editor.desktop ------now running.
It is also in >Menu>System>Configuration-Editor .
But dont know if it will do in Debian Dog .

Regards !


Thanks Fred!!

[zagreb999]

backi,
is your gconf-edit
as in image?

[backi]

Hi Zagreb !
it looks a bit different but quite similar ....I have E17 Enlightenment Desktop ....no nautilus .
Don`t know what gconf-edit does .

So you managed to create gconf-edit.squashfs Module ???

[zagreb999]

yes, backi,
I MADE ALSO ,
BUT THERE IS NOTHING INSIDE...

YOU CAN MADE
gconf-edit.squashfs
BUT THERE IS NOTHING INSIDE

CAN YOU MAKE REAL APP AS IN IMAGE?
CAN YOU POST YOUR squashfs MODULE?
THANK YOU....

[backi]

So it looks in my Case :

[backi]

A Question Zagreb .....how can i upload a downloadable image/file like you did ....instead of showing it in the post directly as i did ?

[dancytron]

Bug Report:

Okay, it started when I did my occasional upgrade. Synaptic showed precord being updateable, but it wouldn't update. After trying to reinstall it and a few other things, I did a "Complete Uninstall" with the intention of installing it again.

When I tried to reinstall it, I got:

"precord:
Depends: gtkwialog but it is not installable"

Not a big issue for me, since I don't think I've ever used precord (and I don't even have a microphone or webcam on my computer), but this might need fixing for others. Also, if gtkwialog is a dependency for other things, that might need to be looked at.

[darry19662018]

@Dancytron

You can download gtkwialog and it will work, I use it in Racy.
http://murga-linux.com/puppy/viewtopic. ... &id=116774

[dancytron]

@Dancytron

You can download gtkwialog and it will work, I use it in Racy.
http://murga-linux.com/puppy/viewtopic. ... &id=116774

Thanks.

LIke I said, I don't actually use it but someone else might need it.

I mainly wanted to let Fred know he has programs in his repo that don't have their dependencies for whatever reason.

[wiak]

@Dancytron

You can download gtkwialog and it will work, I use it in Racy.
http://murga-linux.com/puppy/viewtopic. ... &id=116774

Thanks.

LIke I said, I don't actually use it but someone else might need it.

I mainly wanted to let Fred know he has programs in his repo that don't have their dependencies for whatever reason.

I suggest just removing Precord from the repo for the moment Fred, or put the previous version up there. If anyone wants the dash-compatible 0.9.5 version they can download it themselves from its Puppy forum thread. As you know I only previously put up a test-only binary version of gtkwialog, so those interested could help me test/debug it, and that was not to be used as any published release. The fact that remains available on initial development thread is outside of my control or I would be deleting it pending the being-worked-on version being released for distribution later.

I take the view that there is no urgency in getting gtkwialog finished but it certainly will be released in binary along with the sources in the not too distant future and I will continue to ensure 100% compatibility with legacy gtkdialog as well as earlier testing-only (so that our conversion of pfind, and also that of Precord and cast2chrome will continue to work without further changes).

wiak

Sorry for any inconvenience.

[fredx181]

@dancytron

I mainly wanted to let Fred know he has programs in his repo that don't have their dependencies for whatever reason.

Thanks, I made mistake by putting the i386 gtkwialog deb in the amd64 repo, fixed now.

@wiak, just I read your message, as you can see above it's fixed now, still you are sure to remove gtkwialog based Precord ?.
Also, anything else you'd like me to do ?, there's cast2chrome-gtkwialog and gtkwialog itself in the most recent repos.
I'd say just keep these, but if you want otherwise, just tell me and I'll do.

Fred

[wiak]

@wiak, just I read your message, as you can see above it's fixed now, still you are sure to remove gtkwialog based Precord ?.
Also, anything else you'd like me to do ?, there's cast2chrome-gtkwialog and gtkwialog itself in the most recent repos.
I'd say just keep these, but if you want otherwise, just tell me and I'll do.

Fred

Don't go to any trouble Fred; just do whatever best suits yourself. In practice makes no difference whatever you choose to do in the sense that I can't remove the test binaries anyway since they are in the locked thread. The final gtkwialog will work the same so will also be fine with these programs Precord 0.9.5 and latest cast2chrome.

I guess it needs further testing in other ways anyway - though we both know it is perfectly stable as used so far and I'm not surprised about that.

I'll get back onto the official publishing of all the code later, though you might imagine I need a break following all the goings on. I am working on extra bits during these quiet times still though.

wiak

[Galbi]

I've been fighting with this the last days and, no way I can't boot any Stretch Dog64 in this machine.

I always reach the screen attached.

FatDog64 and LxPupSC64, both boot fine and ran very well.
BionicDog64, boots after doing a countdown from 6 saying it can't find something, but the Stretchs64 no.

Here is the bootloader

Code: Select all

title Stretch-Dog 32
  root (hd0,0) 
  kernel /stretch/live/vmlinuz1 noauto from=/stretch changes=/stretch/live/ 
  initrd /stretch/live/initrd1.xz
  
title Stretch Dog 64
  root (hd0,0)
  kernel /stretch64/live/vmlinuz1 noauto from=/stretch64 changes=/stretch64/live/ 
  initrd /stretch64/live/initrd1.xz

Same HD, same partition, just different folders and 32bit boots and 64bit no.

Any idea?

[dancytron]

Do you have the stretch-x86_64.sgn file in your .../live directory?

[Galbi]

Do you have the stretch-x86_64.sgn file in your .../live directory?

Yes, was the first I looked at, and also the stretch-i486.sgn.

[fredx181]

I've been fighting with this the last days and, no way I can't boot any Stretch Dog64 in this machine.
....
....
Any idea?

Not really, can you test if "live-boot" method works ?

Code: Select all

title Stretch Dog 64 live-boot
  root (hd0,0)
  kernel /stretch64/live/vmlinuz1 boot=live live-media-path=/stretch64/live/ union=aufs
  initrd /stretch64/live/initrd.img

Fred

[Galbi]

Not really, can you test if "live-boot" method works ?

Yes it does, quick and fine.

Can I have persistence?

Thanks.

[fredx181]

Not really, can you test if "live-boot" method works ?

Yes it does, quick and fine.

Can I have persistence?

Yes, it can, but only save-file and it's a bit more complicated (see below).
But can you please first test for me a modified initrd1.xz (perhaps porteus-boot works with this for you):
https://fredx181.github.io/StretchDog/a ... initrd1.xz
(just replace in the "live" directory)
For kernel 4.0.9-6

Ok, persistence with live-boot:
- Download zipped persistence 1GB here:
http://www.smokey01.com/saintless/1Gb-p ... ive-rw.zip
- Extract at the root of the same partition where your stretch64 folder is located.
(it will be found only if it's at the root of the partition)
- Menu.lst entry:

Code: Select all

title Stretch Dog 64 live-boot with persistence
  root (hd0,0)
  kernel /stretch64/live/vmlinuz1 boot=live persistence live-media-path=/stretch64/live/ union=aufs
  initrd /stretch64/live/initrd.img

Note: Don't know which build you did, if it contains 2 modules, e.g. 01-filesystem.squashfs and zz_openbox_lx-jwm_firefox.squashfs, then the alpha numerical order needs to be reversed, so rename e.g. zz_openbox_lx-jwm_firefox.squashfs to 00_openbox_lx-jwm_firefox.squashfs
I know this is a bit weird, but it's the only way I could make it work properly with persistence.
The official "live-boot" way would be to place a "filesystem.module" file in the "live" directory with inside the module names that define the order of loading, but somehow that doesn't work for me.
Well.. now I remember again why I prefer the porteus boot method

Fred

[Galbi]

But can you please first test for me a modified initrd1.xz (perhaps porteus-boot works with this for you):
https://fredx181.github.io/StretchDog/a ... initrd1.xz
(just replace in the "live" directory)
For kernel 4.0.9-6

Sorry, the modified version did not work.

But with the original version, I've noticed something. If I boot with initrd.img in the grub line, boots fine. But if I change it for initrd1.xz does not boot and says it can't find Porteus file etc.

Is initrd1.xz a compressed version of initrd.img?