Unslung/WL500g packages available for Oleg's firmware

Oleg's latest custom firmware now has support for downloadable packages. The package format is the same "ipkg" format used in OpenZaurus, OpenWRT, OpenSlug, and other embedded linux projects.

The NSLU2-Linux project (www.nslu2-linux.org) has a repository of about 280 packages which have been ported to the Linksys NSLU2 device. That repository of package build source files is called the "Unslung" build system, and it lives in the Unslung CVS repository at http://sf.net/projects/nslu.

We have now modified the Unslung build system to support both the NSLU2 with the "Unslung" firmware, and the WL500g with Oleg's custom firmware. Note that the NSLU2 is an XScale (armeb) device running glibc, whilst the WL500g is a Broadcom (mipsel) device running uclibc, so a number of packages will need further modifications to compile for the WL500g. Also be aware that the startup scripts and configuration files have been designed for the NSLU2, and will probably need modification for the WL500g in many cases.

The current status is that the following packages compile for the wl500g:

adns_1.1-1_armeb.ipk appweb_1.2.3-3_armeb.ipk
automake_1.9.4-2_armeb.ipk bash_2.05b-3_armeb.ipk bc_1.06-1_mipsel.ipk
bind_9.3.0-1_mipsel.ipk bitchx_1.1-final-1_mipsel.ipk
busybox_1.00-8_armeb.ipk bzip2_1.0.2-2_armeb.ipk
ccxstream_1.0.15-1_armeb.ipk classpath_0.13-1_armeb.ipk
coreutils_5.2.1-4_armeb.ipk ctags_5.5.4-1_mipsel.ipk
cyrus-sasl_2.1.20-4_armeb.ipk dhcp_3.0.1-1_armeb.ipk
distcc_2.18.3-1_armeb.ipk dnsmasq_2.15-5_armeb.ipk
dropbear_0.44test4-1_armeb.ipk ed_0.2-1_armeb.ipk
expat_1.95.8-1_armeb.ipk ffmpeg_0.4.9-pre1-1_armeb.ipk
fixesext_2.0.1+cvs20050130-1_mipsel.ipk flac_1.1.2-2_armeb.ipk
fontconfig_2.2.99-2_mipsel.ipk freetype_2.1.9-1_mipsel.ipk
ghostscript_8.50-1_armeb.ipk gift-fasttrack_0.8.9-1_armeb.ipk
gift-gnutella_0.0.10-1_armeb.ipk gift-openft_0.2.1.5-1_armeb.ipk
gift-opennap_20050212-1_armeb.ipk gift_0.11.8.1-1_mipsel.ipk
groff_1.19.1-2_armeb.ipk inetutils_1.4.2-4_mipsel.ipk
iptables_1.2.11-1_armeb.ipk ircd-hybrid_7.0.3-2_armeb.ipk
joe_3.1-1_armeb.ipk jove_4.16.0.65-1_armeb.ipk lame_3.96.1-1_armeb.ipk
libcurl_7.12.2-1_armeb.ipk libdvdread_0.9.4-1_armeb.ipk
libevent_0.9-1_armeb.ipk libgd_2.0.33-2_mipsel.ipk
libid3tag_0.15.1b-1_mipsel.ipk libjpeg_6b-2_armeb.ipk
libogg_1.0-1_mipsel.ipk libpng_1.2.8-2_armeb.ipk
libtool_1.5.10-2_mipsel.ipk libvorbis_1.0-1_mipsel.ipk
lua_5.0.2-1_mipsel.ipk lynx_2.8.5-2_armeb.ipk lzo_1.08-2_mipsel.ipk
m4_1.4.1-1_armeb.ipk make_3.80-1_armeb.ipk man-pages_2.01-1_armeb.ipk
man_1.5p-1_armeb.ipk mc_4.1.35-1_armeb.ipk
mt-daapd_0.2.1.1-1_armeb.ipk nano_1.2.4-1_armeb.ipk
ncftp_3.1.8-2_armeb.ipk openvpn_2.0_rc17-1_mipsel.ipk
patch_2.5.4-2_armeb.ipk pkgconfig_0.15.0-1_mipsel.ipk
portmap_4-2_armeb.ipk postgresql_8.0.1-2_mipsel.ipk
proftpd_1.2.10-4_mipsel.ipk python_2.4-1_mipsel.ipk
recordext_1.13+cvs20050130-1_mipsel.ipk
renderext_0.8+cvs20050130-1_mipsel.ipk tcpwrappers_7.6-2_armeb.ipk
torrent_1.0-1_armeb.ipk ttf-bitstream-vera_1.10-1_mipsel.ipk
vdr-mediamvp_0.1.4-2_armeb.ipk w3cam_0.7.2-1_mipsel.ipk
xau_0.1.1+cvs20050130-1_mipsel.ipk
xdmcp_0.1.3+cvs20050130-1_mipsel.ipk xextensions_1.0.2-1_mipsel.ipk
xproto_6.6.2+cvs20050130-1_mipsel.ipk
xtrans_0.1+cvs20050130-1_mipsel.ipk

