Hi,
Would it be possible to make [dnf update] output something immediately after being run? And what would be the right course of action to get this feature implemented? I know it's probably a miniscule thing, but it's one of those small details you notice when shifting over from an apt-based distro. When running [apt update] or [apt upgrade] it responds instantly.
I usually run it like [sudo dnf update] and when you mistype your password it gives you a wait period, but so does [dnf update]. So in a brief moment you're left hanging not knowing whether the password was incorrect or if [dnf] is simply updating. I know changing [sudo] to not give a wait period would be a lesser crime to some, so therefore I'm wondering if we can change [dnf] instead.
If I'm addressing the wrong list, please advise. Also I'm not very good at C languages so I can't just provide a patch unfortunately.
-- Ds
On 08/22/2017 01:28 PM, Daniel Ståhl wrote:
Would it be possible to make [dnf update] output something immediately after being run? And what would be the right course of action to get this feature implemented? I know it’s probably a miniscule thing, but it’s one of those small details you notice when shifting over from an apt-based distro. When running [apt update] or [apt upgrade] it responds instantly.
I usually run it like [sudo dnf update] and when you mistype your password it gives you a wait period, but so does [dnf update]. So in a brief moment you’re left hanging not knowing whether the password was incorrect or if [dnf] is simply updating. I know changing [sudo] to not give a wait period would be a lesser crime to some, so therefore I’m wondering if we can change [dnf] instead.
If I’m addressing the wrong list, please advise. Also I’m not very good at C languages so I can’t just provide a patch unfortunately.
It seems the period of time, at least on my system, between entering a bad password for sudo and getting a "Sorry, try again." prompt is between 1 and 2 seconds. Probably closer to 1. Is this too long?
Anyway, if you think this is a feature everyone would benefit from then you should use bugzilla to submit an RFE (Request For Enhancement) against dnf.
It seems the period of time, at least on my system, between entering a bad password for sudo and getting a "Sorry, try again." prompt is between 1 and 2 seconds. Probably closer to 1. Is this too long?
For me personally, yes. I can't speak for anyone else.
Anyway, if you think this is a feature everyone would benefit from then you should use bugzilla to submit an RFE (Request For Enhancement) against dnf.
Will do, thanks!
-- Ds
On 08/21/2017 11:35 PM, Daniel Ståhl wrote:
It seems the period of time, at least on my system, between entering a bad password for sudo and getting a "Sorry, try again." prompt is between 1 and 2 seconds. Probably closer to 1. Is this too long?
For me personally, yes. I can't speak for anyone else.
Anyway, if you think this is a feature everyone would benefit from then you should use bugzilla to submit an RFE (Request For Enhancement) against dnf.
Will do, thanks!
In the interim, try "dnf -v" to get debug messages. You immediately get stuff like:
cachedir: /var/cache/dnf Loaded plugins: protected_packages, copr, download, generate_completion_cache, playground, reposync, config-manager, builddep, noroot, needs-restarting, Query, system-upgrade, debuginfo-install DNF version: 1.1.10 ...
I agree a sign-on would be nice. dnf is predominately Python, IIRC. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - First Law of Work: - - If you can't get it done in the first 24 hours, work nights. - ----------------------------------------------------------------------
On 08/22/17 01:28, Daniel Ståhl wrote:
Hi,
Would it be possible to make [dnf update] output something immediately after being run? And what would be the right course of action to get this feature implemented? I know it’s probably a miniscule thing, but it’s one of those small details you notice when shifting over from an apt-based distro. When running [apt update] or [apt upgrade] it responds instantly.
I usually run it like [sudo dnf update] and when you mistype your password it gives you a wait period, but so does [dnf update]. So in a brief moment you’re left hanging not knowing whether the password was incorrect or if [dnf] is simply updating. I know changing [sudo] to not give a wait period would be a lesser crime to some, so therefore I’m wondering if we can change [dnf] instead.
You can always wrap it with a shell script which prints something, then invokes the real dnf....
If I’m addressing the wrong list, please advise. Also I’m not very good at C languages so I can’t just provide a patch unfortunately.
--
Ds
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Från: Kevin Cummings [mailto:cummings@kjchome.homeip.net] You can always wrap it with a shell script which prints something, then invokes the real dnf....
Yeah, but that wouldn't be permanent. And I've already registered a ticket, but thanks for the advise.
-- ds
On 08/22/2017 10:16 PM, Daniel Ståhl wrote:
Från: Kevin Cummings [mailto:cummings@kjchome.homeip.net] You can always wrap it with a shell script which prints something, then invokes the real dnf....
Yeah, but that wouldn't be permanent. And I've already registered a ticket, but thanks for the advise.
It would be permanent if you do it properly. That'd be either putting a wrapper named "dnf" in a directory that appears earlier than /usr/bin in the user's PATH variable (/usr/local/bin is suitable on my system), or by putting a wrapper anywhere that's not called "dnf" and using sudo to call that wrapper by its name. Either way:
#!/bin/sh echo "Running dnf" exec dnf "$@"
-
Daniel Ståhl -
Ed Greshko -
Gordon Messmer -
Kevin Cummings -
Rick Stevens