On Wed, 1 Mar 2000, Ken Yap wrote:
> For the definitive list of Linux distributions, go to
> lwn.net/bigpage.phtml There are a few tiny distributions listed there
> that may install and run in as little as 2 MB.
We used to run a very useful system (6 concurrent users) on 3.5mb, mainly
running ma
On Tue, 29 Feb 2000, Alegria Loinaz. Inaki wrote:
> I am a new participant in the list and after reading FAQs I have a couple
> of questions:
> - Is ELKS able to run executable programs from standard Linux?
Not directly, since standard Linux programs are in 32bit code, ELKS is
mainly for 16bit
On Sat, 5 Feb 2000, Greg Haerr wrote:
> Yes. I'm quite familiar with MSDOS EXE format and the current
> code doesn't do anything near what's required. And even if it did,
> there's the problem of having linking with a Linux8086 libc but producing
> .exe files...
I know. I guess someone obviou
On 4 Feb 2000 [EMAIL PROTECTED] wrote:
> I'd be interested in any information/documentation on the MSDOS binary
> compatibility in ELKS.
Oh god, is that still there? I put it in as a joke 2 years ago :)
> What purpose does it serve in the project?
For the project, it had no real purpose.
>
On Wed, 2 Feb 2000, Alistair Riddoch wrote:
> If anyone has contributed code to this directory and is not credited, please
> let me know and I will put you into the files headers.
I've got a new fdisk just about ready to go into elkscmd, which should fix
a number of bugs people have reported. S
On Sat, 22 Jan 2000, Matt Balaun wrote:
> I can create the partition without any problem, but how do I figure out
> how big it is in MB simply from the sector information ELKS fdisk
> displays?
I wrote the fdisk program, but I've basically forgotten how it works. You
should find that it prints
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 Thu, 9 Dec 1999, Alistair Riddoch wrote:
> but as David pointed out, this is not efficient code, so I replaced it with
> his example, as shown above
I never really thought about it being efficient as such, I was more
pointing out the issue that in some instances, the \n isn't at the end of
th
Hi all,
As some of you may have noticed, CVS on elks.doa.org came back up
a couple of hours ago (around midday GMT). Simon had a 3 hour yelling
match with the ISP who finally fixed his connection.
Feel free to start using CVS again, and feel free to try out the
networking code and play s
On Sun, 5 Dec 1999, Mario Frasca wrote:
> login.c removes the trailing '\n' from the password, passwd.c doesn't do
> it. I don't know what is the reason for removing the '\n', but I assume
> there must be one, so I added the following lines to passwd.c
Yes, there is a reason for it. The passwo
On Sat, 27 Nov 1999, Alistair Riddoch wrote:
> mbit.doa.org and elks.doa.org, which both appear to be the same machine
> have been down for a few days
>
> David, have you been in touch with him recently?
I was talking with him yesterday and everything was okay then.
I just did a check, and he'
On Sat, 20 Nov 1999, Alistair Riddoch wrote:
> What, appart from the obvious, does crashme do?
IIRC, basically it just generates random code and runs it, to see if the
system handles it :)
Davey
On Fri, 19 Nov 1999, Alistair Riddoch wrote:
> > Agreed, but for initial coding, it may be best to run in user space
> > till code fairly near to completion.
>
> There is alot to be said for this as an idea. Its much easier to debug
> user space code, and it doesn't bring the system down when it
On Wed, 17 Nov 1999, Alan Cox wrote:
> We dont really have a networking layer. I don't that is in itself a problem
> since you can prove you send/receive frames correctly and the rest is someone
> elses problem.
Agreed. My ne[12]000 code (which should be in the CVS tree by now),
should in theor
On Sat, 20 Nov 1999 [EMAIL PROTECTED] wrote:
> That's SICK! How the h... can anyone take a patent on a time format?!
This is only in America, the land of the free and the stupid.
Davey
On Sun, 14 Nov 1999, Alistair Riddoch wrote:
> I am slightly confused about the int 19h issue however. If cassette BASIC
> uses this mechanism, but is not envoked until Floppy and HDD boot have
> failed, is this what we want?
INT 19 points to a code block which tries to search for the drives the
On Sat, 13 Nov 1999, Blaz Antonic wrote:
> All you have to do is to insure your ROM image uses correct format
> (utils in netboot package create correct images from executable
> binaries) and BIOS will do the rest of the job
Actually, 'format' simply means 0x55aa at the start of the image, and t
On Sat, 13 Nov 1999, Stefan Pettersson wrote:
> So we are back to the usual problem, where in the 640 kB should we put
> or own EPROM.
On x86 you've got 20 address lines, this is 0-1mb. What do you think the
space is reserved for from 640k-1024k? ROMs. When the system boots, it
will probe var
On Thu, 11 Nov 1999, Vali Dragnuta wrote:
> As I knew about ELKS acute need for networking /* :-) */, here is
> an idea I have to deal with the problem quite in a simple way.
Ideas are fine, but I got sick of people talking about networking and just
wrote it. Writing code is much faster fo
On Mon, 4 Oct 1999, Greg Haerr wrote:
> On Monday, October 04, 1999 1:32 PM, Araujo, Isaque G.
>[SMTP:[EMAIL PROTECTED]] wrote:
> : Would be nice if you had some screenshots of nano-X/microwindows running !
> :
> Yes, it would be. Sometime ago this was discussed on this list,
> and IIRC,
On 4 Oct 1999, Vidar Hokstad wrote:
> >I still personally think the MPL is the only standard license that fits
> >the linked in case at all
>
> I agree, but on the other hand I'd gladly support licensing the code under
> both the GPL and the MPL, so that those who wants to develop free softwar
On Fri, 1 Oct 1999, Luciano [ISO-8859-1] José Alves wrote:
> I have a question. Does have ELKS support for Year 2000 bug ?
How about a y2k statement? "Your computer will die before ELKS" sounds
appropriately correct.
Davey
On Fri, 1 Oct 1999, Werner Heuser wrote:
> for me 0.0.79 worked with 'fdisk /dev/bda1' on a C286LT
Don't use /dev/bda1, use /dev/bda. bda1 is partition 1 on the 1st disk,
which is not what you want.
Davey
On Thu, 23 Sep 1999, Ken Yap wrote:
> Anyway this is getting a bit off topic for ELKS.
Not at all. It's a tad off-topic for this list, but still interesting.
No doubt more suited for the elks-z80 list, as well as linux-8086, but I
think both lists are finding it interesting.
Davey
On Wed, 22 Sep 1999, Benjamin Hauger wrote:
> Forget it. I've asked to be unsubscribed about three or four times and
> I've tried. Once you're on this list, there's no escaping it. You might
> want to try setting up a procmail script to bounce all incoming list
> messages back at the list. I'm ab
On Tue, 7 Sep 1999 [EMAIL PROTECTED] wrote:
> Does anybody on the list know where some docs, HOWTO's, books, etc
> are(preferably on the net) on the theories behind OS/kernel development and
> maybe how to implement them? I'm hoping there's something out there not
> necassarily on linux but o
On Tue, 7 Sep 1999, Thierry DELHAISE wrote:
> movb4(di),*36; (What mean the * prefix of value 36)
> ; does 4(di) means [di+4] ???
Simple answer. Assemble it under as86 and see what comes out :)
Davey
On Mon, 30 Aug 1999, Phil Goembel wrote:
> Ok, I can't resist. Please keep in mind I don't know anything about
> the coding conventions for this project. But wouldn't it be better
> to adopt a convention that uses something like WORD16 and WORD32 for
> dealing with memory, since int, long, a
On Mon, 30 Aug 1999, Alan Cox wrote:
> You mean
>
> unsigned long peekd(unsigned short *x)
> {
> return peekw(x)(peekw(x+1)<<8);
> }
Shifting by 8? 16 might work a tad better. Also the +1 makes me
suspicious. +sizeof(x) would be
On Wed, 25 Aug 1999, Chris Starling wrote:
> > ELKS was produced from linux... an MC68000 port can be derived from
> > standard linux-m68k .. any ideas?
>
> Below is a link to a page for the beginnings of a Linux/68000 port.
> Looks like the guy kind of got stalled this summer, but maybe you
On Sat, 21 Aug 1999, thcg wrote:
> I think the same way ELKS was produced from linux... an MC68000 port can
> be derived from standard linux-m68k
There's a few issues here. Firstly, the only stuff you need to port, is
the arch specific stuff. Stuff like networking and file system code is
indep
On Fri, 13 Aug 1999, thcg wrote:
> I am seriously considering starting a cottege industry making little
> diaries/laptops consisting of a cheap mcu like m68k or arm (?) LCD
> screen and keyboard running embedded linux.
> ..away from the rest of the process, the bottleneck seems to be the
> machi
On Sat, 31 Jul 1999, Grant Stockly wrote:
> Does anyone know if there is source code on the internet for a BIOS? It
> doesn't matter how detailed it is, all I want to know is basically what
> is done.
There is one on simtel. I forget where exactly, but I've put it up
on the web, at http://doa
On Thu, 29 Jul 1999, Perry Harrington wrote:
> I brought up a thread a long time ago on this, Borland wasn't interested
> then, but they just released Turbo C for free.
Source, or just free binaries? If it's only binaries it's not much use to
us.
> This means we can use it for compiling in the
Hi all,
At 10:32am GMT, 18th July 1999, a host on the domain shared by
doa.org was entered into the ORBS database. As a result, some users have
had mail bounce from the developers mailing list. Any mail address which
bounces to this list with an error such as the ORBS error, or a 'user d
On Tue, 20 Jul 1999, Blaz Antonic wrote:
> I have already suggested to use BIOS console instead of direct one on
> PS/2 machines long time ago, but noone tried it.
>
> So, disable dircon and enable bioscon support in config, recompile and
> try again. Please let us know whether it works or not (
On Mon, 19 Jul 1999, Greg Haerr wrote:
> > Why has elks chosen a 16 bit inode number for stat when the rest of
> > the world has 32 bit inode numbers? It probably is a good idea to use
> > 32bit inode numbers.
I'd say the simple answer is that because ELKS is targetted at 16bit (or
less, ie. n
On Thu, 15 Jul 1999, Jakob Eriksson wrote:
> On Thu, 15 Jul 1999, David Murn wrote:
>
> > Just a quick note to let everyone know that doa.org has returned, so
> > elks.doa.org now works again for CVS and web.
>
> The web message is not very friendly though!
I know,
Just a quick note to let everyone know that doa.org has returned, so
elks.doa.org now works again for CVS and web. Also, the [EMAIL PROTECTED]
kernel mailing list is now back online.
Davey
On Wed, 14 Jul 1999, Luke (boo) Farrar wrote:
> bcc -0 -O -ansi -s -ansi fsck.c -o fsck -H
> undefined symbol: _S_ISSOCK
>
> It would be nice as a hard disk filing system is fairly useless without
> it.
Well, ISSOCK is checking if stat() was done on a socket. Not much use at
all until the
On Wed, 14 Jul 1999, Greg Haerr wrote:
> The issue here is that the size of the libc.a file itself is > 512k, so
> the filesystem won't let ld86 read it...
It is? I dunno where you got your libc.a from, but mine is 82k. libc
under Linux is > 512k, but under ELKS, it's tiny.
Davey
On Wed, 14 Jul 1999, Scott Lanning wrote:
> 3) Also FAQ Q2.5, it says 'mkfs -t minix -n14 /dev/fd0 1440', but
> my mkfs has no -n14 option. However, 'mkfs.minix -n14 /dev/fd0 1440'
> works okay. (Maybe it's just my (Redhat 5.1) distribution.)
Must be a redhat issue, in slackware (and also when I
On Tue, 13 Jul 1999, Luke (boo) Farrar wrote:
> Do we still have the 512k file size limit?
>
> I thought that libc was bigger than this or something, and that was one of
> the limiting factors on a self hosted bcc.
Not quite. I didn't actually know about the 512k limit, but greg says
it's the
On Tue, 13 Jul 1999, Greg Haerr wrote:
> : I agree, but of late I've had little enthusiasm to try and trim the fat
> : off the larger areas of the code.
>
> Hmm.. I haven't got to that yet. What other areas are bloated?
I basically did an: ls -lS `find -name *.a` to find all the lar
On Mon, 12 Jul 1999, Greg Haerr wrote:
> Killed your baby? Why, it seems this one died from neglect ;-)
> try typing ESC [ H on the console. Nothing happens.
Yep, it won't do anything. The only commands supported, are: m (color),
s (save location), u (unsave location), A (up), B (down),
On Mon, 12 Jul 1999, Greg Haerr wrote:
> BTW, the ansi elks console doesn't work. I can rewrite it quickly if
> nobody minds.
You killed my baby?? Exactly how has it stopped working? It's not a very
complete implementation, only half-a-dozen ANSI commands are supported.
> o added TERM=
On Mon, 12 Jul 1999, Greg Haerr wrote:
> : This is debugging info from the kernel which basically means that signals
> : are working.
>
> Actually signals don't work well yet. Try ^C in a variety of programs,
> and you'll find yourself logged out with the original still running, etc.
Wel
On Sun, 11 Jul 1999, Thomas Stewart wrote:
> I compiled microwin, copied the binary to my elks root disk and it worked.
> Except that the mouse does not work properly, when I move the mouse the
> pointer moves all over at ramdom.
First thought is wrong protocol. But normally this means the mo
On Mon, 28 Jun 1999, Greg Haerr wrote:
> I can't get Micro-Windows to work with the serial mouse driver.
> It appears there's still possibly a bug in select(). Basically, the
> mouse works for about 1 second and then freezes.
As I read this, the first thing that pops into my head is that
On Mon, 28 Jun 1999, Chris Starling wrote:
> Is there a better, more stable way to do ELKS emulation?
Is running ELKS in vmware, or dosemu an option? This is how most
development is done I think, and it means that you can test in the real
ELKS rather than an emulator.
Davey
On Thu, 10 Jun 1999, Jakob Eriksson wrote:
> > BTW: Do you, Jakob, or somebady else know, whether one has to "park"
> > the xt-disk before shutting down the computer?
> > Is this neccessary, and if, how do I do this with > > linux and/or
> > ELKS?
> If no one ports this utility to ELKS, I guess X
On Tue, 1 Jun 1999, Ross Vandegrift wrote:
> ed would be a good start, but I'd rather see a vi implementation.
ed, is called (surprisingly) ed. vi is called levee. Those 2 programs
are already there in the elkscmd package.
Davey
On Tue, 1 Jun 1999, Luke (boo) Farrar wrote:
> Pico would be great, but is is part of Pine, the email program so it
> wouldn't be as easy to port as you might think.
Another issue(?) here, is that pico and pine aren't under the GPL, but are
under a different license. If you fiddle with it (and
On Tue, 1 Jun 1999, Robert Amstadt wrote:
> As you may know, I run one of the mirrors for the ELKS project. I was
> browsing around the web pages and noticed that at least one of the ELKS
> developers was using Geo Cities with their annoying pop-up ads. I have a
> 384k connection to the Interne
On Tue, 1 Jun 1999, Thor Harald Johansen wrote:
> Oh, by the way, the standard shell, is it very poor compared to other
> shells?
Actually, it's not, if you look at all it's doing. Sash as a shell is
very basic, but internal to that one executable are a LOT of prorgams.
>From small programs suc
On Tue, 1 Jun 1999, Thor Harald Johansen wrote:
> Okay. I need a reasonably good text editor. Point me to one, please. ;)
levee comes with the elkscmd package.
Davey
On Thu, 27 May 1999, Luke (boo) Farrar wrote:
> Is it a config option? It doesn't happen using sash, but does with ash.
Probably because sash's inbuilt ls isn't using signals, so doesn't need to
setup a signal handler.
> And why doesn't 286 protected mode stuff compile?
Did it ever?
> I'm jus
On Wed, 19 May 1999, Sven 'Zak' Kozma wrote:
> All I found (with help of this list) was the zcc, but I don´t think it could
> make it ... :-(
zcc (which I think uses scc) was the compiler originally used to compile
ELKS for the Z80, if memory serves correctly (alan?).
If we start back at 0.0.12
On Mon, 17 May 1999, Greg Haerr wrote:
> > 1. IBM MDA.
> no graphics support...
Umm, are you sure? We used to run windows 3.0 on amber monochrome
monitors at college.
Davey
On Wed, 12 May 1999, Ansel wrote:
> Shouldn't ELKS ultimately be able to run on systems without a BIOS?
Yes, in the future it should. Userspace programs should not use BIOS,
however in the kernel it is required sometimes, for example to do some
disk operations and the like. However all of the
On Wed, 12 May 1999, Greg Haerr wrote:
> The point about ELKS being currently limited to 64k code is a very good one.
> I think we're kind of nearing that limit, aren't we?
We've been over this issue many times.
There are many reasons to limiting the size like this, and that is simply
the fact
On Mon, 10 May 1999, Enzo Humberto De Lucca Alday wrote:
> I dont now so much about computers,i am the tipical student that use the
> computer for text only...
For someone who uses it for text only, why did you use a graphical mail
program which HTML encodes your mail?
In response to your quest
On Sun, 9 May 1999, Alessio Morale wrote:
> Dan Olson wrote:
>
> > Well, I'm sure that your correct in that most Z80s only have <= 64k, but
> > there are some exceptions, such as the TRS-80 Model IV and the Commodore
> > 128 (as the name implies).
>
> But isn't a 65XX based computer the Commodo
On Sat, 8 May 1999, Blaz Antonic wrote:
> > Under Linux, the PIC is shown as using ports 0x20-0x3f, so it's definitly
> > part of the PIC.
>
> Actually it's not. Ports 0x22 and 0x23 are used on many chipsets (mostly
> non-intel chipsets, cyrix/AMD processors settings and stuff like that)
> and d
On Sat, 8 May 1999, Tadayoshi Kubo wrote:
> I know the I/O port No.00-0F is DMA controller and the port No.20-21 is
> interrupt controller. But I don't know how to use the port No22 and 23.
> Anyone know the I/O port No.22,23 meaning on the HP200LX?
Assuming it's simply an 8259, you can find th
Hi all,
I've had a problem recently with my mail which may have caused
some of you to get bounces when sending mail to either me or to a mailing
list. That problem has been fixed, so bounces from me should stop. If
anyone has sent anything directly to me, you'll need to resend it, and
I'
On Wed, 5 May 1999, Jonathan Hall wrote:
> 3) Linux won't tell you the CPU Mhz, but your BIOS should.
Not quite true. There's a trick that the kernel is doing at the moment
which seems to be able to figure out the CPU clock speed. I dunno if
that's coming from BIOS or what, but it looks fairly
On Tue, 4 May 1999, Greg Haerr wrote:
> o Nanogui uses ANSI prototypes that won't compile with bcc, unless
> someone wants my ansi modifications, I'm thinking of releasing it myself.
Try giving bcc -ansi, see what it does.
Davey
On Tue, 4 May 1999, Araujo, Isaque G. wrote:
> Shane, I don't know if you read my old mails which I've sent to Alistair
> Riddoch and to the ELKS-list, but this already exists (BOOTELKS by Steffen
> Gabel), what is need is a effort to change this code for don't write any
> VII, just start ELKS. T
On Mon, 3 May 1999, Alistair Riddoch wrote:
> The problem is that the only disk driver we have working yet is the one
> that uses BIOS routines to access the disk. After DOS is loaded the int 13h
> entry in the VII which initially points to this BIOS routine is replaced.
>
> BootELKS gets round
On Thu, 29 Apr 1999, Wenzel Jakob wrote:
> my palmtop boots from DOS from ROM (argh) and i can't create a boot disk
> for generating the ints.bin file. i need a dos-version of this program
> or perhaps somebody can explain me how to generate this file and I'll
> write the program.
I'm guessing
On Thu, 29 Apr 1999, Dustin Lang wrote:
> Anyways, I have a bunch of EPROMs that I'd like to program, but I can't
> get the silly things to erase. They're supposed to be UV-erasable, but
> I don't have a good source of UV. I tried sunlight but apparently the
> ozone is too thick here. Can anyo
On Mon, 26 Apr 1999, Araujo, Isaque G. wrote:
> The home page: http://www.uk.linux.org/ELKS-Home/index.html is outdated.
http://elks.doa.org/ may have more up-to-date info, try there.
Davey
On Fri, 23 Apr 1999, Brian D Chase wrote:
> I don't want to seem overly abrasive here... but in my totally speculative
> opinion... THERE'S NO WAY IN HELL you could do that in 2K of memory!
You've never seen etherboot, have you?
Hardware driver, IP layer, UDP layer, tftp layer, bootp (or dhcp),
> On Wed, 21 Apr 1999, Damon New wrote:
>
> > I'm using Linux and running a masquerade box you
> > fucker!
Well, in that case 'fucker', go tell someone who cares, like a Linux list.
[EMAIL PROTECTED] might be more appealing to you. (Apologies
to whoever runs that list).
Davey
On Thu, 22 Apr 1999, Joshua E. Rodd wrote:
> The GEM code is neat, and it *is* GPL'd, so maybe we can play
> with it, but it's always more fun to write our own code than
> port. =)
Sure, it's more fun, but if you port code, then you can actually get some
sort of relatively fast turnover of appli
On Sun, 18 Apr 1999, Tobias wrote:
> I remembered reading about that older computers didn't have enough
> memory to handle the TCP/IP stack.
Oops, I wish I'd known that before I used cutcp on my XT for a year.
> -Where the memory limitation is a bigger obsticle than the cpu
> performance, we co
On Sun, 18 Apr 1999, Luke(boo) Farrar wrote:
> An ne2000 is a lot easier to get hold of than an ne1000
I don't know if that statement is entirely true. ne2k is easier because
you can settle for a clone, of which there are LOTS.
Davey
On Sat, 17 Apr 1999, Riley Williams wrote:
> However, I note that the original post specifically referred to the ne2k
> and equally specifically excluded even the ne1k...
Sure. In the same way the ne2k driver excludes the 3c503. It's the same
basic nic chip, but there are little subblties diff
On Sat, 17 Apr 1999, Riley Williams wrote:
> > An ne1000 driver can be done later, but to make sure that
> > everybody can join in for now, the more popular the card the
> > better.
>
> That sort of decision appears to be a geographically based one, so may
> not produce the result you are exp
I can't be bothered replying to all the questions individually on the list
about these two topics, so I'll combine them all into one email.
Firstly, Z80.. ELKS used to support Z80, however support was dropped in
about version 0.0.12 (IIRC). There is no reason at all why the code
shouldn't be po
On Wed, 14 Apr 1999, Tracy Camp (Hurrah) wrote:
> > What happened to the mailing list archives?
>
> if they indeed did disappear I'd volunteer to make them available on my
> server if somebody happens to have them.
I sent my entire archive (since about sept 96) to someone a few months
ago, I had
On Wed, 14 Apr 1999, Jonathan Hall wrote:
> Most cards that don't need the 16-bit bus don't come as 16-bit cards
> with the exception of those cards that are specifically designed
> otherwise.
Actually, there's a reason for some coming as 16-bit. That is simply
because they're capable of using
On Wed, 14 Apr 1999, Riley Williams wrote:
> 1. You refer to an "NE2000" card. Presumably you're aware that those
> normally don't work in an XT as they require an AT style connector
> and the similar NE1000 card with its XT style connector has to be
> used instead.
Firstly, 16-bit
On Wed, 14 Apr 1999, Luke(boo) Farrar wrote:
> > is a PLIP driver for elks availible?
>
> We're gonna need a tcp/ip stack first.
We're gonna need a (working) lp driver first :)
> A plip driver won't be that hard, but we need something for it to sit on.
See above :)
Davey
On Tue, 13 Apr 1999, Chris Starling wrote:
> In the Linux ne2k driver, it checks the card's ROM for a couple of magic
> bytes to positively ID the card. If you're using an el cheapo generic ne2k,
> be aware that sometimes those magic bytes aren't what they should be.
ne2k's aren't the only card
On Tue, 13 Apr 1999, Molenda, Mark P wrote:
> 1) My assumption is that the port of linux to 8086 processors is called
> ELKS. Where would I get a tar for that?
Yep, it's called ELKS. The current tgz is available at Alistairs site,
which is ftp://ftp.ecs.soton.ac.uk/pub/elks/
> 2) How many wor
On Tue, 13 Apr 1999, Tracy Camp (Hurrah) wrote:
> the ne2000 chipset is I believe available from National Semiconductor
> under their part numbers, they have some really good documention on
> programming these chips in PDF format
ne2000 uses the same ethernet controller as wd8003 and 3c503, bein
On Tue, 13 Apr 1999, Luke(boo) Farrar wrote:
> I'm sure you can help. Porting driver's etc. isn't nearly as hard as
> writing one from scratch.
Actually it's not that difficult to write one for scratch (at least for
any 8390 based cards).
> We have the socket stuff so my plan is to hack up a cu
On Mon, 12 Apr 1999, Tracy Camp (Hurrah) wrote:
> there is some VERY small TCP/IP code (6502 assembler) as part of AS/OS65
> which as an entire OS fits in something like 20K. The assember code
> wouldn't be overly useful in and of itself, but it would be interesting as
> an example of how to imp
On Mon, 12 Apr 1999, Joseph Dunn wrote:
> I was wondering if it would be possible to port Linux's TCP/IP software
> to ELKS.
Not really. The linux driver is WAY to big to fit in ELKS. Even the
minix driver (which is made for small memory machines), takes around 50k,
iirc. It would need to be
On Sun, 4 Apr 1999, Ted Pavlic wrote:
> Does anyone know how to limit the amount memory used for disk cache by
> Linux?
Firstly, this is the wrong list to ask it on. Try linux-kernel. I've
wanted to do this for a long time too, and the basic answer is "you
can't". Linux has a nice little bug
On Tue, 23 Mar 1999, Stacy D. Coil wrote:
>uint32 v;
>uint32 m;
> #asm
> mov v, eax
> mov m, ebx
> #endasm
>
> But this returns and no symbol for v and m. Could someone be kind enough
> to show me how to pass varibles from c to assembly and back?
You can't just say "m
On Fri, 12 Mar 1999, Molenda, Mark P wrote:
> I was excited to hear about the 8086 listserv. Is there somewhere that I
> can find a complete distribution for the 8088/8086 PC's?I have both
> an IBM XT and a NecV20 laptop that I could use for light duty.
No. There isn't really a distributi
On Fri, 12 Mar 1999, Dan Olson wrote:
> Just for the record, I'd rather see support for the 3c503 than ppp or
> slip, but unfortunatly I can't say I have either the time or knowledge at
> this point to be of any help, but if that changes in the near future I'll
> do what I can.
Well there seems
On Fri, 12 Mar 1999, Alistair Riddoch wrote:
> > What are the files related to network device?
> >
> > And what network card they support?
>
> The arch/i86/drivers/net files were some test drivers David Murn was
> working on. They are no longer included due t
On Mon, 8 Mar 1999, David Given wrote:
> However, with a copy of DOS and NCSA telnet you can make even the lowliest XT
> into a quite decent network terminal (I've done that). You can get NCSA telnet
> from your nearest simtel mirror.
One thing I've found, is that the cutcp package is better f
On Thu, 4 Mar 1999, Jonathan Hall wrote:
> > Unless merced is some device for the 8086, ELKS will probably never
> > support it.
>
> Merced is Intel's new-fangled attempt at making a good processor (64-bit).
> Quite the opposite of the 8086.
In that case take it off our list :)
Davey
On Thu, 4 Mar 1999, H.Oura FCT Headquarters?? wrote:
> I'm very interested in the development status of Merced/linux.
> If there's someone who knows about that, please inform me.
Unless merced is some device for the 8086, ELKS will probably never
support it.
Davey
On Wed, 3 Mar 1999, Jonathan Hall wrote:
> But for your question... you might look at the card itself and see what
> chipset it uses, then look in the Kernel configuration or in
> /usr/src/linux/drivers/net for a driver that matches the chipset. I've
> found drivers for a few of my cards that wa
1 - 100 of 122 matches
Mail list logo
