DebianDog - Jessie (21 June 2017)

[Satori]

Hiyas

Switched out the recently installed Jessie-i586 for the new i686-PAE version and my Dell E6510 likes it

Found 8 cpu cores, and the 4g memory stick.

In order to run Chrome, I needed to download the libnss3 and libgconf .debs off the Debian.org site, they installed
without any problems and Chrome runs with a data-user-dir that I keep separate from the OS.

Chrome complains about gl extensions failing, but that's probably expected since a full open_gl isn't installed.
But it doesn't stop Chrome from playing full screen videos from Hulu.

In order to install the nvidia blob, I assume that I'll need to pick up the kernel headers from Debian as well?
Once I can run OpenGL apps, then I can retire dpup Wheezy.

[fredx181]

Regarding my upgrade and kernel install results vs yours. Before testing I removed your arbitrary pin preferences and all reference to kazza repos. In other words, made DD's apt settings identical to Debian Jessie's. DD fails - Jessie upgrades and installs the kernel without issue.

Good to know you solved it by removing "this kazza" from "this jessie" with "our arbitrary" pin preferences.
Maybe next step is to remove everything related to DebianDog, including "that porteus-boot" and "this live-boot2".
Good luck with that, but... hmm..., it wouldn't be "pure DD" anymore, isn't that "wrong"? And is it even "legitimate"?
Sorry, the above is unreasonable because I trust you won't try to "sell" it as DD™

[saintless]

Hi, Satori.

Chrome complains about gl extensions failing, but that's probably expected since a full open_gl isn't installed.

Try installing:

Code: Select all

apt-get install libgl1-mesa-dri mesa-utils

Then exit X and start X and type in terminal glxgears. It should work or atleast give you some more info what else to install from terminal output.

In order to install the nvidia blob, I assume that I'll need to pick up the kernel headers from Debian as well?

This is the Debian wiki page about nvidia drivers:
https://wiki.debian.org/NvidiaGraphicsDrivers
I think this should do it but read the wiki first.

Code: Select all

apt-get install linux-headers-$(uname -r) nvidia-kernel-dkms

I'm sure you can remove safely after that nvidia-kernel-dkms and linux-headers and run apt-get autoremove after building nvidia kernel modules to safe space. If you have troubles write again and i will search for more information.

Toni

[ally]

I was getting 3.5mb/s from the host site, have mirrored

[saintless]

I will say it again. My only point is, that upgrading DD Wheezy and presenting the result as DD Jessie is cheap.

Your talk is cheap.

Regarding my upgrade and kernel install results vs yours. Before testing I removed your arbitrary pin preferences and all reference to kazza repos. In other words, made DD's apt settings identical to Debian Jessie's. DD fails - Jessie upgrades and installs the kernel without issue.

Your lies are weak.
Fresh DD-Jessie-Jwm (because it has more packages pinned in /etc/apt/preferences).
1. Delete /etc/apt/preferences.
2. Use only official Debian Jessie sources in /etc/apt/sources.list

Code: Select all

deb http://ftp.de.debian.org/debian jessie main 
deb http://ftp.debian.org/debian/ jessie-updates main 
deb http://security.debian.org/ jessie/updates main

3. Update:

Code: Select all

root@debian:~# apt-get update
Get:1 http://ftp.debian.org jessie-updates InRelease [126 kB]
Get:2 http://ftp.debian.org jessie-updates/main i386 Packages [3673 B]         
Get:3 http://ftp.debian.org jessie-updates/main Translation-en [2506 B]        
Get:4 http://security.debian.org jessie/updates InRelease [63.1 kB]            
Get:5 http://ftp.de.debian.org jessie InRelease [128 kB]                  
Get:6 http://security.debian.org jessie/updates/main i386 Packages [77.2 kB]
Get:7 http://security.debian.org jessie/updates/main Translation-en [39.8 kB]
Get:8 http://ftp.de.debian.org jessie/main i386 Packages [6768 kB]             
Get:9 http://ftp.de.debian.org jessie/main Translation-en [4585 kB]            
Fetched 11.8 MB in 44s (266 kB/s)                                              
Reading package lists... Done

