Closed Bug 1287274 Opened 8 years ago Closed 4 years ago

Instructions given for extracting kernel and initrd for Virtual ARM Linux are incorrect

Categories

(Developer Documentation Graveyard :: Mozilla Platform, defect, P5)

ARM
Linux
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mre, Unassigned)

References

()

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

The web page Virtual_ARM_Linux_environment's detailed instructions fail at step "Extracting the kernel and initrd".  This is a complex step involving running the program 'file' and parsing its output with awk and feeding that information to a mount command.  Unfortunately the awk parsing, at least in my attempt, produced an empty string which then caused the mount command to fail.  In particular, the command is:

  mount -o loop,offset="$(file vexpress.img | awk 'BEGIN { RS=";"; } /partition 2/ { print $7*512; }')" -t auto vexpress.img /mnt/tmp

which results in

   mount: invalid offset '' specified

The file vexpress.img was created in the earlier steps and is shown to have a size of 3.0G by ls -lh.  The output of "file vexpress.img" is

   vexpress.img: x86 boot sector

which obviously does not meet the expected criteria of the awk command.  Additionally, when attempting to mount without the use of the offset paramater, via

   mount -o loop -t auto vexpress.img /mnt/tmp

I get the error message

   mount: you must specify the filesystem type

System used: Linux Mint 17 xfce. uname -a:

   Linux armworker 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:08:14 UTC 2014 i686 i686 i686 GNU/Linux
OS: Other → Linux
Hardware: All → ARM
Hi decoder,

you are the original author of this MDN article. Can you help with this know someone who could help here?

Thanks!
Flags: needinfo?(choller)
Sorry, that was written long ago and I don't know how this changed over time, as we are not using this kind of setup anymore.
Flags: needinfo?(choller)
Component: General → Mozilla Platform
This bug's P1 priority was set prior to our current doc process and has not gone through triage. Resetting priority.
Priority: P1 → --

The MDN team is no longer actively working on Mozilla Platform docs. Volunteer contributions are welcome.

Priority: -- → P5
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.