Re: [systemd-devel] [survey] BTRFS_IOC_DEVICES_READY return status

s as /dev/sdf, with sdb/c/d/e being my (multi-type) sdcard, etc, adapter, medialess. Tho if /dev/disk/by-*/* works, I could use that. Tho AFAIK it's udev that fills that in, so udev would be necessary. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a

Re: [systemd-devel] Slow startup of systemd-journal on BTRFS

Goffredo Baroncelli posted on Sat, 14 Jun 2014 09:52:39 +0200 as excerpted: > On 06/14/2014 04:53 AM, Duncan wrote: >> Goffredo Baroncelli posted on Sat, 14 Jun 2014 00:19:31 +0200 as >> excerpted: >> >>> thanks for pointing that. However I am performing my tests o

Re: [systemd-devel] Slow startup of systemd-journal on BTRFS

I could add at this point would be simply noise. But I did consider it important to acknowledge that I had been wrong about the fallocate. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is y

Re: [systemd-devel] Slow startup of systemd-journal on BTRFS

Lennart Poettering posted on Mon, 16 Jun 2014 00:39:39 +0200 as excerpted: > Well, quite frankly I am not entirely sure why fallocate() I was barking up the wrong tree with fallocate(). Sorry. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord,

Re: [systemd-devel] Slow startup of systemd-journal on BTRFS

commented on anything in this area, and neither > did anybody else from the systemd side afaics. THe entire btrfs defrag > thing i wasn't aware of before this thread started on the system ML a > few days ago. I am not sure where you take your ideas about our > "attitude"

Re: [systemd-devel] Slow startup of systemd-journal on BTRFS

t a time. Multi-device-btrfs metadata defaults to raid1-mode, still allocated in chunk pairs but one on each of two separate devices. Data mode always defaults to single, tho on multi-device-btrfs both data and metadata can be (individually) set to various raid modes, each with its own speci

[systemd-devel] Setting up a VPN daemon as a Portable Service

Hi, everyone. The high-level overview: I'm trying to install Tailscale as a portable service on my Steam Deck. Tailscale is a point-to-point VPN service, essentially a wrapper around Wireguard that helps with network setup and management. The Steam Deck is Valve's handhel

Re: [systemd-devel] Setting up a VPN daemon as a Portable Service

advice running as a system extension. > > I think there are mechanisms for setting up system extensions on startup > but I'm not familiar enough with the details. Maybe someone else in the > list knows. > > > > > On Thu, 6 Oct 2022, 20:21 Duncan Gibson, wrote: >

Re: [systemd-devel] Setting up a VPN daemon as a Portable Service

Oh, now that's a new way of doing it. I'll definitely give that a shot. That sounds like it has the best chance of working. On Sat, Oct 8, 2022 at 12:20 PM Luca Boccassi wrote: > On Sat, 2022-10-08 at 11:13 -0400, Duncan Gibson wrote: > > The problem wasn't mount

Re: [systemd-devel] Setting up a VPN daemon as a Portable Service

22 at 2:02 PM Luca Boccassi wrote: > On Sat, 8 Oct 2022 at 18:51, Duncan Gibson wrote: > > > > Hm. Actually, no, I don't think it will. Services installed the normal > way won't survive the A/B update system. > > I don't know what that is and how it works.

Re: [systemd-devel] Setting up a VPN daemon as a Portable Service

Final update, hopefully. Here's a gist with a script, service unit, and readme. <https://gist.github.com/legowerewolf/1b1670457cfac9201ee9d67840952147> On Sun, Oct 9, 2022 at 11:10 AM Duncan Gibson wrote: > After doing some more looking, it seems like the /etc folder is overlaid &

[systemd-devel] Errant error message when starting a service?

rogram_1"? It turns out that if I have several "ExecStartPost=-MISSING_COMMAND" lines, only the first one is silent. Is this by design? I've looked through the source code quite a bit but I have not gotten far enough to dete

[systemd-devel] Bug? /dev/disk/by-path symlinks disappear for iSCSI targets

I was not a "supported parent". I am not aware of any cases where SCSI has given duplicate names to devices Before submitting a patch to fix this for SCSI, I wanted to make sure I understood the intent correctly. Thank you for your help.

Re: [systemd-devel] Bug? /dev/disk/by-path symlinks disappear for iSCSI targets

Ping? I will submit a patch that fixes this regression for SCSI, but I suspect other transports will have problems, too, since the by-path links will now be missing. On 10/07/2014, I wrote: > Date: Tue, 07 Oct 2014 21:21:11 +0500 > From: Lee Duncan > To: systemd-devel@lists.freede

Re: [systemd-devel] Bug? /dev/disk/by-path symlinks disappear, > for iSCSI targets

On 10/12/2014 12:00 PM, Kay Sievers wrote: > > On Tue, Oct 7, 2014 at 6:21 PM, Lee Duncan wrote: >> > I am debugging a problem where the symlinks in /dev/disk/by-path >> > disappeared for iSCSI target devices. >> > >> > I

[systemd-devel] How to use libudev to monitor for /sys/firmware/iscsi_boot*?

evice events? There must be some better way than polling. Thanks. -- Lee Duncan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] How to use libudev to monitor for /sys/firmware/iscsi_boot*?

On 12/05/2014 01:14 PM, Greg KH wrote: > On Fri, Dec 05, 2014 at 11:51:16AM -0800, Lee Duncan wrote: >> Hi: >> >> I am trying to figure out how to use libudev to monitor for new iSCSI >> boot targets. >> >> For Emulex CNA cards, a new directory gets created o