fedup major fail

Sam Varshavchik mrsam at courier-mta.com
Fri Jan 18 23:05:49 UTC 2013


Mark Eggers writes:

> I didn't point to the raw device, but instead I pointed to the mounted
> media:
>
> --device /run/media/[user-name]/Fedora\ 18\ x86_64
>
> as per documentation.
>
> The command switch is a bit misleading, since with device you might think
> to point to /dev/sr0 instead of the mount point.
>
> . . . . just my two cents.

That's exactly what "mountpoint" means to me. That's what I specified, and  
fedup accepted that without any issues. If that's wrong, fedup should've  
thrown this back in my face, or, upon reboot, there should be some kind of  
an informative error message. This should not result in an unexpected  
reboot, with no clue as to its root cause. I'll bugzilla this.

Interestingly enough, the installer now has an option to activate a wireless  
connection and, presumably, also pull in any updates; however with fedup,  
the existing wireless apparently did not get activated, so all it did was  
update the packages in the ISO image, and I had to manually load the updates  
after F18's initial load.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130118/0d06829a/attachment-0001.sig>


More information about the users mailing list