From: "Brian T" <btuch@usa.net>
To: <tglx@linutronix.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 file corruption
Date: Mon, 30 Aug 2004 16:19:28 -0500 [thread overview]
Message-ID: <075f01c48ed7$08dbc570$fd0ba8c0@briantpc> (raw)
In-Reply-To: 1093899187.16320.25.camel@thomas.tec.linutronix.de
> >
> Use a serial console and not syslogd. Else you will have messed debug
> output which is not helpful at all
>
Bummer. Then I am in a catch-22. Console is the main login for these
units.
No video, keyboard, mouse. Only console and Ethernet/Cell Modem/Modem/etc.
-Brian
next prev parent reply other threads:[~2004-08-30 21:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 19:30 jffs2 file corruption Brian T
2004-08-30 19:40 ` Josh Boyer
2004-08-30 20:05 ` Brian T
2004-08-30 20:53 ` Thomas Gleixner
2004-08-30 21:19 ` Brian T [this message]
2004-08-30 21:19 ` Thomas Gleixner
2004-08-31 14:59 ` Brian T
2004-08-31 15:41 ` David Woodhouse
2004-08-31 17:08 ` Brian T
2004-08-31 17:11 ` David Woodhouse
2004-08-31 19:59 ` Brian T
2004-08-31 20:00 ` David Woodhouse
2004-09-01 15:30 ` Brian T
2004-08-31 20:01 ` Brian T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='075f01c48ed7$08dbc570$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox