Yes send me the link so I can learn.

@exponentialmatrix: I'm sorry for all those irrelevant posts on this thread.

You are quite welcome to setup your "Devuan User Repository" on git.devuan.org using the means provided. I know you would like the "user organisations" feature, and if that is a show stopper for you, then it's understandable that you can't use the Devuan's git store.

One avenue for inducing change to Devuan's setup could be to engage with other people than just me. For example, you could take part in the weekly (video) meetings, and in there try to push for the particular changes you want to see. Though it probably will take engagement effort and that you maintain your community oriented spirit.

... Plus perhaps that you reflect on your position regarding organisational shrouding on the git store so as to be able to explain it to us at least how your case is different (and especially not a way to avoid or reduce personal responsibility). We are all just people, with a range of different understandings and opinions, and your views will matter as well.

@exponentialmatrix: perhaps my suggestion doesn't fit your purpose.

Yes, Devuan's git store doesn't have "user organisations" enabled.

The git store is only intended for users keeping and sharing their "source code".

Though, obviously life is full of change. Perhaps you (or someone) will make a sufficiently compelling argument that organisational shrouding is a necessary or at least significantly useful feature for this purpose, and so make us re-open that discussion about its enabling.

But there is no formal vetting here, about the software a user keeps and shares; merely the ordinary care-taking spot reviews that rests heavily on community feedback as means of maintaning relevance and quality.

you need to add a parameter to qemu so that it attaches its "monitor" to either a socket that you can connect to, OR as multiplexed with the serial console.

For the first option, you add the qemu command line arguments -monitor unix:QEMU,server,nowait, and thereby get its monitor serving the socket QEMU in the working directory. You then connect to that via socat with a command like the following

socat -,escape=0x1c,rawer unix:QEMU

which sets up a raw termnal connection to that monitor; you break the connection with key ctrl-\ (control-backslash).

For the second option you instead modify (or add) serial line arguments to be -serial mon:stdio, and thereby get multiplexed monitor and serial console on the run terminal. In that case it starts in serial mode so you need to press ctrl-a c to switch to the qemu monitor.

Then, once you have the monitor, you will issue the commands like sendkey ctrl-alt-f2 etc so as to make the monitor send that key.

hth

We'll stop here.

The first step here is to realize that "packages" implement "functions" (or "facilities", or "virtual services").

Often, most usually, and as normal case, the "function" name is impliedby the package that implements it, so that every package automatically and implicitly provides its function. (That's how language works, isn't it)

Like, the package "udev" provides the function "udev".

However some packages are declared to *provide* aditional functions, such that for example package "eudev" provides "udev"; that is simply the promise for the dependecy system that when you install "eudev" you'll get all API and ABI that is originally provided by "udev".

It's not an uncommon or new thing, and I can't answer why dpkg lodges an error message for it. That whinging is new to me. Possibly it just whinges about that your system has both "udev" as a package and some other package, perhaps eudev, that is declared to provide "udev". Though I'd be eager to learn better or more exactly about this.

1) "/var/log/syslog" is a file. you could use "less /var/log/syslog" to view it.

2) It appears you try to install on the installer USB. Perhaps you meant to install on /dev/sdb rather?

Hmm I've never seen the installer give the message "writing to my partition failed". Perhaps you could show a photo?

One of the policy choices for Devuan experimental is that its packages must reside at git.devuan.org, so that would be your first step. Next, the building would be off branch suites/experimental

Many of those details remain dutifully hidden from public at
https://git.devuan.org/devuan/documenta … aintainers

What is DOT ?