BusterDog + build system (no-systemd)

[fredx181]

Hi again Brenton, tested with "live-boot" now, to check the differences.

The directory /tmp is not a tmpfs filesystem (it used to be in earlier Debian versions but not anymore)

Gotta correct myself, when booting with live-boot, /tmp is a tmpfs filesystem (it is not with porteus boot).

EDIT: Strange that your code works with live-boot and not with porteus-boot, the reason may be that with live-boot you're booting with "overlayfs" rather than aufs, then it's a different case and aufs may work mounting in /tmp (not sure, I didn't test)

So, as /tmp is a tmpfs filesystem, that explains it. (booted with live-boot "union=aufs" and your script works).

as the *cow directory is always empty,

When a "persistence" save file is mounted and used, the /live/cow directory is filled.

Fred

[jbv]

Hi Fred,

Thanks for the response. I checked and you are correct about the /tmp directory with porteus and live. Strange thing is that in porteus, aufs won't overlay any of my physical hdd's either.

I spent some time today playing with all of the hdd's and controller unplugged, as the startup time with everything is quite a while when you're doing a lot of reboots. I've worked out where live keeps the *cow folder, and I've got some of my *cow scripts running with live.

Can't work out how to rebuild initrd.img which is a bit of a pain.
Right now, I'm not sure if it is coming together, or I'm getting more confused

Thanks again, Brenton

[enrique]

Hello fredx181. I have no post here since last year.

Listen I been using my android wifi host-spot as source of internet. But I want to use the USB tethering instead. I can confirm that "usb0" adapter show up. But I have not found the way to tell it to become a DHCP Client. What will be our BusterDog App to do this? In the past I used Peasy Wifi. I did try use Ethernet Tab in Peasy Wifi with usb0 adapter but no luck. Maybe rcrsn51 can help us?

I know that if I install "isc-dhcp-client" from debian I can make it work by manually running some commands. But I was wondering if we do have a default app to do usb tethering? As always thanks ahead.

[rcrsn51]

1. Open the Ethernet section and click Names.
2. Assign "usb0" to "ETH0"
3. Restart PWF and open the Ethernet section.
4. Select the new usb0 interface for DHCP and click Configure.
5. Click Check. You should see a dummy file named "usb0.dhcp".
6. Click Reconnect.

[enrique]

I did follow your instructions on a new change.dat. I works perfect. Thanks. But I do not want to lose eth0, as in fact do have a real eth0 adapter. I will asume I can do this magic with eth1 instead. Will try next.

Now just to report, may or not be important.
On my original change.dat previous of me asking here. I did try almost all step that rcrsn51 except the [Names] rename of the port. And I even try to manually change/edit configs. So I did failed. Last I did install "isc-dhcp-client".

For reasons I do not understand, peasywifi files were deleted from:
./share/pixmaps/peasywifi-24.png
./share/pixmaps/peasywifi-48.png
./share/applications/peasywifi.desktop
./local/bin/peasywifi
./local/peasywifi
./local/peasywifi/green.rc
./local/peasywifi/peasywifi

and most of /etc/pwf. Yesl like if an unistall was performed. One that I did not do? What had cause such a situation?

Edit: I did try with ETH1 and works too. I did reinstall peasywifi_4.6-3_amd64.deb.

[rcrsn51]

I did follow your instructions on a new change.dat. I works perfect.

Excellent.

But I do not want to lose eth0, as in fact do have a real eth0 adapter. I will asume I can do this magic with eth1 instead. Will try next.

Keep in mind that PWF does NOT do auto-network-detection, and you can have only ONE interface using DHCP at a time. So if you need to switch between eth0 and usb0, you would need to reconfigure.

Click the Check button and verify that you have either "eth0.dhcp" or "usb0.dhcp".

For reasons I do not understand, peasywifi files were deleted from:
./share/pixmaps/peasywifi-24.png
./share/pixmaps/peasywifi-48.png
./share/applications/peasywifi.desktop
./local/bin/peasywifi
./local/peasywifi
./local/peasywifi/green.rc
./local/peasywifi/peasywifi

and most of /etc/pwf. Yesl like if an unistall was performed. One that I did not do? What had cause such a situation?

The Control file for PWF lists isc-dhcp-client for "conflicts/replaces". I expect that when you installed isc-dhcp-client, it auto-deleted PWF. Fred would understand this better.

[fredx181]

The Control file for PWF lists isc-dhcp-client for "conflicts/replaces". I expect that when you installed isc-dhcp-client, it auto-deleted PWF. Fred would understand this better.

Yes, indeed, some packages have "conflicts/replaces", other example:. when frisbee is installed, then when installing peasywifi, frisbee will be removed and vice versa, same for isc-dhcp-client <> peasywifi or isc-dhcp-client <> frisbee, to avoid conflicts.

Fred

[enrique]

I was expecting that the problem was my installation of "isc-dhcp-client". Thanks for confirming this.

I am in another dilemma. This time with HDMI Audio setup. To be honest here is where I have almost 0% experience as previous of puppy I never had to deal with this.

Now in peebee's Bionic18.05 after many trial and error I did got audio using retrovol settings. And in fact after many trials I even make it work once on my HTPC running BusterDog64. As you may recalled it is my Satellite Home Theather. Well my hardware failed. In fact it broke. So now I need to reinstall in my previous PC. And I do not recall what I did to make it work. I bet you installing retrovol or any of those packages.

But before I do more nonsence trial and error. I will like to ask what is the proper way to set my HDMI audio. Can you help me. Thanks.

[rcrsn51]

Sound-Card-Selector from here. See the note at the bottom about HDMI.

[enrique]

fredx181's Busterdog have the apps; sound-card-selector & alsamixer.

You must UNmute the S/PDIF controls in Alsamixer (use the M key).

This was the step I was missing. Wao, as always you guys make me feel like a child between giants.

I have to confess something. When I was straggling looking for a reliable puppy build system I saw your "Create Debian 9 (Stretch) minimal ISO similar to DebianDog". But it had over 100 pages. So without reading anything I wrongly pass the page!. Then I was point out to come here "BusterDog + build system (no-systemd)". And I made BusterDog my preferred puppy distro. But rcrsn51 you have a wonderful thread there with so many goodies. Keep the good work.

[enrique]

What about if I want to change cards but do not what to restart Buster!!

I found the basic commands:
alsactl init
alsactl restore
or restarting the service with
/etc/init.d/alsa-utils restart

Any Idea what is best approach after changing cards?

[rcrsn51]

What about if I want to change cards but do not what to restart Buster!!

Are you talking about switching from HDMI to analog?

The whole point of Sound Card Selector is that you select the card-device numbers for the other card and enter them into your ~./asoundrc file.

You are switched. You can verify this by playing some audio.

Please get the latest version so we are talking about the same thing.

[enrique]

Yesterday I was saying same thing. I am having hard time making people to understand my point. I need to see how to improve that. Here we go.

For the most part my own PC's work nicely with what you had teach me. In this case Sound Card Selector & alsamixer. Clearly I do not change their setups, my PCs are are static.

Now I am starting to teach my sister of the benefits of Puppy/BusterDog. And here is where I have trouble. As expected when we try to show off then the Devil is waiting to make our life difficult. She has a laptop that she moves around. So as default she has her default sound card selected. Then when she wants to see a movie, her Buster was boot with original sound card. Then she hook HDMI to TV. Now she uses Sound Card Selector to switch to second card. .asoundrc is updated. alsamixer has unmute S/PDIF. But sound will not go thru HDMI. Not unless she reboots Buster. To restore she has to reboot too. This creates a bad impression on her about Buster.

So last night I was looking into solutions. Found:

Code: Select all

alsactl init
alsactl restore
or restarting the service with
/etc/init.d/alsa-utils restart

But I have no chance to experiment on her laptop yet. Next time I see her I will do.

[Max Headroom]

of DevuanDog Based Simplicity Linux Mini 20 1RC1 on an eXt3 Formatted sda2 Partition w/ grub4dos. I'm trying 2 Create a Persistent saveme Folder, But in vain! I've Read the New Porteus Boot 4 Puppies Thread but alas a solution eScapes me. I'm Confused about the meaning of SysVinit & of course I've Searched the Forum & the iNet.

I've Created a saveme Directory in the Root of sda2 & also inside the live Directory which iz also on the same level & eXecuted Create SaveFile under DDog Special...

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

title SimplicityLinuxMini'20-1RC1 - saveme to /live/ sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ noauto saveme=/live/
initrd /live/initrd1.xz

title SimplicityLinuxMini'20-1RC1 - Always Fresh sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ nomagic base_only norootcopy
initrd /live/initrd1.xz

title SimplicityLinuxMini'20-1RC1 - Copy to RAM sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 noauto from=/ copy2ram
initrd /live/initrd1.xz

title DDog - live-boot-3 (default Debian) Persistence saveme sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin union=aufs
initrd /live/initrd.img

Please Help!

WinkK

[enrique]

1rst I am newbee, so I may be wrong.

I did too had problems at the beginning with my BusterDog. Now it is working. I am newbee & I also have 0% experience with DevuanDog so I
may be wrong.

But assuming "Persistent Porteus Boot save Folder" in DevuanDog behave like BusterDog lets see what I can suggest.

Code: Select all

https://raw.githubusercontent.com/DebianDog/DevuanDog/master/Examples-boot-codes.txt

There you can read:

Code: Select all

Two boot methods available:
1. DevuanDog 'boot style Porteus' - porteus initrd1.xz made for debian kernel and firmware. + encrypted save file option.
(recommended if you are familiar with puppy or porteus boot options)
2. DevuanDog live-boot-3x - debian initrd.img created with initramfs-tools-v3.x. + encrypted save file/partition option.

DevuanDog Based Simplicity Linux Mini 20 1RC1 on an eXt3 Formatted sda2 Partition w/ grub4dos...

I had ONLY played with 1. 'boot style Porteus' so ignoring that you said

I'm trying 2 Create a Persistent saveme Folder

Let me show you what I do using my buster files as example. My Linux ext partition will contain:

Code: Select all

8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
\live\
      \base\
      \changes\
      \modules\
      \optional\
      \rootcopy\
      \01-filesystem.squashfs
      \buster-i486.sgn
      \buster-x86_64.sgn
      \initrd1.xz
      \k-4.19.0-6-amd64.squashfs
      \vmlinuz1

NOTE: the folder \live\changes\ will contain your permanent files.

I guess for # menu.lst produced by grub4dosconfig-v1.7

Code: Select all

title SimplicityLinuxMini'20-1RC1 
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ noauto changes=/live
initrd /live/initrd1.xz

For # menu.lst produced by grub4dosconfig-v1.9.3

Code: Select all

title SimplicityLinuxMini'20-1RC1 
find --set-root uuid () 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ noauto changes=/live
initrd /live/initrd1.xz

For Ubuntu grub2

Code: Select all

menuentry "title SimplicityLinuxMini'20-1RC1"{ 
	search --no-floppy --fs-uuid --set=root  8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
	linux	/live/vmlinuz1 from=/ noauto changes=/live
	initrd	/live/initrd1.xz
}

I never try live-boot-3x I guess it is time to make a test for my self.
From what I read it should be similar.

Code: Select all

1) To save changes you need to create save file persistence or ext partition with label persistence
+ adding persistence.conf file inside.
2) You need to have persistence in kernel boot line otherwise no save file will be used.

If I get a success, I let you know. Hope I had help you.

[enrique]

To try live-boot-3x I used gparted and created new partition ext4 sad9. I change label to "persistence" and added empty file name persistence.conf

Code: Select all

sda9
\persistence.conf
\live\
      \persistence.conf
      \base\
      \changes\persistence.conf
      \persistence\persistence.conf
      \modules\
      \optional\
      \rootcopy\
      \01-filesystem.squashfs
      \buster-i486.sgn
      \buster-x86_64.sgn
      \initrd1.img
      \k-4.19.0-6-amd64.squashfs
      \vmlinuz1

As you see I try to add new folders, and even copied persistence.conf to many places in my attempt to make it work. The OS will but but no permanent folder for changes are stored.

Code: Select all

title BusterDog live-boot-3x (sda1)
root=(hd0,9) 
kernel /live/vmlinuz1 boot=live config persistence swapon quickreboot noeject showmounts union=aufs
initrd /live/initrd.img 

So me to I failed.

[Max Headroom]

Thanx enrique 4 your eFforts, I'm Not having any joy either...

;-)K

[fredx181]

@Max

title SimplicityLinuxMini'20-1RC1 - saveme to /live/ sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ noauto saveme=/live/
initrd /live/initrd1.xz

If you have created "saveme" folder in "live" then it should be pointed to in menu.lst, so this should work then (using changes=....):

