DebianDog - Jessie (21 June 2017)

[saintless]

Hi, Fred.
Lets keep lxinputsave then and mod lxinputsave if something changes in official lxinput package upgrades later.

Toni

[davids45]

G'day saintless,

Thanks for your edited script which fixed the icons for my sdb drive shown by the mounter wizard.

I tried raising the row of desktop/pinboard partition icons by changing the y value you said. I can see the start of the row by changing the x value. The row did move up the display for a new y but there was no wrapping - the line of partition icons still goes off the right side of my 1600x900 monitor.

Which is another small problem. The Jessie default for my radeon graphics card is 1280x1024 which distorts the display a little. I could not get the video wizard to load the 1600x900 setting (which was showing as 'recommended' before I hit <Enter> to use it) but then only the 1280 display would show or the computer freeze (no X).

Thanks again,
David S.

[saintless]

Hi David S.

The row did move up the display for a new y but there was no wrapping - the line of partition icons still goes off the right side of my 1600x900 monitor.

I don't see any settings to make the drive icons appear in two rows in pup-volume-monitor or desktop-drive-icons configuration files. I will search for some kind of solution and post if I can find one. If you don't have the same problem in Puppy my guess is Debian structure makes pup-volume-monitor or desktop-drive-icons to behave different. Or the problem is related with the missing radeon driver from DD.

The Jessie default for my radeon graphics card is 1280x1024 which distorts the display a little. I could not get the video wizard to load the 1600x900 setting (which was showing as 'recommended' before I hit <Enter> to use it) but then only the 1280 display would show or the computer freeze (no X).

I guess video-wizard means lxrandr (monitor settings)? We do not have xorg-wizard or video-wizard in DD. Unfortunately I can only point you to the official and unofficial sources how to install or build radeon driver:
https://wiki.debian.org/ATIProprietary
https://wiki.debian.org/AtiHowTo
http://murga-linux.com/puppy/viewtopic. ... 519#791519
http://wiki.cchtml.com/index.php/Debian
I don't have the needed hardware to test and build radeon driver for each kernel but maybe someday we will find someone who will be interested enough from DD to offer such help.

Toni

[saintless]

First post updated with download links for SMP kernel-3.16.0-4-686-pae iso images.
Uploaded here:
http://kazzascorner.com.au/saintless/De ... og-Jessie/
Jessie and Wheezy dd-repository updated with lxinputsave deb package. Installing lxinputsave will install also lxinput saving the settings after reboot or exit X.

Toni

[anikin]

First post updated with download links for SMP kernel-3.16.0-4-686-pae iso images.
Uploaded here:
http://kazzascorner.com.au/saintless/De ... og-Jessie/...

The download speed is prohibitively low and this kazza is virtually unusable. I must have missed the related discussion again - what's happened to smokey? I've never had issues downloading DD stuff from his site, or from other places you keep it at.

Can DD users just install this 686-pae kertnel https://packages.debian.org/jessie/linu ... -4-686-pae themselves instead of downloading the ISO? I tried and failed to install it via apt-get. Neither, can I do upgrade and dist-upgrade this DD. I get the same errors, that I reported earlier. Installing a kernel and upgrading in Debian Jessie is a relatively simple procedure, though.

[saintless]

The download speed is prohibitively low and this kazza is virtually unusable. I must have missed the related discussion again - what's happened to smokey? I've never had issues downloading DD stuff from his site, or from other places you keep it at.

Virtually unusable is your disrespectful behavior and your Internet Service Provider;



This change is made because the 2Gb space provided from Smokey is almost full with Wheezy files and Kazza was very kind to offer in DD-Wheezy thread 10Gb ftp hosting space (which is the only one suitable for me for DD development) + 10Gb from her megaupload account for final iso images anytime I like to mirror there.
Since I don't read any offer from you for 20Gb free hosting I see no reason to discuss this subject with you.

Can DD users just install this 686-pae kertnel https://packages.debian.org/jessie/linu ... -4-686-pae themselves instead of downloading the ISO? I tried and failed to install it via apt-get.

Yes, DD user can install it in no time. I don't know why you can't:

Code: Select all

root@debian:~# apt-get install linux-image-3.16.0-4-686-pae
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  linux-doc-3.16 debian-kernel-handbook grub-pc extlinux
Recommended packages:
  irqbalance
