public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian Michalk" <michalk@alerta.net>
To: "Dvir Oren" <dviro@ibm.net>
Cc: <mtd@infradead.org>
Subject: Re: Beginner with DoC
Date: Fri, 17 Dec 1999 09:57:30 -0600	[thread overview]
Message-ID: <004a01bf48a7$6cb4f4c0$0202010a@ns.jump.net> (raw)

Spoken like a person whose been bitten.

I did not get the kernel drivers to compile properly, but gave up as soon as
I found out that the patch was for the kernel drivers.
My application is pretty interesting ... at least for me.  It's for data
collection in a vehicle, and the computer is essentially a remote embedded
PC.  For years I wanted something like this with a UNIX I could afford.  Now
with DOC, I can have my computer, log in to it and do anything I would have
been able to do with a full blown computer out there.

I've always fiddled with the various stamps, flashlight controllers, and
lots of ZWorld controllers, but this is going to be much better.

PS: To whom it may concern:
May I make a suggestion (as a newcomer)?  This list has the "reply to" set
to the original author.  I'll bet there are a lot of private email
conversations going on that could answer a lot of the problems for people
like me.  It would be nice if the replyto were set to the list as well as
the original author.


-----Original Message-----
From: Dvir Oren <dviro@ibm.net>
To: Brian K. Michalk <michalk@sisko.awpi.com>
Date: Friday, December 17, 1999 9:16 AM
Subject: Re: Beginner with DoC


> Interesting thing is that fdisk shows four partitions already on the
> chip.  I'll delete them and see what sort of damage I can do now
> Thanks for the help.
>

When fdisk is concerned, if something appears odd, I don't mess
with it before I understand what has happened.  I once had to play
around with the names of the devices since I had a program that
would not install itself to anything but partitions that are named
/dev/hda-hdd.  So I renamed /dev/fla to /dev/hda, and installed it.
However, when I ran fdisk, I got confused with all the names, and
instead of destroying the flash, I destroyed my hard disk!  Luckily,
most was recovered.

If you manage to install MTD drivers in the kernel, and not as
modules, let me know.  For some reason it doesn't work for me.
---------------
Dvir Oren
<dviro@hotpop.com>
<http://thor.prohosting.com/~dviro>




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~1999-12-17 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-17 15:57 Brian Michalk [this message]
1999-12-17 16:04 ` Beginner with DoC David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
1999-12-17 16:48 Brian Michalk
     [not found] <199912162127.PAA21998@sisko.awpi.com>
1999-12-16 22:11 ` Brian K. Michalk
1999-12-14 22:31 Brian K. Michalk
1999-12-14 18:04 ` George Williams
1999-12-16 21:35   ` Dvir Oren

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='004a01bf48a7$6cb4f4c0$0202010a@ns.jump.net' \
    --to=michalk@alerta.net \
    --cc=dviro@ibm.net \
    --cc=mtd@infradead.org \
    /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