[Note that I have tested very few of those packages, so even though they compile, they still may not run correctly. Over time we will sort out which is which.]

If a package listed above has "_mipsel" in the name, then it has been modified to emit an installable ipk correctly targetted for the WL500g. If the package has "_armeb" in the name, it means that it compiles, but still requires a simple (but tedious when there are a lot of them) modification to emit the correct ipk for the WL500g.

You can find out how to build these packages here: http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung

I presume that someone (perhaps Oleg, or one of the other Chupa administrators) will make the "_mipsel" binary packages available somewhere for direct download. Until that time, you can build them yourself following the instructions referenced above. It's a one line ("TARGET=wl500g") change to the top-level Unslung Makefile to retarget it from the NSLU2 to the WL500g and build the packages.

If someone wants to send me a patch for any or all of the "_armeb" packages above to make them generate the correct ipkg control file, I'll be happy to include that patch in the Unslung CVS repository. All that is involved is updating each package's <foo>.mk file to match the control file generation code in the template.mk file. Simple but tedious.

Note that I do not intend to (nor do I have the time to) update packages that I don't personally need on my wl500g, but I am happy to accept patches from others and apply them to the Unslung CVS repository. For frequent contributors, we should be able to grant write access directly to the repository (remembering that the repository was originally set up for the NSLU2-Linux project, and that remains the primary target for the packages, so any contributed packages need to take that into account). Oleg already has write access, and I expect that at least a couple of other experienced developers here will end up being contributors with write access to the Unslung package repository too ...

-- Rod

Quote:

---

Originally Posted by rwhitby

I presume that someone (perhaps Oleg, or one of the other Chupa administrators) will make the "_mipsel" binary packages available somewhere for direct download.

---

They are now available at:

http://ipkg.nslu2-linux.org/feeds/unslung/wl500g

That feed will be updated from the list of packages in the WL500G_PACKAGES variable in the Unslung top-level Makefile.

Note that I am not offering to personally support these packages in any way - they are provided on an as-is basis. In particular, I probably will not personally be answering any "how do I use this package" questions. If you wish to make changes or contribute new packages, then follow the instructions at:

http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung

My hope is that a number of wl500g package developers will take on the task of porting many of the Unslung packages to the wl500g. There are already two developers (Oleg and Jean-Fabrice) who have CVS write access to the Unslung source repository.

-- Rod

Rod, you've done a great job, I will remove my unslung repository shortly as it's outdated now. :)
Also, I will update ipkg package, so it would point to the right place and include rc.unslung to it.

Just a quick note about some big package requesting readline, and readline libs. Is it compiling for wl-500, or does it needs more work?

Quote:

---

Originally Posted by hugo

Just a quick note about some big package requesting readline, and readline libs. Is it compiling for wl-500, or does it needs more work?

---

Fixed - there were some packages that were built as required for other packages but had not been converted.

-- Rod

Several new packages added, including gift plugins, madplay and microperl.
I've removed unslung directory from my server, so from now use this ipkg.conf line:

Code:

---

src unslung http://ipkg.nslu2-linux.org/feeds/unslung/wl500g

---

I've also updated ipkg package, so it's now pointing to the unslung repository. This new version also adds rc.unslung script to the /opt/etc/init.d/rc.unslung, so if some services depends on it, then just add

Code:

---

[ -x /opt/etc/init.d/rc.unslung ] && /opt/etc/init.d/rc.unslung

---

to the end of your post-mount/post-boot script (this depends on the moment then /opt is get mounted).

