Subject: Are Meta/Facebook servers using Fedora Linux?
Good day from Singapore,
I have just come across this article.
Article: Fedora's FESCo Rejects The Idea Of "-fno-omit-frame-pointer"
As Default Compiler Flag
As a change proposal first initiated by Meta/Facebook developers, they
wanted -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer to be
added to the default C/C++ compilation flags.
Meta engineers believe that any performance cost is small and worth it
while SUSE engineers previously cited around possible 5~10%
From the above quotes, I thought that Meta/Facebook servers are using
Fedora Linux, or at least Linux servers.
Anyone can confirm?
Mr. Turritopsis Dohrnii Teo En Ming
Targeted Individual in Singapore
In visiting the backup subject from some time ago, I have found that
from most environment boots that are rescue type boots, there are two
restores that seem to be available.
1. rsync, of course, and;
2. I have seen fsarchiver.
Now I have never seen restore/dump in a rescue environment. So to me
there is no reason to use it. rsync is very complicated but might be
well worth the time and effort mastering. fsarchiver seems ok.
Other than that, clonezilla seems to be that best and fastest to
me, for my purposes. As in incremental backups. dump/restore seems good,
but rescue environments do not seems to have it, not the f37 workstation
iso. Mastering find and using tar might be ok, but, no compression.
Other than these two restore types, rsync and fsarchiver, is anyone
familiar with a commonly available, rescue environment restore?
I'd appreciate any suggestions of a workaround for this situation.
Works fine without the "sudo". It also fails when run in ~root
sudo mpg123 t.mp3
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
version 1.31.1; written and copyright by Michael Hipp and others
free software (LGPL) without any warranty but with best wishes
ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection refused
[src/libout123/modules/alsa.c:open_alsa():181] error: cannot open device default
[src/libout123/libout123.c:check_output_module():947] error: Module 'alsa' device open failed.
[src/libout123/libout123.c:out123_open():439] error: Found no driver out of [alsa] working with device <default>.
main: [src/mpg123.c:check_fatal_output():334] error: out123 error 3: failure loading driver module
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 38.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
What files are basically safe to remove because they are caches and
such? There is the invisible file .cache. And the /var/cache. The files
in /tmp are these safe to delete? Are there any other files you can
delete? For example if you were using rsync, what file would you not
want to backup, because they are just caches?
I have found directories in /usr that are named after architectures. So
something has changed; is it ok to delete these? One is "x86_64",
something and one is another architecture. Are these for the system
installing? They were not in f36.
Time to install Fedora37 and on what?
I have a Lenovo x140e upgraded with 16Gb mem (even though spec says 8Gb
max) and 500GB SSD, but I am looking for something perhaps newer and
perhaps won't hang at times.
eraserhead pointing device (I hate touchpads!)
VGA output (for my KVM)
Affordable from ebay or such.
Most else is negotiable.
Oh, I will be running the Xfce desktop.
And my practice is a clean install, get everything working then rsync my
thanks for any help.
How do I identify what file
is? The component before the "@" in the file name looks like the file
may be relative to my userid. I'm using an F37 system upgraded from F36.
Also how do I determine why "journal-offline" would be denied
"relabelfrom" access on that file by selinux?
I have given journal-offline the access attempted (I know this
might be problematic given the questions I'm asking), but I'm also
trying to determine why it happened in the first place, and whether or
not, as indicated in the error details, I should be raising this as a
bug. The timing of this error seems to be indicating it occurred during
boot this morning, and the audit message is indicating the file is
potentially on device "sdd1", which is potentially my fedora root
partition, which doesn't have /boot nor /boot/efi as they are on another
device, and if it is the root device, that device is a btrfs logical
device and both the physical and logical devices have the same label.
I have a USB drive that I use for backup and in gnome (42.4) it gets
automatically mounted on /run/media/<user>/<drive>. However, I want to
export that as an NFS drive. Obviously this means that the drive be
mounted under a directory independent of the user, and whether or not the
user has started a gnome session.
So I can put an entry in /etc/fstab for that drive, using the UUID, but
how do I keep gnome from mounting it on /run/media in the first place?
I'm guessing it has to be a gnome setting somewhere.
For kicks, I asked chatGPT and this is is what it suggested:
1. Open the "Settings" application from the Applications menu.
2. In the left pane, click on "Details".
3. In the right pane, click on "Removable Media" in the list of options.
4. Under the "Removable Media" section, uncheck the "Automatically mount
removable drives" option.
which is not bad, except that in my gnome (42.4) I do not have a "Details"
item on the left pane. I do have a "Removable Media" item, but it doesn't
say anything about usb drives.