I too am struggling with the decision on a file system.
We have another product that runs out of flash on a non-ts board. It
uses jffs2 and I am not aware of any problems after several years. These
boxes are always just turned off with no sync, abet infrequently. All
the temporary files for the app and the servers are kept in ram disks,
but there is no attempt to keep operating system temp files in RAM.
jffs2 has the advantage of compression and the advantage of being
designed for flash. What's the down side?
Regards,
Jim Ham
Porcine Associates LLC
Clark Dunson wrote:
>
>
> Same questions here Dan & Roberto. I chose JFS for the OS, which I mount
> read-only, except for an occasional remount to do updates.
> The question about /var still stands here though. I cut it as a separate
> partition with ext2 right? Well I am not so sure now,
> as I have read that the loss of the dpkg files in /var will cause the
> system not to boot?! True or False? May have to try it. I have
> already discovered that if I kill power, the network won't come up until
> the second reboot. That is definitely a side effect of
> /var being ext2, and being killed without a sync.
>
>
> On May 4, 2011, at 10:00 AM, parkranger_dan wrote:
>
>> Hi Roberto,
>>
>> Oh man that would be awesome if I could try your image. My 7200 has
>> CF, not SD though, wonder if that will be an issue? Do you happen to
>> have a web-server somewhere I could just wget this from?
>>
>> Have yet to flash the device, need to find a procedure for that. I'm
>> very nervous about bricking!
>>
>> Curious as to why you went with a journaling filesystem on a flash
>> card? From what I've read there's 3 times the writes per write-cycle,
>> which kills the card quicker. I THINK this may be why they chose ext2
>> in the first place, from what I've read.
>>
>> Thanks Roberto!
>>
>> -Dan
>>
>> --- In <ts-7000%40yahoogroups.com>,
>> "r_bergo" <> wrote:
>> >
>> > Hi Dan,
>> > As you I'm on embedded Linux from bit more than one year !
>> >
>> > I had the same corruption problem and kernel questions as you. TS
>> does not support 2.6 yet..... I hope they does soon !
>> >
>> > Now I'm using TS7260 flashed with 2.6 kernel + external SD card
>> partitioned ext3.
>> > This kit works well and I never saw corruption or system crash.
>> >
>> > If you want to try that, I could send you flash image and SD image
>> files...
>> >
>> > Roberto
>> >
>> > --- In <ts-7000%40yahoogroups.com>,
>> "parkranger_dan" <dkeller76@> wrote:
>> > >
>> > > Hey all -
>> > >
>> > > I'm a half-seasoned Linux nut, but pretty new to the embedded
>> computer thing. I chose the TS-7200 for a secure remote-serial/reverse
>> tunnel project, basically linking lasers at customer sites via serial
>> port to LabView machines at the support facility.
>> > >
>> > > Thusfar, all of my code works perfect on it and I pretty much have
>> this thing configured exactly how I need it with the exception of a
>> few key things...
>> > >
>> > > NOTE: I have disabled the console, and the device is now booting
>> from the CF card (I purchased the 2.4 based Debian distro through
>> Technologic Systems).
>> > >
>> > > 1. The version of socat in the repositories is rather old (v1.4),
>> I REALLY need the 2.0.0-b4 version, as the previous is not stable with
>> my app. I tried compiling the newer version but many errors result.
>> > >
>> > > =======
>> > > SNIPPET
>> > > =======
>> > > :socat-2.0.0-b4.generic# make
>> > > gcc -O -D_GNU_SOURCE -Wall -Wno-parentheses -DHAVE_CONFIG_H -I.
>> -I. -c -o socat.o socat.c
>> > > In file included from /usr/include/linux/ext2_fs.h:20,
>> > > from sysincludes.h:163,
>> > > from socat.c:11:
>> > > /usr/include/linux/ext2_fs_sb.h:48: error: syntax error before "u32"
>> > > /usr/include/linux/ext2_fs_sb.h:50: error: syntax error before '*'
>> token
>> > > /usr/include/linux/ext2_fs_sb.h:55: error: syntax error before '}'
>> token
>> > > make: *** [socat.o] Error 1
>> > > ========================================================
>> > >
>> > > The more I read, the more I think I'll need the 2.6 Kernel to
>> compile correctly. I could be wrong. Also, a bit concerned with CF
>> card support in 2.6, as the website indicates that there was no
>> official testing. They recommended different hardware for 2.6.
>> > >
>> > > 2. Powering down unsafely will be common-place once this things is
>> deployed, and I really don't want the CF card corrupted. I've read
>> that some people have managed to mount the card as read-only and
>> create ramdrives for linking things that must change in the OS.
>> > >
>> > > Is there a standard procedure for doing this?
>> > >
>> > > Thanks in advance!
>> > >
>> > > Dan
>> > >
>> >
>>
>
>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 10.0.1325 / Virus Database: 1500/3615 - Release Date: 05/04/11
>
--
Porcine Associates LLC
244 O'Connor St.
Menlo Park, CA 94025
USA
+1(650)326-2669 fax +1(650)326-1071
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
jimham.vcf
Description: Vcard
|