My adventures with Legacy USB Support
by ToddAndMargo
Hi All,
I managed to FINALLY come up with a msdos bootable flash
drive by booting up in Win PE (windows 7 PE disk) and running
"kudzu" which both runs in PE mode and comes with both
Free DOS and MS DOS preloaded. (Of course, Win PE crashes
trying to run the Supermicro's update utility.)
I upgraded my Supermicro C7Z87's BIOS from 1.1 to 2.0.
Where before the C7Z87 would boot the MSDOS flash drive and
hang booting the Xfce Fedora flash drive
(Fedora-Live-Xfce-x86_64-20-1.iso), it would not boot either afterwards.
So, after about an hours fussing with it, I figured out that "Legacy
USB support" had to be enabled. Now both boot find.
[Editorial comment] AAAAAHHHH!!!!!! [/editorial comment]
I have to turn off "Legacy USB Support" to get certain poorly design
HP Inkjet printers to keep XP computers from freezing when they
boot up. (Funny, if you unplug the printer, XP will boot. You
can plug it in afterwards with no problem. No problem that is,
until you reboot.)
Hope this helps someone else,
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9 years
Anyone know how to create a DOS 6.22 Live USB?
by ToddAndMargo
Hi All,
Anyone know how to create a DOS 6.22 Live USB stick
from a Linux machine? Got the DOS ISO and Floppy
images, but dd doesn't work. (Need to upgrade a BIOS.)
Many thanks,
-T
9 years, 1 month
Live USB install to disk question
by ToddAndMargo
Hi All,
I have a Live USB flash drive I cherried out for my
own purposes.
If I hit the install to disk option, what gets installed?
Just the stock stuff from the ISO? Or do I get my slick
and cool customizations too? (Not they are very hard to
put back on.)
Many thanks,
-T
9 years, 1 month
logrotate is failing under a live spin only
by John Florian
All the details I have so far are here: https://bugzilla.redhat.com/show_bug.cgi?id=1127415
Here's the general pain though. logrotate-3.8.7-1.fc20.i686 behaves just fine for me in a regular Fedora 20 install:
# /etc/cron.daily/logrotate ; echo $?
0
However, on all my recent Fedora 20 live spins:
# /etc/cron.daily/logrotate ; echo $?
error: error renaming temp state file /var/lib/logrotate.status.tmp
0
If I tell logrotate to use a different state file, even in the same directory, it works fine. I suspect this is rather telling:
# lsof /var/lib/logrotate.status*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-j 423 root mem REG 0,34 8388608 15250 /var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
systemd-j 423 root 26u REG 0,34 8388608 15250 /var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
dhclient 823 root 5w REG 0,34 519 15707 /var/lib/dhclient/dhclient--eth0.lease
journalct 1003 root mem REG 0,34 8388608 15250 /var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
journalct 1003 root 5r REG 0,34 8388608 15250 /var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
Since I only see the problem with the live spin and a regular install doesn't show this file open by any processes I thought I'd ask around here if anyone has ideas. It seems very odd that these processes would have this file open.
--
John Florian
9 years, 1 month