[Mageia-dev] UsrMove failure

[Remco Rijnders]

On Tue, Aug 14, 2012 at 11:13:48AM +0100, Johnny wrote in 
<201208141213.52280.cooker at solbu.net>:
>On Tuesday 14 August 2012 11:34, Colin Guthrie wrote:
>> I happily have e2fsck in my initrd.
>
>Which was not my whole point. The average user is trained to use fsck to check filesystems when this prompt comes along. Almost every guide out there directed to the normal user describes running fsck, not e2fsck. It is even written in the prompt text that one should run fsck, not e2fsck. Either the text in the prompt should be changed or fsck should be included in the initrd/dracut.
>I even instruct people to use the TABulator to auto complete paths and filenames, to reduce the risk of typos in commands. This doesn't work in the initrd prompt, either.
>This should be fixed.
>
>In my 12 years of using Linux, this is the first time I've had to use it. It is the first time ever that the various fsck.* tools were Not available. It is also the first time the up-arrow did not work in command line. So any typo in commands resulted in having to manually retype the entire command. Which is a royal pain in the Ass when fscking multiple filesystems. No, really.
>
>Another problem with this new setup is that local helper scripts to check filesystems is not available. My brother had Mandriva for about a year. He even thinks Windows is dificult. So I made a shellscript for him to run the next time he saw the fsck prompt, which would run "/sbin/fsck.ext3 -y /dev/sdxx" on all partitions. This no longer works in the current setup, forcing every user to manually running a complicated command in the shell, with options they have never heard of.
>I do not believe I'm alone in having to making this kind of local helper scripts for users who have no intentions of learning to use the command line.

Ok... valid as these points may or may not be... I think this no longer 
has to do with the /usr move procedure? A normal user will not be required 
to update their systems the way we (devs and other interested Cauldron 
users) will have to do this for now using a number of detailed steps.

If the system prompts one to use tools not available, then that's a 
seperate issue that should be addressed (probably not by Colin).

Back on track: 1) Do ensure that when you run the dracut command that an 
image is generated for your current kernel (uname -a) and that you don't 
boot into another kernel. 2) Don't forget to edit the boot options on the 
first boot after doing the above.

Remmy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: </pipermail/mageia-dev/attachments/20120814/21857068/attachment.asc>