Thank you

[L. D. Barnes]

I started with Linux when Mandrake had to be bought from a computer store,
and 56K external modems where used Netscape Navigator. From Mandrake I went
to Suse, that for reasons I don't remember wouldn't work on a new desktop,
I went to Ubuntu, and toyed around with Vector, and when support died back
to Ubuntu. I have tried a plethora of desktop environments.

I now have Fedora security lab installed, you have really done well, I love
the idea of not having sudo access while I am the user, but to have to
login in as SU to use some of the apps, is just wonderful. I always loved
snaptic and I really, really appreciate dnfdragora. This has got to be the
best thought out environments I have ever used, thank you so much.

I came to Fedora for several reasons I had in mind that in my retirement
years I wanted to work on cyber security projects, because now living in a
senior housing community I found out how inept my peers are when it comes
to basic security. I have found I am inept on how to use the security lab,
I've done internet searches to try and get some information, but seem to
come up short, I went to my local university and they want me to get a
degree, at 56 years old really not interested, I already have  a a BA and
MTh I've tried the different online courses through eDX and Udemy, they all
teach using different OS or different types of software.

I am really wondering is there any training for the security lab suite? If
not that's ok  I will just continue to use this configuration I think its
sweet.


Appreciate it.

-- 
-- 
Larry
Verbum Domini Manet Aeternum!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Ed Greshko]

On 9/20/18 8:09 AM, Rick Stevens wrote:
> Do what you wish, just be bloody careful about it. That's all I'm
> saying.

Just a FWIW.

It has been my experience that those responsible for 100s+ system mostly do 
their due
diligence when it comes to configuring automatic updates. 
And those that didn't,  don't last very long in their job.   :-)

The downside to being cautious is that after you retire you keep getting asked 
by
your wife: "I never see you use that (test) system.  Why  don't you just get rid
of it?".  :-)

-- 
Cardinal Rule of Presentations: "Tell them what you are going to tell them, tell
them, then tell them what you told them."



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Louis Garcia]

That is what I do. I have a local repo that I sync. Workstations only have
the local repo enabled. After I'm satisfied the updates cause no pain I let
the rest update. Now my users never bother to update so I end up going
around when their are other issues
 and update as I go. I just wanted to know if there was an easier way.
dnf-automatic looks small enough that I could modify for my purpose.

On Wed, Sep 19, 2018 at 8:10 PM Rick Stevens  wrote:

> On 9/19/18 4:45 PM, Louis Garcia wrote:
> > I handle hundreds of workstations, I am not about to manually update
> > everyone. dnf-automatic the best choice right now.
>
> Go right ahead. I'm just warning you.
>
> I managed 1500-3000 systems in multiple datacenters world wide and at
> least that many additional VMs. Most were under Puppet or Ansible and
> they were regularly audited so I generally knew what they had installed.
>
> I'm just saying that I wouldn't permit automatic upgrades unless I'd
> vetted those upgrades manually on test machines that represented the
> targets involved. I even disabled automatic updates to things like
> docker and kubernetes (which do their own updates outside of dnf/yum) so
> they wouldn't break (and brother, were there ever been some MASSIVE
> screwups there). Even with all those precautions, I was bitten. Hard.
> Multiple times. Not fun. Not in the least.
>
> Do what you wish, just be bloody careful about it. That's all I'm
> saying.
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -  Cuteness can be overcome through sufficient bastardry -
> - --Mark 'Kamikaze' Hughes   -
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Rick Stevens]

On 9/19/18 4:45 PM, Louis Garcia wrote:
> I handle hundreds of workstations, I am not about to manually update
> everyone. dnf-automatic the best choice right now.

Go right ahead. I'm just warning you.

I managed 1500-3000 systems in multiple datacenters world wide and at
least that many additional VMs. Most were under Puppet or Ansible and
they were regularly audited so I generally knew what they had installed.

I'm just saying that I wouldn't permit automatic upgrades unless I'd
vetted those upgrades manually on test machines that represented the
targets involved. I even disabled automatic updates to things like
docker and kubernetes (which do their own updates outside of dnf/yum) so
they wouldn't break (and brother, were there ever been some MASSIVE
screwups there). Even with all those precautions, I was bitten. Hard.
Multiple times. Not fun. Not in the least.

Do what you wish, just be bloody careful about it. That's all I'm
saying.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Cuteness can be overcome through sufficient bastardry -
- --Mark 'Kamikaze' Hughes   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Louis Garcia]

