https://wiki.archlinux.org/api.php?action=feedcontributions&user=Psychogears&feedformat=atomArchWiki - User contributions [en]2024-03-29T00:15:28ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=VMware/Install_Arch_Linux_as_a_guest&diff=161644VMware/Install Arch Linux as a guest2011-09-22T19:40:33Z<p>Psychogears: /* A more suitable cron */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:Virtualization]]<br />
{{i18n|Installing Arch Linux in VMWare}}<br />
<br />
Installing Arch Linux inside a VM (e.g. in VMware running on Windows or using VMware Fusion on Mac OS X) works without trouble.<br />
<br />
You may also be interested in [[VMware|installing VMware in Arch]].<br />
<br />
== VMware Tools ==<br />
The VMware Tools improve networking capability, cut and paste between the host and the guest under X, or access of the directories on host from the guest (called shared folders by VMware). They also provide a set of tools to access advanced options of the Virtual Machine, including shrinking and freeing unnecessary space in the virtual hard drives<br />
<br />
Install the open-vm-tools package from community<br />
pacman -S open-vm-tools<br />
and start VMware tools with:<br />
/etc/rc.d/open-vm-tools start<br />
<br />
To start them automatically at boot, add the daemon to the DAEMONS array in [[rc.conf]].<br />
DAEMONS=( ... open-vm-tools ... )<br />
<br />
To start the vmware toolbox (allows you to configure time synchronization, connect or disconnect devices, shrink the hard disk freeing unnecessary space, etc), run the following command (you may have to run as root to get full functionality)<br />
vmware-toolbox<br />
<br />
{{Note|In previous versions, starting this daemon was not strictly necessary; mouse integration, copy/paste and drag/drop under X would still work, as long as vmware-user was executed. This is no longer the case. Starting with version 2010.07.25 of open-vm-tools, vmware-user is no longer available and its functionality is implemented as a plugin managed by a new daemon (vmtoolsd).}}<br />
<br />
== Installing X ==<br />
<br />
Beyond installing Xorg (see main article [[Xorg]]), the packages needed in order to be able to use X properly can be installed with<br />
# pacman -S xf86-input-vmmouse xf86-video-vmware<br />
and the fallback X drivers<br />
# pacman -S xf86-video-vesa<br />
<br />
Modern versions of Xorg are automatically configured. If you are using a manual configuration, set the mouse driver to "vmmouse".<br />
<br />
=== VMware-user wrapper ===<br />
In order for cut/paste and drag/drop to work between VM and host, you need to start the vmware-user wrapper. First make sure it was installed as a suid binary. type the following:<br />
$ ls -l /usr/bin/vmware-user-suid-wrapper<br />
You should see something like this:<br />
-rwsr-xr-x 1 root root 5768 Aug 20 10:13 /usr/bin/vmware-user-suid-wrapper<br />
If you do not see an ''s'' bit in the fourth position, you should enable it by running the following command as root:<br />
# chmod 4755 /usr/bin/vmware-user-suid-wrapper<br />
<br />
Once you make sure vmware-user-suid-wrapper is set as a suid binary, you should run it on login by either adding the line<br />
vmware-user-suid-wrapper<br />
to {{Filename|~/.xinitrc}} or {{Filename|.xsession}} for startx, or by adding the following file {{Filename|$HOME/.config/autostart/vmware-user.desktop}}<br />
[Desktop Entry]<br />
Type=Application<br />
Name=VMWare User Agent<br />
Exec=vmware-user-suid-wrapper<br />
Icon=system-run<br />
Comment=Enable Unity, DnD, etc.<br />
for e.g. gdm. Note as well that you need to install gtkmm and libnotify for vmware-user to run.<br />
<br />
''Note: If after executing '''vmware-user-suid-wrapper''' you get the following error:''<br />
vmware-user: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory<br />
''You need to install gtkmm''<br />
# pacman -S gtkmm<br />
<br />
== Enable Unity ==<br />
Unity is installed by default, but needs a bit of work to get it running.<br />
First,make sure that open-vm-tools is installed and loaded on startup. If needed, add open-vm-tools to the DAEMONS list.<br />
<br />
Next, add vmware-user-suid-wrapper to autostart either by using your desktop environment's autostart or create a file like {{Filename|~/.config/autostart/vmware-user-agent.desktop}} with following contents:<br />
<br />
[Desktop Entry]<br />
Type=Application<br />
Name=VMWare User Agent<br />
Exec=vmware-user-suid-wrapper<br />
Icon=system-run<br />
Comment=Enable Unity, DnD, etc.<br />
<br />
Log out and restart. Unity will work. Unfortunately at the moment, menus may not display properly, so launch a terminal, switch to Unity and use the terminal to launch whatever you want. If you get an error like<br />
error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory<br />
install gtkmm<br />
pacman -S gtkmm<br />
<br />
== Shared Folders with the Host ==<br />
<br />
Create a new Shared Folder by selecting '''VM -> Settings...''' from the VMware Workstation menu. Select the '''Options''' tab and then '''Shared Folder'''. Check the '''Always enabled''' option and create a new share. For Windows XP you can create a share with the Name '''C''' and the Host Path {{Filename|C:\}}.<br />
<br />
Then add the following line to your {{Filename|/etc/fstab}} file (changing uid/gid as needed):<br />
<br />
.host:/ /mnt/hgfs vmhgfs defaults,user,ttl=5,uid=root,gid=root,fmask=0133,dmask=0022 0 0<br />
<br />
Make the mount directory and mount the Shared Folders:<br />
<br />
mkdir /mnt/hgfs<br />
mount /mnt/hgfs<br />
<br />
All of your shared folders will now be visible by name under {{Filename|/mnt/hgfs}}<br />
<br />
/mnt/hgfs/<Shared Folder Name><br />
<br />
For the Windows XP '''C''' share example:<br />
<br />
ls /mnt/hgfs/C<br />
... all your Windows files under C:\ ...<br />
<br />
== Final touch ==<br />
<br />
=== A more suitable cron ===<br />
<br />
The arch guest is most likely neither running the whole time nor rebooted often. The default crond is therefore inappropriate. Change crond for incron<br />
# pacman -S incron<br />
and edit the system crontab, i.e.<br />
# incrontab -e<br />
so that it looks like<br />
!mail(no)<br />
@ 1h /usr/sbin/run-cron /etc/cron.hourly<br />
@ 1d /usr/sbin/run-cron /etc/cron.daily<br />
@ 1w /usr/sbin/run-cron /etc/cron.weekly<br />
@ 1m /usr/sbin/run-cron /etc/cron.monthly<br />
<br />
=== Prune mlocate DB ===<br />
<br />
It is also useless to add the shared directories to the locate DB. Add the shared directories to PRUNEPATHS in {{Filename|/etc/updatedb}}<br />
<br />
== Paravirtualization ==<br />
<br />
=== Description ===<br />
<br />
[[wikipedia:Paravirtualization|Paravirtualization]] (PV) is a virtualization feature\technique that allows some of the processing, which in an ideal virtualized environment happens inside the virtualization to be done outside of the virtualized context. This will, in most cases, greatly improve the base line performance of a virtual machine. Although in some cases, depending on many variables, it will not.<br />
<br />
With the to-date distributions of Arch, PV works out of the box.<br />
<br />
On newer x86 and x86-64 CPU models (Both AMD and Intel) PV is implemented as a hardware feature and no additional configuration is required.<br />
For older CPU models, You must enable the deprecated VMI protocol that introduces modifications to the guest kernel that makes it aware of the fact that it is virtualized. (Microsoft refers to this as an Enlightened Guest OS)<br />
<br />
=== VMI Retired ===<br />
<br />
VMWare PV was once implemented as the VMI (Virtual Machine Interface) standard.<br />
<br />
In 2009, VMware announced they would [http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html stop supporting VMI] in 2011. The Linux kernel [http://blog.quiettech.org/?p=780 should remove the VMI code] around version 2.6.37. VMI still remains useful since it allows for PV on older CPUs and Arch Linux is well built for a Linux VM Guest on hosts with low resources. VMI offers a tremendous impact on the VM performance under these circumstances.<br />
<br />
In updated vmware products (Workstation 7+ and ESX 4+) VMI is retired. The functionality that was implemented in VMI and not covered by the improvements in modern CPUs is now implemented by the newer VMCI standard.<br />
Again, on to-date Arch Linux and open-vm-tools installations, VMCI works OOB and should not pose any problems. If you do encounter issues then the [http://communities.vmware.com/index.jspa Vmware Community] forums will offer all the aid you need.<br />
<br />
On Vmware Workstation products VMCI is enabled by default. On Vmware ESX products VMCI is disabled by default on the basis that it COULD pose a security risk. You can enable or disable VMCI through the VM settings screen.<br />
VMCI provides extra features, as well as a generic platform, for the area of Guest-To-Host communication.<br />
<br />
=== VMI Installation ===<br />
<br />
{{Note|Be mindful of that VMI support will be removed from the kernel at some point and you will have to downgrade your kernel to continue working with it.}}<br />
<br />
You must install the open-vm-tools before enabling VMI.<br />
<br />
To enable VMI click on "Settings..." from the VM menu. Select the Processors device and enable 'VMWare kernel paravirtualization'<br />
<br />
Once Arch is up and running you can check if you have VMI enabled or not by running the following command:<br />
$ dmesg | grep vmi<br />
<br />
If VMI is enabled you should see an output such as:<br />
Booting paravirtualized kernel on vmi [deprecated]<br />
vmi: registering clock event vmi-timer. mult=9202214 shift=22<br />
vmi: registering clock event vmi-timer. mult=9202214 shift=22<br />
vmi: registering clock source khz=2193979<br />
Switching to clocksource vmi-timer<br />
<br />
=== VMCI Installation ===<br />
<br />
To verify that VMCI is up and running, run the following command:<br />
$ dmesg | grep vmci<br />
<br />
If VMCI is enabled you should see an output such as:<br />
Probing for vmci/PCI.<br />
vmci 0000:00:07.7: PCI INT A -> GSI (level, low) -> IRQ 16<br />
Found vmci/PCI at 0x1080, irq 16.<br />
Registered vmci device.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
If there is a problem with networking, it is possible that the module pcnet32 steals the network interface from vmware, disabling it works, <br />
MODULES=(!pcnet32 ...)<br />
<br />
=== Keyboard/Mouse ===<br />
<br />
If you have no keyboard or mouse in X, you might try removing the line from {{Filename|xorg.conf}} in the "ServerFlags" Section<br />
<br />
Remove Option "AutoAddDevices" "False" (alternatively you can change to true to test it)<br />
<br />
==== Mouse lags and "flickers" after upgrade ====<br />
<br />
After upgrading some packages (includein Xorg) my mouse was slow and unresponsive within vmware. The reason was that the vmmouse driver was not loaded anymore.<br />
<br />
To solve the issue I had to add<br />
Section "ServerFlags"<br />
Option "AllowEmptyInput" "off"<br />
EndSection<br />
and<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "vmmouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
to my {{Filename|xorg.conf}} (actually I created {{Filename|/etc/X11/xorg.conf.d/10-serverflags.conf}} and {{Filename|/etc/X11/xorg.conf.d/10-mouse.conf}} containing the configurations).</div>Psychogearshttps://wiki.archlinux.org/index.php?title=VMware/Install_Arch_Linux_as_a_guest&diff=161643VMware/Install Arch Linux as a guest2011-09-22T19:38:24Z<p>Psychogears: /* A more suitable cron */</p>
<hr />
<div>[[Category:Getting and installing Arch (English)]]<br />
[[Category:Virtualization]]<br />
{{i18n|Installing Arch Linux in VMWare}}<br />
<br />
Installing Arch Linux inside a VM (e.g. in VMware running on Windows or using VMware Fusion on Mac OS X) works without trouble.<br />
<br />
You may also be interested in [[VMware|installing VMware in Arch]].<br />
<br />
== VMware Tools ==<br />
The VMware Tools improve networking capability, cut and paste between the host and the guest under X, or access of the directories on host from the guest (called shared folders by VMware). They also provide a set of tools to access advanced options of the Virtual Machine, including shrinking and freeing unnecessary space in the virtual hard drives<br />
<br />
Install the open-vm-tools package from community<br />
pacman -S open-vm-tools<br />
and start VMware tools with:<br />
/etc/rc.d/open-vm-tools start<br />
<br />
To start them automatically at boot, add the daemon to the DAEMONS array in [[rc.conf]].<br />
DAEMONS=( ... open-vm-tools ... )<br />
<br />
To start the vmware toolbox (allows you to configure time synchronization, connect or disconnect devices, shrink the hard disk freeing unnecessary space, etc), run the following command (you may have to run as root to get full functionality)<br />
vmware-toolbox<br />
<br />
{{Note|In previous versions, starting this daemon was not strictly necessary; mouse integration, copy/paste and drag/drop under X would still work, as long as vmware-user was executed. This is no longer the case. Starting with version 2010.07.25 of open-vm-tools, vmware-user is no longer available and its functionality is implemented as a plugin managed by a new daemon (vmtoolsd).}}<br />
<br />
== Installing X ==<br />
<br />
Beyond installing Xorg (see main article [[Xorg]]), the packages needed in order to be able to use X properly can be installed with<br />
# pacman -S xf86-input-vmmouse xf86-video-vmware<br />
and the fallback X drivers<br />
# pacman -S xf86-video-vesa<br />
<br />
Modern versions of Xorg are automatically configured. If you are using a manual configuration, set the mouse driver to "vmmouse".<br />
<br />
=== VMware-user wrapper ===<br />
In order for cut/paste and drag/drop to work between VM and host, you need to start the vmware-user wrapper. First make sure it was installed as a suid binary. type the following:<br />
$ ls -l /usr/bin/vmware-user-suid-wrapper<br />
You should see something like this:<br />
-rwsr-xr-x 1 root root 5768 Aug 20 10:13 /usr/bin/vmware-user-suid-wrapper<br />
If you do not see an ''s'' bit in the fourth position, you should enable it by running the following command as root:<br />
# chmod 4755 /usr/bin/vmware-user-suid-wrapper<br />
<br />
Once you make sure vmware-user-suid-wrapper is set as a suid binary, you should run it on login by either adding the line<br />
vmware-user-suid-wrapper<br />
to {{Filename|~/.xinitrc}} or {{Filename|.xsession}} for startx, or by adding the following file {{Filename|$HOME/.config/autostart/vmware-user.desktop}}<br />
[Desktop Entry]<br />
Type=Application<br />
Name=VMWare User Agent<br />
Exec=vmware-user-suid-wrapper<br />
Icon=system-run<br />
Comment=Enable Unity, DnD, etc.<br />
for e.g. gdm. Note as well that you need to install gtkmm and libnotify for vmware-user to run.<br />
<br />
''Note: If after executing '''vmware-user-suid-wrapper''' you get the following error:''<br />
vmware-user: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory<br />
''You need to install gtkmm''<br />
# pacman -S gtkmm<br />
<br />
== Enable Unity ==<br />
Unity is installed by default, but needs a bit of work to get it running.<br />
First,make sure that open-vm-tools is installed and loaded on startup. If needed, add open-vm-tools to the DAEMONS list.<br />
<br />
Next, add vmware-user-suid-wrapper to autostart either by using your desktop environment's autostart or create a file like {{Filename|~/.config/autostart/vmware-user-agent.desktop}} with following contents:<br />
<br />
[Desktop Entry]<br />
Type=Application<br />
Name=VMWare User Agent<br />
Exec=vmware-user-suid-wrapper<br />
Icon=system-run<br />
Comment=Enable Unity, DnD, etc.<br />
<br />
Log out and restart. Unity will work. Unfortunately at the moment, menus may not display properly, so launch a terminal, switch to Unity and use the terminal to launch whatever you want. If you get an error like<br />
error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory<br />
install gtkmm<br />
pacman -S gtkmm<br />
<br />
== Shared Folders with the Host ==<br />
<br />
Create a new Shared Folder by selecting '''VM -> Settings...''' from the VMware Workstation menu. Select the '''Options''' tab and then '''Shared Folder'''. Check the '''Always enabled''' option and create a new share. For Windows XP you can create a share with the Name '''C''' and the Host Path {{Filename|C:\}}.<br />
<br />
Then add the following line to your {{Filename|/etc/fstab}} file (changing uid/gid as needed):<br />
<br />
.host:/ /mnt/hgfs vmhgfs defaults,user,ttl=5,uid=root,gid=root,fmask=0133,dmask=0022 0 0<br />
<br />
Make the mount directory and mount the Shared Folders:<br />
<br />
mkdir /mnt/hgfs<br />
mount /mnt/hgfs<br />
<br />
All of your shared folders will now be visible by name under {{Filename|/mnt/hgfs}}<br />
<br />
/mnt/hgfs/<Shared Folder Name><br />
<br />
For the Windows XP '''C''' share example:<br />
<br />
ls /mnt/hgfs/C<br />
... all your Windows files under C:\ ...<br />
<br />
== Final touch ==<br />
<br />
=== A more suitable cron ===<br />
<br />
The arch guest is most likely neither running the whole time nor rebooted often. The default crond is therefore inappropriate. Change crond for incron<br />
# pacman -S incron<br />
and edit the system crontab (via "sudo incrontab -e") so that it looks like<br />
!mail(no)<br />
@ 1h /usr/sbin/run-cron /etc/cron.hourly<br />
@ 1d /usr/sbin/run-cron /etc/cron.daily<br />
@ 1w /usr/sbin/run-cron /etc/cron.weekly<br />
@ 1m /usr/sbin/run-cron /etc/cron.monthly<br />
<br />
=== Prune mlocate DB ===<br />
<br />
It is also useless to add the shared directories to the locate DB. Add the shared directories to PRUNEPATHS in {{Filename|/etc/updatedb}}<br />
<br />
== Paravirtualization ==<br />
<br />
=== Description ===<br />
<br />
[[wikipedia:Paravirtualization|Paravirtualization]] (PV) is a virtualization feature\technique that allows some of the processing, which in an ideal virtualized environment happens inside the virtualization to be done outside of the virtualized context. This will, in most cases, greatly improve the base line performance of a virtual machine. Although in some cases, depending on many variables, it will not.<br />
<br />
With the to-date distributions of Arch, PV works out of the box.<br />
<br />
On newer x86 and x86-64 CPU models (Both AMD and Intel) PV is implemented as a hardware feature and no additional configuration is required.<br />
For older CPU models, You must enable the deprecated VMI protocol that introduces modifications to the guest kernel that makes it aware of the fact that it is virtualized. (Microsoft refers to this as an Enlightened Guest OS)<br />
<br />
=== VMI Retired ===<br />
<br />
VMWare PV was once implemented as the VMI (Virtual Machine Interface) standard.<br />
<br />
In 2009, VMware announced they would [http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html stop supporting VMI] in 2011. The Linux kernel [http://blog.quiettech.org/?p=780 should remove the VMI code] around version 2.6.37. VMI still remains useful since it allows for PV on older CPUs and Arch Linux is well built for a Linux VM Guest on hosts with low resources. VMI offers a tremendous impact on the VM performance under these circumstances.<br />
<br />
In updated vmware products (Workstation 7+ and ESX 4+) VMI is retired. The functionality that was implemented in VMI and not covered by the improvements in modern CPUs is now implemented by the newer VMCI standard.<br />
Again, on to-date Arch Linux and open-vm-tools installations, VMCI works OOB and should not pose any problems. If you do encounter issues then the [http://communities.vmware.com/index.jspa Vmware Community] forums will offer all the aid you need.<br />
<br />
On Vmware Workstation products VMCI is enabled by default. On Vmware ESX products VMCI is disabled by default on the basis that it COULD pose a security risk. You can enable or disable VMCI through the VM settings screen.<br />
VMCI provides extra features, as well as a generic platform, for the area of Guest-To-Host communication.<br />
<br />
=== VMI Installation ===<br />
<br />
{{Note|Be mindful of that VMI support will be removed from the kernel at some point and you will have to downgrade your kernel to continue working with it.}}<br />
<br />
You must install the open-vm-tools before enabling VMI.<br />
<br />
To enable VMI click on "Settings..." from the VM menu. Select the Processors device and enable 'VMWare kernel paravirtualization'<br />
<br />
Once Arch is up and running you can check if you have VMI enabled or not by running the following command:<br />
$ dmesg | grep vmi<br />
<br />
If VMI is enabled you should see an output such as:<br />
Booting paravirtualized kernel on vmi [deprecated]<br />
vmi: registering clock event vmi-timer. mult=9202214 shift=22<br />
vmi: registering clock event vmi-timer. mult=9202214 shift=22<br />
vmi: registering clock source khz=2193979<br />
Switching to clocksource vmi-timer<br />
<br />
=== VMCI Installation ===<br />
<br />
To verify that VMCI is up and running, run the following command:<br />
$ dmesg | grep vmci<br />
<br />
If VMCI is enabled you should see an output such as:<br />
Probing for vmci/PCI.<br />
vmci 0000:00:07.7: PCI INT A -> GSI (level, low) -> IRQ 16<br />
Found vmci/PCI at 0x1080, irq 16.<br />
Registered vmci device.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
If there is a problem with networking, it is possible that the module pcnet32 steals the network interface from vmware, disabling it works, <br />
MODULES=(!pcnet32 ...)<br />
<br />
=== Keyboard/Mouse ===<br />
<br />
If you have no keyboard or mouse in X, you might try removing the line from {{Filename|xorg.conf}} in the "ServerFlags" Section<br />
<br />
Remove Option "AutoAddDevices" "False" (alternatively you can change to true to test it)<br />
<br />
==== Mouse lags and "flickers" after upgrade ====<br />
<br />
After upgrading some packages (includein Xorg) my mouse was slow and unresponsive within vmware. The reason was that the vmmouse driver was not loaded anymore.<br />
<br />
To solve the issue I had to add<br />
Section "ServerFlags"<br />
Option "AllowEmptyInput" "off"<br />
EndSection<br />
and<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "vmmouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/input/mice"<br />
Option "ZAxisMapping" "4 5 6 7"<br />
EndSection<br />
to my {{Filename|xorg.conf}} (actually I created {{Filename|/etc/X11/xorg.conf.d/10-serverflags.conf}} and {{Filename|/etc/X11/xorg.conf.d/10-mouse.conf}} containing the configurations).</div>Psychogearshttps://wiki.archlinux.org/index.php?title=Diaspora&diff=152850Diaspora2011-08-21T12:58:46Z<p>Psychogears: /* Installation */</p>
<hr />
<div>[[Category:Networking (English)]]<br />
{{i18n|Diaspora}}<br />
<br />
[http://www.joindiaspora.com/ Diaspora] is the privacy aware, personally controlled, do-it-all, open source social network.<br />
<br />
On November 23, 2010 was [http://blog.joindiaspora.com/2010/11/23/private-alpha-released.html announced] that Diaspora is in [http://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha private alpha] phase.<br />
<br />
== Installation ==<br />
Since diaspora does not have a stable version, you can install it with the [http://aur.archlinux.org/packages.php?ID=40859 development package] in the [[AUR|Arch User Repository (AUR)]].<br />
<br />
*To run Diaspora:<br />
$ sudo /etc/rc.d/diaspora start<br />
Then access http://localhost:3000/ to see the diaspora main page.<br />
<br />
*To stop Diaspora:<br />
$ sudo /etc/rc.d/diaspora stop<br />
<br />
*(Optional) To start Diaspora automatically at boot, add the diaspora daemon in your /etc/rc.conf file:<br />
DAEMONS=(... diaspora ...)<br />
<br />
*(Optional) To populate the database with sample users:<br />
$ cd /opt/diaspora<br />
$ sudo -u diaspora GEM_HOME=/opt/diaspora-gems rake db:seed:dev<br />
Then access http://localhost:3000/ and login with user 'tom' and password 'evankorth'.<br />
<br />
==Configuration==<br />
You can configure diaspora through its own configuration script:<br />
$ sudo vim /opt/diaspora/config/server.sh<br />
<br />
==Troubleshooting==<br />
===Errors while navigating after an upgrade===<br />
If you get an error after upgrading the package, the first thing you should do is delete the database you were using.<br />
First, stop the diaspora daemon if it is running, and make sure mongodb is running:<br />
$ sudo /etc/rc.d/mongodb start<br />
Enter in the mongo console with:<br />
$ mongo diaspora-development<br />
Finally, drop the old database, it will be regenerated the next time you access diaspora:<br />
> db.dropDatabase()<br />
> exit<br />
<br />
===GDM login screen with diaspora and/or mongodb users===<br />
GDM will insert the users diaspora and mongodb in its login window because it currently considers the id range 500-1000 as normal users while Arch considers this range for system users as defined in /etc/login.defs. GDM does that probably to keep legacy normal users working.<br />
To exclude these users from the login window, add this 'Exclude' line in your /etc/gdm/custom.conf file:<br />
[greeter]<br />
Exclude=mongodb, diaspora<br />
<br />
==More Resources==<br />
*[http://github.com/diaspora/diaspora Diaspora git]</div>Psychogears