From 59ee5c81c066249c567a902a21fad2667b639889 Mon Sep 17 00:00:00 2001 From: Joachim Seemer Date: Sat, 7 Feb 2009 14:02:16 +0000 Subject: [PATCH] Corrected jamming of images, not unnecessarily create root files by first doing a {jam -q} and then {sudo jam -q}. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@29147 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- .../en/installation/install-source-linux.html | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/userguide/en/installation/install-source-linux.html b/docs/userguide/en/installation/install-source-linux.html index 503537d75f..1da74e662a 100644 --- a/docs/userguide/en/installation/install-source-linux.html +++ b/docs/userguide/en/installation/install-source-linux.html @@ -198,8 +198,14 @@ line).

Now the Haiku image is built and installed on the partition:

+
jam -q @disk
+ +

This takes some time and will abort at some point, because some root permissions are needed. That's OK, we'll continue with:

+ 
sudo jam -q @disk
+

If you do it all in one go by going straight with the sudo-line, some files are created under the "root" user, among them the image itself. This would then have to be rededicate with chown etc., so best to stick with the 2-stage approach as described.

+

Installing to its own partition offers some interesting possibilities:

sudo jam -q @disk update-all
@@ -214,11 +220,10 @@ line).

Building a VMWare Image

Just enter:

-
sudo jam -q @vmware
+
jam -q @vmware
+sudo jam -q @vmware
-

You'll now have to rededicate the generated image to satisfy the VMPlayer, before you can run it with an associated .vmx file (There's also a .vmx file in haiku/3rdparty/vmware/):

- -
sudo chown [YourUsername] haiku.image
+

The created image can be run in VMPlayer with an associated .vmx file (There's also a .vmx file in haiku/3rdparty/vmware/).

Booting with GRUB