Create Debian 9 (Stretch) minimal ISO similar to DebianDog

[rufwoof]

sed -i 's/geteuid/getppid/' /usr/bin/vlc
AND VLC WORKS GREAT.

There's a very good reason vlc stop their program running as root as it has known weaknesses that can be exploited to run commands, and if being run as root those commands can do anything. You not only put your system at risk, but any other system in your local area network.

[zagreb999]

STRETCHDOG AFTER QUICKREMASTER IS lousing
THE customisation OF SOME ELEMENTS:
ACTIVATION OF VLC PLAYER, SOME SHORTCUTS ON
DESKTOP, SOME ELEMENTS OF SYNAPTIC P.M. ...

THANKS

[fredx181]

Hi zagreb999, I cannot reproduce that.
Many times I used quick-remaster (GUI) for Stretchdog and different builds of Stretch-live and didn't experience such problems.
Can you please provide more details of what exactly you're using (e.g.Stretchdog ISO ? , which version if quick-remaster you have installed, etc...).
Without details I can't help.

Fred

[zagreb999]

HI FRED, IT IS
StretchDog32-openbox_xfce-jwm-2017-10-10.iso

IT COULD BE MY COMPUTER.
IT IS VERY FAST: 8 GB RAM , HP PAVILION.
WITH XENIAL AND DEBIANDOG ALL IS
PERFECT ON THE SAME COMPUTER.
QUICKREMASTER IS FROM
THAT ISO.

THANKS.

[fredx181]

Hi zagreb, sorry, I have no idea what is wrong at your end, is there something special about your install, you are not doing the remaster on NTFS ?
I tried quick-remastergui again with a fresh Stretchdog install using lz4 compression, and "Clear changes at reboot", after installing vlc (and did the "root" patch) and all is fine for me at reboot.
Maybe run quick-remastergui from terminal and look for errors:

Code: Select all

quick-remastergui

Or try starting fresh with Stretchdog.

Fred

[zagreb999]

HI FRED,
i am apologize for disturbing you...

MX LINUX RECEIVED GREAT NUMBER
OF RECENSIONS AS THE BEST LINUX OS....

IT IS DEBIAN PERFECTLY ORDINATED...

IT WOULD BE GREAT TO HAVE ONE MX-LINUX-DOG
BUT FROM NET INSTALL ...

WHY NOT DO IT INSTEAD OF UBUNTU?!

THANKS.

[fredx181]

Hi zagreb,

IT WOULD BE GREAT TO HAVE ONE MX-LINUX-DOG
BUT FROM NET INSTALL ...

WHY NOT DO IT INSTEAD OF UBUNTU?!

