BusterDog + build system (no-systemd)

[ralcocer]

I got audio working but I have to login as guest first and then login as root and I get audio. Now I work with 3D printing software In I cannot get Slic3r to work anybody out there who does 3d Printng?

[Kennel Dweller]

Yep. I do 3D printing among other things. Using the slic3r appimage works well for me and integrates with Pronterface without issue, also slic3r-prusa works from apt without redirecting files.
https://dl.slic3r.org/linux/

[ralcocer]

How do I compile linux for burterdog bullseye?

[fredx181]

How do I compile linux for burterdog bullseye?

You are nominated for the prize for the most un-clear question

[ralcocer]

Thank you for the honor, all I want to know is if I compile a newer Linux kernel do I have to use anything special to make it work with bullseye

[fredx181]

Thank you for the honor, all I want to know is if I compile a newer Linux kernel do I have to use anything special to make it work with bullseye

Still not really clear to me as you posted in the Busterdog thread, and asking about Bullseye, so I ask:
Is it for a build that you used the Bullseye build script for and you want to compile your own kernel for that ?

[AndresC2]

Hi Fred, happy holidays and a happy new year !!!

can you help me with this please.

this code work good with unionfs

unionfs-fuse -o nonempty -o allow_root -o cow /run/live/overlay/rw=RW:/run/live/rootfs/01-filesystem.squashfs=RO /tmp/merged

with this code I merged changes in overlay in filesystem.squash

now I want try with overlayfs the same code and merged /run/live/overlay/rw with 01-filesystem.squashfs
with overlayfs.

I find this:

mount -t overlay overlay -o lowerdir=/lower,upperdir=/upper,workdir=/work /merged

but how works?

by the way is better overlay that unionfs-fuse?

Thanks.

[fredx181]

Hey Andres, thanks, wish you a great 2022 too !

I may be able to help, but not sure that I understand, is it sort of remastering you are trying to do ? (merging the changes with the main .squashfs)
Are you booting with overlay already ? (or aufs ?)

[AndresC2]

Hi Fred

yes is a remaster, build debian buster with debootstrap only core + mc wifi,
then reboot and later add xorg + jwm etc, and remaster with overlayfs in a new 01-filesystem

I booting with overlay only

I want merged /run/live/overlay/rw with 01-filesystem.squashfs

thanks

[fredx181]

Hi again Andres ,
Although I didn't test on system using "live-boot" (as I think you run with), I guess that the following should work for you (but perhaps needs some adjustments):

Code: Select all

LOWERDIR="/run/live/rootfs/01-filesystem.squashfs"
UPPERDIR=/run/live/overlay/rw
WORKDIR=/run/live/overlay/work # workdir is required, I think it must be at the same level as UPPERDIR
mkdir -p $WORKDIR
MERGED=/tmp/merged  # or change path to a real (mounted) linux partition, e.g /mnt/sda2/merged if not working  
mkdir -p $MERGED
mount -t overlay -o upperdir=$UPPERDIR,lowerdir=$LOWERDIR,workdir=$WORKDIR OVlay $MERGED