4. Upgrade (and keep in mind "The following packages have been kept back:" message. You can google for answer what it means but I will explain just for you in the next step):

Code: Select all

root@debian:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  dpkg lxrandr wget x11-xserver-utils
The following packages will be upgraded:
  adwaita-icon-theme dillo linux-image-3.16.0-4-586 ntfs-3g
4 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 43.7 MB of archives.
After this operation, 908 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.debian.org/ jessie/updates/main linux-image-3.16.0-4-586 i386 3.16.7-ckt9-3~deb8u1 [32.7 MB]
Get:2 http://ftp.de.debian.org/debian/ jessie/main adwaita-icon-theme all 3.14.0-2 [9978 kB]
Get:3 http://ftp.de.debian.org/debian/ jessie/main dillo i386 3.0.4-2+b1 [491 kB]
Get:4 http://security.debian.org/ jessie/updates/main ntfs-3g i386 1:2014.2.15AR.2-1+deb8u2 [531 kB]
Fetched 43.7 MB in 25s (1743 kB/s)                                             
Preconfiguring packages ...
(Reading database ... 31899 files and directories currently installed.)
Preparing to unpack .../linux-image-3.16.0-4-586_3.16.7-ckt9-3~deb8u1_i386.deb ...
Unpacking linux-image-3.16.0-4-586 (3.16.7-ckt9-3~deb8u1) over (3.16.7-ckt4-3) ...
..
Preparing to unpack .../ntfs-3g_1%3a2014.2.15AR.2-1+deb8u2_i386.deb ...
Unpacking ntfs-3g (1:2014.2.15AR.2-1+deb8u2) over (1:2014.2.15AR.2-1+deb8u1) ...
Preparing to unpack .../adwaita-icon-theme_3.14.0-2_all.deb ...
Directory does not exist.
Unpacking adwaita-icon-theme (3.14.0-2) over (3.14.0-0) ...
Preparing to unpack .../dillo_3.0.4-2+b1_i386.deb ...
Unpacking dillo (3.0.4-2+b1) over (3.0.3-1) ...
menu-puppy running...
menu-puppy running...
dpkg: warning: unable to delete old directory '/usr/local/etc': Directory not empty
Processing triggers for initramfs-tools (0.120) ...
/boot/initrd.img-3.16.0-4-586 does not exist. Cannot update.
Processing triggers for menu (2.1.47) ...
menu-puppy running...
menu-puppy running...
Processing triggers for mime-support (3.58) ...
Setting up linux-image-3.16.0-4-586 (3.16.7-ckt9-3~deb8u1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-586
W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100
cryptsetup: WARNING: could not determine root device from /etc/fstab
live-boot: core filesystems devices utils udev wget blockdev ftpfs.
Setting up ntfs-3g (1:2014.2.15AR.2-1+deb8u2) ...
update-initramfs: deferring update (trigger activated)
Setting up adwaita-icon-theme (3.14.0-2) ...
Setting up dillo (3.0.4-2+b1) ...
menu-puppy running...
menu-puppy running...
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-4-586
W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100
cryptsetup: WARNING: could not determine root device from /etc/fstab
live-boot: core filesystems devices utils udev wget blockdev ftpfs.
Processing triggers for libc-bin (2.19-18) ...
root@debian:~# 

Kernel upgraded to version 3.16.7-ckt9-3~deb8u1 and new /boot/initrd.img-3.16.0-4-586 created.
5. See what packages are on hold and unhold them(it was written in /etc/apt/preferences but someone has to read it first):

Code: Select all

root@debian:~# apt-mark showhold
dpkg
libxml2
lxrandr
wget
xinit
root@debian:~# apt-mark unhold dpkg libxml2 lxrandr wget xinit
Canceled hold on dpkg.
Canceled hold on libxml2.
Canceled hold on lxrandr.
Canceled hold on wget.
Canceled hold on xinit.

6. Upgrade again after unhold command (and keep in mind again "The following packages have been kept back:" message. I will explain again why it appears in case you like to learn):

Code: Select all

root@debian:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  wget x11-xserver-utils
The following packages will be upgraded:
  dpkg lxrandr
2 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 3061 kB of archives.
After this operation, 266 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian/ jessie/main dpkg i386 1.17.25 [3012 kB]
Get:2 http://ftp.de.debian.org/debian/ jessie/main lxrandr i386 0.3.0-1 [49.8 kB]
Fetched 3061 kB in 2s (1038 kB/s)
(Reading database ... 33722 files and directories currently installed.)
Preparing to unpack .../archives/dpkg_1.17.25_i386.deb ...
Unpacking dpkg (1.17.25) over (1.17.25) ...
Setting up dpkg (1.17.25) ...
(Reading database ... 33722 files and directories currently installed.)
Preparing to unpack .../lxrandr_0.3.0-1_i386.deb ...
Unpacking lxrandr (0.3.0-1) over (0.1.2-3) ...
menu-puppy running...
menu-puppy running...
Processing triggers for menu (2.1.47) ...
menu-puppy running...
menu-puppy running...
Processing triggers for mime-support (3.58) ...
Setting up lxrandr (0.3.0-1) ...
menu-puppy running...
menu-puppy running...

7. Upgrade the kept back packages. they are kept back because they both have not installed yet dependencies libicu52 and cpp:

Code: Select all

root@debian:~# apt-get install wget x11-xserver-utils
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  cpp cpp-4.9 libicu52 libpsl0
Suggested packages:
  cpp-doc gcc-4.9-locales nickle cairo-5c xorg-docs-core
The following NEW packages will be installed:
  cpp cpp-4.9 libicu52 libpsl0
The following packages will be upgraded:
  wget x11-xserver-utils
2 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.8 MB of archives.
After this operation, 46.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian/ jessie/main libicu52 i386 52.1-8 [6885 kB]
Get:2 http://ftp.de.debian.org/debian/ jessie/main libpsl0 i386 0.5.1-1 [42.4 kB]
Get:3 http://ftp.de.debian.org/debian/ jessie/main wget i386 1.16-1 [504 kB]
Get:4 http://ftp.de.debian.org/debian/ jessie/main cpp-4.9 i386 4.9.2-10 [5155 kB]
Get:5 http://ftp.de.debian.org/debian/ jessie/main cpp i386 4:4.9.2-2 [17.3 kB]
Get:6 http://ftp.de.debian.org/debian/ jessie/main x11-xserver-utils i386 7.7+3+b1 [157 kB]
Fetched 12.8 MB in 10s (1203 kB/s)                                             
Selecting previously unselected package libicu52:i386.
(Reading database ... 33726 files and directories currently installed.)
Preparing to unpack .../libicu52_52.1-8_i386.deb ...
Unpacking libicu52:i386 (52.1-8) ...
Selecting previously unselected package libpsl0:i386.
Preparing to unpack .../libpsl0_0.5.1-1_i386.deb ...
Unpacking libpsl0:i386 (0.5.1-1) ...
Preparing to unpack .../archives/wget_1.16-1_i386.deb ...
Unpacking wget (1.16-1) over (1.16-1) ...
Selecting previously unselected package cpp-4.9.
Preparing to unpack .../cpp-4.9_4.9.2-10_i386.deb ...
Unpacking cpp-4.9 (4.9.2-10) ...
Selecting previously unselected package cpp.
Preparing to unpack .../cpp_4%3a4.9.2-2_i386.deb ...
Unpacking cpp (4:4.9.2-2) ...
Preparing to unpack .../x11-xserver-utils_7.7+3+b1_i386.deb ...
Unpacking x11-xserver-utils (7.7+3+b1) over (7.7+2+b1) ...
menu-puppy running...
menu-puppy running...
Processing triggers for menu (2.1.47) ...
menu-puppy running...
menu-puppy running...
Setting up libicu52:i386 (52.1-8) ...
Setting up libpsl0:i386 (0.5.1-1) ...
Setting up wget (1.16-1) ...
Setting up cpp-4.9 (4.9.2-10) ...
Setting up cpp (4:4.9.2-2) ...
Setting up x11-xserver-utils (7.7+3+b1) ...
menu-puppy running...
menu-puppy running...
Processing triggers for libc-bin (2.19-18) ...
root@debian:~# 

8. Check upgrade and dist-upgrade:

Code: Select all

root@debian:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@debian:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@debian:~# 

Now you are running the same DD-Jessie with much bigger size, not packages on hold and not modded official debs. Save on Exit from porteus-boot will not give you choice not to save if you run reboot from terminal + lxrandr in Jwm will need pressing Enter 2 times to make Cancel/Apply button to appear.
Thank you for wasting my time showing you how to use official debian methods and commands to upgrade the system. Lets hope you have learned something useful.

[anikin]

I absolutely don't understand what this 'fight' about the creation method of Debian-Jessie is all about

I don' understand it either, it's a case of pettiness and aggressive overreaction.

Anyone using DebianDog in any shape and form is benefiting from thousands of hours of hard work from Toni and Fred

By my observation, not a lot of folks are benefitting from using DD, simply because from the very start DD committed the same crime as Puppy - alienated its users by connecting their computers to icanhazip. One particular, pesky user tried to change that ... but it was too late. The result is an half-assed ipinfo and no active users, no user feedback, no roadmap, no discussion - no nothing. Stagnation as in the rest of Puppyland.

As for a boot method being 'wrong' because it comes from an older version of Debian, why should that make anything 'wrong'? Technology has no rights and wrongs unless it is somehow 'morally' hurting this universe's inhabitants surely?

Things are a bit more tangled. Live-boot is part of live-build, which in turn happens to be a fast moving target:
sqeeze
2.0.15-1
wheezy
3.0.1-1
jessie
4.0.2-1
stretch/sid
5.0~a4-1
It's not an old version itself that is wrong, but rather mismatching components and dependencies. There's quite a bit of intertwined components involved: live-boot-initramfs-tools, live-config-sysvinit, live-config-systemd, live-config, their corresponding recommended and suggested packages. Except for Porteus boot, this home-grown concept of choosing a "boot method" is totally ridiculous. How come, other, more prominent projects have managed to survive without it?

Thank you for wasting my time showing you how to use official debian methods and commands to upgrade the system. Lets hope you have learned something useful

I have no problem using official methods upgrading Debian Jessie. I'm not interested in DD anymore. I can't afford to waste my time on communicating with little, unsophisticated hicks like you.

[bark_bark_bark]

I haven't been following this thread very closely, but why is there already name-calling?

@anikin aka Darth Vader, you don't need to get your panties in a knot.

[saintless]

Live-boot is part of live-build, which in turn happens to be a fast moving target:
sqeeze
2.0.15-1
wheezy
3.0.1-1
jessie
4.0.2-1
stretch/sid
5.0~a4-1
It's not an old version itself that is wrong, but rather mismatching components and dependencies. There's quite a bit of intertwined components involved: live-boot-initramfs-tools, live-config-sysvinit, live-config-systemd, live-config, their corresponding recommended and suggested packages.

You have no idea what you are talking about and how live-boot-2 works.
"Committed the same crime as Puppy" makes me proud since the main idea is to keep DD closer to Puppy as possible without loosing Debian compatibility and multiuser function. If you read the section title DebianDog thread is in "Puppy projects". Even not a Puppy it has the closest look and feel comparing to any other live system. And still you can turn it into pure Debian system without problems.

I can't afford to waste my time on communicating with little, unsophisticated hicks like you.

I really hope so.
Coodbye.

[drunkjedi]

Hi,

I am new to debiandog.

I downloaded new DebianDog-Jessie-openbox_xfce-3.16.0-4-686-pae.iso.

1) I wanted to know how to switch from openbox to xfce and back.