First: I think MX-linux is (more than) fine how it is by itself.
And I have already too much projects going on (starting a new project means that I need to give support, which I don't have the time and energy for).

Fred

[fredx181]

Updated mklive-stretch script
Changes:
- Kernel install: version 4.9.0-6 (previously was 4.9.0-5)
- Dropped no-pae support (in most cases it works by adding forcepae to the kernel boot command line in case of no-pae capable cpu)
The new .tar.gz containing custom boot scripts, aufs and squashfs kernel modules is now:
dog-boot-stretch-20180224.tar.gz

For existing build, "upgrade-kernel" can be used on a frugal install to upgrade the kernel to version 4.9.0-6, install with Synaptic or apt-get:

Code: Select all

apt-get update
apt-get install upgrade-kernel # will install latest version 1.0.7

deb package (for both 32 and 64 bit (all)):
https://fredx181.github.io/StretchDog/a ... .7_all.deb
(run from: Menu > System > Upgrade-Kernel ..)

Fred

[rcrsn51]

I updated my mklive script and cranked out a new set of ISOs. They look good.

This takes less time than the average Windows update.

BTW, how safe is it to combine a new "live" folder with an old "changes" folder? Are there kernel-specific things in "changes" that would cause problems after a kernel-upgrade?

[fredx181]

BTW, how safe is it to combine a new "live" folder with an old "changes" folder? Are there kernel-specific things in "changes" that would cause problems after a kernel-upgrade?

I'd say not so safe, not because of kernel-specific things but because of possibly broken package management, see here the problems backi had when doing something similar:
http://murga-linux.com/puppy/viewtopic. ... 440#971440
http://murga-linux.com/puppy/viewtopic. ... 526#971526
http://murga-linux.com/puppy/viewtopic. ... 538#971538

Assuming, btw, that the new "live" is exactly the same build as previous (except for the kernel)
It probably depends, e.g. when the changes contains the same up-to-date status file (in /var/lib/dpkg/) as the new 01-filesystem in "live", then it's safe.
Except then the new kernel version is not registered in the changes, which I guess it's not a real problem.

Fred

[rcrsn51]

Thanks. I looked at the upgrade-kernel script. If I do a kernel-upgrade of a Starter Kit install just by dropping in a new "live" folder, are there a few lines from the script that I could apply to my current "changes" that would finish the job?

The only difference in the new Starter Kit ISO would be the new kernel.

But it is not a major task to start a new "changes".

[fredx181]

Thanks. I looked at the upgrade-kernel script. If I do a kernel-upgrade of a Starter Kit install just by dropping in a new "live" folder, are there a few lines from the script that I could apply to my current "changes" that would finish the job?

Not sure yet, maybe nothing really required, will investigate and edit here later.

EDIT: I hesitate to say something about this because a broken dpkg can be a bad thing to happen and not easy to repair.
You can check with comparing the dpkg status file in changes (if exists) with the one from the (new) main 01-filesystem.squashfs, e.g.:

Code: Select all

sdiff -s /mnt/live/memory/changes/var/lib/dpkg/status /mnt/live/memory/images/01-filesystem.squashfs/var/lib/dpkg/status

Or when booted with changes=EXIT:/...:

Code: Select all

sdiff -s /mnt/live/memory/images/changes-exit/var/lib/dpkg/status /mnt/live/memory/images/01-filesystem.squashfs/var/lib/dpkg/status

In your case you'll see that kernel version is different, OK, it's misleading (but maybe not a problem knowing that), the package management will not know about the latest kernel version installed. But you can try to sync the status file from the changes with the one from: /mnt/live/memory/images/01-filesystem.squashfs/var/lib/dpkg/status, but that would be a real hack...

In general, I'd say, better just start with a new "changes", however depending on the situation, strange things may occur when using old save storage combined with new system.

Fred

[rcrsn51]

Now I understand. Because the kernel upgrade was NOT done through dpkg, the dpkg information still thinks that it is using the old kernel.

I once tried a hack where I ran your upgrade-kernel script on Machine #1. I then squashed the new /lib/modules, and moved it and the new vmlinuz1 to Machine #2.

This appeared to do a kernel upgrade on #2. But I'm guessing that it would have the same potential problem.

[dancytron]

/snipped
For existing build, "upgrade-kernel" can be used on a frugal install to upgrade the kernel to version 4.9.0-6, install with Synaptic or apt-get:

Code: Select all

apt-get update
apt-get install upgrade-kernel # will install latest version 1.0.7

deb package (for both 32 and 64 bit (all)):
https://fredx181.github.io/StretchDog/a ... .7_all.deb
(run from: Menu > System > Upgrade-Kernel ..)

Fred

Did the kernel upgrade, uninstalled old kernel with synaptic, and remastered after that. All went well and works flawlessly as usual.

Dan

[zagreb999]

I MADE NEW DEBLIVE ISO- 311 MB.

IT WORKS PERFECTLY.

GREAT JOB, FRED!

THANKS...

[fredx181]

I MADE NEW DEBLIVE ISO- 311 MB.

IT WORKS PERFECTLY.

GREAT JOB, FRED!

THANKS...

Ah, nice, thanks, what type of build did you choose or configure ? (always curious about that )

Fred

[zagreb999]

HI FRED,
I MADE XFCE WITH

KDEGRAPHICS, VLC PLAYER, WPS OFFICE,
LIBREOFFICE, ABROWSER , gnome-search-tool....

[zagreb999]

HI FRED,
I THINK IT WOULD BE VERY USEFUL
TO CREATE FOR DEBIANDOGS
PUPPY NETWORK WIZARD TO BE ABLE TO USE
MORE WIFI MANAGERS...
AND, ALSO, QUICK SETUP-FIRST RUN
TO ADJUST TIME ZONE, KEYBOARD, ETC...

REGARDS...

[fredx181]

*** Update DogRadio ***

Info, .pet and .deb packages download, topic DogRadio v0.0.8:
http://www.murga-linux.com/puppy/viewtopic.php?t=112858
Install or upgrade "dogradio" with Synaptic or apt-get

Fred

[rcrsn51]

Touchpad updated here.