Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Michael D. Setzer II via users]

On 1 Dec 2020 at 11:16, Samuel Sieb wrote:

Subject:Re: Differences between versions of wine on FC31 and 
FC32? 5.19/5.22
To: users@lists.fedoraproject.org
From:   Samuel Sieb 
Date sent:  Tue, 1 Dec 2020 11:16:53 -0800
Send reply to:  Community support for Fedora users 


> On 12/1/20 3:35 AM, Michael D. Setzer II via users wrote:
> > Didn't realize is was EOL already?? Missed that FC33 was already fully
> > out.  Will have to do an upgrade. Don't care for the latest changes they
> > have forced on vncserver, but guess I'll have to figure it out. That is
> > probable why I had overlooked it going to EOL. Have 4 systems I access
> > via vnc and like the simple vncserver setup versus the new systemd
> > setup..
> 
> It's a change, but it's not too bad.  I got mine working and I'm happier 
> to have it automatically start now.

They had a previous systemd system where you had to make special 
links, but I found that about have the time it would just fail? And process 
was totally random. I generally have it start in the rc.local, and that has 
never failed on me? Will have to give it a shot at some point. Usually, 
had the local user on system use one of the gnome desktops, while the 
vnc was running with the xfce.. Didn't ever notice any problems.

Thanks for the reply. New system does seem simplier than the old 
systemd process they mentioned.


> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Michael D. Setzer II via users]

On 1 Dec 2020 at 21:39, Samuel Sieb wrote:

Subject:Re: Differences between versions of wine on FC31 and 
FC32? 5.19/5.22
To: users@lists.fedoraproject.org
From:   Samuel Sieb 
Date sent:  Tue, 1 Dec 2020 21:39:38 -0800
Send reply to:  Community support for Fedora users 


> On 12/1/20 6:57 PM, Michael D. Setzer II via users wrote:
> > Just updated notebook to FC32 - took almost 14 hours.
> > 25 minutes to download the 5.4G of the 5008 packages.
> > After reboot to upgrade
> > took little over 8 hours for upgrade part
> > then 4.5 hours for the clean part
> > and about another .5 hours for the verify and man-db stuff.
> > Then the reboot and it had to do some things.
> > 
> > So, now have the latest stuff.
> > Still not clear why an upgrade like this takes so long...
> 
> Notebook hard drives are really slow now, but I've never seen one take 
> that long.  This is why I put SSDs in everything.
Copied lines from boot.log and processed it in spreadsheet.
1-Prep Time??   1713.583866 00:28:33.58387
2-Update Total  27533.06156207:38:53.06156
3-Clean Time16712.71967904:38:32.71968
4-Verify Time   1087.992662 00:18:07.99266
5-Final time7.223050005100:00:07.22305
6-Complete Time 47054.58081913:04:14.58082

hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   10030 MB in  1.99 seconds = 5031.74 MB/sec
 Timing buffered disk reads: 412 MB in  3.01 seconds = 136.93 MB/sec

Disk is 
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM035-1RK1

So don't know if that is anything?



> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Samuel Sieb]

On 12/1/20 6:57 PM, Michael D. Setzer II via users wrote:

Just updated notebook to FC32 - took almost 14 hours.
25 minutes to download the 5.4G of the 5008 packages.
After reboot to upgrade
took little over 8 hours for upgrade part
then 4.5 hours for the clean part
and about another .5 hours for the verify and man-db stuff.
Then the reboot and it had to do some things.

So, now have the latest stuff.
Still not clear why an upgrade like this takes so long...


Notebook hard drives are really slow now, but I've never seen one take 
that long.  This is why I put SSDs in everything.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Ed Greshko]

On 02/12/2020 10:57, Michael D. Setzer II wrote:

Just updated notebook to FC32 - took almost 14 hours.
25 minutes to download the 5.4G of the 5008 packages.
After reboot to upgrade
took little over 8 hours for upgrade part
then 4.5 hours for the clean part
and about another .5 hours for the verify and man-db stuff.
Then the reboot and it had to do some things.

So, now have the latest stuff.
Still not clear why an upgrade like this takes so long...


I don't know.  My updates have gone much quicker in comparison.

An old notebook with a single SSD took about 45 minutes to upgrade 2722 
packages and an additional
maybe 20 minutes or so to download them.

Another system with SSD took 31 minutes to upgrade 3096 packages with also 
about 20+ minutes to
download.

In both cases I didn't record the download times and they may have been done 
when other processes
were taking up download bandwidth.

---
The key to getting good answers is to ask good questions.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

[389-users] Re: unattended request cert process

[William Brown]

depending on your version of 389, look at "dsctl  tls import-ca"

{william@ldapkdc 9:12} ~/development $ dsctl localhost tls import-ca --help
usage: dsctl [instance] tls import-ca [-h] cert_path nickname

positional arguments:
  cert_path   The path to the x509 cert to import as a server CA
  nicknameThe name of the certificate once imported

optional arguments:
  -h, --help  show this help message and exit

This allows you to import a PEM  CA file. There are a number of other helpers 
under the tls subcommand to make cert management easier. 

> On 1 Dec 2020, at 18:55, Angel Bosch Mora  wrote:
> 
> hi,
> 
> some time ago I asked for a scriptable way of creating a certificate request, 
> here's the thread:
> 
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/thread/EHWWAHOO3S2HZEWJEXTQKDDRH33NLSMU/#HF7ZPVLMUK32AIEEWPEOLUJGZFXXRCEK
> 
> I didn't have the time to write anything and I would like to invest some time 
> now.
> 
> the goal is to create an unattended script for node creation INCLUDING 
> certification with an external CA.
> 
> 
> I'm thinking about having several precreated certificate databases and 
> download them to nodes.
> something like:
> 
>openssl rand -base64 16 > pwfile.txt && certutil -N -d . -f pwfile.txt
> 
> in several nodes and then scp/wget them to each node.
> also, do all CSR beforehand and already signed with our CA so I will have a 
> repo of cert databases like:
> 
> 
>nss/ca_root.crt
>nss/ldap10
>nss/ldap10/cert9.db
>nss/ldap10/key4.db
>nss/ldap10/ldap10.example.com.crt
>nss/ldap10/pkcs11.txt
>nss/ldap10/pwfile.txt
>nss/ldap11
>nss/ldap11/cert9.db
>nss/ldap11/key4.db
>nss/ldap11/ldap11.example.com.crt
>nss/ldap11/pkcs11.txt
>nss/ldap11/pwfile.txt
>nss/ldap12
>nss/ldap12/cert9.db
>nss/ldap12/key4.db
>nss/ldap12/ldap12.example.com.crt
>nss/ldap12/pkcs11.txt
>nss/ldap12/pwfile.txt
>nss/ldap13
>nss/ldap13/cert9.db
>nss/ldap13/key4.db
>nss/ldap13/ldap13.example.com.crt
>nss/ldap13/pkcs11.txt
>nss/ldap13/pwfile.txt
>nss/ldap14
>nss/ldap14/cert9.db
>nss/ldap14/key4.db
>nss/ldap14/ldap14.example.com.crt
>nss/ldap14/pkcs11.txt
>nss/ldap14/pwfile.txt
>nss/ldap15
>nss/ldap15/cert9.db
>nss/ldap15/key4.db
>nss/ldap15/ldap15.example.com.crt
>nss/ldap15/pkcs11.txt
>nss/ldap15/pwfile.txt
> 
> 
> this step is the only one remaining on my recipe of unattended container 
> creation, so any help will be really appreciated.
> 
> 
> 
> best regards,
> 
> abosch
> 
> 
> -- Institut Mallorqui d'Afers Socials. Aquest missatge, i si escau, qualsevol 
> fitxer annex, es dirigeix exclusivament a la persona que n'es destinataria i 
> pot contenir informacio confidencial. En cap cas no heu de copiar aquest 
> missatge ni lliurar-lo a terceres persones sense permis expres de l'IMAS. Si 
> no sou la persona destinataria que s'hi indica (o la responsable de 
> lliurar-l'hi) us demanam que ho notifiqueu immediatament a l'adreca 
> electronica de la persona remitent. Abans d'imprimir aquest missatge, pensau 
> si es realment necessari.
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Michael D. Setzer II via users]

