I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only
allows me to change the number or rows, not columns it seems.
Any clies as to how I can get what I want-- if necessary, having them
arranged horizontally rather than would be more useful than what I have
now. ( and no, I do not like my taskbar along the right or left edges.)


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 5/5/21 11:16 AM, William Unruh wrote:

I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only allows me to change the number or rows, not columns it seems.
Any clies as to how I can get what I want-- if necessary, having them arranged horizontally rather than would be more useful than what I have
now. ( and no, I do not like my taskbar along the right or left edges.)

Well I use a different fork but what I do is create another panel vertically and stash the pager there along with some other tools
and games. My setup is main panel on top and I have the panel to the
left side. Think of an L rotated 90 degrees clockwise. but I leave a
gap between the horizonal and the vertical panel. Vertical is 60
pixels and Horizontal 58 pixels in width.

bliss-“Nearly any fool can use a GNU/Linux computer. Many do.” After
all here I am...

--
bliss dash SF 4 ever at dslextreme dot com

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: dis-organization (2:250/1@fidonet)

On Wed, 05 May 2021 14:16:26 -0400, William Unruh <unruh@invalid.ca> wrote:

I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only allows me to change the number or rows, not columns it seems.
Any clies as to how I can get what I want-- if necessary, having them arranged horizontally rather than would be more useful than what I have
now. ( and no, I do not like my taskbar along the right or left edges.)

Specify 2 rows. Click on Desktop 1 then the Add button to get a second column in the first row.

Click on the first desktop in row 2, then add to get a second column in the second row.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Once again you come through. This is not something I would ever have
thought of.
Weird
On 2021-05-05, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:

On Wed, 05 May 2021 14:16:26 -0400, William Unruh <unruh@invalid.ca> wrote:

I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only
allows me to change the number or rows, not columns it seems.
Any clies as to how I can get what I want-- if necessary, having them
arranged horizontally rather than would be more useful than what I have
now. ( and no, I do not like my taskbar along the right or left edges.)

Specify 2 rows. Click on Desktop 1 then the Add button to get a second column in the first row.

Click on the first desktop in row 2, then add to get a second column in the second row.

Regards, Dave Hodgins

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 6/5/21 4:16 am, William Unruh wrote:

I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only

I have 4 desktops on Mageia 8 and the arrangement on the taskbar is the
same as for Mageia 7 a square 2x2. So it can be done!

You could isolate it to your setup by comparing with another user
eg: BitTwister's "junk" user

Or just rename each of your appropriate hidden folders until you crack it.

A good way to use up spare time :-)

--
faeychild
Running plasmashell 5.20.4 on 5.10.30-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

Given Hodgins' comments it was finally done.

You have to tell it how many rows you want, and then populate each row
with the number of desktops (giveng them names other than "new Desktop"
The Add button adds them, and will fill them a row at a time. Thus you
tell it you want 2 rows, The first desktop will already by put into row
1. You click on Add, and the second one goes into row 2. then you click
on add again and teh third one goes into row 2 displacing the seond into
row 1, and then again and you get a second on in row 2.

On 2021-05-05, faeychild <faeychild@nomail.afraid.org> wrote:

On 6/5/21 4:16 am, William Unruh wrote:

I like to have 4 virtual desktops. On Mageia 7 they are arranged in a
square (2x2) on the taskbar. In Mageia 8 it seems that the only
arrangment is 4 vertical. Without making the taskbar take up half the
screen, that makes them almost impossible to see. The configuration only

I have 4 desktops on Mageia 8 and the arrangement on the taskbar is the
same as for Mageia 7 a square 2x2. So it can be done!

You could isolate it to your setup by comparing with another user
eg: BitTwister's "junk" user

Or just rename each of your appropriate hidden folders until you crack it.

A good way to use up spare time :-)

As usual I did a fresh install on Mga8 (i had put a new ssd into my
laptop) and then had to fix up everything that broke in the new one.
That has taken up about 3 days of my time. Yeah lots of spare time I
have-- only about 5 papers I have to write:-)


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 6/5/21 10:52 am, William Unruh wrote:

A good way to use up spare time :-)

As usual I did a fresh install on Mga8 (i had put a new ssd into my
laptop) and then had to fix up everything that broke in the new one.
That has taken up about 3 days of my time. Yeah lots of spare time I
have-- only about 5 papers I have to write:-)

YEP

This morning I was switching to different releases on various partitions
only to find on my return that Mageia 8 locked up on the login screen.

I tried various approaches including reinstalling over the the original,
which can be a time saver

Not this time though. I am reinstalling. From scratch - almost.
Fortunately I do have a backup of $HOME so most of the config stuff is
intact.

If not for that I would probably have to kill someone
I am not looking forward to the Printer install

C'est la "bloody" vie

And Yes I know that it's my fault. Last night I was thinking about
running Bit Twister's backup rsync file while I was ahead.


How wonderful it is to be prophetic

Regards

PS Ah yes the signature file must also be reinstalled.

Did you know that the mouse single click option is no longer part of the
mouse settings That is going to infuriate me until I locate it.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Thu, 06 May 2021 20:57:17 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

Did you know that the mouse single click option is no longer part of the mouse settings That is going to infuriate me until I locate it.

For plasma, systemsettings5, Workspace, Workspace Behaviour, General Behaviour

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 7/5/21 11:58 am, David W. Hodgins wrote:

On Thu, 06 May 2021 20:57:17 -0400, faeychild
<faeychild@nomail.afraid.org> wrote:

Did you know that the mouse single click option is no longer part of the
mouse settings That is going to infuriate me until I locate it.

For plasma, systemsettings5, Workspace, Workspace Behaviour, General Behaviour

Thanks Dave. One click has returned


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 7 May 2021 10:57:17 +1000, faeychild wrote:

This morning I was switching to different releases on various partitions
only to find on my return that Mageia 8 locked up on the login screen.

What do you mean "locked up on the login screen"

If you mean entered password and it returned to login screen.
then you have a problem in one or more files used in the login
process. Usual problem is some user file is owned by root because
user used "su" instead of "su -root" or "su -"

If you have a test account, say junk, and you can log into the
junk account then it is a user problem, not a system problem
requiring a reinstall.

All the above assumes no "/" partitions are shared between installs.
/home does not count as a "/" partition.

Checking my faeychild documentation I noticed I do not have what
Desktop Environment you are using. I would appreciate if you gave the
output from the following:

env | sort | grep XDG_

lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 7/5/21 3:38 pm, Bit Twister wrote:

On Fri, 7 May 2021 10:57:17 +1000, faeychild wrote:

This morning I was switching to different releases on various partitions
only to find on my return that Mageia 8 locked up on the login screen.

What do you mean "locked up on the login screen"

When the password was entered the login screen became unresponsive
the shutdown restart sleep icons failed to highlight
I had to power cycle to shutdown

If you mean entered password and it returned to login screen.
then you have a problem in one or more files used in the login
process. Usual problem is some user file is owned by root because
user used "su" instead of "su -root" or "su -"

I tend to be particular about using su with the dash for that very reason

If you have a test account, say junk, and you can log into the
junk account then it is a user problem, not a system problem
requiring a reinstall.

I didn't think to try junk but it may have not been a selectable option either.

All the above assumes no "/" partitions are shared between installs.
/home does not count as a "/" partition.

No! MGA 6 and MGA 7 are on separate partitions with their own
integrated "home" folder

Checking my faeychild documentation I noticed I do not have what
Desktop Environment you are using. I would appreciate if you gave the
output from the following:

I was in the throes of installing and hadn't setup the signature file yet

I am impressed that you have faeychild docs
I have Bit Twister docs :-)

I am not sure the info you ask for will help much. This is a fresh
install - and so far... it's OK

The major stuff was up and running fairly quickly. It;s just the
fiddly bits. Little extra tools and stuff

I still have to install the printer. This time the Mageia installation
did NOT include the dpkg package So it won't have to be disabled for the printer driver script

It should have been included but as I find, every install is a little different.

env | sort | grep XDG_

[root@unimatrix ~]# env | sort | grep XDG_
[root@unimatrix ~]#

[nothing]

Ah-Ha NOT to be run as root.

[faeychild@unimatrix ~]$ env | sort | grep XDG XDG_CONFIG_DIRS=/etc/xdg:/etc/xdg/kf5:/var/lib/plasma5-profiles/common/xdg XDG_CURRENT_DESKTOP=KDE XDG_DATA_DIRS=/var/lib/plasma5-profiles/common/share:/usr/local/share:/usr/share
XDG_MENU_PREFIX=plasma-
XDG_RUNTIME_DIR=/run/user/1000 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=KDE
XDG_SESSION_ID=c2
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
XDG_SESSION_TYPE=x11
XDG_VTNR=1

lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL

[root@unimatrix ~]# lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL sda 5.5T
└─sda1 5.5T ext4 video /video video sdb 29.7G
└─sdb1 29.7G vfat /run/media/faeychild/0000-7E68
sr0 1024M
nvme0n1 119.2G
├─nvme0n1p1 299M vfat /boot/EFI efi ├─nvme0n1p2 22.3G ext4 mageia mageia ├─nvme0n1p3 10.6G swap swap [SWAP] swap ├─nvme0n1p4 12.2G ext4 tmp tmp ├─nvme0n1p5 20.4G ext4 mageia_bu mageia_bu
├─nvme0n1p6 2G ext4 boot_iso boot_iso ├─nvme0n1p7 24.9G ext4 mageia_6 mageia_6 └─nvme0n1p8 26.5G ext4 mga8 / test



I am going for a youtube or reddit break and coffee



regards

--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 07.05.2021 at 17:02, faeychild scribbled:

On 7/5/21 3:38 pm, Bit Twister wrote:

On Fri, 7 May 2021 10:57:17 +1000, faeychild wrote:

This morning I was switching to different releases on various
partitions only to find on my return that Mageia 8 locked up on
the login screen.

What do you mean "locked up on the login screen"

When the password was entered the login screen became unresponsive
the shutdown restart sleep icons failed to highlight
I had to power cycle to shutdown

I am thoroughly surprised that after, what, 15 years, you still don't
know the trick with the Magic SysRq keys. :)

--
With respect,
= Aragorn =


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On Fri, 7 May 2021 17:02:06 +1000, faeychild wrote:

On 7/5/21 3:38 pm, Bit Twister wrote:

On Fri, 7 May 2021 10:57:17 +1000, faeychild wrote:

This morning I was switching to different releases on various partitions >>> only to find on my return that Mageia 8 locked up on the login screen.

What do you mean "locked up on the login screen"

When the password was entered the login screen became unresponsive
the shutdown restart sleep icons failed to highlight
I had to power cycle to shutdown

Ok, Display manager was ok until password which gets you logged
in and then runs ~/bash_profile, .bashrc, and your plasma (DE)
stuff. Since there are no plasma files, it does take X times longer
than normal for the DE to appear

I didn't think to try junk but it may have not been a selectable option either.

The fact that you could enter a password, indicates you should have
been able to pick any user then enter their passwood,

All the above assumes no "/" partitions are shared between installs.
/home does not count as a "/" partition.

No! MGA 6 and MGA 7 are on separate partitions with their own
integrated "home" folder

Quick check of my faeychild text file says you are sharing /tmp
across installs.

Your 12.2G /tmp is a waste since mine shows

[root@wb ~]# cd /tmp
[root@wb tmp]# du --summarize -h .
36K .

blocks used.

In my stupid opinion, /tmp should not be shared.

My suggestion would be modify all installs /etc/fstab to change
/tmp to say, /local, change partition label, create /local mount point
and mount it. Then you could put scripts and whatnot in /local which
could be shared across installs.

For example
$ ls /local/
bin cron icons log opt ppp tmp
config doc lock lost+found phone sounds


I do hope you have a rescue cd just in case of problems with the above.

I am impressed that you have faeychild docs

I have text file for common posters who have questions/problems
about their setup, faeychild, pinnerite, santo.


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 7/5/21 5:24 pm, Aragorn wrote:

I am thoroughly surprised that after, what, 15 years, you still don't
know the trick with the Magic SysRq keys. :)

I can never remember it!!!!



--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 7/5/21 6:25 pm, Bit Twister wrote:

Quick check of my faeychild text file says you are sharing /tmp
across installs.

Yep

Your 12.2G /tmp is a waste since mine shows

[root@wb ~]# cd /tmp
[root@wb tmp]# du --summarize -h .
36K .

blocks used.

Once upon a time I ha a program run out of tmp space

In my stupid opinion, /tmp should not be shared.

I believe you have a point. How about a script to clear all tmp files on shutdown. I have one somewhere currently not running

My suggestion would be modify all installs /etc/fstab to change
/tmp to say, /local, change partition label, create /local mount point
and mount it. Then you could put scripts and whatnot in /local which
could be shared across installs.