For info, if the changes contains "masked" files (deleted files included in the main 01-filesystem.squashfs) these will not apply, so then it will not work properly this way of remastering.
If no deletions, only additions or changed files in the "changes" it probably will be ok.
EDIT: How I would do a (very basic) remaster, for example (best to do from a 'actual' partition e.g. sda2, not from the virtual filesystem):
mksquashfs / 01-filesystem-remaster.squashfs -wildcards -e media/* dev/* mnt/* proc/* sys/* run/* tmp/* tmp/.*
(or add more to it to exclude (after -e ... ...) e.g. boot/* or/and var/cache/*)

[AndresC2]

Hi Fred!

thanks, works fine the overlay script.

and yes is a live-boot remaster.

about this:

mksquashfs / 01-filesystem-remaster.squashfs -wildcards -e media/* dev/* mnt/* proc/* sys/* run/* tmp/* tmp/.*

I try later.

thanks so much fred see you.

[dancytron]

I just noticed this, but in /etc/hosts it has:

Code: Select all

127.0.0.1	 localhost
127.0.1.1	 live

Am I missing something, or should it be:

Code: Select all

127.0.0.1	 localhost
127.0.0.1	 live

I checked in both the premade iso and the buster/chroot of my last homemade one.

[fredx181]

I just noticed this, but in /etc/hosts it has:

Code: Select all

127.0.0.1	 localhost
127.0.1.1	 live

Am I missing something, or should it be:

Code: Select all

127.0.0.1	 localhost
127.0.0.1	 live

I checked in both the premade iso and the buster/chroot of my last homemade one.

It's done on purpose how content of /etc/hosts is on all DebianDogs. To be honest, I don't know why it's like that and can't remember where I got it from (at that time), but here's an article that shows similar:
https://geek-university.com/linux/etc-hosts-file/

[dancytron]

Here's another place that shows similar (at bottom of thread) but doesn't really say why.

https://unix.stackexchange.com/question ... s-properly

It just looked strange...

[krishna88]

How to fix this problem

input signal out of range change settings to 1280x1024-60hz

[fcopurico]

fredx181

I am a user of BusterDog on my AMD64 PCs for some time. Build using script. I like Debian as stock as possible,. Then add only what I need. For that I have only thanks to the forum, this thread and to you.

I write because I am exploring a project. I want to know if is possible to build BusterDog for Arm?
Also what is the latest Kernel Available.
In the case it can be done with other Debiandog, which one?

The Idea is to explore the possibility to run in Dockstar, GoFlex using kirkwood CPU as a server.
Please ignore the fact that your packages at https://doglinux.github.io/busterdog are x86 or AMD64.
Worrying only those elementary that makes porteus-boot and no-systemd. I am willing to compile kernel etc.

Thanks for any Ideas.

[fredx181]

Hi @fcopurico ,

I've never done anything with Arm, so can't really help.
Perhaps you can make your own build script by modifying for Arm, this may be a starting point: https://willhaley.com/blog/custom-debia ... vironment/

[fcopurico]

fredx181

Nice Link, It will be good for me to review the basics of debootstrap, . Thanks
Now I am not asking you to build nothing for me. I know you most be a busy man. But to be honest my reference is your own makelive. I have not started yet. I wanted your opinion 1rst.

As I said Busterdog is my preferred OS and I used it on m PC.
For my embedded project in the other hand, what I want from "BusterDog + build system (no-systemd)" is the boot method and the Puppy like read-only OS. Writing savefile only at logout will definitely save the life of mmc card. Plus I love elogind. See my point.

Lets ignore that the script will most likely fail, and not finish a FULL OS. I guess trying to download your x86 binaries from git that will not run on ARM. Lets start with the basic. 1rs step I guess is the kernel/initrd build.
I know in the old forum there was a post where you help some one to build its Kernel for a sat tuner. I will try to follow what it was done there.

What I need from you is if you recall any x86 binary been used to build Busterdog kernel/initrd. Where I most likely need the sources instead. The sources because I will then be needed to compile them in ARM.

So do you recalled any binary that may require sources.? Remember at this time only for kernel/initrd. I know debian has elogind now its repositories.

I will report you back any advancement on your makelive changes for Arm. So that you could offer it to other users in the future.

[fredx181]

only for kernel/initrd.

I think I see what you want, an Arm based Debian live, working with the porteus-boot options.
It's really not straightforward but I will think about it how to accomplish, will take some time, I guess.

Questions, does it need to be Buster based ? And does it need 'aufs' for you ? Bullseye may be easier (and more up to date, btw), the kernel contains 'overlay' already (so no 'aufs' compiling needed).

[dancytron]

only for kernel/initrd.

I think I see what you want, an Arm based Debian live, working with the porteus-boot options.
It's really not straightforward but I will think about it how to accomplish, will take some time, I guess.

Questions, does it need to be Buster based ? And does it need 'aufs' for you ? Bullseye may be easier (and more up to date, btw), the kernel contains 'overlay' already (so no 'aufs' compiling needed).

Maybe take a look at Berryboot https://www.berryterminal.com/doku.php/ ... tributions . It uses aufs and so has to compile it's own kernel, but iirc it uses a compressed image with basically a save folder to multiboot the Raspberry Pi and some other similar computers. If nothing else, you can probably reuse his kernel if you try to go with AUFS.

Main Berryboot github page - https://github.com/maxnet/berryboot
Other berryboot os images - https://berryboot.alexgoldcheidt.com/images/

[fcopurico]

@dancytron
I am confuse. I have a felling Berryboot is just a multy OS bootloader.
I know there hundreds if not thousands of Linux Arm Images. I really appreciate the links. Thanks. But that may complicate my effort. The devices I will work with uses uBoot as boot loader. That part is fine. On my PC I have many OS. But for this small devices I expect to run the minimal Debian . So the debootstrap method fred181 mention is the way to go.

@fred181
Any help is appreciated, but I sincerely was asking for some notes or ideas, before I started. In fact I been busy for the past few days and have not been able to work or read.
It does not need to be aufs. Regards aufs it is not an issue for me to doing manual updates our self on the final kernel. And as a Busterdog, it is what I use in my PC. And what I feel comfortable.
But Listen the need for aufs is only for the savefile overlay. I do not intent to load multiple sfs. So is only "ro - OS" / "rw - savefile". Remember small device to be use as simple server.

Regards new "Bullseye may be easier (and more up to date, btw), the kernel contains 'overlay' already"
Interesting comment. To be honest, I been so happy with Busterdog. Then I read some of the confusing overlay comments at the beginning of bulleye thread. I decided to wait to a more mature state. I guess it is time to go and read again. And yes it can be any available good option that allow us to have 1 Read Only Debian OS + a Single RW save file. I like porteus-boot system to save at the end. But any similar will do it.

Let me rephrase what I did try to get when I 1rst ask you.
I have the intention to work in this next week. I was hoping to here from you one of three thing:
No It will not work?
or Yes but you will have hard time getting this binary Lib...?
or Yes I see no obstacle.

[dancytron]

Because the method it uses to multiboot is the same method Debian Dog could use to boot. It could save Fred a lot of time if he can reuse that.

edit: To be clearer. Berryboot multiboots by using squashfs of the root filesystem (like Debian Dog) and a separate aufs enabled kernel (like Debian Dog before Bullseye) with changes in a separate folder (like Debian Dog). Lots of the pieces that Fred might be able to use.

[fredx181]

Let me rephrase what I did try to get when I 1rst ask you.
I have the intention to work in this next week. I was hoping to here from you one of three thing:
No It will not work?
or Yes but you will have hard time getting this binary Lib...?
or Yes I see no obstacle.

Well, don't know yet, probably it can work in theory, there's a couple of scripts required for porteus-boot to work (not one bin or lib) and the initrd (special for porteus-boot) needs to be created to match with the kernel. All together rather complicated, but as I said I'll think about what's the best to advice or share with you.
Would this kernel, for example, be usable for you ? (arm64) https://packages.debian.org/bullseye/li ... 0-10-arm64 Or does it need to be armhf ?

One obstacle is that I cannot test on ARM.

[fcopurico]

See that was easy. Just what I was looking.

It may work, but lots of work.
You can suggest but not test, as you do not have arm.

And I finally got dirty myself as at the moment I have not started to test or even read.

Please see my new thread at Debian Dog for kirkwood - embeded armel[Test Project]
https://www.forum.puppylinux.com/viewtopic.php?t=5162

I will continue my chat there to prevent hijack of this wonderfull BusterDog thread.

That is all I had read. But I do not started to build anything. I will start by installing OpenWrt in NAND to be use as System Recovery method. And I plan to install Debian on USB. Latter in Sata HDD.
Please, you do not have to worry about how to boot from ( NAND, USB or SATA). That is all handle by uBoot, just as grub4dos do for you here.

... Would this kernel, for example, be usable for you ? (arm64) https://packages.debian.org/bullseye/li ... 0-10-arm64 Or does it need to be armhf ?

One obstacle is that I cannot test on ARM.

Here we can find oficial kernel and initrd images

Code: Select all

https://ftp.debian.org/debian/dists/bullseye/main/installer-armel/current/images/kirkwood/netboot/vmlinuz-5.10.0-10-marvell
https://ftp.debian.org/debian/dists/bullseye/main/installer-armel/current/images/kirkwood/netboot/initrd.gz

Just for the record, uBoot used them like this. Do not have to worry about this. Posted just for your info.

Code: Select all

https://ftp.debian.org/debian/dists/bullseye/main/installer-armel/current/images/kirkwood/netboot/seagate/dockstar/uImage
https://ftp.debian.org/debian/dists/bullseye/main/installer-armel/current/images/kirkwood/netboot/seagate/dockstar/uInitrd

Conclusion. I hope to be able to builds with dockstar.debian-wheezy.sh. Update to recent Debian. Hopefully I can overcome any Issue. Then I will try to add any suggestion you may provide me.

If success I will provide you with you with my end script. So that you can add it to your collection. Keep your good work. Thanks.

[dcung]

Hi Fred,

I just fresh installed BusterDog64.
As usual, the first thing I do is to install nVidia driver.
But the linux-headers install gave errors. I already tried few times in last 3 days, just in case the repos have problem. It still gives error now.

Code: Select all

root@live:~# apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease                   
Hit:4 http://ftp.us.debian.org/debian buster InRelease                         
Get:5 http://ftp.us.debian.org/debian buster-updates InRelease [51.9 kB]    
Get:3 https://github.com/doglinux/busterdog/raw/master/amd64 ./ InRelease [2,301 B]
Hit:6 http://snapshot.debian.org/archive/debian/20200528 buster InRelease      
Fetched 54.2 kB in 2s (32.9 kB/s)                         
Reading package lists... Done
Building dependency tree       
Reading state information... Done
67 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@live:~# apt install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package linux-headers-4.19.0-14-amd64
E: Couldn't find any package by glob 'linux-headers-4.19.0-14-amd64'
E: Couldn't find any package by regex 'linux-headers-4.19.0-14-amd64'
root@live:~# 

[fredx181]

@dcung
Yes, that's because they don't keep older linux-headers packages in the repos.
Can be fixed by booting with newer kernel, here's a 'package'
https://github.com/DebianDog/BusterDog/ ... d64.tar.gz
Extract in the "live" folder (existing files must be overwritten) , reboot and you should be able to install linux-headers 4.19.0-19 .

[dcung]

Yes, that's because they don't keep older linux-headers packages in the repos.
Can be fixed by booting with newer kernel, here's a 'package'
https://github.com/DebianDog/BusterDog/ ... d64.tar.gz
Extract in the "live" folder (existing files must be overwritten) , reboot and you should be able to install linux-headers 4.19.0-19 .

That works. Thanks Fred.

[Brandy44]

I had a similar problem when I tried to install WhatsApp on my Linux, so I searched the net and found this FM WhatsApp modified app of WhatsApp. After installing this app, I found out. Come on, this is an unofficial app that was developed by a Spanish developer, so I immediately deleted this app from my Linux, but I'm still looking for a solution.

Which version of WhatsApp are you trying to install on your Linux? If you are trying to install an older version of WhatsApp, try the updated version of WhatsApp. I hope your issue is resolved.

Thanks andywilson for this, I had a similar issue with this YOWhatsApp apk but after update it my problem got solved. thank you so much for sharing this info.

Great, thanks for such a discriptive information. It is fabulous!

(links removed by moderator, possible spam)

[dcung]

How to install systemd on BusterDog:

For those who prefer booting with systemd, here's how (a bit of a workaround)
First make sure to Exit X ! Menu > Logout > Exit X
Then from the console type ("apt update" may not be needed if you recently updated the package lists):

Code: Select all

apt update
apt install udev systemd-sysv libpam-systemd

Reboot with changes saved and systemd will be the init system.
(automatic login doesn't work then, btw).

Note: after doing above and booting with systemd, there's no way back to switch to elogind again (at least that I know of)

Fred

Is this still applicable?
I tried installing systemd. (Exit X)

Code: Select all

root@live:~# apt install udev systemd-sysv libpam-systemd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
udev is already the newest version (1:3.2.9+devuan4).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libpam-systemd : Depends: systemd (= 241-7~deb10u9) but it is not going to be installed
 systemd-sysv : PreDepends: systemd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@live:~# 

[fredx181]

.....
.....
Is this still applicable?
I tried installing systemd. (Exit X)

Apparently not, I don't know why
Have you ever tried aptitude ? It's more friendly than apt IMO, because often it gives you choices (solve conflicts, not always possible though) in such a situation where apt refuses.
apt install aptitude
aptitude update
aptitude install ... ... ...

edit: for example in your case, apt says:
libpam-systemd : Depends: systemd (= 241-7~deb10u9) but it is not going to be installed
systemd-sysv : PreDepends: systemd but it is not going to be installed
But apt doesn't say why, generally aptitude gives more explanation (at least).