[DNG] Announce: FlyingTux project
Hello folks, maybe a bit offtopic, but allow me to announce the FlyingTux project: It's an build/runtime infrastructure for running desktop and mobile applications in containers and build an entirely container-based mobile OS based on it. The primary motivation is my long frustration about the monstreaus and practically unmaintainable Android, which also still lacks lots of common management abilities we know from the GNU/Linux world. In some ways, FT can be seen as an conceptional combination of containers (docker, k8s, etc) and apps (android, etc). One major difference is that also the app images are based on some defined distro base (for start, just alpine, others to follow later) and the images are created on the host, based on host specific settings like hw setups (eg. automatically deploys the right mesa drivers). In future steps some packages of the app distro base (called 'osbase# here) will be replaced or customized, in order to provide better integration with the ecosystem and strip unneeded stuff. Another key difference is moving common functionality (eg. various data sources, communication protocols, ...) out of the individual apps into generic services - and the binding between individual apps and actual services instances can be customized by the user (e.g. one can bind some apps to fake gps instead of the real one, separate address books or user directories, etc, etc). Here's a more detailed description: https://github.com/metux/flyingtux/blob/master/README Note that for now its very experimental and fast changing. Don't expect anything field-ready yet. But it's already good enought to isolate some common desktop apps like gimp, chrome, etc. --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] libvirt package without X11 and DBus
On 5/8/21 4:40 am, AP wrote: Hi everyone, first I thank all DEVUAN people for the pure pleasure of running my system (since ASCII 2018) without a bloatware. This is my first message and I am sorry, that my search did not give me the answer about: maintenance of the libvirt package without X11 and DBus Question: is there a way to get the package for libvirt + QEMU/KVM for headless VMs - when no X, no DBus needed? You can always compile it yourself. I've just checked and I'm still running a self-compiled v4 on my main box. Certainly in the v5.6.0 code I just looked at there's an option to disable dbus. From memory I stopped upgrading when they migrated away from autoconf and make. The redhat-isms were just making it too hard to build on older stable debian-based systems, so I stuck with V4. These days it'd be easy enough to use the packaged versions I suppose. Brad -- An expert is a person who has found out by his own painful experience all the mistakes that one can make in a very narrow field. - Niels Bohr ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] libvirt package without X11 and DBus
Hi everyone, first I thank all DEVUAN people for the pure pleasure of running my system (since ASCII 2018) without a bloatware. This is my first message and I am sorry, that my search did not give me the answer about: maintenance of the libvirt package without X11 and DBus Question: is there a way to get the package for libvirt + QEMU/KVM for headless VMs - when no X, no DBus needed? Currently I am solving it like this: I am using QEMU/KVM/libvirt in Beowulf SMP Debian x86_64 My guests are LAMP headless VMs, with no X11 (all DEVUAN Beowulf x86_64). On a supervisor I am using no DBus, so I purged it from the packages installed by default, and put on hold along with elogin and libpam module: ~$sudo apt-mark showhold dbus elogind libpam-elogind System runs stable, for development, production and backup environments. When I simulate an update to the recent libvirt on a supervisor, it starts to pull in all the X11 + DBus dependencies libraries, which were not installed before, smth. around +300MB of archives, like fonts TTF, and others. Using DBus would put my system in the uncontrolled and unmaintained state, since I do not have any experience to manage it, and also no requirements to use it. Do you have any experience about maintaining libvirt without DBus in Devuan/Debian, and can you share what is helpfull/meaningfull strategy here? Is there a chance to install/upgrade libvirt package with no X11 / DBus dependencies, and can I contribute to such package? Thank you! Cheers, Andrzej -- AP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-install device node not found [solved]
On Wed, Aug 04, 2021 at 05:27:48PM +0200, aitor wrote: > Hi, > > On 4/8/21 16:34, Haines Brown wrote: > > But I'd prefer to do the fix direclty within sdc chroot. Is there > > a utility in util-linux to make the node (/dev/sdc1 ?) visible? > > You need to include them in /etc/fstab to suit your needs, i guess. Thanks for the suggestion. In looking at fstab I found that term was no longer accessible. So I inistalled mlterm to look at /etc/fstab. I see that it still has the information I had earlier provided for it. That is, the UUID number for / etc. I worried about MBR. It is msdos as I would expect. Then I checked to see if it had content with # dd if=/dev/sdc of=mbr.bin bs=512 count=1 # od -xa mbr.bin The output of no use to me, but at least there exits an MBR with code. Otherwise I'd have to repartiion the disk In principle I have a fully operating system on the disk. There is a kernel and /boot/grub has its files. The only problem is I have no boot manager. Incidentally when I now try to run # update-grub it ends with device node not found Cannot find list of partitions! (Try mounting /sys.) So I tried to mount /sys within chroot: /# mount -t proc none /proc This did not oslve the problem. I tried from outide chroot: # mount -o bind /sys/ /mnt/devinst/sys Now # update-grub runs and successfully completes. It finds the linux and initrd images, but not those on other disks. I forget whether it can do so before a reboot. I used to do cross installs many years ago and loved it. The process today seems simpler than before. -- Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system
Dear list Beowulf is hit hard by a problem with hardcoded path in grub-efi-amd64-signed leading to an unbootable system as reported on this list and on dev1galaxy (manual intervention in certain configurations needed to boot). This problem also exists on fresh installs of beowulf, as it seems. Is there some effort under way to fix the problem? Best regards, Adrian. Work-around (thanks to fsmithred): # apt purge grub-efi-amd64-signed ... # apt install --reinstall grub-efi-amd64 ... References: On this list: "Strange behaviour with last version of grub" by viverna (04/03/2021 17:22) --> https://lists.dyne.org/lurker/message/20210304.162242.f881d3b8.en.html In the Dev1 Galaxy Forum: "Strange behaviour with last version of grub" by viverna (2021-03-04) --> https://dev1galaxy.org/viewtopic.php?pid=27939 "Issues with booting a fresh Beowulf install" by chomwitt (2021-07-10) -->https://dev1galaxy.org/viewtopic.php?pid=30972#p30972 ...and the mentioned underlaying Debian Bug report: "Wrong prefix directory hardcoded in signed GRUB image" by Pascal Hambourg (2021-03-22) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925309 signature.asc Description: This is a digitally signed message part. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-install device node not found
Hi Haines, On 4/8/21 12:31, Haines Brown wrote: Indeed, fdisk-l returns nothing. There does exist a set of sdc* interfaces in /dev. What is the fix? Take a chance with lsblk and blkid, miscelaneous utilities of util-linux. On the other hand # udevadm info -a -p $(udevadm info -q path -n /dev/sdc) # udevadm info -a -p $(udevadm info -q path -n /dev/sdcX) will list the attributes of sdc and sdcX. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] grub-install device node not found
On Tue, Aug 03, 2021 at 10:31:28PM +0200, Arnt Karlsen wrote: > On Tue, 3 Aug 2021 13:25:19 -0400, Haines wrote in message > <20210803172519.gg29...@engels.histomat.net>: > > > I'm doing a cross install of beowulf. BIOS is legacy. All goes well > > until the end when I run /#: grub-install /dev/sdc . > > > > Installing for i386-pc platform. > > device node not found > > ... > > Installation finished. No error reported. > > > > I should mention that when I initially ran the command my terminal > > (mlterm) crashed (that sometimes happens). So I had to chroot again > > to the mount point /mnt/devinst/ > > > > It seems that the grub-install cannot see the mbr on /dev/sdc > > ..is there one? 'fdisk -l ' or somesuch should work, even if > there are some new fancy /dev names missing symlinks to /dev/sdc, > e.g. killed by that mlterm crash. Indeed, fdisk-l returns nothing. There does exist a set of sdc* interfaces in /dev. What is the fix? -- Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