For example
$ ls /local/
bin cron icons log opt ppp tmp
config doc lock lost+found phone sounds

I do hope you have a rescue cd just in case of problems with the above.

I'll read this later in the day when I have brain function

Of Dear!! My numberlock is not activating despite being set. Same for
junk. It goes on and on...


--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 08.05.2021 at 07:26, faeychild scribbled:

On 7/5/21 5:24 pm, Aragorn wrote:

I am thoroughly surprised that after, what, 15 years, you still
don't know the trick with the Magic SysRq keys. :)

I can never remember it!!!!

Hold Alt and PrtScr/SysRq together and then type the first character of
every word in the following sentence, interspersed by about two seconds
between each key press...:

"Raising Skinny Elephants Is Still Utterly Boring"

:p

--
With respect,
= Aragorn =


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On 08.05.2021 at 07:37, faeychild scribbled:

On 7/5/21 6:25 pm, Bit Twister wrote:
=20

Your 12.2G /tmp is a waste since mine shows
=20
[root@wb ~]# cd /tmp
[root@wb tmp]# du --summarize -h .
36K .
=20
blocks used. =20

=20
Once upon a time I ha a program run out of tmp space
=20

In my stupid opinion, /tmp should not be shared. =20

=20
I believe you have a point. How about a script to clear all tmp files
on shutdown. I have one somewhere currently not running

1. Install tmpwatch. It'll clean out all unused entries in /tmp and
/var/tmp.

2. In a distribution that uses systemd, /tmp will normally be a tmpfs,
and thus it'll automatically be emptied across reboots.

Of Dear!! My numberlock is not activating despite being set. Same
for junk. It goes on and on...

1. In /etc/sddm.conf... =E2=86=93

[General]
InputMethod=3D
Numlock=3Don

2. In Plasma's System Settings... =E2=86=93

Hardware =E2=86=92 Input Devices =E2=86=92 Keyboard =E2=86=92 NumL= ock on Plasma Startup


3. Optionally, still in System Settings:Keyboard, click the
"Advanced" tab and click the "+" next to "Compatibility Options".
Tick the box next to "Numeric keypad always enters digits (like in
macOS".


--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On Fri, 07 May 2021 17:26:04 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

On 7/5/21 5:24 pm, Aragorn wrote:

I am thoroughly surprised that after, what, 15 years, you still don't
know the trick with the Magic SysRq keys. :)

I can never remember it!!!!

Hold down alt+ctrl+sysrq and then press the first letter of each word ... Raising
Skinny
Elephants
Is
Still
Utterly
Boring

Replace Boring with Old for power off instead of boot. https://en.wikipedia.org/wiki/Magic_SysRq_key includes keys for some keyboards that don't have a print screen/sysrq key.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/5/21 7:50 am, Aragorn wrote:

Of Dear!! My numberlock is not activating despite being set. Same
for junk. It goes on and on...

1. In /etc/sddm.conf... ↓

[General]
InputMethod=
Numlock=on

The only one that worked.

I notice that sdd.conf.rpmnew is a lot more extensive.

Is that intended to replace sdd.conf?

regards


--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Sat, 8 May 2021 11:31:38 +1000, faeychild wrote:

On 8/5/21 7:50 am, Aragorn wrote:

Of Dear!! My numberlock is not activating despite being set. Same
for junk. It goes on and on...

1. In /etc/sddm.conf... ↓

[General]
InputMethod=
Numlock=on

The only one that worked.

I notice that sdd.conf.rpmnew is a lot more extensive.

Is that intended to replace sdd.conf?

You get a whatever.rpmnew when the package releases an update
containing a whatever file that does not match the current file,
usually because you modified the whatever file.

If you do upgrades instead of clean installs, you would see larger
number of .rpmnew files.

I always use the .rpmnew file and reapply my changes.


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 08.05.2021 at 11:31, faeychild scribbled:

On 8/5/21 7:50 am, Aragorn wrote:
=20

Of Dear!! My numberlock is not activating despite being set. Same
for junk. It goes on and on... =20

=20
1. In /etc/sddm.conf... =E2=86=93
=20
[General]
InputMethod=3D
Numlock=3Don =20

=20
=20
The only one that worked.
=20
I notice that sdd.conf.rpmnew is a lot more extensive.
=20
Is that intended to replace sdd.conf?

It's "sddm.conf(.rpmnew)" =E2=80=94 spelling matters to a computer! ;)