Hello!

There are 2 packages i would die for to have ;) Namely OpenVPN 2.0 and a PHP4 enabled webserver :$ Could it be possible to package those too? :$ I'm willing to pay for it!

Thanks in advance

Bart

Webserver + PHP4 is allready available on this forum (not as an ipkg package though, just a binary).

Quote:

---

Originally Posted by verwilst

$ I'm willing to pay for it!

---

Sounds interesting... :) How much ?

Well, for 2 cents, I can give you the following URL :
http://www.bobo-rousselin.com/wl/ipkg/

EDIT : and openvpn seems to build perfectly from unslung

Jean-Fabrice, could you please add your thttpd+php package to the unslung? ;-)
Feel free to send patches or files to me for review.

Well, i'm looking into setting up my own build env. to compile openvpn 2.0 ( it has to be 2.0 ) on my gentoo.. Ofcourse if you want to make the openvpn2 pkg yourself for a certain amount, just let me know :) Thanks for the thttpd link ;)

Can you add as a package open dc hub?

Quote:

---

Originally Posted by ela002

Can you add as a package open dc hub?

---

Who are you asking?

The Unslung packages come about by people contributing the packages that they personally need. We have 50+ developers, each of whom only contributed those packages that they personally need (and that weren't there already).

So you should not expect someone to jump into gear and add a package just because someone asks for it ... that is not the way these things work.

You might like to picque someone's interest by at least describing what the package is, what it is used for, and why it would be in someone's self-interest to add it.

Having said that, you might get lucky and someone might just add it out of the goodness of their heart :-)

-- Rod

Quote:

---

Originally Posted by ela002

Can you add as a package open dc hub?

---

Though you could try that wish list thread...

anybody already compiled the affix bluetooth stack?

Can anyone let me know how to install an ipkg file on the WL500g running the latest firmware? The command I am using ipkg install chillispot_1.0RC3-1_mipsel.ipk does not seem to work when I try to install the chillispot program in the root dir. Please let me know if you can help.

Niall

Is it a chillispot ipkg for the wl500g or for openwrt on the wrt54g?

The two are not compatible. Whilst the binary may well work, ipk's for the wrt54g expect a completely different root filesystem layout.

If you have the source package.mk file from openwrt, then it is very easy to convert this to an Unslung package (as the Unslung build system was derived from the OpenWRT system).

-- Rod

Hi Rod,

Thanks for the advice. It is indeed for the WRT54G. I am a real amateur when it comes to this hacking so please forgive any stupid questions. Are the instructions for adapting the WRT files in the new Unslung repository?

Cheers,

Niall

Quote:

---

Originally Posted by Niall

Are the instructions for adapting the WRT files in the new Unslung repository?

---

No, there are no instructions. You need to know a little bit about package development to adapt the files. See make/template.mk in the Unslung source code repository, and study the other packages that are there. Perhaps examine the differences between the wrt54g .mk file and the Unslung .mk file for a package which is in common between the two repositories.

-- Rod

Quote:

---

Originally Posted by Oleg

Jean-Fabrice, could you please add your thttpd+php package to the unslung? ;-)

---

thttpdphp ipk has been added to unslung feed : http://ipkg.nslu2-linux.org/feeds/unslung/wl500g/

Does not support a lot of extensions as I get trouble compiling some unslung available (and php needed) libs.
Still looking for more extension support. help is appreciated (libxml2 would be great).

Thanks Rod,

I will check it out today. I will post the adapted files if I succeed as I think it would be a great addition.

Cheers,

Niall

There's now an ipkg installation HOWTO available on the WebTools website: http://webtools.wl500g.info/wiki/dok...owtoipkgonasus

Perhaps we need to copy/paste the info into an HOWTO on this forum as well...

Hi,

I've seen that there were a fetchmail & xmail package.... does it mean that it should work on the wl500g ???? !

I'm really interested ... !

Oldudu

Quote:

---

Originally Posted by Niall

Thanks Rod,

I will check it out today. I will post the adapted files if I succeed as I think it would be a great addition.

---

Please do. Let me know when you've got a .mk file ready, and I will grant you write access to the Unslung CVS repository.

Read the pages at
http://www.nslu2-linux.org/wiki/Unsl...ckageToUnslung
for the instructions on how to contribute a new package.

-- Rod