Code: Select all

title SimplicityLinuxMini'20-1RC1 - changes to /live/saveme sysvinit
uuid 8d4fde2c-4ee0-4b72-86f0-0f601fc3435a
kernel /live/vmlinuz1 from=/ noauto changes=/live/saveme
initrd /live/initrd1.xz

EDIT: Changed saveme= to changes=

@enrique
About live-boot persistence: the persistence.conf shouldn't be empty, try with this inside :

Code: Select all

/ union

Followed by a new empty line.
Sorry for the confusion, this should be stated in the Examples-boot-codes.txt

EDIT: Also a "persistence" save file should contain a (not empty) persistence.conf
Btw, persistence.conf has many options, see:
https://manpages.debian.org/testing/liv ... .5.en.html

Fred

[Max Headroom]

Thanx Fred, that did the Trick!

;-)K

[Max Headroom]

Sorry Fred 2 bug yoU again, I've installed this DDog again ( it's pretty good! ) on a Different PC Dual Booting w/ the Cursed M$ windoze X, Frugally on the NTFS Partition. But the Create SaveFile isn't working. it indicates that it iz Creating saveme.dat on my USB Flash Dr that I've Booted from, rather than sda2/live/ on the Laptop Hard Dr. But it doesn't! ( my intended work around wood have been 2 simply move it there from me USB Flash Dr ) & also I'm not given a choice of where 2 Create the saveme.dat File.

Also when I ReBooted the DDog I lost M$ windoze 10 ( it's Gone AWOL from the menu.lst ), I Suppoze it Natively Boots from the Hidden sda1 Partition, But I don't know which File & How 2 Edit & Merge them.

Please Help, Thanx

;-)K