On 1 Dec 2020 at 18:32, Ed Greshko wrote:

From:   Ed Greshko 
Subject:Re: Differences between versions of wine on FC31 and 
FC32? 5.19/5.22
To: users@lists.fedoraproject.org
Date sent:  Tue, 1 Dec 2020 18:32:15 +0800
Send reply to:  Community support for Fedora users 


> On 01/12/2020 18:30, Michael D. Setzer II via users wrote:
> > Have 5 linux machine at home with 3 on FC32 and 2 on FC31.
> > One of the FC31s is my notebook, and noticed that the wine on the FC32
> > has gone up to 5.22, while the FC31 are at 5.19? Checked the testing
> > repos to see if it might be there, but nothing.
> >
> > Usually, the latest version will get an update, and the other will show up
> > within a couple days?? Just ran updates on machines, so noticed the
> > differences. Never recall it being more than one different...
> 
> Well, F31 is EOL.  So, it will no longer get updates.

Just updated notebook to FC32 - took almost 14 hours.
25 minutes to download the 5.4G of the 5008 packages.
After reboot to upgrade
took little over 8 hours for upgrade part
then 4.5 hours for the clean part
and about another .5 hours for the verify and man-db stuff.
Then the reboot and it had to do some things.

So, now have the latest stuff. 
Still not clear why an upgrade like this takes so long...



> 
> ---
> The key to getting good answers is to ask good questions.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: [3dprinting] Re: Where's the best place to discuss Cura issues?

[Fulko Hew]

On Tue, Dec 1, 2020 at 6:08 PM Miro Hrončok  wrote:

> On 12/1/20 9:49 PM, Fulko Hew wrote:
> >
> >
> > On Tue, Dec 1, 2020 at 3:36 PM Miro Hrončok  > > wrote:
> >
> > On 12/1/20 8:34 PM, Fulko Hew wrote:
> >  > As the subject line asks, where's the best place to discuss
> issues?
> >  > The 3dprinting list ?
> >
> > Yes, 3dprint...@lists.fedoraproject.org
> > 
> >
> >  > In the meantime, I've been using the released version of Cura on
> F28
> >  > but I couldn't seem to get a slice that had 1 layer wide vertical
> walls.
> >  > So I thought I'd try the most recent version in F33 in a VM.
> >  > [I then had to upgrade a system to F33 rather than in a VM.]
> >  > After installing 'dnf install cura' and running it,
> >  > it hangs with a splash screen that says:
> >  > 'Welcome to Ultimaker Cura.
> >  > Please follow these steps to set up Ultimaker Cura.
> >  > This will only take a few moments.'
> >  >
> >  > And that's it.  It does nothing else, and there isn't anything I
> can
> > click on to
> >  > proceed.
> >  >
> >  > Any suggestions?
> >
> > No idea. What virtualization do you use? I've just tried Fedora 33
> Workstation
> > in GNOME Boxes (Running on Fedora 33 Xfce Spin) and it worked for me.
> >
> >
> > I ended up installing F33 on raw hardware (no VM)
> > and that's what I'm using now.
> >
> > There is a "Get started" button under the "...This will only take a
> few
> > moments." text. Maybe the VM screen is too small to make it visible,
> the window
> > is rather tall.
> >
> >
> > Not on my machine.
>
> Try this:
>
> https://github.com/Ultimaker/Cura/issues/6058#issuecomment-587093671


YES !
THANK YOU, thank you, thank you.
That makes the button appear, and I can continue.

[Sadly my install of the KDE spin seems to have biodegraded to the point
where it is completely unusable.  And all I did was install some software
and personalize some window, desktop and power management options.
After having to add my user to the cdrom group so I could burn CDs,
I logged out and back in.  Burning works, but now I can no longer log
in with KDE over X, and only KDE over Wayland works. I also noticed
via gkrellm that my CPU fan doesn't run and my CPU heats up.
Sadly i've got more testing/diagnosing to do to get a working F33.]
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 13:33 -0700, Chris Murphy wrote:
> On Tue, Dec 1, 2020 at 1:07 PM Samuel Sieb  wrote:
> > 
> > On 12/1/20 8:42 AM, Patrick O'Callaghan wrote:
> > > On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> > > > On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  
> > > > wrote:
> > > > > 
> > > > > On Tue, 1 Dec 2020 14:52:21 +0100
> > > > > Roberto Ragusa wrote:
> > > > > 
> > > > > > How do you power them down?
> > > > > 
> > > > > I don't know about the original poster, but my "noauto" disks
> > > > > timeout and power down all by themselves, then even when they aren't
> > > > > mounted at all, every time I reboot, the reboot hangs while it
> > > > > spins up the disks for some reason. I constantly wish I could make
> > > > > it stop doing that.
> > > > 
> > > > Enumeration. I'm not sure if it's udev scanning everything, or the
> > > > kernel or both. And also maybe libblkid, to know what everything is.
> > > > The only way it can know what it is, it needs to be spun up to read
> > > > the partition map and all the signatures on each partition.
> > > 
> > > Obviously it needs to spin up if it needs to know these things. My
> > > point is that it doesn't need to know them until I tell it.
> > 
> > But it can't know that it shouldn't until it knows what's there. :-)
> > The kernel scanning the USB bus will trigger the dock to check the
> > drives which will spin them up.  Even if the dock didn't, the kernel
> > would still check the drives, so they would still be started.
> 
> Yep. For sure the kernel is what's responsible for reading the
> partition table. And that alone would cause a spin up. e.g.
> 
> [6.426044]  sdb: sdb1 sdb2
> 
> Only later does udev come in with "aha! a partition! let's scan it!"
> and then I see things like:
> 
> [6.506645] BTRFS: device label fedoraroot devid 2 transid 398800
> /dev/sdb2 scanned by systemd-udevd (326)
> 
> And there is an interaction with libblkid in the kernel to determine
> that this partition contains a Btrfs signature, what the label is,
> what the fs UUID is. And it's udev along with that information from
> libblkid that creates the disk by label, disk by uuid, disk by
> partuuid, disk by whatever.

Just for the record, these drives are using ext4, not BTRFS, though
that may change.

> The parameter to use to get detailed udev reporting dumped into the
> journal is udev.log_priority=debug and then you can see what does
> what, and in what order.

Thanks.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 13:21 -0700, Chris Murphy wrote:
> On Tue, Dec 1, 2020 at 9:42 AM Patrick O'Callaghan
>  wrote:
> > 
> > On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> > > On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
> > > > 
> > > > On Tue, 1 Dec 2020 14:52:21 +0100
> > > > Roberto Ragusa wrote:
> > > > 
> > > > > How do you power them down?
> > > > 
> > > > I don't know about the original poster, but my "noauto" disks
> > > > timeout and power down all by themselves, then even when they aren't
> > > > mounted at all, every time I reboot, the reboot hangs while it
> > > > spins up the disks for some reason. I constantly wish I could make
> > > > it stop doing that.
> > > 
> > > Enumeration. I'm not sure if it's udev scanning everything, or the
> > > kernel or both. And also maybe libblkid, to know what everything is.
> > > The only way it can know what it is, it needs to be spun up to read
> > > the partition map and all the signatures on each partition.
> > 
> > Obviously it needs to spin up if it needs to know these things. My
> > point is that it doesn't need to know them until I tell it.
> 
> Yeah that's not how it works.
> 
> $ dmesg | grep sda
> [2.149354] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks:
> (2.00 TB/1.82 TiB)
> [2.149397] sd 0:0:0:0: [sda] 4096-byte physical blocks
> [2.149514] sd 0:0:0:0: [sda] Write Protect is off
> [2.149545] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [2.149722] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [2.235611]  sda: sda1
> [2.236610] sd 0:0:0:0: [sda] Attached SCSI disk
> $
> 
> The second to last line, where it discovers the sda1 partition, is
> needed in order to create all the symlinks for all the various parts
> of that drive. Not just the dev node, but also the /dev/disk/by-
> things.
> 
> If you don't want that to happen, you'd need a udev rule to inhibit
> that. And then when it goes looking for a particular fs UUID in fstab
> to mount, of course it doesn't exist, so the mount will fail. It
> doesn't know it needs to scan everything NOW. There's no correlation
> between fs UUID in fstab to a particular device until it's scanned,
> which happens by udev during early startup.

That wouldn't worry me so much in this case as it's only used by my
backup script which starts and stops the dock directly and can do
whatever is needed. If it was an automount drive of course it would be
different.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 13:15 -0700, Chris Murphy wrote:
> On Tue, Dec 1, 2020 at 9:39 AM Patrick O'Callaghan
>  wrote:
> > 
> > On Tue, 2020-12-01 at 14:52 +0100, Roberto Ragusa wrote:
> > > On 12/1/20 2:15 PM, Patrick O'Callaghan wrote:
> > > > I have a couple of SATA drives connected via a USB dock that I use only
> > > > for backups. Normally they are powered down and only come on at night
> > > > during the backup run. However they also power on any time I reboot the
> > > > system and have to be powered down again manually. I'd prefer not to
> > > > power them on at all until they're needed.
> > > > 
> > > > Is there some magic that would inhibit the boot process from powering
> > > > up these devices? Note that the /etc/fstab entry already has 'noauto'
> > > > but that just prevents them from being mounted.
> > > 
> > > How do you power them down?
> > 
> > Extract from my script ($SLOT is sd[de]):
> > 
> > smartctl --smart=off /dev/$SLOT1 -q errorsonly >> $LOG 2>&1
> > smartctl --smart=off /dev/$SLOT2 -q errorsonly >> $LOG 2>&1
> > echo 1 > /sys/block/$SLOT1/device/delete# 
> > Can't use udisksctl because it removes the
> > echo 1 > /sys/block/$SLOT2/device/delete# 
> > bus, which can't be powered on again
> > 
> 
> 
> I've got a Seagate laptop drive inside an Intel NUC that is only
> storage (not system boot or root). And I use a udev rule.
> 
> $ ls -l /etc/udev/
> hwdb.bin   hwdb.d/rules.d/   udev.conf
> $ ls -l /etc/udev/rules.d/
> total 12
> -rw-r--r--. 1 root root 139 Oct  7 17:47 60-block-scheduler.rules
> -rw-r--r--. 1 root root 179 Oct  7 17:36 69-hdparm.rules
> -rw-r--r--. 1 root root 628 Oct 29 06:40 70-persistent-ipoib.rules
> $ cat /etc/udev/rules.d/69-hdparm.rules
> ACTION=="add", SUBSYSTEM=="block", \
>   KERNEL=="sd*[!0-9]", \
>   ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
>   RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-0x5000c500a93cae8a"
> $

OK, I'll see if I can figure out what the hdparm options do.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 12:06 -0800, Samuel Sieb wrote:
> On 12/1/20 8:42 AM, Patrick O'Callaghan wrote:
> > On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> > > On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
> > > > 
> > > > On Tue, 1 Dec 2020 14:52:21 +0100
> > > > Roberto Ragusa wrote:
> > > > 
> > > > > How do you power them down?
> > > > 
> > > > I don't know about the original poster, but my "noauto" disks
> > > > timeout and power down all by themselves, then even when they aren't
> > > > mounted at all, every time I reboot, the reboot hangs while it
> > > > spins up the disks for some reason. I constantly wish I could make
> > > > it stop doing that.
> > > 
> > > Enumeration. I'm not sure if it's udev scanning everything, or the
> > > kernel or both. And also maybe libblkid, to know what everything is.
> > > The only way it can know what it is, it needs to be spun up to read
> > > the partition map and all the signatures on each partition.
> > 
> > Obviously it needs to spin up if it needs to know these things. My
> > point is that it doesn't need to know them until I tell it.
> 
> But it can't know that it shouldn't until it knows what's there. :-)
> The kernel scanning the USB bus will trigger the dock to check the 
> drives which will spin them up.  Even if the dock didn't, the kernel 
> would still check the drives, so they would still be started.

OK, I can see that it's the scan that's the root of the problem.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Bob Goodwin]