2) I setup my dual monitor setup manually by

Code: Select all

xrandr --output HDMI1 --mode 1920x1080 --left-of VGA1 --output VGA1 --mode 1280x1024

could anyone tell me the name or location of GUI tool to do that.

3) I am booting using live-boot-3, is savefolder option available? I want to save on my ext4 sda7 in a folder named DabianDog.

Thanks in advance.

[saintless]

Hi,

I will let Fred answer the first two questions because he knows the OpenBox version setup much better.

3) I am booting using live-boot-3, is savefolder option available? I want to save on my ext4 sda7 in a folder named DabianDog.

No, you need porteus-boot to save changes in folder. The folder will be always named changes but you can move it inside /DebianDog easy.
If you are booting DebianDog from sda7 but not from live cd or from other partition:
Example 1: This will create automatically /live/changes folder for changes:

Code: Select all

title Debian-PorteusDog (sda7) 
root (hd0,6) 
kernel /live/vmlinuz1 noauto from=/ changes=/live/
initrd /live/initrd1.xz

Example 2: Create manually folder /live/DebianDog and this will create automatically /live/DebianDog/changes folder for changes:

Code: Select all

title Debian-PorteusDog (sda7) 
root (hd0,6) 
kernel /live/vmlinuz1 noauto from=/ changes=/live/DebianDog/
initrd /live/initrd1.xz

