Create Debian 9 (Stretch) minimal ISO similar to DebianDog

[rcrsn51]

I have posted an update to PeasyXorBurn here with an improved remastering tool.

The previous version assumed that the boot files like isolinux.bin were at the root of the ISO source folder.

The new version allows them to be in a subfolder named "isolinux". This is how the Dog ISOs are structured.

[rcrsn51]

Touchpad updated here.

[trister]

I have posted a question about one of my PCs doesn't "see" the graphics cards here:
http://www.murga-linux.com/puppy/viewto ... 51#1041051


I didn't want to clutter this very good topic

[fredx181]

Updated mklive-devuan (ascii) script Here

Fred

[dancytron]

Updated mklive-devuan (ascii) script Here

Fred

So you are going to support devuan going forward?

edit: ran the script and it completed with no errors. I'll try to boot it up tomorrow. It did create itself in the /stretch folder. I imagine that was an slight oversight.

[fredx181]

Updated mklive-devuan (ascii) script Here

Fred

So you are going to support devuan going forward?

Well, probably on request only (I should have mentioned above that I got a PM request for a fix)

edit: ran the script and it completed with no errors. I'll try to boot it up tomorrow. It did create itself in the /stretch folder. I imagine that was an slight oversight.

Yes, in stretch folder, it's so from the beginning of mklive-devuan (started as experiment) and didn't bother to change it.

Fred

[enrique]

Hello fredx181 & rcrsn51

I am looking for a script for mklive-jessie. I am aware of strech & buster. And I seen How Create your own DebianLive from netinstall, witch I will be trying while I wait for answer as instructions seems using debian-8.8.0-i386-netinst.iso.

Short story. I do like to use my AMD GPU using opencl to write cracking code for encryption. For Real live brute force I use a Desktop. But in general I use my laptop to create my code. And it has an old chipset that requires old AMD proprietary fglrx drivers. I use to do this on windows. But since I moving to Linux I want to have that option in the best Puppy/DebiaDog I can get.

After reading a little it seems the last Debian drivers where use in Jessie 8. That is the reason I want to try Jessie. See:

Code: Select all

https://wiki.debian.org/ATIProprietary#jessie

So do you guys know if I can get my hands on mklive-jessie script if available? I will really appreciate you help. As always Thanks ahead.

[enrique]

I did try:
https://github.com/DebianDog/Jessie/rel ... -10-16.iso

And compile driver successfully using amd-catalyst-15.9-linux-installer-15.201.1151-x86.x86_64. And it build the fglrx.3.16.0-4-686-pae.ko.

I think the fglrx.ko is all I need to activate opencl in Internal GPU. I do not think I need the whole driver as I would not use it for rendering video.

Now I want to see if I can use debian strech. I think there is hope if I can get strech to use old kernel 4.4. As I may be able to build driver using:
https://github.com/dacmot/catalyst_15.9_kernel4.4.

So the the new question is. Can I have kernel 4.4 in strechdog?

As always thanks ahead.

[fredx181]

So the the new question is. Can I have kernel 4.4 in strechdog?

That won't be easy (needs to include aufs and the files needed for porteus boot in initrd1.xz), can't you use the stock kernel ? (4.9)

Fred

[enrique]

So the the new question is. Can I have kernel 4.4 in strechdog?

That won't be easy (needs to include aufs and the files needed for porteus boot in initrd1.xz), can't you use the stock kernel ? (4.9)

Fred

I know it is not easy. I will do it the same way I did the 5.4 kernel for my satellite receiver.

See

Code: Select all

https://gist.github.com/mbohun/adacfd4f767259b4723d

If I let me guide by that comment. The last kernel that worked was linux-4.1.6-00. Then there is the patch I mention earlier that if work it does up to 4.4. It is all related to new PIC, Position-independent code and making obsolete the old gcc's like 5 etc. Another screw from Kernel as now there is no Statically Build Binary. As it will depend on ldd!!!

Then AMD used it to remove support to old devices using fglrx. Only new devices got new drivers. As result the debian/Ubuntu where force to removed fglrx as there are no more proprietary blobs update.

SOOO0000ooooo. I guess there is no mklive-jessie script. I was hope you show one. Anyway things are not ALL Lost. As opencl do work in DebianDog-Jessie-openbox_xfce-jwm-2016-10-16.iso.

I am just hopping that at the end I can bring it to work in stretch. Thanks.

Edit:
Wao even in stretch I am having problems with this PIC. And as expected it too had no gcc-5 or earlier. Wepeteeee.... So my best guess is that 1rst I need to build gcc-5 from source. So that then I can try to compile Kernel < 4.2 with a gcc-5 in stretch.

[step]

Issue report:
I downloaded the latest 64-bit appimage and tried to build a 32-bit (forced) openbox_lx conf. I ticked the "Open Xterm" option. The build aborted with an error message about not finding the terminal (see log below). System: Fatdog64; shell: sh; xterm is installed; defaultterm is urxvt in /usr/bin/urxvt; customization: another urxvt is installed in /usr/local/bin/urxvt (comes first in $PATH) and environment variable TERM is set to reflect its capability (see log). Look at the log tail first - the head is just to provide some context.

I need to build a 32-bit minimal system with mpv to run on an Atom N270 with 1GB RAM. Which kit would be the best choice for this project? I understand it's tentative given the very minimal hardware.
If mpv isn't available I could probably do with Firefox but I fear that system resources would not suffice for FF.

Thanks

Code: Select all