The following NEW packages will be installed:
  linux-image-3.16.0-4-686-pae
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 33.3 MB of archives.
After this operation, 121 MB of additional disk space will be used.
Get:1 http://security.debian.org/ jessie/updates/main linux-image-3.16.0-4-686-pae i386 3.16.7-ckt9-3~deb8u1 [33.3 MB]
Fetched 33.3 MB in 22s (1459 kB/s)                                             
Preconfiguring packages ...
Selecting previously unselected package linux-image-3.16.0-4-686-pae.
(Reading database ... 58832 files and directories currently installed.)
Preparing to unpack .../linux-image-3.16.0-4-686-pae_3.16.7-ckt9-3~deb8u1_i386.deb ...
Unpacking linux-image-3.16.0-4-686-pae (3.16.7-ckt9-3~deb8u1) ...
Setting up linux-image-3.16.0-4-686-pae (3.16.7-ckt9-3~deb8u1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-686-pae
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.
root@debian:~# 

Now imagine you did this from porteus-boot saving in /live/changes directory as I did it to post this example. How are you going to boot again with the new kernel since the new generated /boot/initrd.img-3.16.0-4-686-pae is for live-boot and it can't read /live/changes directory where /lib/modules/3.16.0-4-686-pae is installed from porteus-boot? The solution is easy but I will let you find it yourself.
DebianDog is live system using 3 different boot methods and needs modding live-boot2 and porteus-boot initrd after changing the kernel. Since you can't do it yourself there is no reason to ask why I made PAE iso version.

Neither, can I do upgrade and dist-upgrade this DD. I get the same errors, that I reported earlier. Installing a kernel and upgrading in Debian Jessie is a relatively simple procedure, though.

I already posted the log from DD-Wheezy upgrade to Jessie here specially for you but you have missed this again I guess.
Other people also reported upgrade from DD-Wheezy to Jessie without troubles.
I can't say why you can't do it from DD-Wheezy but I and other people can.
If by "this DD" you mean DebianDog-Jessie, the only upgradable package from today is ntfs-3g:

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 will be upgraded:
  ntfs-3g
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 531 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 

Type y and hit Enter to upgrade it. I'm sure it will be upgraded without errors for you too.
I know you are not happy because we do not follow your point of view how to build from scratch DebianDog-Jessie, but please, find different way to release your anger or build your own and better Jessie version and show it to the world.

[saintless]

Uploaded development tools (DEVX) module: 061-DEVX-DebianDog-Jessie.squashfs
Available for download from sfs-get or from Extra-modules section.
Linux-headers for both kernels included. List of installed packages (+ not listed dependencies):

Code: Select all

build-essential automake autoconf libtool pkg-config libcurl4-openssl-dev intltool libxml2-dev libgtk2.0-dev libnotify-dev libglib2.0-dev libevent-dev checkinstall upx-ucl cmake linux-headers-3.16.0-4-686-pae linux-headers-3.16.0-4-586 BaCon

Toni

[Moat]

Code: Select all

apt-get update
apt-get install lxinputsave

Thanks Fred and Toni - the above GUI appears to be working well (although still on LiveCD, testing).

Bob

[anikin]

Virtually unusable is your disrespectful behavior

Overblown BS in its purest form - show me a single disrespectful word in any of my posts.

I know you are not happy because we do not follow your point of view how to build from scratch DebianDog-Jessie, but please, find different way to release your anger or build your own and better Jessie version and show it to the world

I will say it again. My only point is, that upgrading DD Wheezy and presenting the result as DD Jessie is cheap. I don't impose anything on anyone here. I have absolutely no ambitions to show my builds to anyone. 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. The 3 boot methods - live-boot-2 belongs to Squeeze and has been deprecated. Using it in Wheezy/Jessie is wrong and unwarranted.

[mcewanw]

I absolutely don't understand what this 'fight' about the creation method of Debian-Jessie is all about. Anyone using DebianDog in any shape and form is benefiting from thousands of hours of hard work from Toni and Fred. 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?

Older methodologies, can have merits that bring them back into the limelight again - and why not. If the distribution basically uses the same system libraries etc and package system such that Jessie documentation applies to it Jessie then that's all that is important to me (and most others I would think).

Of course it can be useful to point out any minor differences since such comments can be taken into account. But I see nothing helpful in aggressively claiming this or that is 'wrong' or somehow deceitful or that some other build method somehow produces a superior in terms of 'purer' system. People are free to use whatever Debian or Debian-based systems or build methods they wish - so what?

Main thing is: many thanks are due, I feel, to Toni and Fred for providing this alternative route to Debian with the so many advantages of DebianDog being a Puppylike system full of useful Puppylike tools and accessories - that's why I use it anyway.

[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