BusterDog + build system (no-systemd)

[dancytron]

Boot pfix=ram can't be used in Debian Dog.

The same thing can be accomplished by simply removing the "changes=[whatever]" entry. edit :In porteus boot. Debian boot is different.

There are sample explanations of the basic booting setups in the top directory of the iso file.

[backi]

Hi Dancytron !
Booting without changes can be done .
One Example for XENIALDOG i am using .

Booting always fresh Mode :

title XENIALDOG - Always fresh
find --set-root /XENIALDOG/casper/vmlinuz
kernel /XENIALDOG/casper/vmlinuz from=/XENIALDOG noauto nomagic base_only norootcopy
initrd /XENIALDOG/casper/initrd1.xz

This works with Xenial or Bionic Dog (so the UBUNTU Dogs):
Probably does work for the Debian Dogs ..........but have to be appropriately modified for the Debian Dogs .....casper has to replaced with live....and so on .
Probably the Line "noauto nomagic base_only norootcopy" does the magic when applied to the Grub4dos menu.lst to boot without savings .
Not sure .
Therefore we need to know what Grubloader Keniv is using and how the menu.lst looks like .
But it is more easily done as you described .
All those Problems can be avoided by placing the live Folder onto a ext/2/3/4 Partition ......less complicated ......more common .

[dancytron]

Here are my BusterDog menu.1st Grub4dos entries.

#More linux manual frugal installs

title BusterDog (sda2) noauto from=/BusterDog/ changes=EXIT:/BusterDog/ save changes on exit
root (hd0,1)
kernel (hd0,1)/BusterDog/live/vmlinuz1 noauto from=/BusterDog/ changes=EXIT:/BusterDog/
initrd (hd0,1)/BusterDog/live/initrd1.xz

title BusterDog copy2ram (sda2) noauto from=/BusterDog/ changes=EXIT:/BusterDog/
root (hd0,1)
kernel (hd0,1)/BusterDog/live/vmlinuz1 noauto copy2ram from=/BusterDog/ changes=EXIT:/BusterDog/
initrd (hd0,1)/BusterDog/live/initrd1.xz

title BusterDog for upgrade (sda2) noauto from=/BusterDog/ changes=/BusterDog/ save changes as they are made
root (hd0,1)
kernel (hd0,1)/BusterDog/live/vmlinuz1 noauto from=/BusterDog/ changes=/BusterDog/
initrd (hd0,1)/BusterDog/live/initrd1.xz

title BusterDog (sda2) No Changes from=/BusterDog/
root (hd0,1)
kernel (hd0,1)/BusterDog/live/vmlinuz1 noauto from=/BusterDog/
initrd (hd0,1)/BusterDog/live/initrd1.xz

[backi]

Hi Keniv !
No need to do a full Install of BusterDog !

The two drives are respectively 40 and 20MB.

Two Drives or Partitions ?
Are you sure ....not 40 GB and 20 GB ?
I assume your BusterDog is on the 40GB ntfs Partition ????

How did you partition the 20 Gb Partition ?

Post your menu.lst

@dancytron
You have ext2/3/ or /4 Partitions ....therefore you can use changes Folder .
Keniv is using a changes.dat File (probably) either on a fat or ntfs Partition

It is better recommended for Keniv placing/transplanting his Buster Dog live Folder to an ext2/3/4 Partition, if possible.....to use a changes FOLDER (instead a changes.dat FILE) ,to get better Support .

[keniv]

Hi All

@backi

Two Drives or Partitions ?
Are you sure ....not 40 GB and 20 GB ?

Yes your quite right. Two drives. One 40GB the other 20GB My bad.

This is what I've tried tonight. I renamed my working changes.dat to changes1.dat. I rebooted busterdog and got a report that changes.dat could not be found. I was able to continue booting by pressing a key (I had seen this before). This allowed me to boot into a 'fresh' copy of busterdog. I setup wifi, locals and keyboard then elected to make a new savefile. I made it 500MB and named it changes.dat. This seemed to go well and when completed I shutdown. I saw the usual messages on screen and after saving the session the machine shutdown. I then renamed this new savefile to changes2.dat and my original savefile back from changes1.dat to changes.dat. I then rebooted busterdog which used the original savefile. This meant the new file I had made now named changes2.dat was unmounted as Fred suggested it had to be in order to resize it. I resized this file by 100MB but again I am not convinced it worked. Producing a 500MB savefile takes some time. Adding another 100MB probably took about a second. If I look at the properties of changes2.dat I get