Hmm. I try to install ncurses but my router reboots. I'm guessing I run out of memory. I have a USB stick, but don't boot from it. I have installed ipkg using the loop-filesystem trick (a file on my FAT usb stick).

My question is should I have:
dest root /
in my ipkg.conf? Does this mean that I try to download to root, and that is why I run out of memory? Should it be /tmp/harddisk/ or /opt/ ? Or is ncurses just to big for me to install, so that I need to boot from USB to make it work?

S.

All Unslung packages are designed to install everything under /opt, so "dest root /" is correct.

You might want to consider creating a swap file if you are running out of memory.

-- Rod

Quote:

---

Originally Posted by rwhitby

You might want to consider creating a swap file if you are running out of memory.

---

I use a (non rootfs) setup with additional swap memory which works fine (no short of memory) from an USB harddisk, so that would be a good solution. However I don't think that using a Flash USB drive is suitable for swapmemory because of the extensive writes performed on a swapfile and the limited write cycles sustained by Flash memory.

Quote:

---

Originally Posted by Styno

However I don't think that using a Flash USB drive is suitable for swapmemory because of the extensive writes performed on a swapfile and the limited write cycles sustained by Flash memory.

---

Agreed. But it might be a good temporary solution to be able to install a large package. Then you turn it off again (assuming the package fits in memory when it is running).

-- Rod

So how would I go about setting up a swapfile and the removing it again on a FAT drive? Does it matter that it is FAT? If it doesn't I guess I can find instructions on the forum..

S.

Quote:

---

Originally Posted by barsju

So how would I go about setting up a swapfile and the removing it again on a FAT drive?

---

Hmmm - I don't think you can on FAT. You will need to partition the drive and make one partition a linux swap partition.

-- Rod

No, you can create a swap on fat, as a file. Just make and empty file with dd, then use mkswap and you can use it.

Quote:

---

Originally Posted by barsju

So how would I go about setting up a swapfile and the removing it again on a FAT drive? Does it matter that it is FAT? If it doesn't I guess I can find instructions on the forum..

S.

---

That's easy, first you need to create swap file and initalize it (this would create 64MB swap file):

Code:

---

dd if=/dev/zero of=/tmp/harddisk/linux.swp bs=1048576 count=64
mkswap /tmp/harddisk/linux.swp

---

And then activate it in the post-mount:

Code:

---

swapon /tmp/harddisk/linux.swp

---

Here is the current package list of the 135 availables wl500g packages built using the unslung build system.
Again, thanks a lot to rwhitby, oleg and all the nslu2-linux staff.

