On 6/3/19 1:16 PM, Chris Murphy wrote:
On Mon, Jun 3, 2019 at 11:07 AM Adam Williamson
wrote:
Some people don't see any problem with this, personally it drives me
crazy and I wish it were policy that *every* retired package must be
obsoleted. But it isn't.
Not obsoleting retired packages is
On 5/20/19 12:19 PM, Kevin Fenzi wrote:
On 5/20/19 9:09 AM, Przemek Klosowski wrote:
On 5/17/19 4:34 PM, Kevin Fenzi wrote:
So, this is basically the old cloud-init makes a user that can sudo to
root thing. Can anyone explain in small words how this is more secure?
In a large system, it
On 8/20/19 11:15 PM, John Harris wrote:
There is no significant fire risk from this. It's just not good for the
laptop. There's not exactly a temperature range that can cause damage, but
there is a nominal range for each individual chip, and a nominal range for the
entire system based on that.
On 8/20/19 10:32 AM, John Harris wrote:
On Monday, August 19, 2019 2:56:58 PM MST Przemek Klosowski wrote:
the right thing to do is to suspend on inactivity in all cases.
I don't think it's fair for one person to decide what the "right thing to do"
is. This kind of thinking is what leads to
On 8/27/19 8:36 PM, Gerald B. Cox wrote:
Regarding NNTP I've haven't used newsreaders in years and to be honest dealing
with yet another tool isn't something I would want to do
I forgot what email client you use, but all clients I ever used (Emacs
and Thunderbird) also do NNTP. After all,
On 9/10/19 7:55 AM, vvs vvs wrote:
Did I? I thought that I've said that I'm using x86_64 kernel right now and that
I have my memory stretched to the limits already.
But yes, I've experimented with x86_64 userland some time ago, I don't remember
exact numbers but I think that I've lost 100-200
On 9/11/19 2:18 AM, John M. Harris Jr. wrote:
Feel free to ignore any such wording that you disagree with. We don't need to
agree in order to discuss such things, and it's alright if we disagree on
wording. Literally every user I talk to has asked me either how to disable the
hot corner, or
On 7/31/19 4:34 PM, Kevin Fenzi wrote:
On 7/31/19 12:05 PM, Nicolas Mailhot via devel wrote:
And, just to provide another data point, we tried this month to make
the network install iso talk to https dnf repos (a reposync of fedora
devel x86_64, without x86 packages, because we don't have the
On 9/19/19 10:44 PM, Chris Adams wrote:
Once upon a time, Kevin Kofler said:
Randy Barlow wrote:
It is a disservice to our users to provide them with unmaintained
packages,
It is a disservice to our users to NOT provide them with unmaintained
packages. If, as a user, you NEED a package, you
On 11/5/19 7:18 PM, Kevin Kofler wrote:
"name mangling": Why is this a problem? First of all, it is not mangling, it
is suffixing. The original name is retained unchanged and nothing is
prepended to it, only appended. And, e.g., Qt 3, 4, and 5 are all different
packages, so why should they have
On 11/15/19 11:27 AM, Petr Pisar wrote:
No. Modularity solves this combination problem with "stream expansion".
Sources for such module exists only once, you submit them for building
with fedpkg only once, but a build systems computes all combinations
(this the stream expansion) and schedules a
On 12/4/19 5:25 AM, John M. Harris Jr wrote:
Network based decryption keys are possible, but I don't recommend it, because
there's no way to determine that the user booting up the system is actually
meant to have access to the data that's on it.
There are two distinct thread models :
-
On 12/3/19 1:57 AM, John M. Harris Jr wrote:
On Monday, December 2, 2019 12:46:30 PM MST Chris Murphy wrote:
It's almost 2020, and I shouldn't have to pick and choose between
remote access and securing user data at rest by default.
You don't have to. Data at rest would mean that your system is
On 12/6/19 7:19 PM, Kevin Kofler wrote:
Lennart Poettering wrote:
If you know where stuff is located you can change individual blocks in
files. You are not going to know what you are changing them to, but
you can change it and traditional files will not detect that you did that.
Then you get
On 12/6/19 10:02 PM, John M. Harris Jr wrote:
On Friday, December 6, 2019 5:14:24 PM MST Kevin Kofler wrote:
Marius Schwarz wrote:
"Figure out intersection with current work to use the TPM to allow
booting to GDM without entering the password."
Means, if someone steals the device, he can
On 12/12/19 6:56 AM, Marius Schwarz wrote:
On the other hand, as android is capable of FDE, they must have made
some importanted changes that can be of use here.
Right, because Android has full control of the entire boot process, so
they only need the user input at the end where all the
On 12/4/19 6:59 PM, John M. Harris Jr wrote:
On Wednesday, December 4, 2019 12:38:20 PM MST Przemek Klosowski via devel
wrote:
- stolen/lost laptop: I think this is the most important one for most
people; it is mitigaged by a trusted-network-based decryption, unless
the device
On 12/5/19 6:48 PM, John M. Harris Jr wrote:
c. Resource requirements are excessive, there's no dynamic allocation
so to be safe you need to allocate a minimum of 1x RAM for a swap
partition used for a hibernation image. As a consequence, there's now
an excessive amount of relatively slow swap
On 12/6/19 11:40 AM, John M. Harris Jr wrote:
Means, if someone steals the device, he can boot a system. Even if we
assume that the systemcode is safe and there is no way to interrupt the
bootprocess, we are now able to attack the login, which will be much
easier than the encryption key, which
On 12/10/19 1:04 PM, Kevin Kofler wrote:
Przemek Klosowski via devel wrote:
3) Multiple keys allow creating backup keys, preventing the data loss
scenario Kevin is worried about. Of course this assumes that the UX for
creating backup keys exists, and that people actually do that---but it's
On 10/18/19 8:09 AM, J. Scheurich wrote:
gmemusage is a tool to show memory usage per userspace application.
top can show low memory state.
I remember gmemusage from the SGI days and remember using it on Linux
too, but currently
yum whatprovides */gmemusage
claims there are No Matches
On 10/14/19 6:19 AM, Kevin Kofler wrote:
mcatanz...@gnome.org wrote:
John, the third-party software policy was approved after a long and
contentious debate:
On 10/16/19 7:36 PM, Kevin Kofler wrote:
It was never designed to solve parallel installability problem.
… which is exactly why it causes version hell.
Could you expand on that? Since a modular system currently prevents
parallel version installation, it may provide suboptimal/obsolete
On 10/17/19 12:27 PM, Stephen John Smoogen wrote:
people are going to add things into their modules to make whatever
software they need. If I find that I need libfoo2-2.34 in libreoffice
and you need libfoo2-2.40 in evolution.. then only one of the two
modules can be installed.You can either
On 10/15/19 9:26 PM, Stephen Gallagher wrote:
Module stream metadata would gain two new optional attributes,
"upgrades:" and "obsoletes:".
If the "upgrades: " field exists in the metadata, libdnf
should switch to this stream if the following conditions are met:
1) Changing the stream would not
On 11/27/19 2:59 AM, Zbigniew Jędrzejewski-Szmek wrote:
On Tue, Nov 26, 2019 at 09:39:59AM -0700, Chris Murphy wrote:
Mabee systemd-homed is in
a position to solve this by having early enough authentication
capability by rescue.target time that any admin user can login?
Actually, it may.
On 12/1/19 10:37 PM, Kevin Kofler wrote:
I definitely want some mechanism which will tell to user that "THIS
PACKAGE IS NOT FULLY SUPPORTED."
And I think telling that to the user is absolutely unfair and against the
spirit of Fedora.
The dilemma is, how to allow the useful stuff to remain,
On 11/1/19 9:19 AM, Scott Talbert wrote:
On Fri, 1 Nov 2019, Miro Hrončok wrote:
For example, for tk, the commit says:
2014-05-21 Added noautobuild, tcl/tk-8.6 cannot be automatically
rebuild now
..
But the package was rebuilt couple times in the last 5 years actually.
I'm going to
On 10/7/19 4:34 PM, Matthew Miller wrote:
To me, most packages would benefit from having two streams: fast and slow.
That's the essential problem I want solved anyway. (Maybe with CentOS
Streams: fast, slow, very slow.)
The "slow" version would be updated on a careful cadence with big updates
On 10/8/19 3:30 PM, John M. Harris, Jr. wrote:
We could simply stop doing projects that throw wildly different
versions of software into a single installation, which causes this issue.
There's a word for this that I can't remember at the
moment---'producting'? I think it's related to the
On 10/8/19 6:04 AM, Ankur Sinha wrote:
Would anyone else have the cycles to review/update these pages in the
meantime please?
On 10/3/19 12:19 PM, Matthew Miller wrote:
On Thu, Oct 03, 2019 at 11:13:32AM -0500, Michael Cronenworth wrote:
Remote changelog URLs might become inaccessible over time, making tracking down
behavior changes & tricky bugs problematic.
Yes, there are systems that do not have Internet access.
On 3/5/20 2:08 PM, Daniel Mach wrote:
I hope that someday we'll get microdnf close to 100% feature parity
with DNF (Python plugins excluding obviously)
Great plan, but when it happens, could it also get a simple IPC to talk
to the optional Python plugins, and thus replace dnf entirely? What is
On 1/26/20 5:33 PM, Bill Chatfield via devel wrote:
When I type "sudo dnf install something" it takes about 10 minutes to pull
updates from every repository, every time I run dnf. The actual install or update
proceeds at a reasonable pace. I wouldn't call it fast. I could send you a video of
On 1/29/20 10:09 PM, Huzaifa Sidhpurwala wrote:
Do we want to continue the same condition as described here:
On 1/7/20 11:14 AM, Iñaki Ucar wrote:
I'm far from having a satisfactory response to that, but I see two
fronts here. First, marketing. How does Ubuntu managed to be so
popular among less-experienced Linux users? I'm not sure, but I
suspect that good marketing has something to do with it.
I
On 1/15/20 12:56 PM, Chris wrote:
That's an amazing amount of work! My only criticism would be:
- the quest for reducing disk space is getting a bit over the top. I
mean to make comparisons to 3.5" floppy disks which haven't been
around for 20 years? Why is ~100MB so much? If you scale up
On 1/10/20 8:14 PM, Michael Catanzaro wrote:
On Fri, Jan 10, 2020 at 9:46 pm, Richard W.M. Jones
wrote:
OpenSUSE proved years and years ago that dropping %changelog is
possible, easy and desirable. We should do that IMHO.
They still have %changelog at the bottom of each spec file, but as
On 1/13/20 2:47 PM, Neal Gompa wrote:
changelogs often include CVE information, especially useful when the
fixes are backported rather than included as part of the regular
update/release process.
How could the CVE info be available in the absence of changelogs?
In Fedora, this information
On 3/21/20 8:45 AM, Andreas Tunek wrote:
I sidegraded my rawhide install to F32 a couple of weeks ago and from
the start I noticed that booting F32 was really slow. I assumed this
was some kind of bug or some devel stuff and would get solved.
What did you upgrade from? There were Radeon
On 3/31/20 1:40 PM, Bruno Wolff III wrote:
On Tue, Mar 31, 2020 at 13:08:05 -0400,
Matthew Miller wrote:
We did communicate as the very top line of our gathered requirements
that
open source is essential to our community and central to our
feedback. I'm
not trying to be soft on that.
On 5/18/20 3:36 PM, Ben Cotton wrote:
Arm Pointer Authentication (PAC) is a method of hardening code from
Return Oriented Programming (ROP) attacks. It uses a tag in a pointer
to sign and verify pointers. Branch Target Identification (BTI) is
another code hardening method, where the branch/jump
On 5/21/20 11:36 AM, Przemo Firszt wrote:
"FreeCAD -t 0" performs approx 470 tests. No GUI required. Example
output starts here:
That is not the case for me (freecad-0.18.4-5.fc31.x86_64):
...
test60 (PathTests.TestPathLog.TestPathLog)
Verify track handles no argument. ...
On 10/2/20 3:50 AM, Miroslav Suchý wrote:
Do you want to make Fedora 33 better? Please spend 1 minute of your time and
try to run:
sudo dnf --releasever=33 --setopt=module_platform_id=platform:f33 \
--enablerepo=updates-testing --enablerepo=updates-testing-modular \
distro-sync
On 5/23/20 12:18 AM, Nico Kadel-Garcia wrote:
Would the time be better spent enhancing SELinux?
ThatSELinux already labels everything in /bin and /usr/libexec as
system_u:object_r:bin_t:s0
so maybe it could be leveraged to cover everything you are considering?
Is there something
On 5/22/20 8:48 PM, Parker Gibson wrote:
The issue I see is that no package management system I know of handles multiple
so versions, they explicitly state packages conflict with each-other even if in
principle the so versioning means they would not.
The example I gave is from my own system.
On 5/22/20 1:24 PM, Nico Kadel-Garcia wrote:
On Fri, May 22, 2020 at 10:31 AM Steve Grubb wrote:
I am working on our application whitelisting daemon.
Interesting concept---could you please elaborate on your design? It
sounds useful but also challenging, as Nico points out.
On what level
On 5/22/20 6:23 PM, Paul Dufresne via devel wrote:
So let's take an example:
At first you have:
/pkgs/programA_version1 that have a LD_LIBRARY_PATH that contains
/pkgs/libX_version1
/pkgs/libX_version1 contains libX, version 1.
Now you "upgrade" libX vesion 2... because each packages is in
On 7/15/20 1:11 PM, Chris Murphy wrote:
Hi,
While bad RAM is uncommon, it comes up with some regularity to cause
folks a lot of grief. I'm wondering if there's a way to make it easier
to get bad news :-\ In particular there are cases where RAM defects
just don't show up with a few hours of
On 8/12/20 2:27 PM, Sergio Belkin wrote:
Hi!
I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based
swap partition.
I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian
with 4GB of RAM), and EarlyOOM killed Zoom in the middle of a call :(
This is weird---your
On 8/13/20 2:04 PM, Wells, Roger K. via devel wrote:
After some time, usually hours, the following four tasks in top are
running at 100%:
sadc
kworker/6:1+events_freezable
dmesg
systemd-journal
So sadc is not part of current Fedora. It may be some artifact from
older Fedoras (e.g.
On 8/13/20 4:12 PM, Wells, Roger K. via devel wrote:
I'll do something to disable it.
Oh, just thougth I'd mention---what I'd do would be
locate sadc <- hopefully this would return the location of the sadc
binary, perhaps /var/lib64/sa/sadc
rpm -qf /var/lib64/sa/sadc <- this will
On 8/13/20 4:12 PM, Wells, Roger K. via devel wrote:
So sadc is not part of current Fedora. It may be some artifact from
older Fedoras (e.g. sysstat-11.5.7-4.fc27.x86_64 has
/usr/lib64/sa/sadc) or some custom system activity data collection
software that is locally installed at your site.
On 7/8/20 12:15 PM, John M. Harris Jr wrote:
I'd rather crash and restart where I left off than have
the computer drag me along trying to save my application.
Sorry, what? Why would your data not be on your system? What about "the modern
way of computing" would move your data from your system
On 7/6/20 6:49 PM, John M. Harris Jr wrote:
Unless you're actively using all of those tabs (I don't know how you would be,
but it's certainly possible), swap sounds like the perfect solution. Unless
Firefox keeps JS running in there, and it's updating the DOM, these would
likely be able to get
On 7/4/20 8:18 PM, John M. Harris Jr wrote:
I've never managed to get one of my own Fedora machines to the point of
OOMing, and, when I have seen others do it, it's a problem that would have
been solved by having more swap space.
I am a tab hoarder so I used to wedge the browser due to memory
On 7/2/20 4:38 PM, Eric Sandeen wrote:
Running 10 loops on each of btrfs, ext4, and xfs I got results that look
like this (ext4 always creates empty lost+found so it will always find at
least 1 file there)
btrfs
...
== 4 fsck failures, 2 mount failures
ext4
...
== 0 fsck failures, 0 mount
On 7/10/20 5:06 AM, Nicolas Mailhot wrote:
The problem IOT side is not the security of the
software update chain. The problem is that manufacturers skimp on
software updates in the first place
Yes, that's the situation right now: everyone has a custom firmware tied
to a short product
On 7/10/20 7:37 AM, Nicolas Mailhot wrote:
Le vendredi 10 juillet 2020 à 07:12 -0400, Przemek Klosowski via devel
a écrit :
My point is that however the updates are being produced, they need a
secure remote update method. It's not realistic to expect end users
to be in the loop
If you remove
On 7/9/20 2:24 PM, Eric Sandeen wrote:
<50 runs later on btrfs>
16 readonly mounts failed (32% failure rate)
Within the successful mounts, 1 or more files were unreachable in 30 attempts.
Across all 50 attempts, 7720 files were lost.
Is that better than ext4, and will ext4 need fsck just to be
On 7/10/20 8:25 AM, Nicolas Mailhot wrote:
Le vendredi 10 juillet 2020 à 08:00 -0400, Przemek Klosowski a écrit :
Not quite---as I said in next sentence that you didn't include in
your quote, secure boot also tries to prevent unauthorized
modifications,
That does not work either, because if
On 7/10/20 5:22 PM, John M. Harris Jr wrote:
Android, actually, is trying to get it right by a) being a platform so
that common security updates are available from the platform owner, and
can be applied to everyone's system and b) having a secure remote update
method.
The problem with
On 7/9/20 8:44 AM, Kevin Kofler wrote:
Przemek Klosowski via devel wrote:
* disk access is literally O(1) slower than RAM access
This notation is meaningless. By the definition of the O notation,
O(1)=O(1)=O(k) for any constant k.
Yes, you are right of course, but I just hope
On 7/1/20 3:50 PM, Josef Bacik wrote:
This sounds like a "wtf, why are you doing this btrfs?" sort of thing,
but this is just the reality of using checksums. It's a checksum, not
ECC.
Yes, exactly---why isn't it ECC? Wouldn't it work better, especially in
the context of faulty hardware?
On 7/9/20 10:46 AM, John M. Harris Jr wrote:
"Secure Boot" doesn't make root non-uid 0, and can't keep root from
controlling system devices, even uploading unsigned firmware to peripherals.
While it's true that a completely secure software chain doesn't really
exist yet, we are slowly going
On 6/24/20 8:56 AM, Petr Pisar wrote:
On Wed, Jun 24, 2020 at 08:14:39AM -0400, Stephen Gallagher wrote:
On Wed, Jun 24, 2020 at 3:38 AM Petr Pisar wrote:
On Wed, Jun 24, 2020 at 06:51:36AM +, Zbigniew Jędrzejewski-Szmek wrote:
Yes. Putting the "stream identification" into the package
On 6/24/20 5:51 AM, Vitaly Zaitsev via devel wrote:
On 24.06.2020 04:40, Przemek Klosowski via devel wrote:
Nice, thanks for finding this --- but it also lists all the
debugsource/debuginfo packages
This is intended, because debug repositories are disabled by default and
these packages does
I noticed that kmod-wireguard is being updated on F31, even after WireGuard became
a part of Linux kernel since 5.6.0. Shouldn't kernel>5.6.0 obsolete
kmod-wireguard? Is it kept and updated because it was originally installed via
@commandline?
We had a discussion about not removing any
On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
I noticed that kmod-wireguard is being updated on F31, even after
WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because
it was originally installed
On 6/24/20 4:35 PM, Laura Abbott wrote:
On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
I noticed that kmod-wireguard is being updated on F31, even after
WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated beca
On 6/24/20 6:03 PM, Joe Doss wrote:
On 6/24/20 4:28 PM, Przemek Klosowski via devel wrote:
It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and Ian).
This leaves the question: Shouldn't kernel>5.6.0 obsolete
kmod-wireguard and akmod-wireguard? and maybe replace wiregu
On 6/26/20 1:43 PM, Neal Gompa wrote:
One issue that I have
seen mentioned as an issue within the last week is still the problem of
running out of space when it still looks like there's space free. I
didn't read the responses, so not sure of the resolution, but I remember
that being a "thing"
On 6/26/20 10:33 AM, Neil Horman wrote:
If I google how to quit vi, I see a full 10 pages of the answer to the question
documented in detail
The fact that people have to google their way out of such a mundane
circumstance is in my opinion enough to give this proposal a:
+1
As background, I
On 6/26/20 12:31 PM, Chris Murphy wrote:
That pattern will change with btrfs. There will be fewer of some problems,
more of others, and the messages will be different. fsck.ext4 is
pretty much all we have, all we're used to, and it's a binary
pass/fail. Even though we're talking about edge cases
On 6/27/20 11:40 PM, Tom Seewald wrote:
On Sat, Jun 27, 2020 at 7:32 PM Garry T. Williams
Is this hopefully seen by upstream as a bug that will be fixed? This removes
the system availability benefits of raid, and I've never heard of another
system that would behave like this, whether that's
On 6/29/20 12:38 PM, Przemek Klosowski via devel wrote:
On 6/27/20 11:40 PM, Tom Seewald wrote:
On Sat, Jun 27, 2020 at 7:32 PM Garry T. Williams
Just a PSA: btrfs raid1 does not have a concept of automatic degraded
mount in the face of a device failure. By default systemd will not
even
On 6/29/20 7:59 AM, David Kaufmann wrote:
Unfortunately I think this arguing is moot, as the issue seems to have
been decided already anyway. I only remember one change "proposal" to
actually being pulled back in the last year, and I'm really disappointed
about having fake discussions on devel@
On 6/15/20 9:46 PM, Kevin Fenzi wrote:
On Mon, Jun 15, 2020 at 09:05:42PM -0400, Neal Gompa wrote:
So I'm confused here, does anyone know why the animated wallpapers
don't work in KDE Plasma or any other desktop? I personally love
animated wallpapers and I'd like to see this on my KDE Plasma
On 6/27/20 12:50 PM, John M. Harris Jr wrote:
As an alternative, I would like to recommend we make Emacs the default. Emacs
does not require "specialist knowledge", but is much more powerful once you do
learn how to use it properly. It's also not as hard to use as nano.
I used emacs for 30+
On 6/23/20 5:35 AM, Vitaly Zaitsev via devel wrote:
On 23.06.2020 10:39, Miroslav Suchý wrote:
A tool which will give user a list of packages that can/should be removed.
dnf -C list extras
Nice, thanks for finding this --- but it also lists all the
debugsource/debuginfo packages, and for
On 6/4/20 1:36 AM, John M. Harris Jr wrote:
On Wednesday, June 3, 2020 9:05:22 PM MST Chris Murphy wrote:
UEFI Secure Boot doesn't prevent you from gaining access to firmware
setup. It can cause some options in firmware setup to become
unavailable, e.g. compatibility support modules for
On 8/14/20 8:33 AM, Wells, Roger K. via devel wrote:
That was not the cause.
Now when it happens I have only three tasks running at 100% (same ones
as reported earlier).
Everything else, kerneloops, shutdown via power switch, etc, is as before.
Could you repost to the list with more info? I
On 8/14/20 7:33 AM, John M. Harris Jr wrote:
On Wednesday, August 12, 2020 1:16:34 PM MST Przemek Klosowski via devel
wrote:
This is weird---your swap was 100% full, and ram almost full, and yet
killing 4GB VirtualBox didn't seem to free up memory. I suspect some
sort of measurement
On 12/17/20 10:04 AM, Marius Schwarz wrote:
Am 17.12.20 um 14:35 schrieb Stephen John Smoogen:
Right, but it's not automatic, and requires an existing known-good
system, which is the actual 'root of trust' here. This cannot be
assumed about a flash drive, which is why the automatic image
On 12/16/20 2:23 PM, Kevin Fenzi wrote:
Yeah, there has to be an anchor for your trust. Right now that is "I
trust the certificate authority that issued fedoraproject.org's cert".
I was trying to make a point that we don't have a way to check the
initial image: it could be altered to falsely
On 12/11/20 1:07 PM, Matthew Miller wrote:
Right now, when you start Fedora live media to install Workstation or KDE or
etc., you get an ugly text prompt which defaults to doing a media test
...
the most likely failure modes are like this:
1) Doesn't even write properly.
2) Doesn't boot
On 12/16/20 5:38 PM, Kevin Fenzi wrote:
On Wed, Dec 16, 2020 at 04:28:49PM -0500, przemek klosowski via devel wrote:
I was trying to make a point that we don't have a way to check the initial
image: it could be altered to falsely claim to be signed by fedoraproject.
well, we do: https
On 11/17/20 4:24 AM, Lennart Poettering wrote:
dig @9.9.9.9 +nsid heise.de
FWIW, a neat way to look at differences like that is
watch -d dig @9.9.9.9 +nsid heise.de
I use it often for looking at hotplugs (watch -d lsusb) etc.
___
devel
On 12/29/20 5:20 PM, Michael Catanzaro wrote:
I don't think this GNOME bug is in any way related to the topic of
whether KDE should default to Wayland
So I am confused---I thought it is a problem in Wayland, perhaps in its
X11 emulation but still Wayland. Yes, the app is misbehaving,
On 12/29/20 11:26 PM, Samuel Sieb wrote:
More likely what you're really confused about is something that a lot
of people are not aware of. Wayland is a protocol, not a program. I
believe there's a library, but the final implementation is done in
each window manager. The X11 "emulation" is
On 12/28/20 3:51 PM, Gerald B. Cox wrote:
I really don't see we have much of a choice here. X11 is eventually going away
and Wayland is the path forward.
...
If you notice issues, please open bugs.
I have an open bz about reliable wayland crashes:
On 6/16/21 8:45 AM, Stephen John Smoogen wrote:
oh cool. this even works on CentOS and RHEL systems:
```
smooge@xanadu ~]$ podman run fedora:latest /lib64/ld-linux-x86-64.so.2
--help
...
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported,
On 6/16/21 12:09 PM, Florian Weimer wrote
I'm missing something---I get identicaloutput on my v3 Core i7-4810MQ
Why do you expect different output?
Stephen was showing off his 'oldest' system and I assumed that it was
some Penryn-era relic, so I expected a <= v1 result. One cohort of
On 6/17/21 4:44 AM, Vitaly Zaitsev via devel wrote:
On 16.06.2021 22:22, Matthew Miller wrote:
Well, that's certainly A Position. I don't think it's anything nearly so
absolute, though, and depends on what, who, how, why, and a host of
other
things. And "it can help us answer questions like
On 6/16/21 6:26 PM, Kevin Kofler via devel wrote:
Otto Urpelainen wrote:
Also, if the intent is to get rid of the package completely, should not
adding it to fedora-obsolete-packages be required as well?
Why? Adding working packages to fedora-obsolete-packages forces removing
them from users'
On 5/7/21 12:08 PM, Adam Williamson wrote:
Really? I mean, third party repos have been around forever. It's not
like they're a new thing. I'm not really opposing any sensible
improvements here, I'm just not seeing the same clear story as you are
here? Why do you think there are going to be a
On 5/5/21 2:29 AM, Adam Williamson wrote:
If a third party wants to do
something nefarious and can convince you to "install a repository" in
some way, that means that at minimum they convinced you to drop an
arbitrary file in /etc/yum.repos.d . What they probably did was
convince you to
On 5/15/21 11:53 AM, Ralf Corsepius wrote:
Creating a non-root user account, possibly with admin rights (all
possible from within Anaconda) would seem like a safer option for
accasional/emergency password based access to such machines over SSH.
I don't see, how this would any safer than
There are so many moving pieces here that it's hard to get a handle on
this. I had trouble seeing local network printers so I tried following
the advice Zdenek published [1], but I ran into a nest of issues:
printing depending on avahi, which fails quietly and is hard to debug.
Specifically,
On 5/25/21 5:04 PM, Peter Boy wrote:
So the same model works totally fine for both desktop and server.
I myself lack the exact technical knowledge, but (all?) server and file system
experts I hear consider just that a gross misconception.
I think you and Neal talk about two different
1 - 100 of 147 matches
Mail list logo
