From drmarwat at gmail.com  Wed Feb  5 15:23:07 2020
From: drmarwat at gmail.com (Saleem Khan)
Date: Wed, 5 Feb 2020 14:23:07 +0000
Subject: Request for two packages
Message-ID: <CAOV1EpGrJAke2rnOKFthdA3Aes1dS6T=upw7+_1iiQTufrshUQ@mail.gmail.com>

Hello,

Can we have following packages added to the repositories please?

1 ) Bleachbit

2 ) Stacer

Regards,

-- 
Dr.Saleem Khan Marwat
Abbottabad
Khyber-Pakhtunkhwa
Pakistan
Cell # +92333-5393854
WhatsApp # +92333-5393854
Email: drmarwat at gmail.com
Web:  http://saleem-khan.blogspot.com
Registered GNU/Linux User # 413133
Since Aug 2003


From gotar at polanet.pl  Wed Feb  5 19:57:59 2020
From: gotar at polanet.pl (Tomasz Pala)
Date: Wed, 5 Feb 2020 19:57:59 +0100
Subject: Request for two packages
In-Reply-To: <CAOV1EpGrJAke2rnOKFthdA3Aes1dS6T=upw7+_1iiQTufrshUQ@mail.gmail.com>
References: <CAOV1EpGrJAke2rnOKFthdA3Aes1dS6T=upw7+_1iiQTufrshUQ@mail.gmail.com>
Message-ID: <20200205185759.GA21481@polanet.pl>

Hello,

On Wed, Feb 05, 2020 at 14:23:07 +0000, Saleem Khan wrote:

> Can we have following packages added to the repositories please?
> 
> 1 ) Bleachbit
> 2 ) Stacer

Unless someone provides spec files, I doubt such programs would land in
PLD anytime soon. Both seem of little use for properly managed system.

-- 
Tomasz Pala <gotar at pld-linux.org>


From mike at altlinux.org  Wed Feb  5 23:11:24 2020
From: mike at altlinux.org (Michael Shigorin)
Date: Thu, 6 Feb 2020 01:11:24 +0300
Subject: Request for two packages
In-Reply-To: <20200205185759.GA21481@polanet.pl>
References: <CAOV1EpGrJAke2rnOKFthdA3Aes1dS6T=upw7+_1iiQTufrshUQ@mail.gmail.com>
 <20200205185759.GA21481@polanet.pl>
Message-ID: <20200205221124.GC12283@imap.altlinux.org>

On Wed, Feb 05, 2020 at 07:57:59PM +0100, Tomasz Pala wrote:
> On Wed, Feb 05, 2020 at 14:23:07 +0000, Saleem Khan wrote:
> > Can we have following packages added to the repositories please?
> > 1 ) Bleachbit
> > 2 ) Stacer
> Unless someone provides spec files, I doubt such programs would land in
> PLD anytime soon. Both seem of little use for properly managed system.

Saleem has already asked for bleachbit in ALT, here it is:
http://git.altlinux.org/gears/b/bleachbit.git?p=bleachbit.git;a=tree
http://bugzilla.altlinux.org/23106

Hope the already-tested package helps :-)

-- 
?---- WBR, Michael Shigorin / http://altlinux.org
??------ http://opennet.ru / http://anna-news.info


From arekm at maven.pl  Thu Feb  6 19:20:26 2020
From: arekm at maven.pl (=?UTF-8?Q?Arkadiusz_Mi=c5=9bkiewicz?=)
Date: Thu, 6 Feb 2020 19:20:26 +0100
Subject: migrating pld /var/run to /run (and related dirs)
Message-ID: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>


Hi.

We need to finally do this while still keeping sysvinit compatibility
(using symlinks).

Migrate

/var/run to /run and keep /var/run -> /run symlink
/var/lock to /run/lock and /var/lock -> /run/lock symlink
/run/shm -> /dev/shm symlink
(any other?)

I wonder what is the best approach to do that on live servers.

Debian: https://wiki.debian.org/ReleaseGoals/RunDirectory

I guess migration needs to be in rc.sysinit. After rootfs and /var mount do:
- create /run dirs and convert old dirs to symlinks
- add /run* tmpfs mounting entries to /etc/fstab if not existent, so
next time migration logic via rc.sysinit will not be needed at all.