Example 3: Create manually folder at top af your ext sda7 partition /DebianDog and this will create automatically /DebianDog/changes folder for changes:

Code: Select all

title Debian-PorteusDog (sda7) 
root (hd0,6) 
kernel /live/vmlinuz1 noauto from=/ changes=/DebianDog
initrd /live/initrd1.xz

Example 4: Porteus-boot depends on /live folder. It will search for folder with name live and if it is not found an error message will appear. But you can place /live in any folder with different name and to use this code (inside folder /DebianDog for example) automatically saving changes in /DebianDog/live/changes
In your case if you like to boot DebianDog from sda7 this way it should be:

Code: Select all

title PorteusDog (sda7)
root (hd0,6)
kernel /DebianDog/live/vmlinuz1 noauto from=/DebianDog/ changes=/DebianDog/live/
initrd /DebianDog/live/initrd1.xz

If you boot from live cd or usb just create /DebianDog folder at top of sda7 partition and hit tab button on "sysvinit Porteus in RAM changes=/changes.dat "menu entry and edit the line from:

Code: Select all

append initrd=/live/initrd1.xz noauto from=/ copy2ram changes=/changes.dat

to:

Code: Select all

append initrd=/live/initrd1.xz noauto from=/ copy2ram changes=/DebianDog/