# ./mklive-stretch64 -gui
...
Setting up xserver-xorg-legacy (2:1.19.2-1+deb9u5) ...
setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
Processing triggers for menu (2.1.47+b1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for initramfs-tools (0.130) ...
Errors were encountered while processing:
 keyboard-configuration
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apt-utils is already the newest version (1.4.9).
dbus is already the newest version (1.10.28-0+deb9u1).
gnupg is already the newest version (2.1.18-8~deb9u4).
live-boot is already the newest version (1:20170112).
menu is already the newest version (2.1.47+b1).
wget is already the newest version (1.18-5+deb9u3).
xserver-xorg-legacy is already the newest version (2:1.19.2-1+deb9u5).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up keyboard-configuration (1.164) ...
Error opening terminal: rxvt-unicode-256color.
debconf: dialog output the above errors, giving up!
dpkg: error processing package keyboard-configuration (--configure):
 subprocess installed post-installation script returned error exit status 255
Errors were encountered while processing:
 keyboard-configuration
E: Sub-process /usr/bin/dpkg returned an error code (1)
FAILED
Unmounting mount binds in chroot
# echo $TERM
rxvt-unicode-256color

[rcrsn51]

The 32bit build of the Stretch Starter Kit is still available here. It will run fine on your hardware.

[step]

Thank you rcrsn51, this looks very interesting. I downloaded it and I'm taking a walk-around in QEMU.

ok - update packages w/ synaptic
ok - install and run mpv
ok - install peasyport and yassm
ok - port-scan 10.0.2.4:139 the built-in QEMU host share
-- - mount it with yassm (I didn't expect it would work but I tried)
ok - port-scan 10.0.2.2:139 real samba server running in the host network
ok - mount it with yassm

Overall pre-flight checklist passed, so I'm going to test it on the N270 hardware, hopefully audio will be OK (I didn't test audio in QEMU).
Thanks again.

[step]

Report: I used the stretch-live-frugal-install script successfully on Fatdog64 with one exception; copying grldr to the USB target failed with no GUI warning. I copied grldr manually all is well now, I can boot from the resulting USB key. If you want to change your code to support installing from Fatdog64 too, I believe it should be enough to change line 84

Code: Select all

cp $(find /usr/lib -name "grldr") /mnt/data

to take into account the locations where Fatdog64 keeps grldr. These are:

Code: Select all

# find /usr/lib -name "grldr"
# find /usr/lib64 -name "grldr"
# find /usr/share -name "grldr"
/usr/share/grub4dos/grldr
/usr/share/grub4dos-0.4.5c/grldr

The first one is newer. Both locations are included in the base system. Thank you for the script.

[fredx181]

I downloaded the latest 64-bit appimage and tried to build a 32-bit (forced) openbox_lx conf. I ticked the "Open Xterm" option. The build aborted with an error message about not finding the terminal (see log below). System: Fatdog64

Hi step, I see you found solution with the stretch-starter-kit, so fine with me if you ignore the following.

Anyway, I was curious and tested first on Fatdog (older version, I think 710) and could not reproduce the issue, all went fine (forced 32-bit), also opening xterm.
It looks like there was for you also a problem with keyboard -configuration package, no idea why.

Second test on Fatdog 810 went fine for me too, except that xterm didn't run, error message:

Code: Select all

Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm: Xt error: Can't open display: %s

Looks like 810 has different xterm than 710

Fred

[step]

I Fred, thanks for testing. I use 810, never mind 710. My guess is that you got that error message on 810 because the starter kit (or the appImage) doesn't like when root starts a terminal?
Back to the error I got, my guess is that it depends on my specific configuration. Try

Code: Select all

export TERM=rxvt-unicode-256color
./mklive-stretch64

That setting is sensible if package rxvt-unicode_perl_true_color_256-9.22_2019.09.17_dda8c82-x86_64-191214-1.txz is installed using the Fatdog package manager (I'm not saying you should install it. I'm just giving you more context).

[fredx181]

*** Addition and updates in custom Stretchdog repository ***

-Added package: takeashot, (Take A Shot) advanced screen capture utility (by SFR, see here: http://murga-linux.com/puppy/viewtopic.php?t=84528
One nice thing about it is that it can create an animated gif, depends on ffmpeg.
See also here: http://murga-linux.com/puppy/viewtopic. ... 03#1054503

-Updated:
- touchpad and p910nd-print-server (by rcrsn51) Touchpad P910nd Print Server
- mm-view (v 0.28, 'a universal file viewer' by Mochimoppel, see here: http://murga-linux.com/puppy/viewtopic.php?t=109573)
- youtube-viewer (v 3.7.4) (if straw-viewer is installed, it will be replaced by youtube-viewer (and vice versa))

Install with synaptic or apt.

Fred

[dancytron]

Fred, bill or anyone,

I noticed this script in the Puppy Newsletter on how to use VLC as Personal Video Recorder for over the air TV.

http://smokey01.com/newsletters/2018/Au ... 018.html#7

Would it be easy to get this to work in Debian Dog?

The first issue is that instead of channels.conf, later versions of VLC use a *.xfpf file. Mine is called "OTA_TV.xspf". It is really just a play list of channels. I think a search and replaceof channels.conf to OTA_TV.xspf might have fixed that.

The second issue is that I can't seem to figure out how to get it to use cron and I can't figure out how to get that working or maybe anacron is something different??

Any guidance would be appreciated.

Dan

see also http://murga-linux.com/puppy/viewtopic. ... 14#1056514

[ras]

The second issue is that I can't seem to figure out how to get it to use cron and I can't figure out how to get that working or maybe anacron is something different??

I have had to make cron call for cvlc in the past.