Re: [Voyage-linux] sshd in voyage 5.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yup, it is explicitly stated in the README. extract the software tarball: tar --numeric-owner -jxf voyage-version.tar.bz2 It doesn't say you need to be root when you do that. (maybe adding sudo to that command line would make it clear)

Re: [Voyage-linux] sshd in voyage 5.2

Yes, I see it is in README. However, the README is in the tarball itself, so it's a little late to be telling people how to extract it. =) Ben Kochie wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yup, it is explicitly stated in the README. extract the software tarball: tar

Re: [Voyage-linux] sshd in voyage 5.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I agree, hence my request to change the installation method. However it's also on the website right next to the download link as well. - -ben UNIX is user-friendly, it's just picky about its friends. On Tue, 24 Mar 2009, Jeff Ramin wrote:

Re: [Voyage-linux] ext3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Ramin wrote: Anybody using ext3 on their CF cards? Does it make sense to use a journaling filesystem on an ALIX board, since there may be a lot of syncing between tempfs filesystems and the physical storage? I don't bother with ext3 since

Re: [Voyage-linux] ext3

Gustin Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Ramin wrote: Anybody using ext3 on their CF cards? Does it make sense to use a journaling filesystem on an ALIX board, since there may be a lot of syncing between tempfs filesystems and the physical storage? I

Re: [Voyage-linux] ext3

I don't bother with ext3 since it drastically reduces the lifetime of the CF card.  Also, log files and the like are not written to disk so there is not as much IO as you might think. Not to be critical, but your response is contradictory and I can't make sense of it. Can you clarify? Some

Re: [Voyage-linux] ext3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 One option for writing to a flash in a nice pattern would be to use a log filesystem. http://logfs.org/ - -ben UNIX is user-friendly, it's just picky about its friends. On Tue, 24 Mar 2009, Jeff R. Allen wrote: I don't bother with ext3 since

[Voyage-linux] Outcome of the stuck beacon issue

I looked through the archives, but did not see a definitive resolution to the stuck beacon issue. Is the fix in the current daily build? If not, which madwifi version worked out best in the end? Thanks, Dean ___ Voyage-linux mailing list

Re: [Voyage-linux] ext3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Ramin wrote: Gustin Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Ramin wrote: Anybody using ext3 on their CF cards? Does it make sense to use a journaling filesystem on an ALIX board, since there may be a lot of

[Voyage-linux] ext3

Hi, I'm new to Alix and still waiting for a CF Card, so until I get one I'm using Voyage from USB. How about such drives? Do they also have a writes limit? Probably so, but is it bigger than on CFs? I was thinking of a scenario in which I use my CF card as a 'main' disk with the system and

Re: [Voyage-linux] Outcome of the stuck beacon issue

Hi Dean, The daily now is using revision 3942 of madwifi trunk. Stuck beacon still exists after some tests by me and others. Only 0.9.4rc2 is tested being stable. If this really concern you, please downgrade madwifi module to 0.9.4rc2 manually.

Re: [Voyage-linux] Re: Alix6b2 not detect Sierra Wireless MC8775

Jeff, thanks for the AT command ref. The firmware is surprisingly old for a 'new' model card: ati Manufacturer: Sierra Wireless, Inc. Model: MC8790V Revision: K1_0_2_4AP C:/WS/FW/K1_0_2_4AP/MSM6290/SRC 2008/08/26 13:18:25 IMEI: 35... IMEI SV: 2 FSN: D680419072010