Ludwig Nussel wrote:
JFYI openSUSE now has a MicroOS (transactional system with read-only /)
qcow image¹ suitable for use in qemu that uses systemd-boot. The image
is part of the Tumbleweed development process and automatically released
(ie potentially daily). It's fully integrated with
d-boot#Pre-built_MicroOS
[5] https://paste.opensuse.org/pastes/5e1a934d915f
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions Germany GmbH; GF: Ivo Totev, Andrew
McDonald, Werner Knoblich; HRB 36809 (AG Nürnberg)
to give it a try. Or find
arguments why dlopen is still the lesser evil for the sake of
documenting that for the future :-)
cu
Ludwig
[1]
https://manpages.opensuse.org/Tumbleweed/binutils/ld.1.en.html#auxiliary=
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions G
ttach to the console of a
container by means of machinectl?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions Germany GmbH, GF: Ivo Totev
HRB 36809 (AG Nürnberg)
Chris Murphy wrote:
> On Tue, Nov 9, 2021 at 8:48 AM Ludwig Nussel wrote:
>> Lennart Poettering wrote:
>>> Or to say this explicitly: we could define the spec to say that if
>>> we encounter:
>>>
>>>/@auto/root-x86-64:fedora_36.0+3-0
Lennart Poettering wrote:
> On Mo, 08.11.21 14:24, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> [...]
>> MicroOS has a similar situation. It edits /etc/fstab.
>
> microoos is a suse thing?
Yeah. https://get.opensuse.org/microos/
It uses regular package management but instead
.
Anyway in the above example I guess if you install some updates you'd
get eg root-x86-64:fedora_37.2, .3, .4 etc?
I suppose the autodetection is meant to boot the one sorted last. What
if that one turns out to be bad though? How to express rollback in that
model?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions Germany GmbH, GF: Ivo Totev
HRB 36809 (AG Nürnberg)
Kay Sievers wrote:
On Sat, Mar 23, 2013 at 1:57 PM, Kay Sievers wrote:
On Sat, Mar 23, 2013 at 12:16 AM, Lennart Poettering
wrote:
On Tue, 19.03.13 17:36, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
useful to get ACLs on files, sockets etc not known to udev
Can't say I like thi
Tom Gundersen wrote:
On Tue, Mar 19, 2013 at 5:36 PM, Ludwig Nussel wrote:
useful to get ACLs on files, sockets etc not known to udev
Do you have a particular use case in mind?
There are certain proprietary kernel modules that cannot properly
register their device nodes but nevertheless
useful to get ACLs on files, sockets etc not known to udev
---
src/login/logind-acl.c | 59 ++
1 file changed, 59 insertions(+)
diff --git a/src/login/logind-acl.c b/src/login/logind-acl.c
index cb045a9..a44ecdc 100644
--- a/src/login/logind-acl.c
+
user.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
___
systemd-devel mailing list
systemd-devel@lists.freedeskto
doesn't look like a
good idea to me. nss-myhostname may work as workaround to trick some
broken legacy applications but breaks others that have valid reasons to
check whether the hostname can be resolved. Returning fake entries is
not a good solution.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
eplaced behind their back. Asking the user to
reboot just to update e.g. the web browser or mail client would be
retarded though. There has to be a better way.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn
ly preset now" command though.
During package installation the preset package(s) may get installed
after the actual services. You may also need to call that command
when switching presets for whatever reason.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Produ
s, ideas?
Good idea in general. Checking simple files instead of trying to
make sense of shell code in %post also makes life easier for rpmlint.
cu
Ludwig
[1] back in the days when we nearly got lynched for disabling sshd
by default we explicitly decided not to split the package in client
and s
ncluding the symlink in %files instead?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
___
systemd-devel mailing list
sy
we are using.
>
> Hmm, given the rigorous compat logic glibc includes this might be safe,
> so let's merge it. If it breaks, then we can still revisit the issue.
It did indeed break at least once in the past. glibc 2.2/2.3 or
something like that.
Also keep in mind that you are lo
Lennart Poettering wrote:
> On Mon, 04.04.11 13:41, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
>
> > > There are. A lot of software creates subdirectories beneath
> > > /var/lock, for example LVM. If you allow creation of lockfiles in
> > > /var/lock, then
Lennart Poettering wrote:
> On Mon, 04.04.11 10:56, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> > Lennart Poettering wrote:
> >
> > So as long as there are no inherently unsolvable problems
> > with lockdev using /var/lock directly I see no need to go the a half
>
Lennart Poettering wrote:
> On Fri, 01.04.11 16:37, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> > In any case declaring some directory as the standard place for lock
> > files doesn't fully solve the problem anyways. The exact lock file
> > naming isn't quite
Lennart Poettering wrote:
> On Fri, 01.04.11 11:37, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> > Lennart Poettering wrote:
> > > I'd like to see this cleaned up and standardized in a secure way among
> > > the distros, so here's what I propose for adoption:
tly
use the new method, we'd have one less ugly setgid program, the stale
lock file problem wouldn't exist anymore and locking would work for
chroots too.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernber
Kay Sievers wrote:
> On Mon, Mar 28, 2011 at 13:28, Ludwig Nussel wrote:
> > Bill Nottingham wrote:
> >> Andrey Borzenkov (arvidj...@gmail.com) said:
> >> > On Fri, Mar 25, 2011 at 7:07 AM, Kay Sievers
> >> > wrote:
> >> > > Instead
shutdown.
mount --bind /var/run /mnt
mount /var
mount -M /mnt /var/run
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
___
systemd-devel mailing list
systemd-d
Kay Sievers wrote:
> On Thu, Dec 16, 2010 at 23:34, Ludwig Nussel wrote:
> > Kay Sievers wrote:
> >> On Sun, Nov 28, 2010 at 14:06, Ludwig Nussel wrote:
> >> > Kay Sievers wrote:
> >> >> On Fri, Nov 26, 2010 at 18:56, Gustavo Sverzut Barbieri
> &
Kay Sievers wrote:
> On Sun, Nov 28, 2010 at 14:06, Ludwig Nussel wrote:
> > Kay Sievers wrote:
> >> On Fri, Nov 26, 2010 at 18:56, Gustavo Sverzut Barbieri
> >> wrote:
> >> > On Fri, Nov 26, 2010 at 2:17 PM, Dr. Werner Fink wrote:
> >> >
s against udev,
> D-Bus, ... and udev, D-Bus, ... would link against systemd. That would
> need to be sorted out.
Should be no problem in OBS. Just use a source link and a second
spec file that only compiles the shared lib (manually if needed). That way
systemd and the lib are compiled indepe
Lennart Poettering wrote:
> On Tue, 16.11.10 09:36, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> > Lennart Poettering wrote:
> > > On Mon, 15.11.10 16:50, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
> > >
> > > > > Fixed this now. Ideally Deb
Lennart Poettering wrote:
> On Mon, 15.11.10 16:50, Ludwig Nussel (ludwig.nus...@suse.de) wrote:
>
> > > Fixed this now. Ideally Debian/Ubuntu would stop renaming agetty like
> > > this, or at least do it via symlink only. I'd love to get rid of the
> > >
ic
> systemd we print them for all services (including D-Bus services, which
> actually account for more services than SysV on most setups right
> now). The effect of that is that services come all the time and there's
> little point in synchronizing getty startup to that.
The
Gustavo Sverzut Barbieri wrote:
> On Mon, Nov 15, 2010 at 7:05 AM, Ludwig Nussel wrote:
> > Lennart Poettering wrote:
> > [...]
> >> I am really not a big fan of Suse's $ALL extension.
> >
> > Making SuSEfirewall2 run last via $ALL mostly is a boot sp
ports. SuSEfirewall2 can't do either
operation incrementally (yet). So if it's known beforehand that an
event would cause several SuSEfirewall2 calls it's better to block
all calls and only do one full run at the end. That's the case
during boot and when calling rcnetwork restart.
32 matches
Mail list logo