You can edit /isolinux/live.cfg in your usb to add custom menu entry or rebuild the iso with changes in live.cfg in case you prefer live cd boot. Isomaster is included for editing iso images.
More information about porteus-boot here:
http://murga-linux.com/puppy/viewtopic. ... 456#774456

Toni

[drunkjedi]

Thanks Toni,

I forgot to tell you, I am booting from usb,
The usb has Fatdog installed in a folder, I copied live folder in usb.
Copied and added entries from live.cfg to fatdog's syslinux.cfg.
It works, all 6 options boot ok.

I will try what you said about using porteus method with changes=/DebianDog/ and creating /DebianDog folder on sda7.
EDIT: should it be 'changes=/sda7/DebianDog/' ??

I also noticed all 3 'no save' options were using systemd.
Is it just a matter of adding 'persistent' to menu entry or systemd can't save... yet?

Thanks.

[saintless]

I also noticed all 3 'no save' options were using systemd.
Is it just a matter of adding 'persistent' to menu entry or systemd can't save... yet?

Yes, it is a matter of adding persistent option to the systemd boot code. Or just use any sysvint persistent option adding init=/bin/systemd at the end and you get systemd boot with persistent.
I tried to make bigger live.cfg menu for the iso but it looks very bad (on my machine atleast). This why we have only 6 menu entries and systemd was the choise for no-persistent and no-copy-to-ram menu entries.
If you use grub4dos from DebDog-installer you will get much more menu entries:

Code: Select all

# menu.lst produced by grub4dosconfig-v1.7
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

title DebianDog  -  live-boot-2 Persistent Changes sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live persistent config swapon quickreboot noprompt autologin
 initrd /live/initrd1.img

title DebianDog  -  live-boot-2 (no persistent) sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live config swapon quickreboot noprompt autologin
 initrd /live/initrd1.img
 
title DebianDog  -  live-boot-2 Copy to RAM sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs
 initrd /live/initrd1.img

title Debian-PorteusDog  -  changes to /live/ sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 from=/ noauto changes=/live/
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Always Fresh sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 from=/ nomagic base_only norootcopy
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Copy to RAM sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 noauto from=/ copy2ram
 initrd /live/initrd1.xz
 
title DebianDog  -  live-boot-3 Persistence Changes sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin
 initrd /live/initrd.img

title DebianDog  -  live-boot-3 (no persistence) sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live config quickreboot noeject autologin
 initrd /live/initrd.img
 
title DebianDog  -  live-boot-3 Copy to RAM sysvinit
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs
 initrd /live/initrd.img

title DebianDog  -  live-boot-2 Persistent Changes systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live persistent config swapon quickreboot noprompt autologin init=/bin/systemd
 initrd /live/initrd1.img

title DebianDog  -  live-boot-2 (no persistent) systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live config swapon quickreboot noprompt autologin init=/bin/systemd
 initrd /live/initrd1.img
 
title DebianDog  -  live-boot-2 Copy to RAM systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs init=/bin/systemd
 initrd /live/initrd1.img

title Debian-PorteusDog  -  changes to /live/ systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 from=/ noauto changes=/live/ init=/bin/systemd
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Always Fresh systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 from=/ nomagic base_only norootcopy init=/bin/systemd
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Copy to RAM systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 noauto from=/ copy2ram init=/bin/systemd
 initrd /live/initrd1.xz
 
title DebianDog  -  live-boot-3 Persistence Changes systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin init=/bin/systemd
 initrd /live/initrd.img

title DebianDog  -  live-boot-3 (no persistence) systemd
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live config quickreboot noeject autologin init=/bin/systemd
 initrd /live/initrd.img
 
title DebianDog  -  live-boot-3 Copy to RAM systemd 
 uuid '"$UUID"'
 kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs init=/bin/systemd
 initrd /live/initrd.img

title Reboot computer
  reboot

Toni

[saintless]

EDIT: should it be 'changes=/sda7/DebianDog/' ??

No, the system will search for /DebianDog on any available ext partition and will use the first one found. Just create only one /DebianDog folder on sda7 and it will be found on boot creating changes folder inside. I will test it myself in a minute to make sure.

Edit: Yes, it works booting from usb and having /DebianDog folder on sda2 (ext3). Post again if you have problems to make it boot with persistent changes.

[mcewanw]

Example 4: Porteus-boot depends on /live folder. It will search for folder with name live and if it is not found an error message will appear. But you can place /live in any folder with different name and to use this code (inside folder /DebianDog for example) automatically saving changes in /DebianDog/live/changes
In your case if you like to boot DebianDog from sda7 this way it should be:

Code: Select all

title PorteusDog (sda7)
root (hd0,6)
kernel /DebianDog/live/vmlinuz1 noauto from=/DebianDog/ changes=/DebianDog/live/
initrd /DebianDog/live/initrd1.xz

