Le 09/01/2022 à 13:23, Benjamin Riefenstahl a écrit :
Hi Didier,
Didier Kryn writes:
But the launchers are to be installed/uninstalled by every user in
their own ~/.local
benny wrote:
What happens, if you add another user after installation? AFAIU default
launchers should be in a global pla
Hi Didier,
>> Didier Kryn writes:
>>> But the launchers are to be installed/uninstalled by every user in
>>> their own ~/.local
benny wrote:
>> What happens, if you add another user after installation? AFAIU default
>> launchers should be in a global place.
Didier Kryn writes:
> We want to
Le 08/01/2022 à 20:40, Benjamin Riefenstahl a écrit :
Hi Didier,
Didier Kryn writes:
But the launchers are to be installed/uninstalled by every user in
their own ~/.local
What happens, if you add another user after installation? AFAIU default
launchers should be in a global place.
We wan
Hi Didier,
Didier Kryn writes:
> But the launchers are to be installed/uninstalled by every user in
> their own ~/.local
What happens, if you add another user after installation? AFAIU default
launchers should be in a global place.
benny
___
Dng maili
Le 08/01/2022 à 17:18, tito via Dng a écrit :
On Sat, 8 Jan 2022 15:56:19 +0100
Didier Kryn wrote:
Le 07/01/2022 à 23:27, Hendrik Boom a écrit :
Install can be user-configurable, this is easy, but the package
provides
the way to uninstall and, for the uninstall to work, the install
must
On Sat, 8 Jan 2022 15:56:19 +0100
Didier Kryn wrote:
> Le 07/01/2022 à 23:27, Hendrik Boom a écrit :
> >> Install can be user-configurable, this is easy, but the package
> >> provides
> >> the way to uninstall and, for the uninstall to work, the install must be
> >> hardcoded because the so
Le 07/01/2022 à 23:27, Hendrik Boom a écrit :
Install can be user-configurable, this is easy, but the package provides
the way to uninstall and, for the uninstall to work, the install must be
hardcoded because the source of the package cannot remember what the user
has done at install time.
On Fri, Jan 07, 2022 at 05:48:08PM +0100, Didier Kryn wrote:
> Le 07/01/2022 à 12:13, Olaf Meeuwissen a écrit :
> > > Concerning installation in /usr/local:
> > > --
> > >
> > > My first investigations indicate that there is provision in
> > > Freedesktop.or
Le 07/01/2022 à 12:13, Olaf Meeuwissen a écrit :
Concerning installation in /usr/local:
--
My first investigations indicate that there is provision in
Freedesktop.org to put icons and launchers under $HOME/.local, but
nothing for /usr/local. Therefore the
Le 07/01/2022 à 13:06, Benjamin Riefenstahl a écrit :
Hi Didier,
Didier Kryn writes:
My first investigations indicate that there is provision in
Freedesktop.org to put icons and launchers under $HOME/.local, but
nothing for /usr/local.
I do not think that ~/.local is related to /usr/local
Hi Didier,
Didier Kryn writes:
> Le 07/01/2022 à 10:18, Didier Kryn a écrit :
>> Le 06/01/2022 à 22:00, Bob Proulx via Dng a écrit :
>>> Didier Kryn wrote:
Hendrik Boom a ecrit :
>>> software that isn't properly packaged as a .deb, but instead has an
>>> "installer" that needs to be
On 1/7/22 8:59 AM, Hendrik Boom wrote:
On Fri, Jan 07, 2022 at 11:44:59AM +0100, Didier Kryn wrote:
Le 07/01/2022 à 10:18, Didier Kryn a écrit :
Le 06/01/2022 à 22:00, Bob Proulx via Dng a écrit :
Didier Kryn wrote:
Hendrik Boom a ecrit :
software that isn't properly packaged as a .deb, but
On Fri, Jan 07, 2022 at 11:44:59AM +0100, Didier Kryn wrote:
> Le 07/01/2022 à 10:18, Didier Kryn a écrit :
> > Le 06/01/2022 à 22:00, Bob Proulx via Dng a écrit :
> > > Didier Kryn wrote:
> > > > Hendrik Boom a ecrit :
> > > > > > > software that isn't properly packaged as a .deb, but
> > > > > >
Hi Didier,
Didier Kryn writes:
> My first investigations indicate that there is provision in
> Freedesktop.org to put icons and launchers under $HOME/.local, but
> nothing for /usr/local.
I do not think that ~/.local is related to /usr/local in any meaningfull
way. /usr/local is for the adm
Le 07/01/2022 à 10:18, Didier Kryn a écrit :
Le 06/01/2022 à 22:00, Bob Proulx via Dng a écrit :
Didier Kryn wrote:
Hendrik Boom a ecrit :
software that isn't properly packaged as a .deb, but instead has an
"installer" that needs to be run as root.
Immediately I think of all of those script "
Le 06/01/2022 à 22:00, Bob Proulx via Dng a écrit :
Didier Kryn wrote:
Hendrik Boom a ecrit :
software that isn't properly packaged as a .deb, but instead has an
"installer" that needs to be run as root.
Immediately I think of all of those script "installers" that request
the user do this and
On Thu, Jan 06, 2022 at 02:00:57PM -0700, Bob Proulx via Dng wrote:
>
> > > > If the installer must be run as root, it is precisely because it
> > > > needs
> > > > to install software in /usr.
>
> Or into /usr/local which now requires root. Back in the better days
> of Debian it used to be
Didier Kryn wrote:
> Hendrik Boom a ecrit :
> > > > software that isn't properly packaged as a .deb, but instead has an
> > > > "installer" that needs to be run as root.
Immediately I think of all of those script "installers" that request
the user do this and similar to install their software as r
Le 05/01/2022 à 23:12, Hendrik Boom a écrit :
On Wed, Jan 05, 2022 at 09:54:20PM +0100, Didier Kryn wrote:
Le 05/01/2022 à 16:11, Hendrik Boom a écrit :
On Wed, Jan 05, 2022 at 12:08:18AM +0100, Didier Kryn wrote:
Le 04/01/2022 à 23:38, Hendrik Boom a écrit :
On Tue, Jan 04, 2022 at 05:09:58P
On Wed, Jan 05, 2022 at 09:54:20PM +0100, Didier Kryn wrote:
> Le 05/01/2022 à 16:11, Hendrik Boom a écrit :
> > On Wed, Jan 05, 2022 at 12:08:18AM +0100, Didier Kryn wrote:
> > > Le 04/01/2022 à 23:38, Hendrik Boom a écrit :
> > > > On Tue, Jan 04, 2022 at 05:09:58PM +0100, Didier Kryn wrote:
> >
Le 05/01/2022 à 16:11, Hendrik Boom a écrit :
On Wed, Jan 05, 2022 at 12:08:18AM +0100, Didier Kryn wrote:
Le 04/01/2022 à 23:38, Hendrik Boom a écrit :
On Tue, Jan 04, 2022 at 05:09:58PM +0100, Didier Kryn wrote:
There is no utility in splitting the OS in several partitions.
Might it make se
On Wed, Jan 05, 2022 at 12:08:18AM +0100, Didier Kryn wrote:
> Le 04/01/2022 à 23:38, Hendrik Boom a écrit :
> > On Tue, Jan 04, 2022 at 05:09:58PM +0100, Didier Kryn wrote:
> > > There is no utility in splitting the OS in several partitions.
> > Might it make sense to have /usr mounted readonly ex
Aitor:
> On 4/1/22 22:17, k...@aspodata.se wrote:
> > the problem is that the lib is on a
> > filesystem that isn't available at kernel to init handover time.
> Did you try something like this:
> copy_exec /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> in a hook located at/usr/share/initramfs-tools, i
Hi Karl,
On 4/1/22 22:17, k...@aspodata.se wrote:
the problem is that the lib is on a
filesystem that isn't available at kernel to init handover time.
Did you try something like this:
copy_exec /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
in a hook located at/usr/share/initramfs-tools, in order
Le 04/01/2022 à 23:38, Hendrik Boom a écrit :
On Tue, Jan 04, 2022 at 05:09:58PM +0100, Didier Kryn wrote:
There is no utility in splitting the OS in several partitions.
Might it make sense to have /usr mounted readonly except when upgradng
or installing paackages?
What could you fear whic
On Tue, Jan 04, 2022 at 05:09:58PM +0100, Didier Kryn wrote:
> There is no utility in splitting the OS in several partitions.
Might it make sense to have /usr mounted readonly except when upgradng
or installing paackages?
-- hendrik
___
Dng mailing li
Antoine:
> On Monday, 3 January at 18:25, k...@aspodata.se wrote:
...
> >$ ldd /sbin/init | grep /usr
> >libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> > (0x7f737ba28000)
...
> Maybe your /etc/ld.so.cache is misconfigured?
...
What makes you believe that ?
ld.so.cach
On Monday, 3 January at 18:25, k...@aspodata.se wrote:
The first one gives me an unbootable system
$ ldd /sbin/init | grep /usr
libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
(0x7f737ba28000)
fortunately /bin/bash didn't depend on /usr so I could boot with
init=/bin/ba
Le 04/01/2022 à 18:48, k...@aspodata.se a écrit :
Didier:
The simplest way to kick off problms with /usr merge is to *not*
make /usr a mountpoint.
Perhaps, but why break working systems, especially when they are
3h car ride from home and all in differnt locations.
That is just rude.
There is
Didier:
> The simplest way to kick off problms with /usr merge is to *not*
> make /usr a mountpoint.
Perhaps, but why break working systems, especially when they are
3h car ride from home and all in differnt locations.
That is just rude.
> There is no utility in splitting the OS in several parti
> On Jan 4, 2022, at 11:10 AM, Didier Kryn wrote:
>
> The simplest way to kick off problms with /usr merge is to *not* make
> /usr a mountpoint. There is no utility in splitting the OS in several
> partitions. This wouldn't help you recover the OS if one partition is broken
> since the
The simplest way to kick off problms with /usr merge is to *not*
make /usr a mountpoint. There is no utility in splitting the OS in
several partitions. This wouldn't help you recover the OS if one
partition is broken since the package manager installs/deinstalls files
not only on /usr, but
Ralph:
> On Mon, 3 Jan 2022 18:25:12 +0100 (CET)
> k...@aspodata.se wrote:
> > The first one gives me an unbootable system
> > $ ldd /sbin/init | grep /usr
> > libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> > (0x7f737ba28000)
> >
> > fortunately /bin/bash didn't depe
On Mon, 3 Jan 2022 18:25:12 +0100 (CET)
k...@aspodata.se wrote:
> The first one gives me an unbootable system
> $ ldd /sbin/init | grep /usr
> libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> (0x7f737ba28000)
>
> fortunately /bin/bash didn't depend on /usr so I could
Steve Litt:
> k...@aspodata.se said on Tue, 4 Jan 2022 00:08:01 +0100 (CET)
...
> >busybox can replace the mount command, but there is no fsck.* in
> >busybox.
>
> Rather than fighting the mostly political fight of usr-merge,
If it makes systems unbootable it isn't a "political" fight.
> my fir
k...@aspodata.se said on Tue, 4 Jan 2022 00:08:01 +0100 (CET)
>Karl:
>> The first one gives me an unbootable system
>> $ ldd /sbin/init | grep /usr
>> libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
>> (0x7f737ba28000)
>>
>> fortunately /bin/bash didn't depend on /usr
Martin:
> k...@aspodata.se - 03.01.22, 18:25:12 CET:
> > The first one gives me an unbootable system
> > $ ldd /sbin/init | grep /usr
> > libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> > (0x7f737ba28000)
> [â¦]
> > Soo, what can I do to help with that ?
> https://manpa
k...@aspodata.se - 03.01.22, 18:25:12 CET:
> The first one gives me an unbootable system
> $ ldd /sbin/init | grep /usr
> libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> (0x7f737ba28000)
[…]
> Soo, what can I do to help with that ?
https://manpages.debian.org/bullseye/d
Karl:
> The first one gives me an unbootable system
> $ ldd /sbin/init | grep /usr
> libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
> (0x7f737ba28000)
>
> fortunately /bin/bash didn't depend on /usr so I could boot with
> init=/bin/bash, but there is more breakage:
..
The first one gives me an unbootable system
$ ldd /sbin/init | grep /usr
libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0
(0x7f737ba28000)
fortunately /bin/bash didn't depend on /usr so I could boot with
init=/bin/bash, but there is more breakage:
$ ldd /bin/mount | gr
40 matches
Mail list logo