I handle hundreds of workstations, I am not about to manually update
everyone. dnf-automatic the best choice right now.

On Wed, Sep 19, 2018 at 7:18 PM Rick Stevens  wrote:

> On 9/19/18 3:42 PM, Louis Garcia wrote:
> > How well does dnf-automatic work? I often rebuild workstations through
> > pxe and kickstart so a bad update is not an issue.
>
> As far as I know, dnf-automatic is a replacement for "dnf upgrade" that
> is more suitable for use in a script.
>
> 95% of the time "dnf --refresh -y upgrade" won't cause issues, but it's
> that 5% of the time where it DOES screw up that will drive you barking
> mad. Microsoft has had some absolutely horrific problems doing this
> "upgrade on shutdown" behind the scenes crud and THEY have utter control
> of ALL the software being upgraded during the process. That's not
> necessarily the case with any community-supported system with multiple
> repositories such as Fedora.
>
> I'm just saying that "here be dragons." Thou hast been warned and may
> proceed at thy own risk! :-)
>
> > On Wed, Sep 19, 2018 at 2:36 PM fred roller  > > wrote:
> >
> > I whole hardheartedly agree with Rick on this point.  That being
> > said, yes, put the script in the shutdown sequence.  Inject it
> > either first or where ever makes the most since. It has been awhile
> > since I messed with this but I think you need to research
> > manipulation of the rc.local directory files.  Hope it helps, just a
> > pointer for you to look into.
> >
> > regards,
> > -- Fred
> >
> > On Wed, Sep 19, 2018 at 10:39 AM Rick Stevens  > > wrote:
> >
> > On 9/19/18 10:24 AM, Louis Garcia wrote:
> > > Is there a way to have fedora workstation to update on
> > shutdown? When a
> > > user logs off or shutdown there box I would like fedora to
> > pkcon update
> > > -y or dnf upgrade -y. I thought about creating a systemd unit
> > file to do
> > > this but would that conflict with offline update?
> >
> > I'm sure you could do something like that, but I'm absolutely
> not in
> > favor of unsupervised updates. There are times where updates can
> > result
> > in an unbootable system or various other issues. Error messages
> > would
> > not be visible during the upgrade, conflicts with packages from
> > other
> > sources might be missed, many other things might end up with a
> > system
> > that, even if it works, might behave rather differently than the
> > system
> > you shut down before.
> >
> > You only have to look at the number of "bricked" Winblows system
> > upgrades that have occurred in the past using this scheme. No,
> > unsupervised or unobserved updates are a bad idea IMHO. I never
> > use "-y"
> > with dnf or pkcon or yum. I look at the proposed upgrades before
> > I ever
> > approve them--and there are MANY times I've rerun the command
> > with an
> > "--exclude=" so specific packages do NOT get upgraded.
> >
> > You might disagree with much he did, but as Reagan said, "Trust,
> but
> > verify!"
> >
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -If Windows isn't a virus, then it sure as hell is a carrier!-
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Rick Stevens]

On 9/19/18 3:42 PM, Louis Garcia wrote:
> How well does dnf-automatic work? I often rebuild workstations through
> pxe and kickstart so a bad update is not an issue.

As far as I know, dnf-automatic is a replacement for "dnf upgrade" that
is more suitable for use in a script.

95% of the time "dnf --refresh -y upgrade" won't cause issues, but it's
that 5% of the time where it DOES screw up that will drive you barking
mad. Microsoft has had some absolutely horrific problems doing this
"upgrade on shutdown" behind the scenes crud and THEY have utter control
of ALL the software being upgraded during the process. That's not
necessarily the case with any community-supported system with multiple
repositories such as Fedora.

I'm just saying that "here be dragons." Thou hast been warned and may
proceed at thy own risk! :-)