Yes, I tend to use porteus boot method above for both my DD-jwm and DD-openbox installs. I like to keep DD live folder in a subdir, which is similar to how I arrange frugal installs of Puppy Linux distributions. Note that with the following DD menu.lst examples the changes folder gets created automatically inside the live folder on booting. The grub4dos menu.lst file I have on this particular machine I'm typing on, follows. I don't know if all the boot line codes are required or even correct(!), but it seems to work fine. It includes several different frugal installs on both different hard drive partitions and some on usb stick (note that it IS better to use a uuid for the usb stick, as in Toni's above examples, since the correct usb is always then found - I haven't done that below). On this particular machine I have my menu.lst on my harddrive in partition /dev/sda2 along with my grub4dos grldr and grldr.mbr and I have my Win7 BCD bootmanager detect it per the method documented in Lin'N'Win http://www.icpug.org.uk/national/linnwi ... innwin.htm. So I have some of my frugal installs coexisting with my Win7 install (I used the shrink NTFS partition tool available in Win7 to create space for a separate /dev/sda4 partition on my harddrive, which I then formated as ext4 especially for some of the following Linux frugal installs):

Code: Select all

######################################################
# GvR Sept 30th 2004
###############################################
   color black/cyan yellow/cyan
   timeout=5
   default=0


title debiandog_jwm
# on partition 4 of harddrive which is /dev/sda4, with live and changes in subdir /debiandog_jwm
  root (hd0,3)
  kernel /debiandog_jwm/live/vmlinuz1 noauto from=/debiandog_jwm/  changes=EXIT:/debiandog_jwm/live/
  initrd /debiandog_jwm/live/initrd1.xz

title debiandog_openboxjessie 
# on first partition of usb stick which is /dev/sdb1, with live and changes in subdir /debiandog_openboxjessie
  root (hd1,0)
  kernel /debiandog_openboxjessie/live/vmlinuz1 noauto from=/debiandog_openboxjessie/  changes=EXIT:/debiandog_openboxjessie/live/
  initrd /debiandog_openboxjessie/live/initrd1.xz

# Below requires you to extract vmlinuz and initrd.lz from the bento live-cd iso and put them in subdir /bento-sushi-vivid on hd0,3 (/dev/sda4)
title Frugal bento ubuntu sushi vivid with persistence Method1
  root (hd0,3)  
  kernel /bento-sushi-vivid/casper/vmlinuz boot=casper iso-scan/filename=/bento-sushi-vivid/sushi-vivid-rc1-with-resolvconf-x86_64.iso splash --
  initrd /bento-sushi-vivid/casper/initrd.lz

title Puppy tahrpuppy
# on partition 4 of harddrive i.e. /dev/sda4, which is (hd0,3) in grub notation
   root (hd0,3)
   kernel /tahrpuppy/vmlinuz PMEDIA=idehd psubdir=tahrpuppy
   initrd /tahrpuppy/initrd.gz

title Puppy GuyDog 
# on partition 3 of harddrive i.e. /dev/sda3, which is (hd0,2) in grub notation
   kernel (hd0,2)/guydog/vmlinuz PMEDIA=idehd PDEV1=sda3 psubdir=guydog pfix=copy
   initrd (hd0,2)/guydog/initrd.gz

# Method1 boot Lubuntu requires you to extract vmlinuz and initrd.lz from the lubuntu live-cd iso and put them in subdir /frugal-lubuntu on hd0,2 (/dev/sda3)
# On partition 4 of harddrive i.e. /dev/sda3, which is (hd0,2 in grub notation)
title Frugal Lubuntu with persistence Method1
  kernel (hd0,2)/frugal-lubuntu/vmlinuz boot=casper persistent iso-scan/filename=/frugal-lubuntu/lubuntu-13.10-desktop-i386.iso splash --
  initrd (hd0,2)/frugal-lubuntu/initrd.lz

# Method2 boot Lubuntu does not require extraction of vmlinuz and initrd.lz from the iso
title Frugal Lubuntu with persistence Method2
  find --set-root /frugal-lubuntu/lubuntu-13.10-desktop-i386.iso
  map /frugal-lubuntu/lubuntu-13.10-desktop-i386.iso (0xff) || map --mem /frugal-lubuntu/lubuntu-13.10-desktop-i386.iso (0xff)
  map --hook
  root (0xff)
  kernel /casper/vmlinuz  file=/cdrom/preseed/lubuntu.seed noprompt boot=casper persistent iso-scan/filename=/frugal-lubuntu/lubuntu-13.10-desktop-i386.iso quiet splash --
  initrd /casper/initrd.lz

