Should be OK if the build finished for the rest without errors (required packages for running mklive-stretch probably already installed).johnywhy wrote:i ran the dpkg command in another window as soon as i saw the message. But does the dpkg alert indicate this iso is already borked?
Seems good! Booted fine.fredx181 wrote: Should be OK if the build finished for the rest without errors (required packages for running mklive-stretch probably already installed).
Did that dpkg command you ran "do" or indicate something ?
johnywhy wrote:Seems good! Booted fine.
I noticed some StretchDogs ask if you want to save the session before leaving xfce-- some give you a DOS-style dialog-box after leaving xfce4. And some don't ask, they just do it.
i prefer the type that does it without asking, and before leaving xfce.
Code: Select all
changes=EXIT:/........Code: Select all
changes=/.........then i'm guessing that if my grub boots from iso file (instead of loose files), then i'll get the live-CD behavior, right?fredx181 wrote:booting with "live-boot" will not ask for save or not, it has different options though. (and save to folder not supported, only savefile or partition)
Code: Select all
# Porteus-32
set p32fldr=/porteus32
set p32iso=$p32fldr/Porteus-XFCE-v4.0-i586.iso
set p32mods="extramod="
menuentry "Porteus 4.0-32 ISO" {
set boot_parms="volume=33 reboot=cold $p32mods$p32fldr/modules copy2ram changes=EXIT:$p32fldr/porteussave.dat"
search -f $p32iso --set=root
loopback loop $p32iso
linux (loop)/boot/syslinux/vmlinuz from=$p32iso $boot_parms
initrd (loop)/boot/syslinux/initrd.xz
}How's that different than my manual method?fredx181 wrote:You may want to try Isobooter
Hi Fred !The structure of Porteus ISO is very much different, so your example won't work.fredx181 wrote:
You may want to try Isobooter
How's that different than my manual method?
OK for me to post here about XFCE starter kit, it's different from rcrsn51's starter kit, so could lead to confusion.
Yes, it's very minimal (maybe too minimal) so you need to install what you need from Synaptic e.g. unzip, zip.Some issues:
can't get xarchiver to work.
Quote:
Failed to execute child process "unzip" (No such file or directory)
Sorry, don't know about numlock and the blank dialogs I've never seen.numlock lost on reboot
getting intermiittent blank dialogs, eg the "save changes" dialog on closing mousepad, and adding bookmarks to Opera.
Thanks Andres!, I will check it out.Smile Hi Fred !
jwm-obmenu is cool in debian stretch then i compiled with:
SVG support
https://bitbucket.org/geekless/openbox-menu/
settings and other buttons next to shutdown button are not enabledfredx181 wrote:It's complete XFCE, AFAIK
Confused:fredx181 wrote:Stretch-Live has systemd installed, but boots by default without it, so there's choice to use it or not. For those who are absolutely anti systemd see:
Create Devuan ascii minimal live ISO similar to 'DebianDog'
seems i have both systemd and init running. i'm ignorant about this, but i think it should be one or the other.fredx181 wrote:looks like you are right about systemd (fully enabled ? partly ?, not sure, to be honest)
Code: Select all
root@live:~# cat /proc/cmdline
from=/slive noauto changes=EXIT:/slive/live init=/bin/systemd
root@live:~# systemctl list-units --type=service --state=active
UNIT LOAD ACTIVE SUB DESCRIPTION
acpid.service loaded active running ACPI event daemon
alsa-restore.service loaded active exited Save/Restore Sound Card S
cgmanager.service loaded active running Cgroup management daemon
console-setup.service loaded active exited Set console font and keym
cpufrequtils.service loaded active exited LSB: set CPUFreq kernel p
dbus.service loaded active running D-Bus System Message Bus
........
........Code: Select all
root@live:~# cat /proc/cmdline
from=/slive noauto changes=EXIT:/slive/live
root@live:~# systemctl list-units --type=service --state=active
Failed to list units: No such method 'ListUnitsFiltered'
root@live:~# pidof systemd
root@live:~#
root@live:~# pidof init
1
root@live:~# Code: Select all
apt-get install systemd-sysvLooking at the screenshot you show, this is build with mklive-stretch using XFCE option, right ?johnywhy wrote:fredx181 wrote:
It's complete XFCE, AFAIK
settings and other buttons next to shutdown button are not enabled
how to grab those messages?fredx181 wrote:During boot I noticed all sorts of messages related to systemd
Why are you sharing the install command?Code: Select all
apt-get install systemd-sysv
i get:find out if booted with systemd or not.
Code: Select all
# pstree -p
init(1)─┬─cgmanager(2062)
├─dbus-daemon(2253)
.....
├─run-parts(2621)───freechk(2622)───sleep(16855)
├─systemd-logind(2184)
├─systemd-udevd(1123)
├─udhcpc(2872)
...Code: Select all
menuentry "MyStretchNetinst1" {
search -f /MyStretchNetinst1/live/vmlinuz1 --set=root
linux /MyStretchNetinst1/live/vmlinuz1 from=/MyStretchNetinst1 noauto changes=EXIT:/MyStretchNetinst1/live/changes.dat
initrd /MyStretchNetinst1/live/initrd1.xz}Yesfredx181 wrote:this is build with mklive-stretch using XFCE option, right ?
Yes.do you have "zz_xfce_config.squashfs" inside "live" folder ?
Code: Select all
root@live:/mnt/live/mnt/sda1/MyStretchNetinst1/live# ls -l
total 2274445
-rwxrwxrwx 1 root root 169701376 Sep 5 06:11 01-filesystem.squashfs
drwxrwxrwx 1 root root 0 Sep 5 06:14 base
-rwxrwxrwx 1 root root 1572864000 Sep 7 10:12 changes.dat
-rwxrwxrwx 1 root root 221638536 Sep 6 13:46 changes.dat-3.gz
-rwxrwxrwx 1 root root 330137953 Sep 6 22:29 changes.dat-4.tar.gz
-rwxrwxrwx 1 root root 12950360 Sep 5 06:08 initrd1.xz
-rwxrwxrwx 1 root root 15891532 Sep 5 06:06 initrd.img
drwxrwxrwx 1 root root 0 Sep 5 06:14 modules
drwxrwxrwx 1 root root 0 Sep 5 06:14 optional
drwxrwxrwx 1 root root 0 Sep 5 06:14 rootcopy
-rwxrwxrwx 1 root root 437 May 26 2015 stretch-i486.sgn
-rwxrwxrwx 1 root root 437 May 26 2015 stretch-x86_64.sgn
-rwxrwxrwx 1 root root 3661600 Aug 13 19:31 vmlinuz1
-rwxrwxrwx 1 root root 2179072 Aug 16 19:09 zz_xfce_config.squashfsmaybe would be cool to have option during your iso script, to select init or systemd, and then don't install any systemd stuff if init is picked? Seems like you're including it so can run with or without it via a grub switch. Why needed? That seems like a "try it out" thing. My preference is to make the slimmed OS i want, without any stuff i don't want-- isn't that the point of your script? I already know if i want systemd or not.Stretch-Live has systemd installed, but boots by default without it
Even if you are not booting with systemd, some packages that you install from the Debian repo will have libsystemd (or something similar) as a dependency.johnywhy wrote:Still wondering- If mklive-stretch iso boots without systemd by default, then why do we need this Devuan thing?
ok, thx, that makes sense. And therefor make sense that systemd has to remain resident in RAM. So, maybe my install is correct (re systemd/init)?rcrsn51 wrote:johnywhy wrote:Even if you are not booting with systemd, some packages that you install from the Debian repo will have libsystemd (or something similar) as a dependency.
apt-get install systemd-sysv
Why are you sharing the install command?
Is it loaded ? You can check if you see it when running:Quote:
do you have "zz_xfce_config.squashfs" inside "live" folder ?
Yes.
Code: Select all
losetup -athx Fred. If i add to kernel line, do i need to install?fredx181 wrote:Why are you sharing the install command?
Installing that package makes Debian work exclusively with systemd, so you may you want that...
(then there's no need to add to kernel line "init=/bin/systemd")
Code: Select all
# whereis systemd
systemd: /usr/lib/systemd /bin/systemd /etc/systemd /lib/systemd /usr/share/systemd
root@live:~# fuser systemd
Specified filename systemd does not exist.
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /usr/lib/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /bin/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /etc/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /lib/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /usr/share/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handleNo, adding it to kernel line will boot with systemd without needing to install systemd-sysv.johnywhy wrote:thx Fred. If i add to kernel line, do i need to install?
is this what i should see?fredx181 wrote:Is it loaded ? You can check if you see it when running:Code: Select all
losetup -a
Code: Select all
# losetup -a
/dev/loop1: [2049]:15034 (/mnt/live/mnt/sda1/MyStretchNetinst1/live/zz_xfce_config.squashfs)
/dev/loop2: [2049]:15390 (/mnt/live/mnt/sda1/MyStretchNetinst1/live/changes.dat)
/dev/loop0: [2049]:15016 (/mnt/live/mnt/sda1/MyStretchNetinst1/live/01-filesystem.squashfs)