>X-Authentication-Warning: Consulate.UFP.CX: rhw owned process doing -bs
>Date: Mon, 6 Mar 2000 02:07:56 + (GMT)
>From: Riley Williams <[EMAIL PROTECTED]>
>X-Sender: [EMAIL PROTECTED]
>To: Juanjo Marin <[EMAIL PROTECTED]>
>Subject: Re: dd command (it was C
(I sent it again because It doesn't appear on my ELKS list, sorry if you
receive twice this message)
At 22:44 5/03/00 +, you wrote:
Hi Riley and others,
>There are two points that need considering:
>
> 1. Larger block sizes are indeed faster up to a point.
>However, all floppy disks used
A french translation sounds great!
>On Mon, Jan 24, 2000 at 08:32:05PM +, Alistair Riddoch wrote:
>> > Good idea, when it is available I will translate into Spanish,
>>
>> Thanks for the offer.
>>
>> I have put the modified version of the files on a new documentation
>> page at http://www.
On Mon, Jan 24, 2000 at 08:32:05PM +, Alistair Riddoch wrote:
> > Good idea, when it is available I will translate into Spanish,
>
> Thanks for the offer.
>
> I have put the modified version of the files on a new documentation
> page at http://www.elks.ecs.soton.ac.uk/doc/.
All right. If an
Thanks! I'll have those up on the EDP as soon as possible.
>Hi people,
>
>Here are the translations into Spanish of README.TXT and INSTALL.TXT
>(with
>the modifications made by Al)
>
>best regards,
>
> Juanjo
>
>PS: about install.txt, in the Linux users section, it is said that the
>cat
>c
Hi people,
Here are the translations into Spanish of README.TXT and INSTALL.TXT (with
the modifications made by Al)
best regards,
Juanjo
PS: about install.txt, in the Linux users section, it is said that the cat
command is used to create the disks... is dd the same that the cat command
On Mon, Jan 24, 2000 at 07:56:29PM +0100, Juanjo Marin wrote:
> Al,
>
> Good idea, when it is available I will translate into Spanish,
>
Thanks for the offer.
I have put the modified version of the files on a new documentation
page at http://www.elks.ecs.soton.ac.uk/doc/.
Matt's file included
Thanks to everyone who has submitted for this. Both major contributions have
some good strong points, and both have there mistakes. I will put together
a pair of files from the best of the two, and post them back for approval.
Al
Al,
Good idea, when it is available I will translate into Spanish,
best regards,
Juanjo
At 16:21 24/01/00 +, you wrote:
>Thanks to everyone who has submitted for this. Both major contributions have
>some good strong points, and both have there mistakes. I will put together
>a pair
on increased my knowledge. And Matt had an excellent DOS instruction
set, too.
Bruce
-Original Message-
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, January 22, 2000 10:11 AM
Subject: RE: Call for a README
>Here'
Here you are the Spanish translation of README, called LEEME
Bye,
Juanjo
At 18:41 21/01/00 -0800, you wrote:
>
>>: If you have any suggestions for this readme send your comments to
>>: [EMAIL PROTECTED]
>>: or
>>: [EMAIL PROTECTED]
>>:
>>: --Phillip J Rhoades
>>
>>Fantastic job! You'r
> Anyone who wants to contribute to the project, but can't code, here is your
> chance. Don't worry about discussing in depth what the files should contain.
> Just write something and we will go from there.
Hi,
What I think would be good is a file describing very basically how the kernel works,
: If you have any suggestions for this readme send your comments to
: [EMAIL PROTECTED]
: or
: [EMAIL PROTECTED]
:
: --Phillip J Rhoades
Fantastic job! You're definitely hired for a writing position!!
Greg
>: If you have any suggestions for this readme send your comments to
>: [EMAIL PROTECTED]
>: or
>: [EMAIL PROTECTED]
>:
>: --Phillip J Rhoades
>
>Fantastic job! You're definitely hired for a writing position!!
>
>Greg
>
>
Thanks I've attached a copy with some correction to punctuation, spelli
On Fri, 21 Jan 2000, Alistair Riddoch wrote:
> Anyone who wants to contribute to the project, but can't code, here is your
> chance. Don't worry about discussing in depth what the files should contain.
I was thinking this could also be a good place for an (almost) howto.
If people try to insta
On Fri, Jan 21, 2000 at 01:19:26PM -0800, iwishihadda realname wrote:
> How about this? I read that slashdot article someone
> posted the link to. I'm one of those types who
> doesn't know a whole lot about programming, but is
> learning, and is certainly interested in learning, and
> thus might
How about this? I read that slashdot article someone
posted the link to. I'm one of those types who
doesn't know a whole lot about programming, but is
learning, and is certainly interested in learning, and
thus might be able to contribute in the documentation
area. I whipped up this real quick.
Here's a README I've attached the text file too in case you mail program mangles it.
What do you think?
(1) Introduction
(2) Trying out ELKS using the disk images
(3) Compiling your own kernel
(1) Introduction
Hello and welcome to
: So I decided I need to put a README and an INSTALL file with the distribution
: in future releases, but that I am not really qualified to write them.
Al,
Not to disagree with you, but I think that it's important that the actually
useful Real Technical Information (tm) be included in an INST
I've already written a basic 'install' procedure for the Psion which is on
my web site. This covers how to program a SSD (given the image) and how to
install the Kernel.
I don't feel I know enough about the PC stuff, but am happy to contribute
more on the Psion specific stuff.
Simon Wood
Hardwa
I was looking at my release procedure with a view to making sure each
release of ELKS is accessible as possible to users, and I realised
that the lack of any kind of immediate documentation with the
binary images is a serious flaw. I also realised that many things that I take
for granted are not
21 matches
Mail list logo