Or do fstab entries on rc-scripts package upgrade and only change
/var/dirs to symlinks in rc.sysinit.

End result is that /run entries are always tmpfs mounts while /var/ has
symlinks for backward compatibility.

Ideas?

-- 
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )


From gotar at polanet.pl  Sat Feb  8 18:52:34 2020
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 8 Feb 2020 18:52:34 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
Message-ID: <20200208175234.GA20513@polanet.pl>

On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Mi?kiewicz wrote:

> We need to finally do this while still keeping sysvinit compatibility
> (using symlinks).

Why do we need to do this? Legacy SysVinit uses /var/run and works,
while systemd systems are already handled well (tmpfiles etc.) in /run.

In other words: what problem are you going to solve and in which
scenarios? IMHO the /etc/init.d/ scripts should be kept as they are.

-- 
Tomasz Pala <gotar at pld-linux.org>


From jajcus at jajcus.net  Sat Feb  8 20:00:47 2020
From: jajcus at jajcus.net (Jacek Konieczny)
Date: Sat, 8 Feb 2020 20:00:47 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <20200208175234.GA20513@polanet.pl>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
 <20200208175234.GA20513@polanet.pl>
Message-ID: <e8b87b64-79e2-2d45-27e8-a0511731b635@jajcus.net>

On 2/8/20 6:52 PM, Tomasz Pala wrote:
> On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Mi?kiewicz wrote:
> 
>> We need to finally do this while still keeping sysvinit compatibility
>> (using symlinks).
> 
> Why do we need to do this? Legacy SysVinit uses /var/run and works,
> while systemd systems are already handled well (tmpfiles etc.) in /run.

New systemd won't even boot properly when /run is a symlink. And many
system components rely on /run and /var/run contents to be the same,
especially when they are supposed to run on SysVinit and systemd systems
with the same default config.

> In other words: what problem are you going to solve and in which
> scenarios? IMHO the /etc/init.d/ scripts should be kept as they are.

That is why the /var/run -> /run symlink should be provided.

Jacek


From gotar at polanet.pl  Sat Feb  8 20:08:39 2020
From: gotar at polanet.pl (Tomasz Pala)
Date: Sat, 8 Feb 2020 20:08:39 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <e8b87b64-79e2-2d45-27e8-a0511731b635@jajcus.net>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
 <20200208175234.GA20513@polanet.pl>
 <e8b87b64-79e2-2d45-27e8-a0511731b635@jajcus.net>
Message-ID: <20200208190839.GA11070@polanet.pl>

On Sat, Feb 08, 2020 at 20:00:47 +0100, Jacek Konieczny wrote:

> New systemd won't even boot properly when /run is a symlink. And many

How about mount --bind?

> That is why the /var/run -> /run symlink should be provided.

Yes, what is I'm afraid is that our rpm doesn't handle dir->symlink
transition.
We still need to clean /var/run at system start as long as we support
kernels without tmpfs.

-- 
Tomasz Pala <gotar at pld-linux.org>


From baggins at pld-linux.org  Sun Feb  9 10:09:29 2020
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 9 Feb 2020 10:09:29 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <e8b87b64-79e2-2d45-27e8-a0511731b635@jajcus.net>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
 <20200208175234.GA20513@polanet.pl>
 <e8b87b64-79e2-2d45-27e8-a0511731b635@jajcus.net>
Message-ID: <20200209090929.GC2224@starbug>

On Sat, 08 Feb 2020, Jacek Konieczny wrote:

> On 2/8/20 6:52 PM, Tomasz Pala wrote:
> > On Thu, Feb 06, 2020 at 19:20:26 +0100, Arkadiusz Mi?kiewicz wrote:
> > 
> >> We need to finally do this while still keeping sysvinit compatibility
> >> (using symlinks).
> > 
> > Why do we need to do this? Legacy SysVinit uses /var/run and works,
> > while systemd systems are already handled well (tmpfiles etc.) in /run.
> 
> New systemd won't even boot properly when /run is a symlink. And many

Do we even have that anywhere (/run as symlink)?

