On 1/3/21 8:05 PM, Mark LaPierre wrote:
So how would one use this shiny bit of information? Is there a way to
discover if an EPEL application is going to clobber your system before
you install it?
As long as the upstream developers observe semantic versioning, dnf
would tell whether or
On 1/3/21 5:34 PM, Stephen John Smoogen wrote:
Except in cases where packages in a RHEL point release are being rebased.
This is something which is happening with a lot more gusto than in any
previous releases so there may be points where say a QT or a
gnomelib provides in Stream is ahead of
On 1/3/21 8:34 PM, Stephen John Smoogen wrote:
On Sun, 3 Jan 2021 at 18:20, Gordon Messmer
wrote:
On 1/3/21 2:51 PM, Kay Schenk wrote:
is it still OK to set up EPEL as a repo?
Yes. CentOS Stream is expected to be backward-compatible with RHEL, for
the same reason that each RHEL point
On Sun, 3 Jan 2021 at 18:20, Gordon Messmer
wrote:
> On 1/3/21 2:51 PM, Kay Schenk wrote:
> > is it still OK to set up EPEL as a repo?
>
>
> Yes. CentOS Stream is expected to be backward-compatible with RHEL, for
> the same reason that each RHEL point release is backward-compatible with
>
OK, I think I've got it set up as described here, while fixing the
misplaced fields in /etc/fstab:
UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup ext4
x-systemd.automount,x-systemd.idle-timeout=15min,noauto 0 2
now when I do, e.g., "ls /mnt/backup"
I get:
$ sudo !!
sudo
On 1/3/21 2:51 PM, Kay Schenk wrote:
is it still OK to set up EPEL as a repo?
Yes. CentOS Stream is expected to be backward-compatible with RHEL, for
the same reason that each RHEL point release is backward-compatible with
previous point releases.
Hello all--
All good in the Stream for me. :)
Because Stream will tend to be more "forward moving" than previous
CentOS releases, is it still OK to set up EPEL as a repo? So far, I've
only installed terminus fonts from CentOS 8 EPEL, but I'm just wondering
about this. Generally, are there
>
> I commented out those entries in /etc/auto.master before modifying the
> fstab entry:
>
> UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup
> ext4,x-systemd.automount,x-systemd.idle-timeout=15min noauto 0 2
That's not correct. See 'man fstab'. It should be
device
The first question I would have is this: Has the auto-reboot occurred
since the machine was last built or did this begin at some point after
the build?
Apologies if I missed this in the many threads stemming from your OP…
- - -
On 2 Jan 2021, at 6:44, Fred wrote:
Hi all, I'm hoping
Reboot is not necessary as long as local-fs.target is restarted, but a fix for
the /etc/fstab might be needed.
Best Regards,
Strahil Nikolov
В неделя, 3 януари 2021 г., 21:18:30 Гринуич+2, Simon Matter
написа:
> $ cat /etc/centos-release
> CentOS Linux release 7.9.2009 (Core)
>
>
Erm ... the noauto should be part of the options column, so append it to the
previous option (and of course delimit with a ",").
I see that the '.automount' was not generated ... Maybe it's related to the
noauto issue.
By the way , "mount -a" should complain if fstab is not OK.
Best Regards,
> $ cat /etc/centos-release
> CentOS Linux release 7.9.2009 (Core)
>
> $ sudo systemctl status mnt-backup.mount mnt-backup.automount
> [sudo] password for fredex:
> ● mnt-backup.mount - /mnt/backup
>Loaded: loaded (/etc/fstab; bad; vendor preset: disabled)
>Active: active (mounted) since
$ cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)
$ sudo systemctl status mnt-backup.mount mnt-backup.automount
[sudo] password for fredex:
● mnt-backup.mount - /mnt/backup
Loaded: loaded (/etc/fstab; bad; vendor preset: disabled)
Active: active (mounted) since Sat 2021-01-02
Are you still on 7.6 ? I recently discovered that a bug in sysstat was fixed in
7.7 that prevented autofs from umounting the filesystem.
The following should show if it's taking into action:
systemctl status mnt-backup.mount mnt-backup.automount
systemctl cat mnt-backup.mount
Strahil:
I WAS using that, but the automatic umount never worked, leaving it mounted
all the time.
I commented out those entries in /etc/auto.master before modifying the
fstab entry:
UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup
Hi Fred,
do you use automatic umount for the map in /etc/auto.master (--timeout) ?
If yes, then the systemd mount options probably won't help.
Best Regards,
Strahil Nikolov
В неделя, 3 януари 2021 г., 04:27:17 Гринуич+2, Fred
написа:
Yeah, and the instructions for setting
16 matches
Mail list logo