> On Wed, Sep 19, 2018 at 2:36 PM fred roller  > wrote:
> 
> I whole hardheartedly agree with Rick on this point.  That being
> said, yes, put the script in the shutdown sequence.  Inject it
> either first or where ever makes the most since. It has been awhile
> since I messed with this but I think you need to research
> manipulation of the rc.local directory files.  Hope it helps, just a
> pointer for you to look into.
> 
> regards,
> -- Fred
> 
> On Wed, Sep 19, 2018 at 10:39 AM Rick Stevens  > wrote:
> 
> On 9/19/18 10:24 AM, Louis Garcia wrote:
> > Is there a way to have fedora workstation to update on
> shutdown? When a
> > user logs off or shutdown there box I would like fedora to
> pkcon update
> > -y or dnf upgrade -y. I thought about creating a systemd unit
> file to do
> > this but would that conflict with offline update?
> 
> I'm sure you could do something like that, but I'm absolutely not in
> favor of unsupervised updates. There are times where updates can
> result
> in an unbootable system or various other issues. Error messages
> would
> not be visible during the upgrade, conflicts with packages from
> other
> sources might be missed, many other things might end up with a
> system
> that, even if it works, might behave rather differently than the
> system
> you shut down before.
> 
> You only have to look at the number of "bricked" Winblows system
> upgrades that have occurred in the past using this scheme. No,
> unsupervised or unobserved updates are a bad idea IMHO. I never
> use "-y"
> with dnf or pkcon or yum. I look at the proposed upgrades before
> I ever
> approve them--and there are MANY times I've rerun the command
> with an
> "--exclude=" so specific packages do NOT get upgraded.
> 
> You might disagree with much he did, but as Reagan said, "Trust, but
> verify!"
> 
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-If Windows isn't a virus, then it sure as hell is a carrier!-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Changing the LABEL of an iso9660 file system

[Rick Stevens]

On 9/19/18 2:46 PM, Samuel Sieb wrote:
> On 9/19/18 2:37 PM, Chris Murphy wrote:
>> On Wed, Sep 19, 2018, 12:37 PM Samuel Sieb > > wrote:
>>     Disks don't have labels, unless the whole disk is a filesystem
>> with no
>>     partition table, which was the case when you wrote the ISO to it. 
>> The
>>     partition table doesn't have a label.
>> GPT supports partition name (36 UTF-16LE code units).
>>
>> MBR lacks any naming.
> 
> Yes, *partition* name, not disk name.

Yup. The OP was talking about using e2label to change the label on an
ISO9660 filesystem, which it cannot do. e2label deals with _filesystem_
labels on ext2, ext3 and ext4 filesystems ONLY.

There is no filesystem label on ISO9660 images, but there IS an
optional "volume" label, which may be set when the ISO image is created.
There may even be a utility that lets you bugger the volume label on an
already-created ISO image file (but ISO images are supposed to be read-
only).

Most commonly used read/write filesystems support filesystem labels.
Ext2|3|4, XFS, BTRFS, NTFS, VFAT and a number of others all do. Some
support longer labels than others (ext2|3|4 allows up to 16 characters,
XFS only 12, etc.).

Raw disks don't have labels. MBR partition tables do not support
_partition_ labels. GPT partition tables DO support partition labels and
one should note that GPT _partition_ labels are separate from any
_filesystem_ labels applied to filesystems on those partitions. Here's
an example from a 1TB USB drive I use for backups:

[root@prophead ~]# parted /dev/sdb
GNU Parted 3.2
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: Seagate BUP Slim SL (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End SizeFile system  NameFlags
 1  1049kB  1000GB  1000GB  ext4 BackupDisk

(parted) quit
[root@prophead ~]# e2label /dev/sdb1
BackUps

The output from parted shows partition 1 as having the _partition_ label
"BackupDisk", but the output from e2label querying the ext4 filesystem
on that partition comes up with a _filesystem_ label of "BackUps",
showing that they are, indeed, separate entities.

Please excuse my being so bombastic here. Just trying to be thorough.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- If this is the first day of the rest of my life... -
-I'm in BIG trouble! -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Louis Garcia]

How well does dnf-automatic work? I often rebuild workstations through pxe
and kickstart so a bad update is not an issue.

On Wed, Sep 19, 2018 at 2:36 PM fred roller  wrote:

> I whole hardheartedly agree with Rick on this point.  That being said,
> yes, put the script in the shutdown sequence.  Inject it either first or
> where ever makes the most since. It has been awhile since I messed with
> this but I think you need to research manipulation of the rc.local
> directory files.  Hope it helps, just a pointer for you to look into.
>
> regards,
> -- Fred
>
> On Wed, Sep 19, 2018 at 10:39 AM Rick Stevens 
> wrote:
>
>> On 9/19/18 10:24 AM, Louis Garcia wrote:
>> > Is there a way to have fedora workstation to update on shutdown? When a
>> > user logs off or shutdown there box I would like fedora to pkcon update
>> > -y or dnf upgrade -y. I thought about creating a systemd unit file to do
>> > this but would that conflict with offline update?
>>
>> I'm sure you could do something like that, but I'm absolutely not in
>> favor of unsupervised updates. There are times where updates can result
>> in an unbootable system or various other issues. Error messages would
>> not be visible during the upgrade, conflicts with packages from other
>> sources might be missed, many other things might end up with a system
>> that, even if it works, might behave rather differently than the system
>> you shut down before.
>>
>> You only have to look at the number of "bricked" Winblows system
>> upgrades that have occurred in the past using this scheme. No,
>> unsupervised or unobserved updates are a bad idea IMHO. I never use "-y"
>> with dnf or pkcon or yum. I look at the proposed upgrades before I ever
>> approve them--and there are MANY times I've rerun the command with an
>> "--exclude=" so specific packages do NOT get upgraded.
>>
>> You might disagree with much he did, but as Reagan said, "Trust, but
>> verify!"
>> --
>> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
>> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
>> --
>> -  When all else fails, try reading the instructions.-
>> --
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Changing the LABEL of an iso9660 file system

[Samuel Sieb]

On 9/19/18 2:37 PM, Chris Murphy wrote:
On Wed, Sep 19, 2018, 12:37 PM Samuel Sieb > wrote:

Disks don't have labels, unless the whole disk is a filesystem with no
partition table, which was the case when you wrote the ISO to it.  The
partition table doesn't have a label. 


GPT supports partition name (36 UTF-16LE code units).

MBR lacks any naming.


Yes, *partition* name, not disk name.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Changing the LABEL of an iso9660 file system

[Chris Murphy]

On Wed, Sep 19, 2018, 12:37 PM Samuel Sieb  wrote:

> On 9/19/18 5:31 AM, Kevin Wilson wrote:
> > Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?
>
> Disks don't have labels, unless the whole disk is a filesystem with no
> partition table, which was the case when you wrote the ISO to it.  The
> partition table doesn't have a label.


GPT supports partition name (36 UTF-16LE code units).

MBR lacks any naming.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Changing the LABEL of an iso9660 file system

[Samuel Sieb]

On 9/19/18 5:31 AM, Kevin Wilson wrote:

Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?


Disks don't have labels, unless the whole disk is a filesystem with no 
partition table, which was the case when you wrote the ISO to it.  The 
partition table doesn't have a label.  You're only seeing the existing 
label because you're using the wrong tool and it's finding that info in 
the unused areas.  As Tim said, if you really want to clear it (which is 
unnecessary), you could write zeros to the first part of the disk and 
then repartition.  You will of course lose any existing data on the disk.

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

Re: Forcing updates install on shutdown

[fred roller]

I whole hardheartedly agree with Rick on this point.  That being said, yes,
put the script in the shutdown sequence.  Inject it either first or where
ever makes the most since. It has been awhile since I messed with this but
I think you need to research manipulation of the rc.local directory files.
Hope it helps, just a pointer for you to look into.

regards,
-- Fred

On Wed, Sep 19, 2018 at 10:39 AM Rick Stevens  wrote:

> On 9/19/18 10:24 AM, Louis Garcia wrote:
> > Is there a way to have fedora workstation to update on shutdown? When a
> > user logs off or shutdown there box I would like fedora to pkcon update
> > -y or dnf upgrade -y. I thought about creating a systemd unit file to do
> > this but would that conflict with offline update?
>
> I'm sure you could do something like that, but I'm absolutely not in
> favor of unsupervised updates. There are times where updates can result
> in an unbootable system or various other issues. Error messages would
> not be visible during the upgrade, conflicts with packages from other
> sources might be missed, many other things might end up with a system
> that, even if it works, might behave rather differently than the system
> you shut down before.
>
> You only have to look at the number of "bricked" Winblows system
> upgrades that have occurred in the past using this scheme. No,
> unsupervised or unobserved updates are a bad idea IMHO. I never use "-y"
> with dnf or pkcon or yum. I look at the proposed upgrades before I ever
> approve them--and there are MANY times I've rerun the command with an
> "--exclude=" so specific packages do NOT get upgraded.
>
> You might disagree with much he did, but as Reagan said, "Trust, but
> verify!"
> --
> - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
> - AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
> --
> -  When all else fails, try reading the instructions.-
> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Forcing updates install on shutdown

[Rick Stevens]

On 9/19/18 10:24 AM, Louis Garcia wrote:
> Is there a way to have fedora workstation to update on shutdown? When a
> user logs off or shutdown there box I would like fedora to pkcon update
> -y or dnf upgrade -y. I thought about creating a systemd unit file to do
> this but would that conflict with offline update?

I'm sure you could do something like that, but I'm absolutely not in
favor of unsupervised updates. There are times where updates can result
in an unbootable system or various other issues. Error messages would
not be visible during the upgrade, conflicts with packages from other
sources might be missed, many other things might end up with a system
that, even if it works, might behave rather differently than the system
you shut down before.

You only have to look at the number of "bricked" Winblows system
upgrades that have occurred in the past using this scheme. No,
unsupervised or unobserved updates are a bad idea IMHO. I never use "-y"
with dnf or pkcon or yum. I look at the proposed upgrades before I ever
approve them--and there are MANY times I've rerun the command with an
"--exclude=" so specific packages do NOT get upgraded.

You might disagree with much he did, but as Reagan said, "Trust, but
verify!"
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  When all else fails, try reading the instructions.-
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Forcing updates install on shutdown

[Louis Garcia]

Is there a way to have fedora workstation to update on shutdown? When a
user logs off or shutdown there box I would like fedora to pkcon update -y
or dnf upgrade -y. I thought about creating a systemd unit file to do this
but would that conflict with offline update?

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

Re: Changing the LABEL of an iso9660 file system

[Rick Stevens]

On 9/19/18 9:27 AM, Rick Stevens wrote:
> On 9/19/18 5:31 AM, Kevin Wilson wrote:
>> Hello,
>> I have a USB stick on which I had in the past an Ubunutu installatilon.
>> When I run "e2label /dev/sdb" I get:
>>
>> e2label /dev/sdb
>> e2label: Bad magic number in super-block while trying to open /dev/sdb
>> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'
>>
>> Now, I did not need this installation anymore, so I created a single
>> Linux partition on the USB stick (/dev/sdb1)
>> with fdisk, and labeled it as sandiskUSB.
>> When I run:
>> e2label /dev/sdb1
>> I get
>> sandiskUSB
>>
>> Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?
>>
>> Tying
>> e2label /dev/sdb sandiskUSB
>> does not work, it gives:
>> e2label: Bad magic number in super-block while trying to open /dev/sdb
>> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'
> 
> You can only use e2label on ext2/3/4 filesystems, not on entire block
> devices. Had you formatted /dev/sdb ENTIRELY as an ext2/3/4 filesystem,
> you could label it. This is born out by you creating a filesystem
> partition via fdisk and being able to label that partition.

I should also say that, since the subject is "...label of an iso9660
file system", the label for an ISO9660 filesystem is actually a volume
label, set during image creation via the "-V " option of the
xorrisofs command.

Again, "e2label" inserts a label into the partition table and superblock
for ext2|3|4 filesystems, not on the host block device that holds them.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-  Always remember you're unique, just like everyone else.   -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Changing the LABEL of an iso9660 file system

[Tim Seifert via users]

On Wed, 2018-09-19 at 15:31 +0300, Kevin Wilson wrote:
> Is there a way to change also the lablel of /dev/sdb to be sandiskUSB
> ?

Sometimes using a series of different tools to prepare drives leaves
you with things you can't change.

You could try writing zeros to the beginning of the drive (several
blocks worth) to blank things out, then repartition and reformat.

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

Re: Changing the LABEL of an iso9660 file system

[Rick Stevens]

On 9/19/18 5:31 AM, Kevin Wilson wrote:
> Hello,
> I have a USB stick on which I had in the past an Ubunutu installatilon.
> When I run "e2label /dev/sdb" I get:
> 
> e2label /dev/sdb
> e2label: Bad magic number in super-block while trying to open /dev/sdb
> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'
> 
> Now, I did not need this installation anymore, so I created a single
> Linux partition on the USB stick (/dev/sdb1)
> with fdisk, and labeled it as sandiskUSB.
> When I run:
> e2label /dev/sdb1
> I get
> sandiskUSB
> 
> Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?
> 
> Tying
> e2label /dev/sdb sandiskUSB
> does not work, it gives:
> e2label: Bad magic number in super-block while trying to open /dev/sdb
> /dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'

You can only use e2label on ext2/3/4 filesystems, not on entire block
devices. Had you formatted /dev/sdb ENTIRELY as an ext2/3/4 filesystem,
you could label it. This is born out by you creating a filesystem
partition via fdisk and being able to label that partition.
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- If Bill Gates got a dime for every time Windows crashes... -
-  ...oh, wait.  He does.  THAT explains it! -
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Changing the LABEL of an iso9660 file system

[Kevin Wilson]

Hello,
I have a USB stick on which I had in the past an Ubunutu installatilon.
When I run "e2label /dev/sdb" I get:

e2label /dev/sdb
e2label: Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'

Now, I did not need this installation anymore, so I created a single
Linux partition on the USB stick (/dev/sdb1)
with fdisk, and labeled it as sandiskUSB.
When I run:
e2label /dev/sdb1
I get
sandiskUSB

Is there a way to change also the lablel of /dev/sdb to be sandiskUSB ?

Tying
e2label /dev/sdb sandiskUSB
does not work, it gives:
e2label: Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb contains a iso9660 file system labelled 'Ubuntu-Server 17.04 amd64'

Regards,
Kevin
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: resize

[Chris Murphy]

On Tue, Sep 18, 2018, 8:09 AM Patrick Dupre  wrote:

> Hello,
>
> Did I made a mistake?
> This what did:
>
> umount -l /home
>


There is no need to umount when growing ext4. Only for shrinking must it be
unmounted.

XFS can only be grown,.no shrink. And growing can only be done while
mounted.

Btrfs grows and shrinks, only while mounted.


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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: [f28] Unable to print from Fedora 28

[Neal Becker]

Marco Guazzone wrote:

> On Mon, Sep 17, 2018 at 12:32 PM Marco Guazzone 
> wrote:
> 
>>
>>
>> On Mon, Sep 17, 2018 at 11:05 AM Marco Guazzone
>>  wrote:
>>
>>> Hello,
>>>
>>> Today I am having trouble in printing from Fedora. I have tried two
>>> different network printers without success.
>>>
>>> Specifically, if I print a test page (in XFCE, open the "Print Settings"
>>> application and click on the "Print Test Page"), cups says that the page
>>> has been printed successfully:
>>>
>>> Sep 17 10:27:33 wildcat cupsd[799]: UPO-KyoceraKM3035-LotB sguazt 172
>>> [17/Sep/2018:10:27:33 +0200] 1 1 - localhost Test Page - -
>>> Sep 17 10:27:34 wildcat cupsd[799]: REQUEST localhost - - "POST /
>>> HTTP/1.1" 200 364 Create-Printer-Subscriptions successful-ok
>>>
>>> But the printer does not receive any data.
>>>
>>> My system is an up-to-date Fedora 28 x86_64 (kernel:
>>> 4.18.7-200.fc28.x86_64).
>>> Last time I have successfully printed to these printers from Fedora was
>>> Sep 12, 2018.
>>> The printers work without problems under Windows 7.
>>>
>>> Any idea?
>>>
>>> Thank you in advance for your help.
>>>
>>> Cheers,
>>>
>>> Marco
>>>
>>
>>
>> For you interest, a downgrade of cups from ver. 2.2.6-22 to ver. 2.2.6-14
>> does not solve the problem.
>>
>> Marco
>>
> 
> 
> Solved!
> After downgrading ghostscript from from 9.24-1 to 9.23-1, I am able to
> print again.
> See: https://bugzilla.redhat.com/show_bug.cgi?id=1629086
> 
> Best,
> 
> Marco
I recently posted here about what sounds like the same issue.  I used 
lpadmin to switch from gs to cairo backend, IIRC, which sounds like a 
longterm win anyway to me.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: One webcam, two /dev/video

[François Patte]

Le 19/09/2018 à 01:28, Joe Zeff a écrit :
> On 09/18/2018 09:35 AM, François Patte wrote:
>> Bonjour,
>>
>> On my desktop, when I plug an usb webcam, two /dev/video (0 and 1) are
>> created. Only one displays video though.
>>
>> Why?
> 
> I don't know, but I just checked and I have the same thing.  As long as
> your webcam works, it's probably nothing to worry about.

I am not worrying about, I just want to understand... And.. some
stupidly built applications like skype are unable to choose the right
device and chooses the one which does not work!

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org