On 2020-12-01 17:14, Samuel Sieb wrote:


I haven't found one that doesn't work with Fedora.  There's a standard 
USB protocol for them.

__

Ok, I'll find one, thank you.

--
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Bob Goodwin]

On 2020-12-01 17:13, Jorge Fábregas wrote:

Bob: Haven't followed the whole thread but...did you try booting off a
CD/USB? a Fedora 33 Live CD? Ubuntu?  And see if it works there...?


No but I tried Fedora-32 live I had on a flash drive, same problem.

--
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Samuel Sieb]

On 12/1/20 2:05 PM, Bob Goodwin wrote:

On 2020-12-01 16:26, Samuel Sieb wrote:


You can get really cheap USB sound devices now.
__
Presumably they have a USB plug at one side and a mini phone jack on the 
other end, can you suggest one likely to work without Windows?


I haven't found one that doesn't work with Fedora.  There's a standard 
USB protocol for them.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Jorge Fábregas]

On 12/1/20 5:14 PM, Bob Goodwin wrote:
> It is also possible the audio circuit has failed on the motherboard. I 
> may also create a new Fedora-33 on the another drive in that computer, 
> there is still /dev/sdb I can install on.

Bob: Haven't followed the whole thread but...did you try booting off a
CD/USB? a Fedora 33 Live CD? Ubuntu?  And see if it works there...?

-- 
Jorge
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Bob Goodwin]

On 2020-12-01 16:26, Samuel Sieb wrote:


You can get really cheap USB sound devices now.
__
Presumably they have a USB plug at one side and a mini phone jack on the 
other end, can you suggest one likely to work without Windows?


--
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: squishy bell

[Michael Hennebry]

On Tue, 1 Dec 2020, Samuel Sieb wrote:


On 12/1/20 1:14 PM, Michael Hennebry wrote:

F33 or gnome is giving me lost of squishy bells.


On Gnome, go to the Sound settings and turn off the System Sounds volume 
level.


Thanks.  It worked.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Samuel Sieb]

On 12/1/20 1:14 PM, Bob Goodwin wrote:
I also wasted a lot of time this morning trying to prove to myself that 
that computer still was able to produce sound somehow, it did not! I 
found a working Fedora-30 on a third hard drive, unfortunately the audio 
problem is the same on everything I tried, F30 and with ab E32 live on a 
flash drive I had.


That definitely suggests a hardware problem.

The best solution may turn out to be a different motherboard. I will 
consider that ...


You can get really cheap USB sound devices now.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Unable to remove grub menuentry for kernel 5.9

[Michael Hennebry]

On Tue, 1 Dec 2020, Chris Murphy wrote:


As mad as this all sounds, and is, because of this work we're very
close to being able to support dual boot Fedoras. Right now we only
explicitly support Windows or macOS plus one Fedora. Two Fedoras, is a
nope.


You're right: It's mad.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: squishy bell

[Samuel Sieb]

On 12/1/20 1:14 PM, Michael Hennebry wrote:

F33 or gnome is giving me lost of squishy bells.
In particular I'm getting them from gvim, gedit
and sometimes from a terminal.
How do I make the squishy bells go away?

I found this, but it did not help:
https://lists.centos.org/pipermail/centos/2018-June/169131.html


On Gnome, go to the Sound settings and turn off the System Sounds volume 
level.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Chris Murphy]

On Tue, Dec 1, 2020 at 1:38 PM Tom Horsley  wrote:
>
> On Tue, 1 Dec 2020 13:33:22 -0700
> Chris Murphy wrote:
>
> > Yep. For sure the kernel is what's responsible for reading the
> > partition table. And that alone would cause a spin up. e.g.
>
> But why would it need to scan when it is shutting down the
> system (which is my case :-).

O. Yeah. Hmm. Not sure. You could set both
'systemd.log_level=debug udev.log_priority=debug' and then boot once
and reboot without. Then look at: journalctl -b-1 for clues why that
device is being looked at, at all. I don't know if there's some sort
of udev tear down of things, I don't know why it would be necessary.
But *shrug*. My suspects are systemd because that's responsible for
running the fstab generator, so there may be dev units based on the
fstab entry that somehow cause this. And also udev.

And when does it spin up? Use Esc to see what jobs are running and if
spinup happens before the umounts of  /home /boot /boot/efi or after
that. If it's after that - then it might even be after / goes ro in
which case it's not logged. And in that case there's this:

https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1

>I swear it didn't use to do that,
> then a few releases ago (probably several releases ago) it
> starting hanging on shutdown till the disks spin up.

I'm not sure I've noticed one way or another when the drive I have
spins up. I just assumed it was the *firmware* that's doing it on
UEFI. Not anything to do with Linux. I'll try to pay attention to the
NUC next time I do an update and reboot.



-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Fedora-33 No Sound -

[Bob Goodwin]

On 2020-11-30 18:19, Wolfgang Pfeiffer wrote:


Or you're already a bit sick of it and install F32 ...

Wolfgang

.
No, I would probably wait for Fedora 34 and hope it works.

It is also possible the audio circuit has failed on the motherboard. I 
may also create a new Fedora-33 on the another drive in that computer, 
there is still /dev/sdb I can install on.


I also wasted a lot of time this morning trying to prove to myself that 
that computer still was able to produce sound somehow, it did not! I 
found a working Fedora-30 on a third hard drive, unfortunately the audio 
problem is the same on everything I tried, F30 and with ab E32 live on a 
flash drive I had.


I wonder if it is a setting in the cmos/bios in the MSI motherboard? 
That is a scary mess of fancy artwork with a number of icons that seem 
to do nothing. The last time I tried to make a change to the boot order 
it turned out bad. I had to remove the battery and reset it to the 
default conditions. I thought I had working sound after that, but I am 
beginning to think perhaps not?


The best solution may turn out to be a different motherboard. I will 
consider that ...


Thanks to all for the help,   Bob

--
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

squishy bell

[Michael Hennebry]

F33 or gnome is giving me lost of squishy bells.
In particular I'm getting them from gvim, gedit
and sometimes from a terminal.
How do I make the squishy bells go away?

I found this, but it did not help:
https://lists.centos.org/pipermail/centos/2018-June/169131.html

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Unable to remove grub menuentry for kernel 5.9

[Chris Murphy]

On Tue, Dec 1, 2020 at 1:13 PM Tim via users
 wrote:
>
> On Tue, 2020-12-01 at 20:52 +0530, Sreyan Chakravarty wrote:
> > What am I doing wrong?
>
> I suppose some questions are:  How did you install kernels, in the
> first place.  And have you been manually altering grub menus, too?
>
> I've been using Fedora since it used to be Red Hat Linux, and had
> always let yum or dnf install new kernels as it found them, and remove
> old kernels along the way, and it's never got that wrong.  And I've
> never had to manually intervene to change GRUB menus regarding this.
> I've even had dual-boot systems (Windows, other Linuxes), where the
> dnf/yum kernel install and remove procedures simply work as they're
> supposed to.
>
> Over the years I've simply removed parameters like quiet, rhgb, splash,
> so I can see what's going on while a system is booting, and I haven't
> fouled up the automatic processes for the GRUB menus in doing so, nor
> had to go around madly regenerating things to make my changes.
>
> Some people seem to be endlessly horsing around with grub-install, or
> grub2-mkconfig, etc., and I do not know why.

Maybe you need to make some customizations to boot parameters, which
should happen in /etc/default/grub, and then grub2-mkconfig. Because
grub.cfg shouldn't be directly modified. Can you? *shrug* yes you can
but upstreams has since forever said please don't. The grub.cfg even
includes such text.

On Fedora ~30 to 32 a macro was used for bootparameters, saving them
in grubenv, which grub2-mkconfig would write to. GRUB reads grub.cfg
which says load grubenv, then blscfg (module) which then also goes out
to read the BLS snippets. The snippets have $kernelopts reference to
the bootparameters found in grubenv. This is all very Rube Goldberg
machine-like.

Fedora 33 does away with the macro, the BLS snippets have the boot
parameters in them. Which now means grub2-mkconfig rewrites the BLS
snippets (whether or not you use -o).

The grub.cfg does still contain an explicit entry for Windows, and on
UEFI systems there's also an entry to get to the firmware's setup.

And for many years now, grub2-install should only be used on BIOS
systems. It's not ever automatically updated during upgrades, so
that's left as an exercise for the user to do manually. If not done we
do sometimes see problems because the stage2 bootloader (the core.img)
can contain code that's not necessarily compatible with newer modules
like blscfg.mod. *shrug* pretty esoteric stuff, and is one of the
things bootupd project wants to solve.

Meanwhile on UEFI grub-install should not be used. The EFI OSLoader
binary is updated as part of the grub rpm package updates, on
traditional installations of Fedora. On rpm-ostree this update doesn't
happen, either BIOS or UEFI, and again hence bootupd project.

As mad as this all sounds, and is, because of this work we're very
close to being able to support dual boot Fedoras. Right now we only
explicitly support Windows or macOS plus one Fedora. Two Fedoras, is a
nope.

This is the draft test case for that:
https://fedoraproject.org/wiki/User:Sumantrom/Draft/dualboot_f33_btrfs

The gist is you do an automatic default installation first. Then for
the second installation, reuse /boot/efi, /boot, do not reformat. Also
reuse /home if you want. And then you need to create a new / (it's
required you can't use an existing "root" and assign it to /) mount
point. So now you have two "root" subvolumes (different names of
course) containing the two different Fedoras but they share a /boot.

You might see some confusion if one Fedora deletes a kernel that the
other one depends on, but there you have it. And there is also this
bug to watch out for:
https://bugzilla.redhat.com/show_bug.cgi?id=1874724

But otherwise, it works. For the adventurous bold and brave, you can
even build bees and dedup. I expect a significant ability to dedup the
same version OS because the binaries will be identical. That is,
Workstation 33 and KDE 33 will share a lot of the same binaries. Same
for Workstation 33 and Silverblue 33. You could have a very low
footprint for having multiple Fedoras on the same Btrfs file system.


-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Where's the best place to discuss Cura issues?

[Fulko Hew]

On Tue, Dec 1, 2020 at 3:49 PM Fulko Hew  wrote:
... snip ...


> There is a "Get started" button under the "...This will only take a few
>> moments." text. Maybe the VM screen is too small to make it visible, the
>> window
>> is rather tall.
>>
>
> Not on my machine. See the attached:
>

Sorry, the screen shot may not come through.
Suffice it to say, yes there is room for a button, but nothing
is visible. And for laughs, I tried clicking everywhere anyway, and
there isn't a hidden button on that window anywhere.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Tom Horsley]

On Tue, 1 Dec 2020 13:33:22 -0700
Chris Murphy wrote:

> Yep. For sure the kernel is what's responsible for reading the
> partition table. And that alone would cause a spin up. e.g.

But why would it need to scan when it is shutting down the
system (which is my case :-). I swear it didn't use to do that,
then a few releases ago (probably several releases ago) it
starting hanging on shutdown till the disks spin up.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Chris Murphy]

On Tue, Dec 1, 2020 at 1:07 PM Samuel Sieb  wrote:
>
> On 12/1/20 8:42 AM, Patrick O'Callaghan wrote:
> > On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> >> On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
> >>>
> >>> On Tue, 1 Dec 2020 14:52:21 +0100
> >>> Roberto Ragusa wrote:
> >>>
>  How do you power them down?
> >>>
> >>> I don't know about the original poster, but my "noauto" disks
> >>> timeout and power down all by themselves, then even when they aren't
> >>> mounted at all, every time I reboot, the reboot hangs while it
> >>> spins up the disks for some reason. I constantly wish I could make
> >>> it stop doing that.
> >>
> >> Enumeration. I'm not sure if it's udev scanning everything, or the
> >> kernel or both. And also maybe libblkid, to know what everything is.
> >> The only way it can know what it is, it needs to be spun up to read
> >> the partition map and all the signatures on each partition.
> >
> > Obviously it needs to spin up if it needs to know these things. My
> > point is that it doesn't need to know them until I tell it.
>
> But it can't know that it shouldn't until it knows what's there. :-)
> The kernel scanning the USB bus will trigger the dock to check the
> drives which will spin them up.  Even if the dock didn't, the kernel
> would still check the drives, so they would still be started.

Yep. For sure the kernel is what's responsible for reading the
partition table. And that alone would cause a spin up. e.g.