poldek:/all-avail> desc -ll FHS | grep /run
mode            size	name
drwxr-xr-x         6	/run
drwxr-xr-x         6	/var/run/

And FHS.spec commit 4e9a06c31d tells me it was so from the very start.

Our current systemd package has var-run.mount bind mounting /run there,
so in this case is just a matter of removing that file and symlinking
/var/run on next boot.

Don't know how it looks for SysVinit running systems, but can't be more
complicated IMHO.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From baggins at pld-linux.org  Sun Feb  9 10:13:37 2020
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 9 Feb 2020 10:13:37 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
Message-ID: <20200209091337.GD2224@starbug>

On Thu, 06 Feb 2020, Arkadiusz Mi?kiewicz wrote:

> 
> Hi.
> 
> We need to finally do this while still keeping sysvinit compatibility
> (using symlinks).
> 
> Migrate
> 
> /var/run to /run and keep /var/run -> /run symlink
> /var/lock to /run/lock and /var/lock -> /run/lock symlink
> /run/shm -> /dev/shm symlink
> (any other?)
> 
> I wonder what is the best approach to do that on live servers.
> 
> Debian: https://wiki.debian.org/ReleaseGoals/RunDirectory
> 
> I guess migration needs to be in rc.sysinit. After rootfs and /var mount do:
> - create /run dirs and convert old dirs to symlinks
> - add /run* tmpfs mounting entries to /etc/fstab if not existent, so
> next time migration logic via rc.sysinit will not be needed at all.

/run should already be a dir. Looks at FHS.spec.

I see one problem with your rc.sysinit proposal, what about systemd
systems? You do need to do the convertsion, and you don't have that
file.

What about plugging all this symlinking into geninitrd / dracut?
This way we would have everything sorted before we even start booting to
the filesystem in question.

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From baggins at pld-linux.org  Sun Feb  9 11:36:46 2020
From: baggins at pld-linux.org (Jan =?utf-8?Q?R=C4=99korajski?=)
Date: Sun, 9 Feb 2020 11:36:46 +0100
Subject: The proliferation of kernel packages (plan to drop nopae, 4.4
 and 4.14)
In-Reply-To: <5E2D77B3.208@pld-linux.org>
References: <20200123113645.GA2224@starbug>
 <5E2D77B3.208@pld-linux.org>
Message-ID: <20200209103646.GF2224@starbug>

On Sun, 26 Jan 2020, Marcin Krol wrote:

> On 23-Jan-20 12:36, Jan R?korajski wrote:
> > I want to drop nopae, 4.4 and 4.14 kernels from Th,
> > leaving us with longterm releases 4.9 (the last kernel that supports vserver),
> > 4.19, 5.4 and a latest stable.
> >
> > Thoughs? Cons?
> 
> 4.14 has longest planned support - up to Jan 2024 while 4.19 will EOL on 
> Dec 2020 and 5.4 will EOL on Dec 2021. It may be a good idea to keep 
> 4.14. Of course these date may change in future.

Good point.

That said, I will soon drop 4.4, 4.19 and nopae kernel.

And disable PAE on i686 kernel on head.

https://cl4ssic4l.wordpress.com/2011/05/24/linus-torvalds-about-pae/

-- 
Jan R?korajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/


From gotar at polanet.pl  Sun Feb  9 13:30:59 2020
From: gotar at polanet.pl (Tomasz Pala)
Date: Sun, 9 Feb 2020 13:30:59 +0100
Subject: migrating pld /var/run to /run (and related dirs)
In-Reply-To: <20200209091337.GD2224@starbug>
References: <4ff8038b-8848-17d9-8ca0-ae1c598a3538@maven.pl>
 <20200209091337.GD2224@starbug>
Message-ID: <20200209123059.GA14967@polanet.pl>

On Sun, Feb 09, 2020 at 10:13:37 +0100, Jan R?korajski wrote:

> What about plugging all this symlinking into geninitrd / dracut?
> This way we would have everything sorted before we even start booting to
> the filesystem in question.

Won't work on systems without initrd, won't be functional without
regenerating images on systems using it.

But it should be possible to make this as systemd unit itself.

-- 
Tomasz Pala <gotar at pld-linux.org>