Total size of files=600MB
Size on disk=500MB

Which again suggest to me it has not worked. I hope all of the above makes sense to you.

Regards,

Ken.

[backi]

Hi Keniv !

Total size of files=600MB
Size on disk=500MB

Would mean there is no space left on that (40Gb) Partition .
You`re sure ?

I assume your Windows installation and your BusterDog is on the 40Gb ntfs Partition .....yes or no ?
On which Partition is your BusterDog Installation and the live Folder ?
post your menu.lst please .

What about your 20Gb Partition ....how formatted ?.....how much free Space ?

[fredx181]

Adding another 100MB probably took about a second

That's normal I guess, same for me, it goes too quick to see the progress bar.
Btw, I updated resize-save-file package, now it refuses to resize a mounted savefile, so works only with savefile that's not in use.

Code: Select all

apt install resize-save-file

To see if it's mounted (in use) look at the output of:

Code: Select all

losetup -a

To see if it shows the name and path of your savefile
Also it probalbly says "/dev/loop2"
To see size and available look at "/dev/loop2" at:

Code: Select all

df -m

(it doesn't lie)

Below is in case you use grub4dos bootloader:

To be able to use e.g. changes1.dat changes2.dat etc.. you need to edit (add new entry to) your bootloader config e.g. menu.lst (grub4dos),:
example pointing to changes1.dat :

Code: Select all

title busterdog64
 root (hd0,0)
 kernel /31119busterdog/live/vmlinuz1 from=/31119busterdog noauto changes=/31119busterdog/live/changes1.dat
 initrd /31119busterdog/live/initrd1.xz

change (hd0,0) to what it is for you (copy from already existing entry, maybe it's: uuid ....)
EDIT: edited above according to the path: /31119busterdog/ as I noticed in your earlier post
See also dancytron's post for example of multiple entries in menu.lst :
http://murga-linux.com/puppy/viewtopic. ... 18#1041218

Setting up a savefolder is very easy in your case because you have Ubuntu Mate partition, suitable for savefolder.
Create a folder with unique name on the root (/ where bin,boot,etc are) on that Ubuntu partition, say for this example "b_dog" (there should not be a folder with same name on other partition), then on the kernel line edit the changes= part:

Code: Select all

changes=/b_dog

It should be found because it's unique name and inside b_dog there will appear a "changes" folder (if all is well )
EDIT: As mikeslr said, Ubuntu doesn't care (or even know) about that folder on it's root (/)

Fred

[fredx181]

Added 10+ updated packages that Bill (rcrsn51) kindly contributed to the BusterDog repository, thanks Bill !
https://doglinux.github.io/busterdog/

Fred

[fredx181]

Forgot to mention earlier:
The antiX and MX repositories can be enabled in /etc/apt/sources.list
By default disabled:

Code: Select all

#deb http://la.mxrepo.com/antix/buster buster main nonfree
#deb http://mxrepo.com/mx/repo/ buster main non-free

Enable by removing the "#" e.g:

Code: Select all

deb http://la.mxrepo.com/antix/buster buster main nonfree

and update the package lists:

Code: Select all

apt update

These repos often contain newer versions and/or extra packages.
I didn't test much, use at your own risk, there may be conflicts with the custom repository packages.

Fred

[dancytron]

One bug. the .desktop file for synaptic didn't work. Changed the exec line from "Exec=synaptic-pkexec" to "Exec=synaptic" and that fixed it.

Uninstalled Palemoon, did a few misc things, and then remastered. That went fine.

Then went to install nvidia drivers. Installed bleachbit mesa-utils mesa-utils-extra. Ran "glx-gears -info" to confirm nouveau driver was running.

Then installed and ran nvidia-detect, which told me what I already knew, which is what driver I needed.

Following the directions from Stretch, I then ran.

"apt install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//') nvidia-legacy-340xx-driver"

Which worked flawlessly. I saved the console output if anyone is interested for some unknown reason.

Rebooted, ran "glxgears -info" and it is working.

I searched for and found the 3 files starting with "linux-header" in synaptic and uninstalled them.

Seems to be working fine. I am sure there is other stuff I could uninstall for space, but I am not going to bother, at least for now.

edit: Somehow I managed to break it and now it fails when loading the x-server. I'll step back and see if I can figure out what I did.

[keniv]

Hi All,
I've followed Fred's instructions above.

apt install resize-save-file

Here's the output I get so I don't think I've installed anything or have I missed something.

Code: Select all

root@live:~# apt install resize-save-file
Reading package lists... Done
Building dependency tree       
Reading state information... Done
resize-save-file is already the newest version (1.0.0-2).
The following packages were automatically installed and are no longer required:
  ccrypt libnotify4
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded

losetup -a

Here's the output

Code: Select all

/dev/loop1: [2049]:32341 (/mnt/live/mnt/sda1/31119busterdog/live/01-filesystem.squashfs)
/dev/loop2: [2049]:31896 (/mnt/live/mnt/sda1/31119busterdog/live/k-4.19.0-6-686-pae.squashfs)
/dev/loop0: [2049]:104 (/mnt/live/mnt/sda1/31119busterdog/live/changes.dat)

Am I right in thinking this means the savefill is mounted?

df -m

Here's the output

Code: Select all

Filesystem     1M-blocks  Used Available Use% Mounted on
tmpfs                846     2       844   1% /mnt/live
devtmpfs              10     0        10   0% /dev
/dev/sda1          38155 20428     17727  54% /mnt/live/mnt/sda1
/dev/loop0          1937   979       843  54% /mnt/loop0
aufs                1937   979       843  54% /
/dev/loop1           218   218         0 100% /mnt/live/memory/images/01-filesystem.squashfs
/dev/loop2            38    38         0 100% /mnt/live/memory/images/k-4.19.0-6-686-pae.squashfs
tmpfs                170     1       169   1% /run
tmpfs                  5     1         5   1% /run/lock
tmpfs                339     0       339   0% /dev/shm
cgroup                 1     0         1   0% /sys/fs/cgroup
tmpfs                170     1       170   1% /run/user/0

I guess this tells me what I want know about my savefile.

Code: Select all

/dev/loop0          1937   979       843  54% /mnt/loop0

I have also made a savefolder on the 20GB ext3 disk on which Ubuntu resides and I tested this new savefolder to check it's working. I have retained my 2GB savefile on the 40GB ntfs disk on which XP and the frugal installs of pups and BustedDog reside. Probably the only difference between Fred's instructions and my setup is I use Ubuntu's version of grub (grub2 I think). I now have two entries for BusterDog. One to boot using the savefile and the other to boot from the savefolder. I have removed DevuanDog as BusterDog will replace it. I've also removed the 500/600MB extra changes.dat file. One advantage I already see with the savefolder is that it will not need 'resizing'.

Regards,

Ken.

[fredx181]

apt install resize-save-file

Here's the output I get so I don't think I've installed anything or have I missed something.

Sorry, I should have said that the package lists needs updated first (apt update), without it, it sees 1.0.0-2 as newest , so do (to install 1.0.0-3):

Code: Select all

apt update
apt install resize-save-file

Code:
/dev/loop1: [2049]:32341 (/mnt/live/mnt/sda1/31119busterdog/live/01-filesystem.squashfs)
/dev/loop2: [2049]:31896 (/mnt/live/mnt/sda1/31119busterdog/live/k-4.19.0-6-686-pae.squashfs)
/dev/loop0: [2049]:104 (/mnt/live/mnt/sda1/31119busterdog/live/changes.dat)

Am I right in thinking this means the savefill is mounted?

Well, yes, it says that your changes.dat is mounted and therefore cannot be resized, so this way you can resize another, e.g. changes1.dat (if exist)

I guess this tells me what I want know about my savefile.
Code:
/dev/loop0 1937 979 843 54% /mnt/loop0

Yes, correct.

One advantage I already see with the savefolder is that it will not need 'resizing'.

Congrats ! Much more convenient.

Fred

[fredx181]

One bug. the .desktop file for synaptic didn't work. Changed the exec line from "Exec=synaptic-pkexec" to "Exec=synaptic" and that fixed it.

Thanks, will fix in next ISO.

edit: Somehow I managed to break it and now it fails when loading the x-server. I'll step back and see if I can figure out what I did.

Always good to know how to break things !

Fred

[keniv]

Hi Fred,

Sorry, I should have said that the package lists needs updated first (apt update)

Yes I should have thought of that. Now installed.
Thanks again,

Ken.

[Null_ID]

Hello. This post is just to report, that after giving BusterDog 64-bit a spin (frugal from an SDHC card), everything works smoothly, except for a piece of missing firmware for my wireless, which luckily was fixed by taking it from the "99-firmware-BusterDog-2019-01-10.squashfs" which fredx181 also kindly offered, so no biggie. The bothersome missing firmware was the iwlwifi-1000-1 to iwlwifi-1000-5 series for Intel's Centrino Wireless-N 1000 [Condor Peak], on a Thinkpad T510i target machine.

Now that this is fixed, everything else seems to be working, so it looks like you delivered another winner, Fred. Do keep 'em coming as long as possible, your Dog-series at this time seems to be the only hassle free way to use Chrome-based browsers in a Puppy-like system, after they got really uptight with their stance on user privileges. Also nice for the TOR-browser for the same reason. And apt-get access is a blessing.

This has been a post from a BusterDog-running system. Take care now, ya hear.

[AndresC2]

Hi Fred : )

Congratulations for BusterDog!!!

[fredx181]

Thanks Andres !!

I see now that you edited your post by removing the subject about converting from systemd to elogind on standard buster, did you solve it ? (if so, how ?)

Fred

[AndresC2]

Hi Fred

No my friend

when try install firefox ask for libgtk-3-0

then i have that install libgtk-3-0 for get firefox

works with some apps if install firts libgtk2 + adwaita-icon-theme but
is trial and error.

when install elogind from antix repo, that remove libsystemd and break apt.

how do you did it with busterdog?

maybe anticapitalista can help.

still with runit

sorry i can not help very much.

bye and good luck.

[fredx181]

Hi Andres,

Yes it's a bit of a puzzle.
When building with debootstrap, once in chroot after the debootstrap process, I added on top the Busterdog repo in sources.list, e.g. 32 bit:

Code: Select all

deb [trusted=yes] https://github.com/doglinux/busterdog/raw/master/i386/ ./

(EDIT: added [trusted=yes] above, otherwise won't work.)
Followed by "apt update"
Add a file "00systemd" in /etc/apt/preferences.d/ with content:

Code: Select all

Package: *systemd*
Pin: origin ""
Pin-Priority: -1

And then first install sysvinit-core and the elogind packages (before installing any other):

Code: Select all

apt install sysvinit-core elogind libelogind0 libpam-elogind libpam-elogind-compat dbus-x11

EDIT: Added dbus-x11 later (seems required also)
That's how it works for me to avoid systemd.
Probably it works also when adding the AntiX repo instead of Busterdog repo, but didn't test that.

=======================================================

On a already existing install, (with systemd and libsystemd0 installed) more tricks are required.
Install sysvinit-core (will not completely remove systemd)

Code: Select all

root@live:~# apt install sysvinit-core
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libip4tc0 systemd
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  initscripts insserv startpar sysv-rc
Suggested packages:
  bootchart2 bootlogd
The following packages will be REMOVED:
  libpam-systemd systemd-sysv
The following NEW packages will be installed:
  initscripts insserv startpar sysv-rc sysvinit-core
0 upgraded, 5 newly installed, 2 to remove and 0 not upgraded.
Need to get 402 kB of archives.
After this operation, 288 kB of additional disk space will be used.
Do you want to continue? [Y/n] 

Then REBOOT ! (with changes saved)
After that you can install the elogind packages:

Code: Select all

apt install elogind libelogind0 libpam-elogind libpam-elogind-compat dbus-x11

(and all systemd related should be removed then)
EDIT: Added dbus-x11

I don't understand the issue you have with firefox and libgtk-3-0, anyway I have no problems with that.

Good luck !

EDIT: You may also want to install eudev (will replace udev)

Fred

[AndresC2]

Bravo fred

Debian Buster Standar

add sources.list:
deb http://ftp.us.debian.org/debian experimental main ( this install libpam-elogind-compat )
Followed by "apt update"

Add a file "00systemd" in /etc/apt/preferences.d/ with content:
Package: *systemd*
Pin: origin ""
Pin-Priority: -1

And then first install sysvinit-core and the elogind packages (before installing any other):
Code:apt install sysvinit-core elogind libelogind0 libpam-elogind libpam-elogind-compat dbus-x11

firefox-esr work fine
lxde work fine

thank you so much fred!!!