From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <4ECA333A.2010600@gmail.com> From: Jens Staal Date: Mon, 21 Nov 2011 16:04:57 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] 9vx instability Topicbox-Message-UUID: 4216c43a-ead7-11e9-9d60-3106f5b1d025 2011/11/21 Sergey Kish : > Jens, > vx32-hg is already in AUR > http://aur.archlinux.org/packages.php?ID=28147Maybe it should use > rminnich/vx32 repo by default > /_hgroot/c_hgroot="https://bitbucket.org/rminnich/vx32". http://aur.archlinux.org/packages.php?ID=28147 uses http://code.swtch.com/vx32 https://aur.archlinux.org/packages.php?ID=49816 uses https://bitbucket.org/rminnich/vx32 Another difference is that the second installs under a new directory in /opt and my plan was to add extensions under this directory (for example an installable plan9 rootfs) This is however Arch-specific discussions and probably not suitable for 9fans. The strategies of setting up a union-mounted rootfs with iso+directory with proper user permissions with 9vx (some standardized startup scripts) is far more interesting in general (and I was planning to put up an AUR automatically updating the rootfs with the plan9 daily build isos). I had once plans of trying to make an automated build of NIX as a PKGBUILD but I have not had time to look into how to do those things as 9vx arguments.