[6.426044]  sdb: sdb1 sdb2

Only later does udev come in with "aha! a partition! let's scan it!"
and then I see things like:

[6.506645] BTRFS: device label fedoraroot devid 2 transid 398800
/dev/sdb2 scanned by systemd-udevd (326)

And there is an interaction with libblkid in the kernel to determine
that this partition contains a Btrfs signature, what the label is,
what the fs UUID is. And it's udev along with that information from
libblkid that creates the disk by label, disk by uuid, disk by
partuuid, disk by whatever.

The parameter to use to get detailed udev reporting dumped into the
journal is udev.log_priority=debug and then you can see what does
what, and in what order.

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Chris Murphy]

On Tue, Dec 1, 2020 at 9:42 AM Patrick O'Callaghan
 wrote:
>
> On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> > On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
> > >
> > > On Tue, 1 Dec 2020 14:52:21 +0100
> > > Roberto Ragusa wrote:
> > >
> > > > How do you power them down?
> > >
> > > I don't know about the original poster, but my "noauto" disks
> > > timeout and power down all by themselves, then even when they aren't
> > > mounted at all, every time I reboot, the reboot hangs while it
> > > spins up the disks for some reason. I constantly wish I could make
> > > it stop doing that.
> >
> > Enumeration. I'm not sure if it's udev scanning everything, or the
> > kernel or both. And also maybe libblkid, to know what everything is.
> > The only way it can know what it is, it needs to be spun up to read
> > the partition map and all the signatures on each partition.
>
> Obviously it needs to spin up if it needs to know these things. My
> point is that it doesn't need to know them until I tell it.

Yeah that's not how it works.

$ dmesg | grep sda
[2.149354] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks:
(2.00 TB/1.82 TiB)
[2.149397] sd 0:0:0:0: [sda] 4096-byte physical blocks
[2.149514] sd 0:0:0:0: [sda] Write Protect is off
[2.149545] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[2.149722] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[2.235611]  sda: sda1
[2.236610] sd 0:0:0:0: [sda] Attached SCSI disk
$

The second to last line, where it discovers the sda1 partition, is
needed in order to create all the symlinks for all the various parts
of that drive. Not just the dev node, but also the /dev/disk/by-
things.

If you don't want that to happen, you'd need a udev rule to inhibit
that. And then when it goes looking for a particular fs UUID in fstab
to mount, of course it doesn't exist, so the mount will fail. It
doesn't know it needs to scan everything NOW. There's no correlation
between fs UUID in fstab to a particular device until it's scanned,
which happens by udev during early startup.


-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Where's the best place to discuss Cura issues?

[Fulko Hew]

On Tue, Dec 1, 2020 at 2:59 PM Tom Horsley  wrote:

> On Tue, 1 Dec 2020 14:34:17 -0500
> Fulko Hew wrote:
>
> > Any suggestions?
>
> Start it from a terminal and see if anything shows up on stderr.
>

This is the stuff a some initial 'Loading machines', 'Loading UI' happens.
I don't see anything catastrophic in there.

2020-12-01 15:00:55,292 - DEBUG - [MainThread] cura.CuraApplication.run
[830]: Booting Cura took 1.5601575374603271 seconds
2020-12-01 15:00:55,292 - DEBUG - [Thread-1]
cura.Machines.ContainerTree.run [174]: Started background loading of
MachineNodes
2020-12-01 15:00:55,292 - DEBUG - [Thread-1]
cura.Machines.ContainerTree.run [185]: All MachineNode loading completed
2020-12-01 15:00:55,405 - DEBUG - [MainThread]
cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [33]:
Updating CustomQualityProfilesDropDownMenuModel.
2020-12-01 15:00:55,406 - DEBUG - [MainThread]
cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [38]:
No active GlobalStack, set CustomQualityProfilesDropDownMenu
Model as empty.
2020-12-01 15:00:55,407 - DEBUG - [MainThread]
cura.Machines.Models.QualityProfilesDropDownMenuModel._update [62]:
Updating QualityProfilesDropDownMenuModel.
2020-12-01 15:00:55,407 - DEBUG - [MainThread]
cura.Machines.Models.QualityProfilesDropDownMenuModel._update [74]: No
active GlobalStack, set quality profile model as empty.
/usr/lib/python3.9/site-packages/UM/Qt/Bindings/PointingRectangle.py:106:
DeprecationWarning: an integer is required (got type float).  Implicit
conversion to integers using __int__
is deprecated, and may be removed in a future version of Python.
 target_offset = self._target - QPoint(self.x(), self.y())
2020-12-01 15:00:55,474 - DEBUG - [MainThread] UM.Qt.QtRenderer._initialize
[210]: Support for Vertex Array Objects: True
2020-12-01 15:00:55,480 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__
[112]: Initialized OpenGL subsystems.
2020-12-01 15:00:55,480 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__
[113]: OpenGL Version:  4.6 (Core Profile) Mesa 20.2.3
2020-12-01 15:00:55,480 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__
[114]: OpenGL Vendor:   Intel
2020-12-01 15:00:55,480 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__
[115]: OpenGL Renderer: Mesa Intel(R) HD Graphics 620 (KBL GT2)
2020-12-01 15:00:55,481 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__
[116]: GLSL Version:4.60.0
2020-12-01 15:00:55,481 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/default.shader]...
2020-12-01 15:00:55,486 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/selection.shader]...
2020-12-01 15:00:55,487 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/select_face.shader]...
2020-12-01 15:00:55,488 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/default.shader]...
2020-12-01 15:00:55,489 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/composite.shader]...
/usr/lib/python3.9/site-packages/UM/Qt/QtRenderer.py:225:
DeprecationWarning: tostring() is deprecated. Use tobytes() instead.
 data = numpy.array([
/usr/lib/python3.9/site-packages/UM/Qt/QtRenderer.py:132:
DeprecationWarning: an integer is required (got type float).  Implicit
conversion to integers using __int__ is deprecated,
and may be removed in a future version of Python.
 self._gl.glViewport(0, 0, self._viewport_width, self._viewport_height)
2020-12-01 15:00:55,490 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/overhang.shader]...
2020-12-01 15:00:55,492 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/striped.shader]...
2020-12-01 15:00:55,494 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/transparent_object.shader]...
2020-12-01 15:00:55,495 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/striped.shader]...
2020-12-01 15:00:55,496 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/xray.shader]...
2020-12-01 15:00:55,497 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/cura/resources/shaders/xray_composite.shader]...
2020-12-01 15:00:55,499 - DEBUG - [MainThread]
UM.View.GL.ShaderProgram.load [58]: Loading shader file
[/usr/share/uranium/resources/shaders/platform.shader]...
/usr/lib/python3.9/site-packages/UM/View/GL/FrameBufferObject.py:18:
DeprecationWarning: an integer is required (got type float).  Implicit
conversion to integers using __int__ is d
eprecated, and may be removed 

Re: Inhibiting device startup at boot

[Chris Murphy]

On Tue, Dec 1, 2020 at 9:39 AM Patrick O'Callaghan
 wrote:
>
> On Tue, 2020-12-01 at 14:52 +0100, Roberto Ragusa wrote:
> > On 12/1/20 2:15 PM, Patrick O'Callaghan wrote:
> > > I have a couple of SATA drives connected via a USB dock that I use only
> > > for backups. Normally they are powered down and only come on at night
> > > during the backup run. However they also power on any time I reboot the
> > > system and have to be powered down again manually. I'd prefer not to
> > > power them on at all until they're needed.
> > >
> > > Is there some magic that would inhibit the boot process from powering
> > > up these devices? Note that the /etc/fstab entry already has 'noauto'
> > > but that just prevents them from being mounted.
> >
> > How do you power them down?
>
> Extract from my script ($SLOT is sd[de]):
>
> smartctl --smart=off /dev/$SLOT1 -q errorsonly >> $LOG 2>&1
> smartctl --smart=off /dev/$SLOT2 -q errorsonly >> $LOG 2>&1
> echo 1 > /sys/block/$SLOT1/device/delete# 
> Can't use udisksctl because it removes the
> echo 1 > /sys/block/$SLOT2/device/delete# 
> bus, which can't be powered on again
>


