[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howtos:hardware:arm:qemu_support_in_slackware_arm [2018/11/30 22:53 (UTC)] – [QEMU Bridged Mode Networking] mralk3howtos:hardware:arm:qemu_support_in_slackware_arm [2019/01/10 02:03 (UTC)] – [Configure Network File System services] mralk3
Line 1: Line 1:
 ====== Qemu Support in Slackware ARM ====== ====== Qemu Support in Slackware ARM ======
  
-This document describes the process of installing **Slackwarearm** inside of QEMU.+This document describes the process of installing **Slackware ARM** inside of QEMU.
  
   * QEMU is a full system emulator that can emulate a range of real hardware architectures. In this case we will use QEMU to emulate the ARM Ltd. "Versatile Express" development board.   * QEMU is a full system emulator that can emulate a range of real hardware architectures. In this case we will use QEMU to emulate the ARM Ltd. "Versatile Express" development board.
   * QEMU provides a platform to allow an operating system to believe that it is running on real hardware.   * QEMU provides a platform to allow an operating system to believe that it is running on real hardware.
-  * QEMU runs on your Intel-based Slackware PC/server (in most cases this will be a desktop machine, but it is possible to run QEMU on a headless server and use VNC for graphics).+  * QEMU runs on your Slackware PC or server.  In most cases this will be a desktop machine.  However, it is possible to run QEMU on a headless server and use VNC for graphics.
  
 ===== Who is Slackware ARM in QEMU aimed at? ===== ===== Who is Slackware ARM in QEMU aimed at? =====
Line 104: Line 104:
 <code> <code>
 # chmod +x /etc/rc.d/{rc.rpc,rc.nfsd} # chmod +x /etc/rc.d/{rc.rpc,rc.nfsd}
-# /etc/rc.d/rc.nfsd+# /etc/rc.d/rc.nfsd start
 # exportfs -va # exportfs -va
 </code> </code>
Line 319: Line 319:
 ===== Boot Slackware ARM with QEMU ===== ===== Boot Slackware ARM with QEMU =====
  
-**Work in Progress** +Congratulations for making it this far!  The next step is booting into your fresh installation of Slackware ARM.  Locate the **disk_launch** helper script in /export/armhost and modify it to fit your needs.
- +
-For making it this far, congratulations!  The next step is booting into your fresh installation of Slackwarearm-current.  Locate the **disk_launch** helper script in /export/armhost and modify it to fit your needs.+
  
 <code> <code>
Line 335: Line 333:
   * **NETTYPE** - network configuration, NAT mode or bridged mode   * **NETTYPE** - network configuration, NAT mode or bridged mode
  
-The **disk_launch** script can be found online, [[http://ftp.arm.slackware.com/slackwarearm/boardsupport/qemu/slackwarearm-current/helper-scripts/disk_launch|here]].+The **disk_launch** script for Slackwarearm-current can be found online, [[http://ftp.arm.slackware.com/slackwarearm/boardsupport/qemu/slackwarearm-current/helper-scripts/disk_launch|here]].
  
 The first boot will take quite a while.  This is due to the fact that Slackware will generate the font cache for the first time.  Start up QEMU by executing the disk_launch script. The first boot will take quite a while.  This is due to the fact that Slackware will generate the font cache for the first time.  Start up QEMU by executing the disk_launch script.
Line 343: Line 341:
 </code> </code>
  
 +Assuming all is well, you can begin using Slackware ARM just as you would any other Slackware installation.
 ===== Slackware ARM Graphical User Interface ===== ===== Slackware ARM Graphical User Interface =====
  

Trace:

howtos:hardware:arm:qemu_support_in_slackware_arm ()