(On Thu, 2020-03-12 at 6:22 PM, I wrote)
> Tomorrow, I'll stick it to my workstation again,
> and try to do something "rooty", and report.
Tried it. After booting up off the stick, I had to do "su -" to do
anything "rooty". But I notice that even then, I could not see much of
anything in the workstation itself. For example, whether I do a
journalctl or use the logs tool, I saw only the logs from the Fedora
live session. So if something went wrong and I had to fall back to a
Fedora live session, how would I access logs or other diagnostic
information, or (for example) edit grub-related files, or (for example)
free up disk space on the actual workstation hard drive?
(responding to Tim's 2020-03-13 1:12 AM post)
> While it's entirely possible that some motherboards
> can't boot from some USB connectors at all, and some
> could be user-configured that way, it should be
> possible to create your install on USB stick plugged
> into any of the ports.
In my case, I think the problem is trying to boot from the USB-3 ports,
not writing to the USB-3 port.
> Or that one particular creation techique won't work
> for them. I've had sticks where I simply used dd to copy
> to the ISO to them, and that worked fine. Others I had
> to use a tool like mediawriter.
I used mediawriter. I don't see how simply using dd could work. I see
that, using mediawriter puts only one file into my Downloads directory,
but 5 top-level directories end up on my stick (was new/empty
beforehand). That suggests that mediawriter did more than merely
download and then copy.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
