<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Oh good grief!!<br><br>The image on the CF is a DOS FAT filesystem that the bootloader<br>reads to load the kernel and RAM image for the filesystem.<br><br>I wouldn't be too terribly concerned about a RAM filesystem<br>that thinks it needs to be fsck-ed.<br><br>Jim<br><br><br><div>> Date: Mon, 18 Nov 2013 11:24:24 -0600<br>> From: ars.w5omr@gmail.com<br>> To: app_rpt-users@ohnosec.org<br>> Subject: Re: [App_rpt-users] e2fsck<br>> <br>> On 11/18/2013 10:45 AM, Benjamin L. Naber wrote:<br>> > That's what it appears to me.<br>> ><br>> > A ham this morning told me the problem maybe the person making the<br>> > distro images is using a windows machine, not linux, and he is making<br>> > the .img files for FAT when they *should* be ext2<br>> ><br>> > I've been trying everything that I can find to do the filesystem check,<br>> > but every embedded distro I've tried doesn't support checking DOS or FAT<br>> > files systems.<br>> ><br>> <br>> it shouldn't matter what platform is used to burn an image.<br>> <br>> There -might- be an issue in putting the image on a thumb-drive. I'm not <br>> sure what the native format of a thumb-drive is, but I'd venture that <br>> 99% of 'em are FAT32.<br>> <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br></div> </div></body>
</html>