I've got a Seagate laptop drive inside an Intel NUC that is only
storage (not system boot or root). And I use a udev rule.

$ ls -l /etc/udev/
hwdb.bin   hwdb.d/rules.d/   udev.conf
$ ls -l /etc/udev/rules.d/
total 12
-rw-r--r--. 1 root root 139 Oct  7 17:47 60-block-scheduler.rules
-rw-r--r--. 1 root root 179 Oct  7 17:36 69-hdparm.rules
-rw-r--r--. 1 root root 628 Oct 29 06:40 70-persistent-ipoib.rules
$ cat /etc/udev/rules.d/69-hdparm.rules
ACTION=="add", SUBSYSTEM=="block", \
  KERNEL=="sd*[!0-9]", \
  ENV{ID_SERIAL_SHORT}=="WDZ47F0A", \
  RUN+="/usr/sbin/hdparm -B 100 -S 252 /dev/disk/by-id/wwn-0x5000c500a93cae8a"
$

--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Unable to remove grub menuentry for kernel 5.9

[Tim via users]

On Tue, 2020-12-01 at 20:52 +0530, Sreyan Chakravarty wrote:
> What am I doing wrong?

I suppose some questions are:  How did you install kernels, in the
first place.  And have you been manually altering grub menus, too?

I've been using Fedora since it used to be Red Hat Linux, and had
always let yum or dnf install new kernels as it found them, and remove
old kernels along the way, and it's never got that wrong.  And I've
never had to manually intervene to change GRUB menus regarding this. 
I've even had dual-boot systems (Windows, other Linuxes), where the
dnf/yum kernel install and remove procedures simply work as they're
supposed to.

Over the years I've simply removed parameters like quiet, rhgb, splash,
so I can see what's going on while a system is booting, and I haven't
fouled up the automatic processes for the GRUB menus in doing so, nor
had to go around madly regenerating things to make my changes.

Some people seem to be endlessly horsing around with grub-install, or
grub2-mkconfig, etc., and I do not know why.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.6.1.el7.x86_64 #1 SMP Tue Nov 17 13:59:11 UTC 2020 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Samuel Sieb]

On 12/1/20 8:42 AM, Patrick O'Callaghan wrote:

On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:

On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:


On Tue, 1 Dec 2020 14:52:21 +0100
Roberto Ragusa wrote:


How do you power them down?


I don't know about the original poster, but my "noauto" disks
timeout and power down all by themselves, then even when they aren't
mounted at all, every time I reboot, the reboot hangs while it
spins up the disks for some reason. I constantly wish I could make
it stop doing that.


Enumeration. I'm not sure if it's udev scanning everything, or the
kernel or both. And also maybe libblkid, to know what everything is.
The only way it can know what it is, it needs to be spun up to read
the partition map and all the signatures on each partition.


Obviously it needs to spin up if it needs to know these things. My
point is that it doesn't need to know them until I tell it.


But it can't know that it shouldn't until it knows what's there. :-)
The kernel scanning the USB bus will trigger the dock to check the 
drives which will spin them up.  Even if the dock didn't, the kernel 
would still check the drives, so they would still be started.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Where's the best place to discuss Cura issues?

[Tom Horsley]

On Tue, 1 Dec 2020 14:34:17 -0500
Fulko Hew wrote:

> Any suggestions?

Start it from a terminal and see if anything shows up on stderr.
When I run it I get thousands of lines of output (but I apparently
did the initial setup long ago and forgot about it because it
already knows I have a solidoodle 2 (antique :-) 3d printer.

Even though I'm up to date on fedora 33, I also get a notice
that a new version of cura is available, so f33 isn't the latest
either.

I normally use Repetier Host (because I'm used to it) and it can
use the cura engine as a slicer.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Where's the best place to discuss Cura issues?

[Fulko Hew]

As the subject line asks, where's the best place to discuss issues?
The 3dprinting list ?

In the meantime, I've been using the released version of Cura on F28
but I couldn't seem to get a slice that had 1 layer wide vertical walls.
So I thought I'd try the most recent version in F33 in a VM.
[I then had to upgrade a system to F33 rather than in a VM.]
After installing 'dnf install cura' and running it,
it hangs with a splash screen that says:
'Welcome to Ultimaker Cura.
Please follow these steps to set up Ultimaker Cura.
This will only take a few moments.'

And that's it.  It does nothing else, and there isn't anything I can click
on to proceed.

Any suggestions?

Thanks
Fulko
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Samuel Sieb]

On 12/1/20 3:35 AM, Michael D. Setzer II via users wrote:

Didn't realize is was EOL already?? Missed that FC33 was already fully
out.  Will have to do an upgrade. Don't care for the latest changes they
have forced on vncserver, but guess I'll have to figure it out. That is
probable why I had overlooked it going to EOL. Have 4 systems I access
via vnc and like the simple vncserver setup versus the new systemd
setup..


It's a change, but it's not too bad.  I got mine working and I'm happier 
to have it automatically start now.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 09:01 -0700, Chris Murphy wrote:
> On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
> > 
> > On Tue, 1 Dec 2020 14:52:21 +0100
> > Roberto Ragusa wrote:
> > 
> > > How do you power them down?
> > 
> > I don't know about the original poster, but my "noauto" disks
> > timeout and power down all by themselves, then even when they aren't
> > mounted at all, every time I reboot, the reboot hangs while it
> > spins up the disks for some reason. I constantly wish I could make
> > it stop doing that.
> 
> Enumeration. I'm not sure if it's udev scanning everything, or the
> kernel or both. And also maybe libblkid, to know what everything is.
> The only way it can know what it is, it needs to be spun up to read
> the partition map and all the signatures on each partition.

Obviously it needs to spin up if it needs to know these things. My
point is that it doesn't need to know them until I tell it.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 08:59 -0500, Tom Horsley wrote:
> On Tue, 1 Dec 2020 14:52:21 +0100
> Roberto Ragusa wrote:
> 
> > How do you power them down?
> 
> I don't know about the original poster, but my "noauto" disks
> timeout and power down all by themselves, then even when they aren't
> mounted at all, every time I reboot, the reboot hangs while it
> spins up the disks for some reason. I constantly wish I could make
> it stop doing that.

They do power down themselves, but only after 30 minutes of
"inactivity", which seems to mean "being disconnected from the bus"
rather than actual inactivity (so just unmounting them won't do it).

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 14:52 +0100, Roberto Ragusa wrote:
> On 12/1/20 2:15 PM, Patrick O'Callaghan wrote:
> > I have a couple of SATA drives connected via a USB dock that I use only
> > for backups. Normally they are powered down and only come on at night
> > during the backup run. However they also power on any time I reboot the
> > system and have to be powered down again manually. I'd prefer not to
> > power them on at all until they're needed.
> > 
> > Is there some magic that would inhibit the boot process from powering
> > up these devices? Note that the /etc/fstab entry already has 'noauto'
> > but that just prevents them from being mounted.
> 
> How do you power them down?

Extract from my script ($SLOT is sd[de]):

smartctl --smart=off /dev/$SLOT1 -q errorsonly >> $LOG 2>&1
smartctl --smart=off /dev/$SLOT2 -q errorsonly >> $LOG 2>&1
echo 1 > /sys/block/$SLOT1/device/delete# Can't 
use udisksctl because it removes the
echo 1 > /sys/block/$SLOT2/device/delete# bus, 
which can't be powered on again

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Chris Murphy]

On Tue, Dec 1, 2020 at 6:59 AM Tom Horsley  wrote:
>
> On Tue, 1 Dec 2020 14:52:21 +0100
> Roberto Ragusa wrote:
>
> > How do you power them down?
>
> I don't know about the original poster, but my "noauto" disks
> timeout and power down all by themselves, then even when they aren't
> mounted at all, every time I reboot, the reboot hangs while it
> spins up the disks for some reason. I constantly wish I could make
> it stop doing that.

Enumeration. I'm not sure if it's udev scanning everything, or the
kernel or both. And also maybe libblkid, to know what everything is.
The only way it can know what it is, it needs to be spun up to read
the partition map and all the signatures on each partition.

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How do I restore BTRFS snapshots ?

[Chris Murphy]

On Tue, Dec 1, 2020 at 2:06 AM Sreyan Chakravarty  wrote:
>
>
>
> On Mon, Nov 30, 2020 at 10:12 PM Chris Murphy  wrote:
>>
>>
>> I don't understand why you're going to another forum to ask the same
>> question, and posting different information. It's just making it more
>> difficult to provide answers. Here is what you posted there:
>>
>
> Since I did not know about BTRFS.
>
>>
>> $ btrfs subvolume list /
>> ID 256 gen 3794 top level 5 path fedora
>> ID 264 gen 2296 top level 256 path root/snapshots/test
>>
>> That is not a default subvolume layout for Fedora 33. I have no idea
>> how you arrived at this layout but it's not the default. If you do a
>> default (automatic) installation of Fedora 33, you will have two
>> subvolumes: home and root, at the top level.
>
>
> Ok, I have managed to get BTRFS snapshots working.
>
> I must have messed up the installation somehow. Now I have a subvolume under 
> the toplevel volume which I can now rename.
>
> But the problem is that I have to reboot to a live CD just to take a snapshot.

No you don't.

> Any way to do it within the OS ?

I gave an explicit, line by line example, in this thread, two days ago.

The unintuitive part of that particular example, is mounting the
top-level of the file system. If you have a default Fedora 33
installation, this can be done by mounting the main volume (the
device+partition listed in 'df' for both / and /home) to something
like /mnt or wherever else you prefer. And now you will see what look
like directories named "root" and "home" - but those are subvolumes.
And you can snapshot them. Keeping all subvolumes and snapshots in
this normally hidden top-level is referred to as the "flat" layout.

https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Layout

In the "nested" layout, you don't have to mount the top-level, you can
just directly snapshot the mountpoint. e.g.

btrfs subvolume snapshot /home /home/home.snapshot1

That will snapshot the "home" subvolume that is mounted at /home, and
place it in /home with the name home.snapshot1. The reason it's
referred to as "nested" layout is because these subvolume snapshots
appear to be located within the subvolume you just just snapshot.

As a consequence of this, if you 'du /home' it will add up all of the
stuff in /home two times. Once for the "home" subvolume and again for
the "home.snapshot1" subvolume snapshot. It doesn't know that one of
them is a snapshot, nor that you'd want to exclude one of them from
the usage calculation. Hence 'btrfs filesystem du -s /path/' which
provides more information.

Another example:

btrfs subvolume snapshot / /root.snapshot

This will snapshot the "root" subvolume that is mounted at /, and
place it /, with the name root.snapshot1. Btrfs snapshots are not on
rails. It will let you create a snapshot anywhere. Another set of
examples:

btrfs subvolume snapshot /home /root/home.snapshot
btrfs subvolume snapshot / /home/

I'm not sure why anyone would organize snapshots that way, but btrfs
doesn't care, it'll let you do it.


-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Unable to remove grub menuentry for kernel 5.9

[Chris Murphy]

On Tue, Dec 1, 2020 at 8:23 AM Sreyan Chakravarty  wrote:
>
> Hi,
>
> I have uninstalled kernel 5.9 via dnf remove, and I have also re-generated my 
> grub.cfg using grub2-mkconfig, but the GRUB menuentry for kernel 5.9 still 
> persists.
>
> Any other way to get rid of it ?
>
> I cannot understand the format of the grub.cfg file hence can't modify it 
> manually.
>
> I tried to find menuentry sections but I could only find 1:
>
> menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
> fwsetup
> }
>
> What am I doing wrong?

Fedora users BootLoaderSpec snippets found in /boot/loader/entries -
if the associated snippet for the deleted kernel isn't being deleted
then there's a bug somewhere. It's not one I've come across though.

-- 
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Unable to remove grub menuentry for kernel 5.9

[Sreyan Chakravarty]

Hi,

I have uninstalled kernel 5.9 via dnf remove, and I have also re-generated
my grub.cfg using grub2-mkconfig, but the GRUB menuentry for kernel 5.9
still persists.

Any other way to get rid of it ?

I cannot understand the format of the grub.cfg file hence can't modify it
manually.

I tried to find menuentry sections but I could only find 1:

menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
fwsetup
}

What am I doing wrong?
-- 
Regards,
Sreyan Chakravarty
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Roberto Ragusa]

On 12/1/20 2:59 PM, Tom Horsley wrote:

On Tue, 1 Dec 2020 14:52:21 +0100
Roberto Ragusa wrote:


How do you power them down?


I don't know about the original poster, but my "noauto" disks
timeout and power down all by themselves, then even when they aren't
mounted at all, every time I reboot, the reboot hangs while it
spins up the disks for some reason. I constantly wish I could make
it stop doing that.


I suppose that the disks are always "on", even when they are not spinning.
At boot of course they will be scanned for partitions etc. so they will
spin up.
Then, they may have a timeout (in SATA firmware or USB firmware) to spin
down when not receiving requests, and that works for me even if the
filesystem is mounted (no process does anything on that fs).

This is why I was asking about the "manual shutdown".
It could be all entirely automatic and power-saving based.
Otherwise, I would like to know details.

Regards.

--
   Roberto Ragusamail at robertoragusa.it
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Tom Horsley]

On Tue, 1 Dec 2020 14:52:21 +0100
Roberto Ragusa wrote:

> How do you power them down?

I don't know about the original poster, but my "noauto" disks
timeout and power down all by themselves, then even when they aren't
mounted at all, every time I reboot, the reboot hangs while it
spins up the disks for some reason. I constantly wish I could make
it stop doing that.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Inhibiting device startup at boot

[Roberto Ragusa]

On 12/1/20 2:15 PM, Patrick O'Callaghan wrote:

I have a couple of SATA drives connected via a USB dock that I use only
for backups. Normally they are powered down and only come on at night
during the backup run. However they also power on any time I reboot the
system and have to be powered down again manually. I'd prefer not to
power them on at all until they're needed.

Is there some magic that would inhibit the boot process from powering
up these devices? Note that the /etc/fstab entry already has 'noauto'
but that just prevents them from being mounted.


How do you power them down?

--
   Roberto Ragusamail at robertoragusa.it
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Inhibiting device startup at boot

[Patrick O'Callaghan]

I have a couple of SATA drives connected via a USB dock that I use only
for backups. Normally they are powered down and only come on at night
during the backup run. However they also power on any time I reboot the
system and have to be powered down again manually. I'd prefer not to
power them on at all until they're needed.

Is there some magic that would inhibit the boot process from powering
up these devices? Note that the /etc/fstab entry already has 'noauto'
but that just prevents them from being mounted.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Patrick O'Callaghan]

On Tue, 2020-12-01 at 21:35 +1000, Michael D. Setzer II via users
wrote:
> Didn't realize is was EOL already?? Missed that FC33 was already fully 
> out. 

It's worth subscribing to the Announce list. It's low-traffic.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Ed Greshko]

On 01/12/2020 19:35, Michael D. Setzer II wrote:

Thanks for pointing out the EOL..


In case others have missed it, this was sent out on Nov. 20.

Fedora 31 will go end of life for updates and support on 24th of
November 2020. No further updates, including security updates, will be
available for Fedora 31 after the said date. All the updates of Fedora
31 being pushed to stable will be stopped as well.

Fedora 32 will continue to receive updates until approximately one
month after the release of Fedora 34. The maintenance schedule of
Fedora releases is documented on the Fedora Project wiki [0]. The
fedora Project wiki also contains instructions [1] on how to upgrade
from a previous release of Fedora to a version receiving updates.



---
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Michael D. Setzer II via users]

On 1 Dec 2020 at 18:32, Ed Greshko wrote:

From:   Ed Greshko 
Subject:Re: Differences between versions of wine on FC31 and 
FC32? 5.19/5.22
To: users@lists.fedoraproject.org
Date sent:  Tue, 1 Dec 2020 18:32:15 +0800
Send reply to:  Community support for Fedora users 