adns_1.1-1_mipsel.ipk
appweb_1.2.3-5_mipsel.ipk
atftp_0.7-5_mipsel.ipk
audiofile_0.2.6-1_mipsel.ipk
autoconf_2.59-2_mipsel.ipk
automake_1.9.4-3_mipsel.ipk
bash_2.05b-4_mipsel.ipk
bc_1.06-1_mipsel.ipk
bitchx_1.1-final-1_mipsel.ipk
busybox-base_1.00-10_mipsel.ipk
busybox-links_1.00-10_mipsel.ipk
busybox_1.00-10_mipsel.ipk
bzip2_1.0.2-3_mipsel.ipk
ccxstream_1.0.15-3_mipsel.ipk
chillispot_1.0RC3-1_mipsel.ipk
classpath_0.13-3_mipsel.ipk
coreutils_5.2.1-5_mipsel.ipk
cpio_2.5-2_mipsel.ipk
cron_4.1-4_mipsel.ipk
ctags_5.5.4-1_mipsel.ipk
cyrus-sasl-libs_2.1.20-6_mipsel.ipk
cyrus-sasl_2.1.20-6_mipsel.ipk
diffutils_2.8.1-3_mipsel.ipk
distcc_2.18.3-2_mipsel.ipk
dnsmasq_2.15-6_mipsel.ipk
e2fsprogs_1.35-3_mipsel.ipk
expat_1.95.8-1_mipsel.ipk
fetchmail_6.2.5-5_mipsel.ipk
file_4.12-2_mipsel.ipk
findutils-doc_4.1.20-3_mipsel.ipk
findutils_4.1.20-3_mipsel.ipk
fixesext_2.0.1+cvs20050130-1_mipsel.ipk
flex_2.5.4a-2_mipsel.ipk
fontconfig_2.2.99-5_mipsel.ipk
freeradius-doc_1.0.2-1_mipsel.ipk
freeradius_1.0.2-1_mipsel.ipk
freetype_2.1.9-1_mipsel.ipk
ftpd-topfield_1.0-4_mipsel.ipk
gconv-modules_2.2.5-4_mipsel.ipk
gdb_6.3-2_mipsel.ipk
gdbm_1.8.3-2_mipsel.ipk
gift-ares_20050212-1_mipsel.ipk
gift-fasttrack_0.8.9-1_mipsel.ipk
gift-gnutella_0.0.10-1_mipsel.ipk
gift-openft_0.2.1.5-1_mipsel.ipk
gift_0.11.8.1-1_mipsel.ipk
git_pasky-0.6.2-1_mipsel.ipk
grep_2.4.2-4_mipsel.ipk
gzip_1.2.4-2_mipsel.ipk
hdparm_5.9-1_mipsel.ipk
inetutils_1.4.2-4_mipsel.ipk
joe_3.1-2_mipsel.ipk
lame_3.96.1-3_mipsel.ipk
less_381-2_mipsel.ipk
libcurl_7.12.2-1_mipsel.ipk
libdb_4.2.52-2_mipsel.ipk
libevent_1.0b-1_mipsel.ipk
libgd_2.0.33-2_mipsel.ipk
libid3tag_0.15.1b-1_mipsel.ipk
libjpeg_6b-2_mipsel.ipk
libmad_0.15.1b-1_mipsel.ipk
libogg_1.0-1_mipsel.ipk
libol_0.3.15-2_mipsel.ipk
libosip2_2.0.9-1_mipsel.ipk
libpng_1.2.8-3_mipsel.ipk
libtool_1.5.10-2_mipsel.ipk
libusb_0.1.8-2_mipsel.ipk
libvorbis_1.0-1_mipsel.ipk
libxslt_1.1.12-2_mipsel.ipk
logrotate_3.7-2_mipsel.ipk
lua_5.0.2-1_mipsel.ipk
lynx_2.8.5-3_mipsel.ipk
lzo_1.08-2_mipsel.ipk
m4_1.4.1-2_mipsel.ipk
madplay_0.15.2b-1_mipsel.ipk
make_3.80-2_mipsel.ipk
man-pages_2.01-2_mipsel.ipk
man_1.5p-3_mipsel.ipk
mc_4.1.35-2_mipsel.ipk
miau_0.5.3-9_mipsel.ipk
microperl_5.8.6-3_mipsel.ipk
minicom_2.1-1_mipsel.ipk
mktemp_1.5-1_mipsel.ipk
mt-daapd_0.2.1.1-3_mipsel.ipk
nano_1.2.4-2_mipsel.ipk
ncftp_3.1.8-2_mipsel.ipk
ncurses_5.4-3_mipsel.ipk
ntpclient_2003_194-3_mipsel.ipk
nylon_1.2-3_mipsel.ipk
openssl_0.9.7d-3_mipsel.ipk
openvpn_2.0_rc17-1_mipsel.ipk
patch_2.5.4-3_mipsel.ipk
php-dev_5.0.3-7_mipsel.ipk
php-gd_5.0.3-7_mipsel.ipk
php-mysql_5.0.3-7_mipsel.ipk
php-thttpd_2.25b-5.0.3-4_mipsel.ipk
php_5.0.3-7_mipsel.ipk
pkgconfig_0.15.0-1_mipsel.ipk
popt_1.7-1_mipsel.ipk
portmap_4-3_mipsel.ipk
procps_3.2.3-4_mipsel.ipk
proftpd_1.2.10-5_mipsel.ipk
puppy_1.8-2_mipsel.ipk
rdate_1.4-2_mipsel.ipk
readline_5.0-1_mipsel.ipk
recordext_1.13+cvs20050130-1_mipsel.ipk
renderext_0.8+cvs20050130-1_mipsel.ipk
rsync_2.6.3-7_mipsel.ipk
siproxd_0.5.10-1_mipsel.ipk
sqlite_3.2.1-1_mipsel.ipk
strace_4.5.8-1_mipsel.ipk
stunnel_4.07-7_mipsel.ipk
syslog-ng_1.6.6-2_mipsel.ipk
tar_1.14-3_mipsel.ipk
tcpdump_3.8.3-1_mipsel.ipk
tcpwrappers_7.6-2_mipsel.ipk
termcap_1.3.1-2_mipsel.ipk
textutils_2.1-1_mipsel.ipk
thttpd_2.25b-1_mipsel.ipk
unfs3_0.9.10-1_mipsel.ipk
units_1.80-2_mipsel.ipk
vorbis-tools_1.0.1-1_mipsel.ipk
vsftpd_2.0.1-7_mipsel.ipk
w3cam_0.7.2-1_mipsel.ipk
wakelan_1.1-2_mipsel.ipk
wget-ssl_1.9.1-2_mipsel.ipk
which_2.16-2_mipsel.ipk
xau_0.1.1+cvs20050130-1_mipsel.ipk
xdmcp_0.1.3+cvs20050130-1_mipsel.ipk
xextensions_1.0.2-1_mipsel.ipk
xinetd_2.3.13-4_mipsel.ipk
xproto_6.6.2+cvs20050130-1_mipsel.ipk
xtrans_0.1+cvs20050130-1_mipsel.ipk
xvid_20050214-2_mipsel.ipk
zlib_1.2.2-2_mipsel.ipk