# The following is just for my own machine, which I'm just including here as a record for my own use.
title Default Win 7 Boot code on hd0,1 (/dev/sda2), which on the emachines (Acer) netbook I am using boots the win 7 installation on /dev/sda3
   rootnoverify (hd0,1)
   chainloader +1
   boot
   
###################################################### 

[drunkjedi]

Yes, it works booting from usb and having /DebianDog folder on sda2 (ext3). Post again if you have problems to make it boot with persistent changes.

Yes it detects my folder on sda7 and saves changes, except the display resolution which I set using xrandr.
After reboot it goes back and mirrors desktop on both monitors.

Anyway I have made a script with

Code: Select all

xrandr --output HDMI1 --mode 1920x1080 --left-of VGA1 --output VGA1 --mode 1280x1024

and now just click it to get it as I want.

But how to make this permanent.

Thanks.

[saintless]

Anyway I have made a script with

Code: Select all

xrandr --output HDMI1 --mode 1920x1080 --left-of VGA1 --output VGA1 --mode 1280x1024

and now just click it to get it as I want.

But how to make this permanent.

Copy or link the script in /root/Startup (or ~/Startup if you decide to use user instead root account).
The script will be executed after starting X.
Maybe Fred will post better solution later.

Edit: What happens if you use save button with lxrandr (Monitor settings)? It will save the resolution but I don't know if it works well for dual monitor setup.

Toni

[drunkjedi]

Thanks Toni,

lxrander gives option to edit and save resolutions on both monitors.
It also uses a script in startup folder which points to a config file in /root/.config, which in turn has the same code I used in my script.


The reason I didn't use lxrander before because I didn't see it in any menu.
Even now I executed it from terminal.
From where did you envoke it?

Anyway it's working now.
Sorry to have caused you trouble with my silly problem.

Thanks again.

[fredx181]

Hi drunkjedi

I downloaded new DebianDog-Jessie-openbox_xfce-3.16.0-4-686-pae.iso.

1) I wanted to know how to switch from openbox to xfce and back.

Well, I must admit the name "openbox_xfce" is a litlle misleading, like you could start an "openbox" session or a "xfce" session.
This is not the case, it's just one: openbox as a base with xfce elements on top of it, like thunar, xfdesktop and xfce4-panel.

Good luck.

Edit: You are right lxrandr (Monitor Settings) is not in the menu.
To make show do in terminal:

Code: Select all

leafpad /usr/share/applications/lxrandr.desktop

Then change the bottom line from this:

Code: Select all

NotShowIn=GNOME;KDE;XFCE;

To this:

Code: Select all

NotShowIn=GNOME;KDE;

Save the file.
That will make it show in the xfce menu: Settings > Monitor Settings
Sorry for the inconvenience, it's a mistake from me that I forgot to change it before iso release.

Fred

[saintless]

The reason I didn't use lxrander before because I didn't see it in any menu.
Even now I executed it from terminal.
From where did you envoke it?

Sorry, yes, I also can't find menu entry in OpenBox version and it is because lxrandr deb has NotShowIn line for XFCE.
Open /usr/share/applications/lxrandr.desktop with text editor and remove the line (or XFCE: from the line) and save.

Code: Select all

NotShowIn=GNOME;KDE;XFCE;

Then run in terminal update-menus and Monitor Settings will appear in Settings section.

Edit: Thanks, Fred, I didn't see your edit.

Edit2: Added in fixes post (the second thread post).

Toni

[musher0]

@saintless:

In your jwm | icewm version, how can I change the window manager
for another simple one such as wmx, aewm or echinus? (NOT a big
environment such as Mate or Gnome.)

Thanks in advance.

musher0