> On 01/12/2020 18:30, Michael D. Setzer II via users wrote:
> > Have 5 linux machine at home with 3 on FC32 and 2 on FC31.
> > One of the FC31s is my notebook, and noticed that the wine on the FC32
> > has gone up to 5.22, while the FC31 are at 5.19? Checked the testing
> > repos to see if it might be there, but nothing.
> >
> > Usually, the latest version will get an update, and the other will show up
> > within a couple days?? Just ran updates on machines, so noticed the
> > differences. Never recall it being more than one different...
> 
> Well, F31 is EOL.  So, it will no longer get updates.

Didn't realize is was EOL already?? Missed that FC33 was already fully 
out.  Will have to do an upgrade. Don't care for the latest changes they 
have forced on vncserver, but guess I'll have to figure it out. That is 
probable why I had overlooked it going to EOL. Have 4 systems I access 
via vnc and like the simple vncserver setup versus the new systemd 
setup..

Thanks for pointing out the EOL..

> 
> ---
> The key to getting good answers is to ask good questions.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Ed Greshko]

On 01/12/2020 18:30, Michael D. Setzer II via users wrote:

Have 5 linux machine at home with 3 on FC32 and 2 on FC31.
One of the FC31s is my notebook, and noticed that the wine on the FC32
has gone up to 5.22, while the FC31 are at 5.19? Checked the testing
repos to see if it might be there, but nothing.

Usually, the latest version will get an update, and the other will show up
within a couple days?? Just ran updates on machines, so noticed the
differences. Never recall it being more than one different...


Well, F31 is EOL.  So, it will no longer get updates.

---
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Differences between versions of wine on FC31 and FC32? 5.19/5.22

[Michael D. Setzer II via users]

Have 5 linux machine at home with 3 on FC32 and 2 on FC31.
One of the FC31s is my notebook, and noticed that the wine on the FC32 
has gone up to 5.22, while the FC31 are at 5.19? Checked the testing 
repos to see if it might be there, but nothing.

Usually, the latest version will get an update, and the other will show up 
within a couple days?? Just ran updates on machines, so noticed the 
differences. Never recall it being more than one different...

Thanks. Have a nice day, and be Safe..

++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: mysterious/suspicious internet activity.

[J.Witvliet--- via users]

From: "home user" mailto:mattis...@comcast.net>>
Date: Monday, 30 November 2020 at 18:57:40
To: "users@lists.fedoraproject.org" 
mailto:users@lists.fedoraproject.org>>
Subject: mysterious/suspicious internet activity.

Fedora-32 home workstation; gnome.

In ksysguard, I've been noticing internet activity that I can't explain.  This 
has been going on for weeks, and it's making me uncomfortable.

What I do:
1. After the system has been powered down overnight, I boot it up.
2. I sign in to a user account.
3. My .bash_profile sources my .bashrc, sets PATH, and launches xeyes.  My 
.bashrc sources /etc/bashrc, sets PS1 and PATH, and defines aliases.
4. I launch ksysguard, then Spectacle.
5. I wait several seconds, then take a screen-capture of ksysguard's display.

To get a good sample, I did five screen-captures.  Here are the google drive 
links to them:
"https://drive.google.com/file/d/1EdlSgKY0fJpU7r3nbstWA7G_2C93gOgO/view?usp=sharing;
"https://drive.google.com/file/d/1jfocTMRnwguRdDIchoBtsNYYwQZr647i/view?usp=sharing;
"https://drive.google.com/file/d/1Tx3kDEMbL_TCZZ-F0YOVOXSy2D9G3MAM/view?usp=sharing;
"https://drive.google.com/file/d/157KU27QtsJTZghyRgeuafYSnvxR85im4/view?usp=sharing;
"https://drive.google.com/file/d/1AyZDRvcKYHYypNSU6AF9Fh34rh_l3q2J/view?usp=sharing;

This is way outside my knowledge and experience.  I need good step-by-step 
instructions on this.

Thank-you in advance.
Bill.
___


Hi,

What puzzles me, is that you don’t refer to the firewall.
It’s the firewall responsibility to block unexpected incoming, but also 
outgoing traffic.
Often people trust all outgoing traffic on 443 and 80 (and corresponding 
replies), but you can initially LOG it all, and subsequently change your rules 
to DROP all you don’t want to see. (Before logging the uncaught)

Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet 
de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u 
verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat 
aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband 
houdt met risico's verbonden aan het elektronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are 
not the addressee or if this message was sent to you by mistake, you are 
requested to inform the sender and delete the message. The State accepts no 
liability for damage of any kind resulting from the risks inherent in the 
electronic transmission of messages.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How do I restore BTRFS snapshots ?

[Sreyan Chakravarty]

On Mon, Nov 30, 2020 at 10:12 PM Chris Murphy 
wrote:

>
> I don't understand why you're going to another forum to ask the same
> question, and posting different information. It's just making it more
> difficult to provide answers. Here is what you posted there:
>
>
Since I did not know about BTRFS.


> $ btrfs subvolume list /
> ID 256 gen 3794 top level 5 path fedora
> ID 264 gen 2296 top level 256 path root/snapshots/test
>
> That is not a default subvolume layout for Fedora 33. I have no idea
> how you arrived at this layout but it's not the default. If you do a
> default (automatic) installation of Fedora 33, you will have two
> subvolumes: home and root, at the top level.
>

Ok, I have managed to get BTRFS snapshots working.

I must have messed up the installation somehow. Now I have a subvolume
under the toplevel volume which I can now rename.

But the problem is that I have to reboot to a live CD just to take a
snapshot. Any way to do it within the OS ?
-- 
Regards,
Sreyan Chakravarty
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

[389-users] unattended request cert process

[Angel Bosch Mora]

hi,

some time ago I asked for a scriptable way of creating a certificate request, 
here's the thread:

https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/thread/EHWWAHOO3S2HZEWJEXTQKDDRH33NLSMU/#HF7ZPVLMUK32AIEEWPEOLUJGZFXXRCEK

I didn't have the time to write anything and I would like to invest some time 
now.

the goal is to create an unattended script for node creation INCLUDING 
certification with an external CA.


I'm thinking about having several precreated certificate databases and download 
them to nodes.
something like:

openssl rand -base64 16 > pwfile.txt && certutil -N -d . -f pwfile.txt

in several nodes and then scp/wget them to each node.
also, do all CSR beforehand and already signed with our CA so I will have a 
repo of cert databases like:


nss/ca_root.crt
nss/ldap10
nss/ldap10/cert9.db
nss/ldap10/key4.db
nss/ldap10/ldap10.example.com.crt
nss/ldap10/pkcs11.txt
nss/ldap10/pwfile.txt
nss/ldap11
nss/ldap11/cert9.db
nss/ldap11/key4.db
nss/ldap11/ldap11.example.com.crt
nss/ldap11/pkcs11.txt
nss/ldap11/pwfile.txt
nss/ldap12
nss/ldap12/cert9.db
nss/ldap12/key4.db
nss/ldap12/ldap12.example.com.crt
nss/ldap12/pkcs11.txt
nss/ldap12/pwfile.txt
nss/ldap13
nss/ldap13/cert9.db
nss/ldap13/key4.db
nss/ldap13/ldap13.example.com.crt
nss/ldap13/pkcs11.txt
nss/ldap13/pwfile.txt
nss/ldap14
nss/ldap14/cert9.db
nss/ldap14/key4.db
nss/ldap14/ldap14.example.com.crt
nss/ldap14/pkcs11.txt
nss/ldap14/pwfile.txt
nss/ldap15
nss/ldap15/cert9.db
nss/ldap15/key4.db
nss/ldap15/ldap15.example.com.crt
nss/ldap15/pkcs11.txt
nss/ldap15/pwfile.txt


this step is the only one remaining on my recipe of unattended container 
creation, so any help will be really appreciated.



best regards,

abosch


-- Institut Mallorqui d'Afers Socials. Aquest missatge, i si escau, qualsevol 
fitxer annex, es dirigeix exclusivament a la persona que n'es destinataria i 
pot contenir informacio confidencial. En cap cas no heu de copiar aquest 
missatge ni lliurar-lo a terceres persones sense permis expres de l'IMAS. Si no 
sou la persona destinataria que s'hi indica (o la responsable de lliurar-l'hi) 
us demanam que ho notifiqueu immediatament a l'adreca electronica de la persona 
remitent. Abans d'imprimir aquest missatge, pensau si es realment necessari.
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org