Fora vs. mailing lists
by Thomas Cameron
<Insert obligatory "old man shouting at cloud" meme here>
Quick definition: fora is the plural of forum, as in a web based forum
to discuss a topic or technology, like
https://discussion.fedoraproject.org/.
Having said that...
I love mailing lists. I have filters set up they silently go to the
correct mail folder, I can read through them at my leisure, and I only
have to deal with one client - my mail client. My mail client defaults
to sane viewing rules, threaded, in the order I prefer. It's the same
experience across every mailing list I'm a member of. I love that. It's
very accessibility-friendly.
I hate using fora. I generally have to open a separate tab for each
forum I'm on, and I'm on a LOT. And I have to go out of my way to even
remember all the fora I am a member of. For those of us who are members
of a bunch, it's kind of a beating - especially if you're an ADHD
person, like me. I get that I can (sometimes) set up email notifications
when there are responses to my posts or comments, but... if we're
already emailing forum members, why the heck don't we just use email lists?
I also love that I see interesting problems on mailing lists that I'd
never thought of or dealt with, and it's right there, in the list's mail
folder. I learn a LOT perusing those messages. It's there, I can easily
read through the threads when I get a minute. And I don't have to
remember to fire up a new browser tab to parse them.
The whole "fora are an archive" argument is kinda nonsensical, since
mailing lists are generally archived on the web, as well. In my
experience, mailing list archives are easier to search than a forum.
I get the sense that moving from email lists to fora was a move to force
folks to go to a web site to drive advertising. I kinda hate that. When
Red Hat moved from email lists to fora (log in required), I got the
sense that it was really to gather information about who was interacting
with their web site. Ditto pretty much every other vendor who moved from
email lists to web based fora - this isn't a Red Hat or Fedora specific
thing.
Am I the only one who feels this way? Has the day finally come where I'm
just old and set in my ways? Are there others who prefer mailing lists
to fora?
To be clear, I am not bashing fora, per se - I'm just saying that for
me, they're not NEARLY as easy to deal with as email lists. If you like
fora, that's awesome. I'm not attacking you. Let's nip that in the bud.
I'm not looking for a flame war, just trying to see if other feel the
same way. Let's keep it civil.
Thanks,
Thomas
2 months, 2 weeks
dmesg suddenly fails when run as normal user on FC39
by Ron Flory
Hi-
does not happen on FC38, or any prior RedHat/Fedora version since
forever.
dmesg
dmesg: read kernel buffer failed: Operation not permitted
Userspace scripts (such as used to read pics from cameras & sdcards)
and many progs often use dmesg to detect or identify things like startup
probe info, USB devs, partition numbers etc.
I worked around this by setting the suid bit of `which dmesg`, but it
would be rude to force everybody to manually do this as part of
post-install cleanup.
Hopefully an unintended side-effect and not a new "feature" that
wasn't thought through completely. A web-search suggests debian/ubuntu
may have been doing this for awhile- but we really don't need to be just
like them... ;)
2 months, 2 weeks
Failed to start jobs message from today's F39 update
by Neal Becker
Running today's dnf update:
...
Running scriptlet: grub2-common-1:2.06-118.fc39.noarch
32/32
Running scriptlet: armadillo-12.8.0-1.fc39.x86_64
32/32
Failed to start jobs: Failed to enqueue some jobs, see logs for details:
Invalid argument
Should I worry? I don't even know what armadillo is.
2 months, 2 weeks
Configuring LXC containers
by Patrick O'Callaghan
I'd like to play with LXC but I find the docs not very newbie-friendly.
I'm trying to follow a guide at:
https://brandonrozek.com/blog/lxc-fedora-38/
(basically because it mentions Fedora). I followed the steps closely
and rebooted, but I get the following error:
$ systemd-run --unit=my-unit --user --scope -p "Delegate=yes" -- lxc-start test
Running scope as unit: my-unit.scope
lxc-start: test: lxccontainer.c: wait_on_daemonized_start: 877 Received container state "ABORTING" instead of "RUNNING"
lxc-start: test: tools/lxc_start.c: main: 306 The container failed to start
lxc-start: test: tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
lxc-start: test: tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
Any insights would be welcome. (Just in case, I tried running with
SElinux turned off, but it made no difference.)
poc
2 months, 2 weeks
port forwarding and RDP or ssh
by Alex
Hi, I have a fedora38 system on Optonline with port 1024 forwarded from the
router to 1024 on the fedora38 system where ssh is listening. I'm currently
using the following to connect:
$ ssh -i ~/.ssh/mykey-key.rsa -L 5901:127.0.0.1:5901 -Y -l gary remotehost
-p 1024
I'd like to be able to have applications launched on the remote system
appear on my desktop, also using fedora38. What's the best way to do that?
I've read about RDP and gnome-remote-session but much of the docs appear to
be out-of-date. General advice on what works in 2024 would be appreciated.
My friend is having difficulty with his evolution configuration. I'd like
to be able to launch evolution on his PC and have it appear on mine.
2 months, 3 weeks
ghost town
by Tim
* * *
* **
some tumbleweeds drift through
So, is everything working fine, or did a new release break everyone's
systems so badly they can't email any more? ;-)
--
uname -rsvp
Linux 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 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.
2 months, 3 weeks
Re: Configuring LXC containers
by Patrick O'Callaghan
On Sun, 2024-03-10 at 19:37 -0700, Mike Wright wrote:
> On 3/10/24 15:40, Patrick O'Callaghan wrote:
> > On Sun, 2024-03-10 at 11:13 -0700, Mike Wright wrote:
> > > The last two lines are key. Add these flags: -F -o logfile. The
> > > default loglevel is ERROR. If you want more detail include -l
> > > LEVEL.
> > >
> > > e.g. lxc-start -n containerName -F -o containerName.log -l WARN
> > >
> >
> > This is what I get:
> >
> > $ lxc-start -n test -F -o test.log -l WARN
> ...
> > lxc-start test 20240310223702.945 ERROR start -
> > start.c:print_top_failing_dir:99 - Permission denied - Could not
> > access /home/poc/.local. Please grant it x access, or add an ACL
> > for the container root
>
> This one looks interesting
>
$ ls -ld /home/poc/.local
drwx------. 1 poc poc 56 Aug 28 2021 /home/poc/.local
IOW, it already has x access (and lxc-start is not setuid so it's
running as me).
poc
2 months, 3 weeks
Marble problem: libicui18n.so.69
by ToddAndMargo
# dnf install marble
Last metadata expiration check: 0:58:05 ago on Sat 09 Mar 2024 09:03:09
PM PST.
Dependencies resolved.
================================================================================
Package Architecture Version Repository
Size
================================================================================
Installing:
marble x86_64 1:23.08.5-1.fc39 updates
188 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 188 k
Installed size: 585 k
Is this ok [y/N]: y
Downloading Packages:
marble-23.08.5-1.fc39.x86_64.rpm 186 kB/s | 188 kB
00:01
--------------------------------------------------------------------------------
Total 114 kB/s | 188 kB
00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing :
1/1
Installing : marble-1:23.08.5-1.fc39.x86_64
1/1
Running scriptlet: marble-1:23.08.5-1.fc39.x86_64
1/1
Verifying : marble-1:23.08.5-1.fc39.x86_64
1/1
Installed:
marble-1:23.08.5-1.fc39.x86_64
Complete!
root@rn6:/home$ marble
marble: error while loading shared libraries: libicui18n.so.69: cannot
open shared object file: No such file or directory
2 months, 3 weeks
Virtualization: Windows 32-bit i686 guest not working on Fedora 39
x86_64 ?
by Franta Hanzlík
After 'dnf system-upgrade...' my machine from F37 x86_64 to F39, win7-32
guest did not start due to BSOD 0x0000007B boot problem, while win10
64-bit works fine on the same machine.
I then tried:
- a newly created virtual machine consisting only of Win7-32 or Win10-32
installation ISO image freezes after start on the first inquiry window
- the keyboard and mouse do not respond.
- the same way created virtual win10 64-bit installation CD ISO works
correctly.
- I received the same behavior on a cleqan, freshly installed F39 system
- Win7 or Win10 32-bit did not work, but 64-bit without problems.
- on a new installation of F38 - Win7 guest works without problems,
as well as both guest installations of 32-bit windows from the CD ISO
image.
On F38 is libvirt-daemon-9.0.0-4.fc38.x86_64 + qemu-kvm-7.2.8-1.fc38.x86_64
On F39 is libvirt-daemon-9.7.0-2.fc39.x86_64 + qemu-kvm-8.1.3-4.fc39.x86_64
Does anyone have any idea where the problem could be?
--
Thanks, Franta Hanzlik
2 months, 3 weeks
Strange issue with name resolution systemd-resolved.service - Network Name Resolution
by Michael D. Setzer II
Currently in Nevada accessing 4 of my computers back in Guam.
Has been working fine, until earlier today.
VNC into the machines using same name of router, but different
ports mapped to machines.
Generally login to each one, and then next with no problem.
But today, got error messages that couldn't resolve names.
then tried dig on name and got similar timeout problem with it.
Tried restarting service, and that would work for a while, but then
it would give error again.
IP is a dyndns.org address, so it can change, but very seldom.
Added the address to /etc/hosts and then problem went away
completely. Connections made with no problem. Works, unless IP
changes.
Don't know if something was changed with service recently, or if
their is some way to have it have a backup if the 127.0.0.53 isn't
working? Just says timedout?
Any options to optimize things to prevent this? Have also seen a
similare issue running dnf updates. Sometimes it reports that it
can't resolve names of repos?
Note: Cox is ISP where I'm located, so don't know. The speed is
good, getting 175+M down, and about 11M up.
Long ago use to use multiple name servers including 8.8.8.8, but
then at somepoint it changed to the 127.0.0.53 thing.
Thanks.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor (Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
mailto:msetzerii@gmx.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
2 months, 3 weeks