The .rpmnew file contains some changes =E2=80=94 often they are only inline comments =E2=80=94 and it is up to you to merge this file with the regular configuration file. The package installs the new configuration file as sddm.conf.rpmnew if you have made any modifications to the original
sddm.conf file.

Compare the two files side by side, and merge the changes from the
..rpmnew file into the regular sddm.conf without removing your own modifications. Afterwards you can delete the .rpmnew file.

We have a similar thing in Manjaro. Only there, they are .pacnew
files, because Manjaro is based upon Arch and therefore it uses the Arch
Linux Package Manager, pacman, with .pkg.tar.zstd packages.

--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On 7/5/21 6:25 pm, Bit Twister wrote:

In my stupid opinion, /tmp should not be shared.

My suggestion would be modify all installs /etc/fstab to change
/tmp to say, /local, change partition label, create /local mount point
and mount it. Then you could put scripts and whatnot in /local which
could be shared across installs.

For example
$ ls /local/
bin cron icons log opt ppp tmp
config doc lock lost+found phone sounds

I would like to clean up all the installs and just keep mageia 6. That's
the only release that dvdstyler will work on.

I assume from the above that you mean to reduce /tmp and create a
"local" partition.

I do hope you have a rescue cd just in case of problems with the above.

The sysrescuecd is installed.

I still have trouble getting my head around, name, label, partlabel, and Google searches don't make it any clearer.

The setup is currently working fine. It just need fine tuning. And I
would like to run your fstab script sometime to re-label fstab


And the PRINTER.

--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 07 May 2021 21:31:38 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

I notice that sdd.conf.rpmnew is a lot more extensive.
Is that intended to replace sdd.conf?

With all configuration files they will not be automatically replaced. I normally use
"kdiff3 /etc/sddm.conf.rpmnew /etc/sddm.conf &" (as root) to view the changes between
the new and old config files and select which ones I want, which may be new options,
or changes I (or config programs like mcc) have made based on my choices.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Fri, 07 May 2021 22:40:50 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

I would like to clean up all the installs and just keep mageia 6. That's
the only release that dvdstyler will work on.

I don't have any working dvd drives to test it with. What's not working with it in
Mageia 8?

I assume from the above that you mean to reduce /tmp and create a
"local" partition.

The intention is to reuse the space currently mounted as /tmp with that space being mounted using some other (not currently existing) mountpoint for things you
intend to share across multiple installs. Let /tmp be mounted as a tmpfs filesystem,
kept in ram. It's limited to growing in size to a max of half the amount of ram by default.

I still have trouble getting my head around, name, label, partlabel, and Google searches don't make it any clearer.

The name in lsblk is the partition device name, such as /dev/sda4.

The label is is inside the partition's header and is specified during partition formatting, such as "mfks.ext4 /dev/sda4 -L mychoice" or changed later using
a command such as e2label. The label can be used in /etc/fstab entries for selecting
the file system to mount. Like a uuid, if it's used for selecting partitions during
boot, it must be unique. Each partition formatting command such as mkswap has an option to specify the label. Most filesystem types have a way to change the label, though the partition must be unmounted.

The above are the same whether using mbr or gpt partition tables.

The partlabel (also called partition name) is only availble with gpt. It's not used
for anything in linux so can be whatever you want. In a windows install, typical
names are EFI system partition, Microsoft reserved partition, and Basic data partition.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 08.05.2021 at 12:40, faeychild scribbled:

I still have trouble getting my head around, name, label, partlabel,
and Google searches don't make it any clearer.

=C2=B0 The NAME field refers to the device special file, e.g. /dev/sda1.


=C2=B0 A LABEL is a text string set in the filesystem itself as a (pseudo=
-)
unique identifier, which can be used for mounting the filesystem,
e.g. by way of /etc/fstab. An example of an /etc/fstab entry with
a label follows below. =E2=86=93

LABEL=3Dmyhomefs /home ext4 defaults 0 0

The LABEL is chosen by the sysadmin, and that is why it's only
pseudo-unique; if the sysadmin screws up, then he or she could be
having two partitions with the same LABEL, which will confuse the
system. Yet, mnemonically, using a LABEL instead of a UUID is
easier on the fingers and on the old memory cortex.


