Pipewire without systemd

[Member stevesr0]

PulseAudio is currently the usual “go to” answer given to people who have trouble getting alsa to “deliver” audio to the correct speaker (or headphones). Pipewire is an audio server in development that is supposed to be better for some uses than PulseAudio and is being promoted as its replacement.

I am happily using Pipewire on my Sid system to listen to music via headphones that alsa alone has problems connecting to.

It is usable without systemd – while I have libelogind0 installed.

When I simulate a removal of libelogind0, my pipewire packages are automagically selected for removal, along with synaptic, lxterminal, two libapt packages (libapt-inst2.0 and libapt-pkg5.0) and (of course elogind and libpam-elogind).

Users of several distributions (void, artix and devuan) have stated they have managed to run Pipewire without systemd. However, I haven’t seen a novice level step-by-step that obviously translates to an antiX install.

At this point, I have a vague notion that an install with seatd as a replacement for libelogind0 and proper setting of the default user runtime directory might be all that is needed. (However, I DO have seatd installed and my system still thinks that libelogind0 is required for Pipewire <sigh>).

According to the Gentoo wiki article on Pipewire (https://wiki.gentoo.org/wiki/Pipewire#Service), it appears to be mainly a matter of installing the proper autostart files in /etc/xdg/autostart/pipewire.desktop or setting XDG_RUNTIME_DIR as an environment variable.

Other sources mention scripts that set the default directory (pam_rundir).

However, I realize that getting all to work may be more complicated.

A very recent thread on the artiX forum (https://forum.artixlinux.org/index.php/topic,1923.0/prev_next,next.html) describes getting Pipewire to work without elogind. For example it mentions that wireplumber (the new session manager for Pipewire) might require a special compilation to use seatd rather than elogind.

I welcome any thoughts, comments or suggestions. Happy to try different things to get Pipewire working without libelogind0 or elogind or libpam-elogind.

stevesr0

(P.S. remember I am a permanent noobie – thankfully, this Sid install is my system for playing/learning and if I break it, that’s OK.)

• This topic was modified 9 months, 1 week ago by stevesr0.

[Member marcelocripe]

Helpful

Up

0

::

Hello stevesr0.

I appreciate you starting this topic.

I started implementing PipeWire in my antiX installations about 3 months ago, I always refer to the tutorial Pipewire to manage audio in antiX 21Pipewire to manage audio in antiX 21 that Xecure created.

PipeWire without PulseAudio can output sound on ZSNES, but cannot output Kega-Fusion sound, apparently PulseAudio is required for Kega-Fusion to work with sound. Some sound cards were only able to work properly after installing and configuring PipeWire. But this process of installing and configuring PipeWire is not so simple for everyone to do, even with Xecure’s excellent explanation.

Debian’s repository is full of the crap called “SystemD”, unfortunately this is the way to input “SystemD” in antiX. As much as the Debian repository has an immense amount of extremely useful application programs, “SystemD” will always be a pest that will enter at some point in an installation or update of some program.

I had already written something about this in another topic, I think that sooner or later the GNU/Linux distributions that don’t want “SystemD” in their operating system at all, need to get closer to each other and maybe share their repositories free from “SystemD” with each other. Bearing in mind that porting the entire Debian repository with “SystemD” to another repository without “SystemD” is a huge job and we would have to have many people working on this process. I hope I can learn to do this in order to help, but for this to be possible, we volunteers need to be trained and the development team will no longer be small and will be able to increase gradually, because if it doesn’t increase, one day, inevitably it won’t have no more developers because life will end for everyone one day since death is the only thing that human beings cannot escape. However, operating systems and programs can continue to exist and continue to live through other people.

PulseAudio slows down antiX, so I turn it on or off when needed. As you have the trial version of antiX, you can access the latest version of PipeWire, unfortunately I don’t have the necessary technical knowledge to be an eternal tester, because I don’t have so much free time to study and learn to fix the system operational with each update.

I’m also happy to test different things on a LiveUSB without persistence to make PipeWire work without libelogind0 or elogind or libpam-elogind or anything that has “SystemD”.

Libera.Chat’s #antiX-translators channel on HexChat with the machine translation program that Robin developed, is still the easiest way for me to be able to communicate and help test together with others from any program, I hope to be able to talk to you through this medium at some point.

– – – – –

Olá stevesr0.

Eu agradeço por você iniciar este tópico.

Eu comecei a implementar o PipeWire nas instalações que eu faço do antiX há cerca de 3 meses, eu sempre utilizo como referência o tutorial Pipewire to manage audio in antiX 21 que o Xecure criou.

O PipeWire, sem o PulseAudio consegue emitir o som no ZSNES, mas não consegue emitir o som do Kega-Fusion, ao que parece o PulseAudio é necessário para o Kega-Fusion funcionar com o som. Algumas placas de som só conseguiram funcionar corretamente após a instalação e a configuração do PipeWire. Mas este processo de instalação e configuração do PipeWire não é tão simples de ser feito por todas as pessoas, mesmo com a excelente explicação do Xecure.

O respositório do Debian está cheio da porcaria chamada “SystemD”, infelizmente é este o meio de entrada do “SystemD” no antiX. Por mais que o respositório do Debian possua uma quantidade imensa de programas aplicativos extremamente úteis, o “SystemD” sempre será um praga que entrará em algum momento em uma instalação ou na atualização de algum programa.

Eu já havia escrito algo sobre isso em outro tópico, eu penso que cedo ou tarde as distribuições GNU/Linux que não querem de forma alguma o “SystemD” em seu sistema operacional, precisam se aproximarem uma das outras e quem sabe compartilharem os seus repositórios livres do “SystemD” umas com as outras. Haja vista que portar todo o respositório do Debian com o “SystemD” para um outro o respositório sem o “SystemD” é um trabalho gigantesco e teríamos que ter muitas pessoas trabalhando neste processo. Eu espero poder aprender a fazer isso para poder ajudar, mas para que isso seja possível, nós voluntários precisamos ser treinados e a equipe de desenvovimento deixará de ser pequena e poderá aumentar de forma gradual, porque se não aumentar, um dia, inevitavelmente não terá mais nenhum desenvolvedor porque a vida acabará para todos um dia já que a morte é única coisa que o ser humano não tem como escapar. Contudo, os sistemas operacionais e os programas podem continuar existindo e continuar vivos por meio de outras pessoas.

O PulseAudio causa lentidão no antiX, por isso eu ativo ou desativo quando é necessário. Como você possui a versão de teste do antiX, você consegue ter acesso a versão mais recente do PipeWire, infelizmente eu não tenho conhecimentos técnicos necessários para ser um testador eterno, pois eu não tenho tanto tempo livre para ficar estudando e aprendendo a consertar o sistema operacional a cada atualização.

Eu também fico contente em testar coisas diferentes em um LiveUSB sem persistência para fazer o PipeWire funcionar sem libelogind0 ou elogind ou libpam-elogind ou qualquer coisa que tenha o “SystemD”.

O canal #antiX-translators do Libera.Chat no HexChat com o programa de tradução automática que o Robin desenvolveu, ainda é o meio mais fácil para eu poder me comunicar e ajudar a fazer testes em conjunto com outras pessoas de qualquer programa, eu espero poder conversar com você por este meio em algum momento.

[Member stevesr0]

Helpful

Up

0

::

Hi marcelocripe,

Thanks for response.

Xecure’s thread (and his responses to my questions in that thread) were very helpful to my getting Pipewire running.

I never heard of Kega-Fusion. I just looked and found a thread (https://aur.archlinux.org/packages/kega-fusion) which indicated that it works with Pipewire if you add some libraries (lib32-pipewire and pipewire-alsa). You probably already tried that.

Yes, Pipewire is still basically provided by debian in a usable form (apparently) in Sid and testing, not in Bullseye-backports.

I am working on this figuring that in the next year of so, Pipewire may become mainstream and then the main barrier to running it will be the adjustments needed to run it without systemd.

Since I am able to use it (in my simple fashion), I thought it might be useful to try to make it work with antiX in order to allow other antiXers to use it when the time is right.

stevesr0

—————————–
Oi marcelocripe,

Obrigado pela resposta. O fio de Xecure (e suas respostas às minhas perguntas nesse segmento) foram muito úteis para a minha corrida pipewire.

Nunca ouvi falar de Kega-Fusion. Eu só olhei e encontrei um fio (https://aur.archlinux.org/packages/kega-fusion) que indicava que ele funciona com Pipewire se você adicionar algumas bibliotecas (lib32-pipewire e pipewire-alsa). Você provavelmente já tentou isso.

Sim, Pipewire ainda é basicamente fornecido por debian em uma forma utilizável (aparentemente) em Sid e testando, não em bullseye-backports. Estou trabalhando nisso, descobrindo que no próximo ano, a Pipewire pode se tornar mainstream e, em seguida, a principal barreira para executá-lo serão os ajustes necessários para executá-lo sem sistema.

Como eu sou capaz de usá-lo (da minha maneira simples), eu pensei que poderia ser útil para tentar fazê-lo funcionar com antiX, a fim de permitir que outros antiXers usá-lo quando for a hora certa.

stevesr0

• This reply was modified 9 months, 1 week ago by stevesr0.
• This reply was modified 9 months, 1 week ago by stevesr0.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Pipewire already runs without systemd installed on antiX sid/testing via the use of elogind.
However, at the moment, it does not run without either systemd or elogind.
It might work in the future with seatd: ie no systemd/elogind baggage. Who knows?
I have tried to build systemd/elogind – free versions of Pipewire, but all attempts have failed.

Does void/artix install parts of elogind to get it to work?
If they do, then they are not doing anything different to what already exists in antiX,

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Helpful

Up

0

::

Hi anticapitalista,

Thanks much for your response.

anticapitalista wrote,
Pipewire already runs without systemd installed on antiX sid/testing via the use of elogind.
However, at the moment, it does not run without either systemd or elogind.
It might work in the future with seatd: ie no systemd/elogind baggage. Who knows?
I have tried to build systemd/elogind – free versions of Pipewire, but all attempts have failed.

Does void/artix install parts of elogind to get it to work?
If they do, then they are not doing anything different to what already exists in antiX,

My answer is that several distro forums including Devuan, void and artix have indicated that Pipewire works without systemd, and I have seen posts suggesting that the primary mechanism involved setting a user runtime directory either setting an environmental variable (such as XDG_RUNTIME_DIR) or using a script (such as pam_rundir). However, I haven’t found a thread on these nonsystemd forums which described how to do this in a complete step-by-step.

However, many sites reference the instructions on the Gentoo wiki page on Pipewire. Here is a part of the page dealing with installation without systemd.

Login without session management

Ensure there is a viable D-Bus session active:
FILE ~/.xinitrc

if command -v dbus-launch >/dev/null && test -z "${DBUS_SESSION_BUS_ADDRESS}"; then
       eval $(dbus-launch --sh-syntax --exit-with-session)
fi

Check that XDG_RUNTIME_DIR is set. This is usually managed by either systemd-logind, its fork elogind for OpenRC and similar init systems, or seatd - an alternative free-standing implementation of logind. In addition to running one of the 3 logind variants, a PAM module must also be loaded to let the daemon interact with users logging in and out of the system.

"On systems without any such logind implementation and the required PAM module, the user must create the required directory and set the environment variable manually:

# Ensure XDG_RUNTIME_DIR is set
unset XDG_RUNTIME_DIR
export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX)

The PipeWire executable must also be called:
FILE ~/.xinitrc

/usr/bin/gentoo-pipewire-launcher"

Whether this would also work on antiX Sid or not, I do not know. (HINT: With some guidance about problems that pop up, I would be willing to try – even if it breaks my “minimalist” Sid install.)

(Not sure if that adequately addresses your question – let me know if you want me to provide specific pages on the nosystemd forums and I shall.)

stevesr0
————————————————

Γεια αντικαπιταλίστα,
Ευχαριστώ πολύ για την απάντησή σας. «αντικαπιταλιστής έγραψε, Το Pipewire λειτουργεί ήδη χωρίς εγκατεστημένο σύστημα σε antiX sid / δοκιμές μέσω της χρήσης του elogind. Ωστόσο, προς το παρόν, δεν λειτουργεί χωρίς ούτε systemd ούτε elogind. Μπορεί να λειτουργήσει στο μέλλον με καθήμενους: δηλαδή χωρίς systemd / elogind αποσκευές. Ποιος ξέρει; Έχω προσπαθήσει να οικοδομήσουμε systemd / elogind – δωρεάν εκδόσεις του Pipewire, αλλά όλες οι προσπάθειες έχουν αποτύχει. Το void / artix εγκαθιστά τμήματα του elogind για να το κάνει να λειτουργήσει; Εάν το κάνουν, τότε δεν κάνουν τίποτα διαφορετικό από αυτό που υπάρχει ήδη στο antiX, ` Η απάντησή μου είναι ότι πολλά φόρουμ διανομής, συμπεριλαμβανομένων των Devuan, void και artix, έχουν δείξει ότι το Pipewire λειτουργεί χωρίς σύστημα και έχω δει αναρτήσεις που υποδηλώνουν ότι ο κύριος μηχανισμός περιελάμβανε τη ρύθμιση ενός καταλόγου χρόνου εκτέλεσης χρήστη είτε ορίζοντας μια περιβαλλοντική μεταβλητή (όπως XDG_RUNTIME_DIR) είτε χρησιμοποιώντας ένα σενάριο (όπως pam_rundir).

Ωστόσο, δεν έχω βρει ένα νήμα σε αυτά τα μη συστηματικά φόρουμ που περιέγραψε πώς να το κάνετε αυτό σε ένα πλήρες βήμα προς βήμα. Ωστόσο, πολλοί ιστότοποι αναφέρονται στις οδηγίες στη σελίδα wiki του Gentoo στο Pipewire. Εδώ είναι ένα μέρος της σελίδας που ασχολείται με την εγκατάσταση χωρίς systemd. «Συνδεθείτε χωρίς διαχείριση συνεδρίας Βεβαιωθείτε ότι υπάρχει ενεργή μια βιώσιμη συνεδρία D-Bus: ΑΡΧΕΙΟ ~/.xinitrc if command -v dbus-launch >/dev/null && test -z “${DBUS_SESSION_BUS_ADDRESS}”; τότε eval $(dbus-launch –sh-syntax –exit-with-session) υγ. Βεβαιωθείτε ότι έχει οριστεί XDG_RUNTIME_DIR. Αυτό συνήθως το διαχειρίζεται είτε το systemd-logind, το πιρούνι του elogind για το OpenRC και παρόμοια συστήματα init, είτε το seatd – μια εναλλακτική ανεξάρτητη υλοποίηση του logind. Εκτός από την εκτέλεση μίας από τις 3 συνδεδεμένες παραλλαγές, πρέπει επίσης να φορτωθεί μια λειτουργική μονάδα PAM για να επιτρέψει στον δαίμονα να αλληλεπιδράσει με χρήστες που συνδέονται και εξέρχονται από το σύστημα.

“Σε συστήματα χωρίς τέτοια συνδεδεμένη υλοποίηση και την απαιτούμενη μονάδα PAM, ο χρήστης πρέπει να δημιουργήσει τον απαιτούμενο κατάλογο και να ορίσει τη μεταβλητή περιβάλλοντος με μη αυτόματο τρόπο: # Βεβαιωθείτε ότι έχει οριστεί XDG_RUNTIME_DIR αναίρεση XDG_RUNTIME_DIR export XDG_RUNTIME_DIR=$(mktemp -d /tmp/$(id -u)-runtime-dir.XXX) Το εκτελέσιμο αρχείο PipeWire πρέπει επίσης να ονομάζεται: ΑΡΧΕΙΟ ~/.xinitrc /usr/bin/gentoo-pipewire-launcher” ` Αν αυτό θα λειτουργούσε επίσης στο antiX Sid ή όχι, δεν ξέρω. (ΣΥΜΒΟΥΛΗ: Με κάποια καθοδήγηση σχετικά με τα προβλήματα που εμφανίζονται, θα ήμουν πρόθυμος να προσπαθήσω – ακόμα κι αν σπάσει την “μινιμαλιστική” εγκατάσταση Sid μου.)

(Δεν είμαι σίγουρος αν αυτό αντιμετωπίζει επαρκώς την ερώτησή σας – επιτρέψτε μου να ξέρω αν θέλετε να παράσχω συγκεκριμένες σελίδες για τα φόρουμ nosystemd και θα το κάνω.)

stevesr0

• This reply was modified 9 months, 1 week ago by stevesr0.
• This reply was modified 9 months, 1 week ago by stevesr0.
• This reply was modified 9 months, 1 week ago by stevesr0.

[Member marcelocripe]

Helpful

Up

0

::

I never heard of Kega-Fusion. I just looked and found a thread (https://aur.archlinux.org/packages/kega-fusion) which indicated that it works with Pipewire if you add some libraries (lib32-pipewire and pipewire-alsa). You probably already tried that.

Stevesr0, thanks for this suggestion, I’ll test it on a fresh install of antiX that I’ll be doing in the next few days. If the sound works without PulseAudio, I’ll return in this thread with detailed information. I downloaded the kega-fusion package from this URL https://www.carpeludum.com/kega-fusion/. This is a package that could be available in the antiX/MX Linux repository.

Whether this would also work on antiX Sid or not, I do not know. (HINT: With some guidance about problems that pop up, I would be willing to try – even if it breaks my “minimalist” Sid install.)

I can also help test on a LiveUSB without persistence.

– – – – –

I never heard of Kega-Fusion. I just looked and found a thread (https://aur.archlinux.org/packages/kega-fusion) which indicated that it works with Pipewire if you add some libraries (lib32-pipewire and pipewire-alsa). You probably already tried that.

Stevesr0, obrigado por esta sugestão, eu vou testar em uma nova instalação do antiX que eu vinher a fazer nos próximos dias. Se funcionar o som sem o PulseAudio, eu retorno neste tópico com informações detalhadas. Eu baixei o pacote kega-fusion neste URL https://www.carpeludum.com/kega-fusion/. Este é um pacote que poderia estar disponível no repositório do antiX/MX Linux.

Whether this would also work on antiX Sid or not, I do not know. (HINT: With some guidance about problems that pop up, I would be willing to try – even if it breaks my “minimalist” Sid install.)

Eu também posso ajudar a testar em um LiveUSB sem persistência.

[Member marcelocripe]

Helpful

Up

0

::

Hello Stevesr0.

Today I am completing a fresh install of antiX 21 and on this computer I tried to install PipeWire without PulseAudio. I tried installing the “lib32-pipewire” and “pipewire-alsa” packages.

The result of the command was this:

nome_de_usuario@antix:~
$ sudo apt update

nome_de_usuario@antix:~
$ sudo apt upgrade

nome_de_usuario@antix:~
$ sudo apt install pipewire pipewire-audio-client-libraries lib32-pipewire pipewire-alsa
[sudo] senha para nome_de_usuario:
Lendo listas de pacotes… Pronto
Construindo árvore de dependências… Pronto
Lendo informação de estado… Pronto
E: Impossível encontrar o pacote lib32-pipewire
E: Impossível encontrar o pacote pipewire-alsa
nome_de_usuario@antix:~
$

On the page http://ftp.br.debian.org/debian/pool/main/p/pipewire/ there is only the package “pipewire-alsa”, both the apt command in Terminal and Synaptic cannot find the packages “lib32-pipewire” and “pipewire-alsa”.

– – – – –

Olá Stevesr0.

Hoje eu estou concluindo uma nova instalação do antiX 21 e neste computador eu tentei realizar a instalação do PipeWire sem o PulseAudio. Eu tentei instalar os pacotes “lib32-pipewire” e “pipewire-alsa”.

O resultado do comando foi este:

nome_de_usuario@antix:~
$ sudo apt update

nome_de_usuario@antix:~
$ sudo apt upgrade

nome_de_usuario@antix:~
$ sudo apt install pipewire pipewire-audio-client-libraries lib32-pipewire pipewire-alsa
[sudo] senha para nome_de_usuario:
Lendo listas de pacotes… Pronto
Construindo árvore de dependências… Pronto
Lendo informação de estado… Pronto
E: Impossível encontrar o pacote lib32-pipewire
E: Impossível encontrar o pacote pipewire-alsa
nome_de_usuario@antix:~
$

Na página http://ftp.br.debian.org/debian/pool/main/p/pipewire/ existe apenas o pacote “pipewire-alsa”, tanto o comando apt no Terminal, quanto o Synaptic que não conseguem encontrar os pacotes “lib32-pipewire” e “pipewire-alsa”.

[Member stevesr0]

Helpful

Up

0

::

Hi marcelocripe,

Thanks for trying this.

I just checked and the pipewire-alsa package is available only on Unstable and Testing. Debian doesn’t have a lib32-pipewire package in any repo as far as I see.

So the Artix solution isn’t applicable.

Sorry for wild goose chase <g>.

stevesr0

————————————————–

Oi marcelocripe,

Obrigado por tentar isso. Acabei de verificar e o pacote pipewire-alsa está disponível apenas em Instável e Teste. Debian não tem um pacote lib32-pipewire em qualquer repo, tanto quanto eu vejo.

Então a solução Artix não é aplicável.

Desculpe pela caça ao ganso selvagem.

stevesr0

[Member marcelocripe]

Helpful

Up

0

::

–

[Member stevesr0]

Helpful

Up

0

::

Hi all,

Several posts about running Pipewire without systemd (including WITHOUT elogind/libelogind0) have been recently exchanged on the thread, “What are the different types of dependencies?”.

Notably, anticapitalista posted a link to Pipewire packages he created that are systemd free for testing.

I will post about my efforts to make these packages work without elogind/libelogind0 on this thread.

stevesr0

• This reply was modified 8 months, 2 weeks ago by stevesr0.

[Moderator Brian Masinick]

Helpful

Up

0

::

@stevesr0: Thanks for your efforts and also taking the time to learn how it works.

--
Brian Masinick

[Member olsztyn]

Helpful

Up

0

::

stevesr0 wrote:

I will post about my efforts to make these packages work without elogind/libelogind0 on this thread.

Just to add to Brian’s note, pursuing this project to make pipewire work in antiX is greatly appreciated. Although current antiX *elogind*-free is optional, the future versions (starting with soon to come antiX 22) will come as *elogind*-free by default. It would be great to adopt this new pipewire technology going forward.
This is very encouraging that anticapitalista created systemd-free and *elogind*-free packages to test and further develop. I tried and failed but I am just at the beginning of this challenging curve so it will take some time to figure this new technology out…
Thanks very much for your spearheading this project…

• This reply was modified 8 months, 2 weeks ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member stevesr0]

Helpful

Up

0

::

(UPDATE: See following post)

Hi Brian and olsztyn,

Thanks for you kind comments. I am very aware of my limited skills and great ignorance, so any assistance is gratefully received and tried out.

Yesterday in the thread on “types of dependencies”, I posted an error message

I see an error message about a missing file (module-rt.c in libwireplumber-module-logind.so) and an error in m-lua-scripting in ../modules/modules-rt.c.

So, I will have to look to see if anyone on the internet has dealt with this.

Today, I saw a post from someone running Void Linux (https://gitlab.freedesktop.org/pipewire/wireplumber/~/issues/236), which was solved by

"running as a dbus-session by creating a simple runit service: 

#/bin/sh
sv check pipewire > /dev/null || /dev/null || exit 1
exec env HOME=/var/run/pipewire chpst -u _pipewire:_pipewire:audio:video dbus-run-session wireplumber

The poster was lacking a /usr/lib/x86_64-gnu-linux/wireplumber/libwireplumber-module-logind.so. On my working install, there is such a file. On the live usb,that file doesn’t exist.

So in the absence of an install which generates a wirplumber-module-logind.so file, apparently a dbus session has to be started by other means.

Since the live usb is using runit as an init (my first time trying it), I guess I could use the same script?

My challenge is to make this work without a reboot, unless I can add persistence or logout and log back in without changing the system. I haven’t seen this listed as an option. If someone knows the answer, please advise.

I will provide update with substantial progress (or problems) or next Monday, which will give others a chance to help me <g>.

All suggestions welcome!

stevesr0

• This reply was modified 8 months, 2 weeks ago by stevesr0.
• This reply was modified 8 months, 2 weeks ago by stevesr0.

[Moderator Brian Masinick]

Helpful

Up

0

::

Hi @stevesr0: To be honest with you, I do not know the definitive answer to your question because I have not looked into the use of pipeware, nor have I recently used antiX runit sid (though in distant years past I used it often).

MY thoughts on this, since I do not know the answer, provided you have the time and energy to work on this is:

1) Explicitly back up the entire system with a rewrite, remaster, or full backup.
2) Try using the same script that the live USB script uses, and see if it works. If YES, save this result, then reboot and see if it still works.
3) If unsuccessful, examine whatever logs and any other “remains” or information sources that could possibly help, and repeat the process.
4) If you really mess it up, restore from the backup or remastered copy.
5) If you get it right, be sure to remaster the work, then give us a write up, and I’ll be happy to review your work.

Good luck; this is a GREAT idea!

--
Brian Masinick

[Member stevesr0]

Helpful

Up

0

::

Hi all,

Obviously still in full noobie mode. I just realized that I had still elogind and libelogind0 installed. Tried to uninstall and fournd out that the system STRONGLY objects to uninstalling such packages.

So, I need to start with a minimal system like Xaver’s (but at least next time still including dbus).

I will update when I have something useful to say (or seeking help…).

stevesr0

[Author]

Posts