<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=UTF-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16450"></HEAD>
<BODY style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=role_body
bottomMargin=7 leftMargin=7 rightMargin=7 topMargin=7><FONT id=role_document
color=#000000 size=2 face=Arial>
<DIV>I am running the Limey VIA on a CA-22 using the flash that came with it
with no problems.</DIV>
<DIV>Tim has the same box running.</DIV>
<DIV>I have also attached a lap top HD to it and installed ACID with no
problems.</DIV>
<DIV>Lee</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV>In a message dated 11/18/2013 9:07:35 P.M. Pacific Standard Time,
Benjamin@kb9lfz.com writes:</DIV>
<BLOCKQUOTE
style="BORDER-LEFT: blue 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"><FONT
style="BACKGROUND-COLOR: transparent" color=#000000 size=2 face=Arial>Tim, et
al:<BR><BR>Here's what I'm doing, the same way I've done it before, which
much<BR>success.<BR><BR>The machine is a neoware thin client, CA-22, with 1GHz
processor, 1GB<BR>RAM, 256MB flash.<BR><BR>on my allstar node 28569, same
physical setup, using Limey Linux for<BR>i686. the distro VIA version did not
work at all.<BR><BR>I'm using DamnSmallLinux on a thumbdrive on the designated
machine to<BR>cfdisk the Disk-on-module, not compact flash or another USB
thumbdrive,<BR>to delete what was on it, and format for FAT16. I tried also
EXT2.<BR><BR>If I had a USB to laptop IDE adapter with pins on it, I'd just
connect<BR>the DOM to it and see what the main machine says with gparted or
the<BR>other disk utility program. <BR><BR>DamnSmallLinux and Puppy Linux do
not have dosfsck support. I've been<BR>trying to get TinyCore to work, but
that is not being my friend today. I<BR>have TinyCore that works fine for me
on a few other thin client boxes<BR>with 128MB RAM and 65MB
flash.<BR><BR>anyway, I digress, I go right away into console when DSL
boots.<BR>I "sudo su" then cd to the folders I have the Limey linux, or
other<BR>embedded Linux .img files are in.<BR><BR>the command I have used
before was "dd if=cfimg-1.1.4_i686 of=/dev/hda"<BR>I've tried using "dd
if=cfimg-1.1.4_i686 of=/dev/hda bs=16k" as that<BR>works for other embedded
distro versions, but did not work here. I've<BR>never seen the e2fsck error
before, even after reformatting the drive to<BR>be used.<BR><BR>~Benjamin,
KB9LFZ<BR><BR>On Mon, 2013-11-18 at 20:32 -0800, Tim Sawyer wrote:<BR>>
Never seen a e2fsck problem. I don’t know what but you’ve got something else
wrong. Are you using the right CPU architecture?<BR>> --<BR>>
Tim<BR>> :wq<BR>> <BR>> On Nov 18, 2013, at 7:59 PM, Benjamin L.
Naber <benjamin@kb9lfz.com> wrote:<BR>> <BR>> > tune2fs does
not work either. Says could not find superblock.<BR>> > <BR>> > on
another linux machine, I typed in info tune2fs and it states it is<BR>>
> for Linux file systems.<BR>> > <BR>> > I don't care about
that. I'd like to disable the file system checking<BR>> > altogether so
I can at least get the thing to boot. <BR>> > <BR>> > presently,
it still comes to a dead halt when the e2fsck warning comes<BR>> >
up.<BR>> > <BR>> > Is there something I can modify in the
SYSLINUX.cfg?<BR>> > <BR>> > -or-<BR>> > <BR>> > When
it does get stuck on the e2fsck checktime warning, how long does it<BR>>
> *usually* take to let whatever program do it's job and then
continue<BR>> > booting?<BR>> > <BR>> > -or-<BR>> >
when it does get stuck, beside mashing the power button and smoking a<BR>>
> cigarette, is there a key sequence I can use to troubleshoot or
force<BR>> > the machine to continue booting?<BR>> > <BR>> >
~Benjamin, KB9LFZ<BR>> > <BR>> > <BR>> > On Mon, 2013-11-18
at 10:25 -0800, Joel wrote:<BR>> >> Benjamin L. Naber wrote:<BR>>
>>> this is coming up when trying to boot a new install of Limey
Linux<BR>> >>> <BR>> >>> last time I checked, e2fsck
is for EXT2 and other Linux extensions, not<BR>> >>> FAT.<BR>>
>>> <BR>> >>> Booting comes to a dead halt when the
e2fsck checktime has been<BR>> >>> reached.<BR>> >>>
<BR>> >>> Any way around this, or disable this checking when
booting?<BR>> >> <BR>> >> <BR>> >> I've never used
any of these AllStar distro's - but I have admin's Linux servers for over 15
years and am just starting to play with AllStar. With that in mind, I can
offer the following more generic Linux info...<BR>> >> <BR>>
>> CD-ROM images are always in the iso9660 filesystem format - which is
completly different than FAT/EXT2/3/4/etc. Doesn't matter what OS was used to
create the img - or burn the CD. That format is only on the optical disc (or
local loopback of the image file if you install that way). Typical thumb-drive
images I've seen have a small FAT filesystem that boots and mounts the install
iso image as lookback. The installer, as part of system setup/install formats
the local storage device (typically /dev/hda or /dev/sda) in a Linux file
format. These days either EXT2 (non-journaled) or EXT3/4 for journaling. This
has no relation to the install media!<BR>> >> <BR>> >> If
the init scripts detect a problem on any of the file systems which are to be
mounted (i.e. system disks), as outlined in /etc/fstab they will abort and
drop you to a single-user mode shell. This is the same as typing in "linux 1"
on the grub boot line (or LILO on old distro's). The point is to leave the
main system disks unmounted and allow you to repair them. Typically just
running fsck will repair them. You will need to do this for each partition
(logical or physical) that has a problem. It will typically prompt you about
problems it finds - pay attention as fsck runs - you might have to answer
"yes" many times! Might be good idea to run fsck on all filesystems while your
in there. Afterwords, when you type "exit" from the single-user shell, the
system will automatically reboot - and if all is well will boot back to
Runlevel 3 or 5 depending on your init setup with your repaired filesystems
mounted properly. This is full multi-user/normal mode of operation your used
to<BR>> > .<BR>> >> <BR>> >> In some cases, if the
file system is too damaged to even load the ramdisk - it will just die on
boot. In that case you will need a rescue disk to boot from. Most distro's
install disks offer a "rescue mode"... so just download/burn a current copy of
Fedora/CentOS/etc and you can use them as a rescue tool - and don't need to
even have that same distro installed! Just look at the install menu and see if
they offer a rescue mode. Typically you just type "rescue" and hit enter. It
will then load up a minimal system into a ramdisk with most drivers installed
that will detect your disk controller and other devices. When it asks if you
want to have it mount filesystems answer "N". Then once it drops you to a
shell start "fsck.ext2 /dev/hda1"/etc on EACH of your filesystems.<BR>>
>> <BR>> >> Finally, most filesystems in EXTx format are set to
do full checking after so many months of being mounted and/or after X many
boots. Those limits/trigger points are set using the "tune2fs" tool. Just run
"man tune2fs".<BR>> >> <BR>> >> Joel<BR>> >>
N7GLV<BR>> >> <BR>> >> <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>> >
<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>>
<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></FONT></BLOCKQUOTE></DIV></FONT></BODY></HTML>