=C2=B0 Unlike a LABEL and a UUID, the PARTLABEL and PARTUUID are not set
in the filesystem itself =E2=80=94 and thus, they will not change when = the
partition is reformatted =E2=80=94 but instead, they are stored in the = GPT
partition table. MS-DOS MBR-style partition tables do not have
PARTLABELs or PARTUUIDs, although the kernel will fake them when
the filesystem is mounted, similar to how a vfat or NTFS filesystem
do not support POSIX file ownership and permissions but are given a
fake permissions mask and ownership when they are mounted. In
other words, you can refer to partitions by their PARTLABEL or
PARTUUID in the same way as you would do so by way of their=20
regular LABEL or UUID, but only on GPT drives.

Thus, to summarize, the LABEL and UUID are stored in the filesystem
itself and will (respectively) be erased and/or altered when the
partition is reformatted. The PARTLABEL and PARTUUID are stored in
the partition table on a GPT drive and do not change when the
partition is reformatted. You can even set a PARTLABEL on an
unformatted partition, such as the "bios_grub" partition on a GPT
drive that's being used on a system that boots in legacy BIOS
compatibility mode.


--=20
With respect,
=3D Aragorn =3D


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Strider (2:250/1@fidonet)

On Sat, 8 May 2021 12:40:50 +1000, faeychild wrote:

On 7/5/21 6:25 pm, Bit Twister wrote:

In my stupid opinion, /tmp should not be shared.

My suggestion would be modify all installs /etc/fstab to change
/tmp to say, /local, change partition label, create /local mount point
and mount it. Then you could put scripts and whatnot in /local which
could be shared across installs.

For example
$ ls /local/
bin cron icons log opt ppp tmp
config doc lock lost+found phone sounds

I would like to clean up all the installs and just keep mageia 6. That's
the only release that dvdstyler will work on.

I assume from the above that you mean to reduce /tmp and create a
"local" partition.

Not trying to reduce /tmp per say. Just pointing out /tmp usage size
is pretty small under normal operation.

As for /local, just a suggestion about a partition that has common stuff
you would want to share across installs. I want to have a consistent
look and feel regardless of DE so I use the icons from /local/icons, /local/sounds have wav files used by by my scripts ti get my attention.

/local/cron has my cron jobs so I do not have to do much change
in the /etc/cron.* directories.

I still have trouble getting my head around, name, label, partlabel, and Google searches don't make it any clearer.

It is pretty straight forward. There is no relationship between
label and partlabel. GPT partition allows you to have a partlabel.

label is available in GPT and MSDOS partition and can be/is used as
the mount point if not defined in /etc/fstab depending on OS.

Formatting of a partition with a label will wipe out the label/UUID but
does not change the partlabel/PUUID.

The name can change based on when the partition becomes available
during the boot process. Because of that and label/partlabel might
not be unique so UUID was chosen as the best way of picking the
desired partition to attach to a given mount point.

mount allows you to use name, label, partlabel.*UUID, ... at the
command line, or in /etc/fstab.

For the "normal" system admin everything just works.

For the more advanced sysadmin doing multi OS boot/installs
that are re-cycling partitions the UUID becomes a problem every time
a partition is formatted and is pretty human unfriendly as to
what the partition us used for.

Sysadmins using labels have to be very careful to never have the
same label on different partitions. Otherwise the last partition
found could me mounted on top of the first partition found. :(

I found that out the hard way the first time I brought up my backup
usb drive. Current / was switched to usb / when it came up. :-(


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/5/21 11:46 am, Bit Twister wrote:

If you do upgrades instead of clean installs, you would see larger
number of .rpmnew files.

I always use the .rpmnew file and reapply my changes.

Understood
--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/5/21 12:15 pm, Aragorn wrote:

It's "sddm.conf(.rpmnew)" — spelling matters to a computer! ;)

Yep! My typo Bad day



--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 8/5/21 1:42 pm, Aragorn wrote:

On 08.05.2021 at 12:40, faeychild scribbled:

I still have trouble getting my head around, name, label, partlabel,
and Google searches don't make it any clearer.

° The NAME field refers to the device special file, e.g. /dev/sda1.

° A LABEL is a text string set in the filesystem itself as a (pseudo-)
unique identifier, which can be used for mounting the filesystem,
e.g. by way of /etc/fstab. An example of an /etc/fstab entry with
a label follows below. ↓

LABEL=myhomefs /home ext4 defaults 0 0

snipped for latter reading


--
faeychild
Running plasmashell 5.20.4 on 5.10.33-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)