Quote:

---

Originally Posted by Jean-Fabrice

Here is the current package list of the 135 availables wl500g packages built using the unslung build system.
Again, thanks a lot to rwhitby, oleg and all the nslu2-linux staff.

---

And a big thanks to Jean-Fabrice for taking on the job of Unslung/WL500g packages release manager, and performing it so well. It is good to see Jean-Fabrice and Josh (our Unslung/NSLU2 packages release manager) working together to keep a single source for both WL500g and NSLU2 packages, and to drive both sets of packages forward!

-- Rod

Can I draw attention to:
this comment from barsju:

Join Date: Nov 2004
Posts: 141
Hmm. I try to install ncurses but my router reboots. I'm guessing I run out of memory. I have a USB stick, but don't boot from it. I have installed ipkg using the loop-filesystem trick (a file on my FAT usb stick).

My question is should I have:
dest root /
in my ipkg.conf? Does this mean that I try to download to root, and that is why I run out of memory? Should it be /tmp/harddisk/ or /opt/ ? Or is ncurses just to big for me to install, so that I need to boot from USB to make it work?

S.

I need to know whether dest root needs to be changed too

No dest root is fine. Once I setup a swap file, it installed fine. Once finished installing I switched off the swap file.

S.

Quote:

---

Originally Posted by jago25_98

Can I draw attention to:
this comment from barsju:

Join Date: Nov 2004
Posts: 141
Hmm. I try to install ncurses but my router reboots. I'm guessing I run out of memory. I have a USB stick, but don't boot from it. I have installed ipkg using the loop-filesystem trick (a file on my FAT usb stick).

My question is should I have:
dest root /
in my ipkg.conf? Does this mean that I try to download to root, and that is why I run out of memory? Should it be /tmp/harddisk/ or /opt/ ? Or is ncurses just to big for me to install, so that I need to boot from USB to make it work?

S.

I need to know whether dest root needs to be changed too

---

No, / is the base for al packages. Root just gives the base for where to install packages
You may have to add some swap in order to be able to install larger packages. Details on how to do that have been given in other threats
like http://wl500g.info/showthread.php?t=...ghlight=swapon or do a search for swapon
/Louis

I've updated ipkg to 0.99.149. rc.unslung, ipkg.conf are included. Use

Code:

---

ipkg update
ipkg upgrade ipkg

---

to update to latest.

Hello Oleg,

Installation of the new version ended successfully, but now if I try to update:

"ipkg update" returns following:

ipkg: Cannot create directory `//usr/lib/ipkg': Read-only file system
ipkg: Cannot create directory `/usr/lib/ipkg': Read-only file system
ipkg: Cannot create directory `//usr/lib/ipkg': Read-only file system
ipkg: Cannot create directory `/usr/lib/ipkg': Read-only file system
An error ocurred, return value: 22.
Collected errors:
ipkg_update_cmd: ERROR: failed to make directory /usr/lib/ipkg/lists: Read-only file system

Is this new version not compatible (path) with the earlier version installed with the how-to of macsat?