Hello there,
(after a looong time not using Fedora, just back to it!)
I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron
N3450 inside) but this happens to fail. I've tried F25 but it has
not the right kernel to make it (I've read about 4.10 minimum), then
tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could
reach the graphical login. They both boot, some steps take a lot of
time and I end up in a state I don't understand but which is not
friendly ;-).
Here's a link to a rdsosreport.txt file generated using Rawhide, I must
admit that I don't know what to do now..
https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRL...
BTW, I could install and run a Ubuntu 17.10 daily
(artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly -
and that gave me hope!
Any hint or experience w/ such hardware?
Regards,
--
wwp

In previous Fedora distros was (IMHO) right way to log only to syslog,
without journald and its (for me) unwanted annoying binary logs, by using
configuration as:
*) Set systemd log target to syslog:
systemd.log_target=syslog (syslog-or-kmsg) ---- on kernel cmdline
systemd.default_standard_output=syslog --/
and
LogTarget=syslog ---- in systemd.conf
DefaultStandardOutput=syslog --/
*) configuring rsyslog to listen on /dev/log unix socket:
$SystemLogSocketName /dev/log ------ in rsyslog.conf
$ModLoad imuxsock ----/
$OmitLocalLogging off ---/
$AddUnixListenSocket /run/systemd/journal/syslog --/(legacy directives)
$AddUnixListenSocket /run/systemd/journal/socket -/
$AddUnixListenSocket /run/systemd/journal/stdout /
(not sure when all last three directives needed)
*) prevent to run journald:
systemctl mask systemd-journald.service
(and maybe mask systemd-journal-flush.service)
And it works fine.
But in actual Fedora 24 in systemd man page values syslog-or-kmsg and
syslog are missing in LogTarget option. As systemd/journald man pages
say hardly anything about exact mean of appropriate configuration for
this purpose, then please when someone more knowledgeable can advise:
- where to direct the systemd output? Maybe to kmsg an then read it in
rsyslog via imklog?
(rsyslog should have also imkmsg module, but is not in rsyslog-8.12.0-3.fc24)
- what about /run/log/journal/.../system.journal ?
On my test F24 system it have open rsyslogd, abrt-dump-journal-oops and
abrt-dump-journal-xorg (no need for these last two) processes. Uses it
also something else?
- what about /run/systemd/journal/{dev-log,socket,stdout} unix sockets?
Should rsyslogd listen on them?
- /dev/log seems be now symlink to /run/systemd/journal/dev-log socket
(as defined by systemd-journald-dev-log.socket) Should it be left
(because now something sends to /run/systemd/journal/dev-log), or can
be /run/systemd/journal/dev-log removed?
Thanks in advance for some clarification about this.
Franta Hanzlik

Good afternoon,
I found out the rather hard way what caused those boot failure problems
that were the subject of a threat starting last month. After my weekly
"dnf upgrade" last Thursday, I checked my root e-mail, and found the
hard drive had 8 bad sectors, then 16 bad sectors. A smartctl short
test showed several parameters "pre-fail", and the others "old-age". I
obtained a new drive. My Cray Research friend gave me a USB stick with
"Clonezilla-Live-Version" on it. That duplicated the old hard drive
onto the new one, but apparently not 100%. After the old drive was
removed and the new drive installed, I could not boot. The system was
being put into a grub shell(?). (It displayed the "grub> " prompt.)
After beating out heads against the wall (or the phone), my Cray
research friend gave me another USB stick with "Boot-Repair-Disk" on it.
That rebuilt a grub file, but not correctly. But at least I got a
grub menu when booting, and I was able to edit the shell that the grub
menu entry would run. I had to take the "efi" off the commands
"linuxefi" and "initrdefi". That allows me to boot up Fedora. But the
menu is missing an entry for windows, and I still have to edit that
script every time.
I want the grub menu to offer the three most recent patches of Fedora,
the most recent Fedora rescue shell, and windows-7, in that order.
(This is a dual-boot system.) And I want the shells launched by the
menu entries to be correct. How do I get that accomplished - the
correct Fedora-25 way? If it matters, the motherboard uses UEFI bios.
Thank-you in advance.
Bill.

Ok guys,
I know this isn't strictly "Fed" related, but the group might have suggestions.
My use case, the process has a number of remote servers. I'd like to
be able to run a bunch of commands on the remote servers as fast as
posible. The initial thought was to loop through the different
IPAddresses, and SSH into each server, to run the commands.
However, this process was still "sequential" in that each SSH session
needs to complete, prior to running the next server/ssh command.
So, my question/need -- is to figure out how to run a ssh as a
background on the local server. This approach would/should allow the
process to quickly fire off commands to the remote ipaddresses/servers
in a much faster/parallel manner.
sortof:
foreach iplist as ipaddress
ssh user1@ipaddress command & (assuming that the '&' runs the local
ssh in the background -- it doesn't!)
Running "stuff" on the remote can occur in a "Screen" session, which
would allow the ssh process to fire off the remote cmd, but it still
doesn't run the local ssh as a "background" process..
Rick has mentioned/discussed the "Screen" function in past threads.
Thoughts/comments....

I have enabled html5, and yet youtube claims
Browser does not currently recognize any of video formats available
Click here to visit our frequently asked questions about HTML5 video.
When I do click on "Click here ....etc"
I get the same page tat I access directly with the URL
https://www.youtube.com/html5
and it shows
The HTML5 player is currently used when possible.
For a sample live video, I clicked on
https://www.youtube.com/watch?v=RtU_mdL2vBM
just in case you wanted to know what I clicked on.
Thanx!!

Hello,
for reasons I have to send the input from an audio interface to an other.
I can do this with
pactl load-module module-loopback \
source="alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" \
sink="alsa_output.usb-M-AUDIO_M-Track_Hub-00.analog-stereo"
and this works as desired.
Currently I have to issue this command (realized as procedure) after each login.
I want a permanent solution. Where to place this command? Or is there an other
permant solution beside this command?
BTW, rc.local doesnt't work.
Any pointer welcome.
Kind regards, Frank