Seen on /. Zilog announces the eZ80.
http://www.zilog.com/ez80/
Mentions a TCP/IP stack too.
: I have frequently experienced very bizare behavoir whenever the commandline
: for a program gets very long, including hung processes, a hung system, and
: some really messy crashes. I think this is the problem you are having with
: wildcards. Somewhere the length of the commandline is not being
Simon Wood wrote:
>
> Yes the start of a port has been done but I kind of got distracted by
> various other toys (new distro's, TV card, tiling Kitchen...)
>
> A (not quite up to date) version of the port can be found at:
> http://www.mungewell.ndirect.co.uk/linux/index.htm
>
> I'll
Alistair Riddoch writes:
>
> Phil Kos writes:
> >
> > Chris Starling wrote:
> > > And the nifty thing is that I always get the message upon creating the
> > > 63rd file and any file thereafter.
> >
> > Sounds like this message happens when the function goes from the first
> > to the second allo
Yes the start of a port has been done but I kind of got distracted by
various other toys (new distro's, TV card, tiling Kitchen...)
A (not quite up to date) version of the port can be found at:
http://www.mungewell.ndirect.co.uk/linux/index.htm
I'll try and get motivated enough to po
Jacek Lipkowski writes:
>
> On Sun, 19 Sep 1999, Chris Starling wrote:
>
> > fsck seems to have no effect (does it really do anything yet?) Anyone
> > else ever had this problem? How do you make it go away?
>
> it doesn't seem to do anything, i've tried this on several block devices
> (flop
Chris Starling writes:
>
> In a perhaps unrelated problem, I've experienced weirdness when using
> the * wildcard when copying a large number of files. The cp process will
> freeze completely, although the machine is fine. I can kill the shell out
> from under it, but I can't kill -9 the cp
Chris Starling writes:
>
>
> Boy I've had the last 4 posts on the list now, I'll give you guys one
> guess as to what I did today... :)
>
Already replied to the other issue..
>
> Question #2
>
> I compiled Robert de Bath's man program in the sys_utils directory, but
> I can't get it to
Phil Kos writes:
>
> Chris Starling wrote:
> > And the nifty thing is that I always get the message upon creating the
> > 63rd file and any file thereafter.
>
> Sounds like this message happens when the function goes from the first
> to the second allocation unit of the directory. (62 files plus
Chris Starling writes:
>
>
> Maybe this is common knowledge, but I just thought I'd mention that in
> order to get 0.0.79 to compile, I had to make two minor changes to
> arch/i86/Makefile. Below is a diff of the old and new:
>
> 29c29
> < -0 -nostdinc -Iinclude -S -o $*.s $<
> -
I saw this note on the ELKS page:
"[1999 07 21] ELKS booted on psion 3A."
Is a Psion release expected? This looks really interesting, and I would
very much like to see Linux on my 3c.
Regards,
Gaute Hvoslef Kvalnes
386 World: http://come.to/386
Psion 3a/c/mx/Siena: http://www.crosswinds.n
Just found this fragment. I'd like to mention, that the first Versions
of UNIX ran on PDP's with (as far as I remember w/o looking it up first)
128 KWORD. There also was a unixish OS LSX patterned after V7, which
ran on a DEC (8bit ?) Microprocessor with 28 KWORDs and the kernel took up
around 8
> This is the main reason I'm posting ;-) The above is off by a DRAM
> generation. The original PC-1 had 16K Drams and you could have a
> whopping 64K on the motherboard. It came with a minimum 16Kbytes and
> a Rom Basic from you-know-who. There was also a tape-machine interface
> built in for "
13 matches
Mail list logo
