Phil Kos writes:
As Alan says, the standard libc build already splits each C file into lots
of .o files, one per function, which are the bundlued into libc.a.
Gee, I sure hope not... .c files should *never* turn into multiple .o files.
Any .c should be converted by cc (cpp/cc1/as) into
Mireles-Cordova, Ricardo writes:
According to ELKS FAQ Q1.2
... swapping, shared libraries, parallel and serial I/O, and
networking.
are not available.
As others have mentioned serial and parallel do work to some degree. There
is no swapping yet, but I have been working over the
Louis Paul Santillan writes:
I'm not sure about the Psion, but Sharp 100x or 100LX handhelds,
according to someone on the DJGPP list, have a x186. They were asking
if it is possible to port DJGPP to 8086/8088 code generation but the
person was directed to DJ's little port which is still
John Oram writes:
Al:
Send a request to the PoqetPC mailing list and ask if someone in england
has one. The Psion seems to be the big deal over there, from what I read
on this side of the pond.
Send personal email and I may be able to help you out.
Psion are very big here, and I
Blaz Antonic writes:
Please report back to the list including information about any software you
can get to work.
Just FYI, serial with ioctl()s will probably be debugged in few days and
working as expected along with simple dumb terminal program that doesn't
use select() (it uses
Robert de Bath writes:
Almost as is, I've merged in a patch that allows read or write access
depending on the permissions that the user running it has. So
non-superuser read access is still allowed.
I spotted this very shortly after sending you the patch, and had a feeling
I was going to
Beau Kuiper writes:
Yeah, isn't it about time we all forgot about this off-topic stuff. No
matter what
we do, we will always get off-topic posts from newbies, ppl with nothing
better to do,
and ppl who don't know better. The traffic generated by all these replies far
outweighs the
David Given writes:
[...]
We create a meta driver called something like the user device driver which
has a whole load of generically named devices in /dev/udd0 -- /dev/uddn.
[...]
while ((y = ioctl(x, UDD_WAIT_REQUEST, bar)) == 0) {
process_device_request(bar);
}
David Given writes:
what if the module had a list of function pointers at the begining of its
address space? then a snippit of org 0 asm code (well, actually just
data) could be used within each module to set up the pointers properly in
a 16 bit link, and the same asm stubs in the
Blaz Antonic writes:
Thinking in the bath last night I came up with a way of building user space
How romantic :-)
We create a meta driver called something like the user device driver which
has a whole load of generically named devices in /dev/udd0 -- /dev/uddn.
It is a nice idea
Shane Kerr writes:
I'm fairly excited about the plans to incorporate loadable device drivers
in ELKS. Unfortunately, after I thought about it, they STILL won't help
me get my HP 200LX booted. :(
The problem is that there is neither a floppy drive nor a hard disc on the
machine, which I
David Murn writes:
On Tue, 16 Feb 1999, Alistair Riddoch wrote:
A single make command can now be used to build a complete filsystem image,
or a (nearly) bootable floppy image, including configuring and
building the kernel and bootblocks code.
How was this different to before? Make
Simon Weijgers writes:
On Tue, 16 Feb 1999, Alistair Riddoch wrote:
elkscmd.tar.gz - Compressed user program source
The user command package elkscmd has been re-organised in preparation for
inclusion in the CVS system. The old sash/stand-alone directory is now
Simon Wood writes:
Hello all,
I'm new to the list and was wondering what the 'state of play' is for those
alternative bits of hardware, in particular the Psion 3a.
I wouldn't be suprised if no code existed, but has any foundation work been
done w.r.t. how ELKS might be implemented on a
Araujo, Isaque G. writes:
Hi guys,
I left the list for half year more or less and now I'm joining you
again.
I'd like to know if somebody got to run ELKS on HP200LX and how he
did it.
Getting ELKS to run on palmtops is one of my areas of interest. I am
currently working with
Hyung Goo Lee writes:
Hi
I'm a man with problem when compile elks-0.0.75.
Yesterday I show my error message, and Blaz Antonic advised (thank you)
First, do not use any of direct drivers. Use BIOS HD and FD driver.
I tried as he said, but I still have the same error message.
So I
=?EUC-KR?B?wMzH/LG4?= writes:
Hi
I'm new to ELKS, and very excited as you were. :)
I hope that I will be able to see a continued improvement of this
mailing list.
Now I ask you a question.
I've got the elks-0.0.68.tar.gz, and I have two queries about this
source.
What are
Simon Wood writes:
As 'Linux' is the current craze :-) then it seems appropriate to update the
very outdated web page - the people have a right to know what is going on
with ELKS, and perhaps some of them will be able to offer coding time
towards the project.
Secondly regarding Psion
Hi,
Here is the early port of fsck.minix.c from the Linux utils package. This
will be included in the next ELKS release, and I will check it into CVS
tomorrow. I have tested it under elksemu where is seems to work under some
conditions. Please give it a try and see whether it works for you.
The
=?ISO-8859-1?Q?Fr=E9d=E9ric_Renet?= writes:
I have written a SLIP/IP/ICMP/UDP-stack that fits in 2000 bytes program
and 36 bytes RAM (not KILObytes) including operating system and device drivers,
that fits in a PIC 16F84.
So it isn't a problem to implement networking in limited
Alistair Riddoch writes:
I agree about GEM. The late ST version which were supposed to run on a
multitasking OS were not well suited to it.
One of the more promising possibilities is the nanogui project found at
http://www.linuxhacker.org/nanogui/
This is designed to be as small
Simon Weijgers writes:
On Tue, 27 Apr 1999, David Murn wrote:
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.
I'm afraid it's not online yet.
Alistair Riddoch writes:
Simon Weijgers writes:
On Tue, 27 Apr 1999, David Murn wrote:
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
Perry Harrington writes:
We could really do with a tool that looks at the vector interrupt table
so we can try and sort out how to boot ELKS on these strange palmtop
machines. It may be possible to load ELKS from DOS without replacing the
VII on some machines.
There are a couple
Wenzel Jakob writes:
We could really do with a tool that looks at the vector interrupt table
so we can try and sort out how to boot ELKS on these strange palmtop
machines. It may be possible to load ELKS from DOS without replacing the
VII on some machines.
Al
This would be great.
Hi all,
I have fixed the code surrounding select(2) and checked the changes into
cvs. Anyone who is interested please give the code a try. I was using the
tty_select() function for the purposes of testing because I could not think
of another one that would work.
Getting select(2) to work
Greg Haerr writes:
Alistair -
I've got the nanoGui project moved up quite a bit. It now runs the sample
programs pretty well. As Alan mentioned, I'll be checking all this stuff in shortly.
I look forward to looking at the code.
I've also made a makefile option that allows the
Li Rong writes:
Hi, Everybody,
I'm a newbie for this discuss group. I have developed
a intelligent network interface card using Amd186 micro-
controller and AMD Pcnet 10Base-T network controller.
I am looking for a embedded linux-like system supporting
TCP/IP stack. I reviewed the
Eric J. Korpela writes:
o MSDOS driver support. I wrote a 640x480x16 color driver in about 45 minutes.
NanoX now runs on DOS! (OK, I did this only to see how portable nanoX
is, and the
mouse driver still isn't written) This still uses MSC graphics library.
I'll have the bios
Greg Haerr writes:
On Tuesday, May 11, 1999 8:06 AM, Alistair Riddoch [SMTP:[EMAIL PROTECTED]] wrote:
Li Rong writes:
Hi, Everybody,
I'm a newbie for this discuss group. I have developed
a intelligent network interface card using Amd186 micro-
controller and AMD Pcnet
Diversia writes:
Hi all,
Where can I find the newest ELKs, for I can't find it on the ftpsites
yet...
Erik (AKA Diversia)
It is available from the two sites mentioned in the announcement. I only
announce new releases after I have verified that I can download them.
The URLS are
David Given writes:
[...]
This is a kernel only release. For userland sources and binaries, and disk
images please see release 0.0.75.
[...]
We have pipes, and signals, and select() --- this sounds suspiciously as if we now
have a kernel that's actually usable. All that's needed now is
David Given writes:
[...]
This is a kernel only release. For userland sources and binaries, and disk
images please see release 0.0.75.
[...]
We have pipes, and signals, and select() --- this sounds suspiciously as if we now
have a kernel that's actually usable. All that's needed now is
Jacek Lipkowski writes:
On Sat, 29 May 1999, Alistair Riddoch wrote:
Any thoughts anyone?
i thought about this some time ago. if you had enough ram, you could put
elks in an eprom (or actually two eproms - the xt used 32k eproms if i can
remember correctly). during start you could
Simon Wood writes:
The advent of nano-X and graphics under ELKS, together with this discusion
has set me thinking more seriously about ROMing ELKS.
In the bath last night (as always) I thought about how I could modify ELKS
so it would run without a filesystem, and came up with a way
Luke writes:
On Tue, 25 May 1999, Sven 'Zak' Kozma wrote:
Hi Greg
Wow, I didn't realize that ELKS once ran on z80's! What is the zcc
Maybe ...
compiler that you're talking about? Is the src available? What is scc?
Scc is a SmallC Compiler for the z80. SmallC
Luke writes:
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
Thor Harald Johansen writes:
It is included in the standard distribution in binary form on the root
disk, and as source in the elkscmd package.
How do I make it the default shell?
You could do the following:-
mv /bin/sh /bin/sash
mv /bin/ash /bin/sh
which does exactly what you want,
[EMAIL PROTECTED] writes:
Just a Question:
How hard is it to create an ELKS distribution? I am thinking of creating
one, since there seems to be interest on the list for one, and bluebell
seems o have been erased off the face of the planet.
Shouldn't be too hard to start off with.
Ross Vandegrift writes:
Tell me of another editor. :)
You're not going to like your more reasonable options, but I'll be blunt: vi
or ed should work nicely, when ported.
Why would anyone want to use any editor other than vi?
Al
ZZ
Thor Harald Johansen writes:
I can remember when I used to find vi awkward to use, but now I find all
other editors cumbersome and inelegant. Best not to get into a debate
about
it here, but I remain firmly in the vi camp.
You'd actually use an editor like that for word processing?
Greg Haerr writes:
On Tuesday, June 01, 1999 2:07 PM, Alistair Riddoch [SMTP:[EMAIL PROTECTED]] wrote:
: Ross Vandegrift writes:
:
: Tell me of another editor. :)
:
:
: You're not going to like your more reasonable options, but I'll be blunt: vi
: or ed should work nicely, when
Greg Haerr writes:
: Bcc. I think that its one of the things that needs porting the most. Why?
: Here's why.
:
: ELKS is shaping up quite nicely. We have a useable unixish system. But I
: think that it needs certain things:
:
:
: A C compiler.
I have had as a top
Greg Haerr writes:
On Thursday, June 03, 1999 7:27 PM, Alan Cox [SMTP:[EMAIL PROTECTED]] wrote:
:This brings up my wishlist again, that we should have bcc compiler
: support for medium and large models for x86. Al Ridoch doesn't want to
: move to supporting the _far keyword. I think
Greg Haerr writes:
Al,
I worked on getting up to date this weekend on the linux-86 devkit (v0.14.8)
and ELKS (v0.77). After quite a few compile time problems, I got everything
compiling and working. I'll detail the problems later, and submit a patch.
I can't get
Thomas D Stewart writes:
I downloaded dev and elks to make the kernal. Made and ran the kernal
with no probs.
I then downloaded elkscmd and tryed to compile it, i am pritty new to
linux so i am not sure what is wrong.
These are the errors that i get when i do "make all":-
make[1]:
Greg Haerr writes:
I will be releasing another update to Micro-Windows shortly. This version
will contain the following additions/enhancements:
o Single makefile for ELKS and Linux makes. Previously, three
makefiles had to be modified for ELKS vs Linux making. Fixed bogus
David Murn writes:
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
Greg Haerr writes:
Al,
I have added the clock program to MicroWindows v0.82, which
I will release shortly.
It's pretty cool! Anyway, I have a couple comments. I changed
the color model to RGB a while back, so any function that takes a GR_COLOR,
like GrSetGCForeground, must
Greg Haerr writes:
I have released another version of Micro-Windows, which allows
Basically it compiled cleanly for me, and worked under both systems. The
only problem was that there is a C++ style comment at line 432 of winuser.c.
I still can't move windows under microwindows, in XOR or
Simon Wood writes:
Hi all,
I've been reading up about how to use a CVS server... I think I ought to
have a go at the practical side of things.
Is the Elks CVS server functioning and if so where is it?
I have finished sorting out the Makefiles based on the changes you sent me.
I fixed
Simon Wood writes:
Hi Alistair,
I'm afraid you are going to have to baby talk me through the CVS stuff. For
the modules of the Gnome stuff the documentation says you do:
export CVSROOT = ':pserver:[EMAIL PROTECTED]:/cvs/gnome
cvs login (though only the first time!)
Hi all,
I have just spent the day hacking, and have finished off some bits and
pieces, and commited them into CVS. As CVS mail reporting doesn't seem to
be wroking while doa.org is down, here is a summary of what I have
commited.
Tweaked the bioshd driver to make sure it still works when hd is
Greg Haerr writes:
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.
This is because sash does not catch SIGINT. This is fixed in the next
release.
Al
Scott Lanning writes:
On Tue, 13 Jul 1999, Alistair Riddoch wrote:
Clean your source tree using 'make distclean', and then do 'make config'
I see my mistake now. I initially used non-default options, then
it didn't work, so I did 'make clean' instead of 'make distclean'.
It compiled fine
Greg Haerr writes:
MicroWindows version 0.83 is released at
ftp://microwindows.censoft.com/pub/microwindows
This version of MicroWindows is released in tandem with Al Riddoch's ELKS v0.78,
which fixes a kernel select() bug with certain mice.
The ChangeLog for this version is:
Greg Haerr writes:
Al,
After receiving ELKS v0.78, I compiled Microwindows and Nano-X for
it and found we need one more kernel patch, and have several other items
in elkscmd, some of which were missed. Overall, ELKS 0.78 is a great step
forward for ELKS and MicroWindows.
Scott Lanning writes:
~elkscmd/sash/sash.c, line 382,
#ifdef CND_ALIAS
should be
#ifdef CMD_ALIAS
Anyway, CMD_ALIAS is not defined (c.f. sash/config.h).
Thanks for the patch, it is now integrated.
Al
Luke writes:
In the mtools directory there was this readme:
8
mtools - tools to read msdos floppies from unix pc
Compiled with a couple of tweaks, but cannot read disks, even under dosemu.
Al ([EMAIL PROTECTED]) Sun 11 Oct 1998 16:20
8
I
Greg Haerr writes:
:
:
: I tried to make a 0.0.78 kernel than and got this error:
:
: make[2]: Leaving directory `/usr/local/src/elks/arch/i86/drivers/block'
: bcc -D__KERNEL__ -O -i \
: 2 -nostdinc -Iinclude -c -o boot/crt1.o boot/crt1.c
: boot/crt1.c:5.25: error: cannot find
I have have had a go at implementing vfork() for ELKS as I thought it would
gain us quite a lot in lower overhead for running processes. I have managed
to get a version of vfork() working as follows.
The parent process's data segment is not copied, just re-alloced, and
rather than returning to
Eric J. Korpela writes:
: The parent process's data segment is not copied, just re-alloced, and
: rather than returning to the parrent process, fork sleeps on the parents
: child_wait wait queue.
Let me try to remind myself of the vfork semantics Basically,
rather
Greg Haerr writes:
: This is essentially what I have done. The only problem with doing this is
: that when fork() returns to the child, and the child calls exec(), the stack
: will be modified, so when the parent comes to return from fork(), it will
: crash, or at best do something odd.
ObiTuarY writes:
Hello,
I don't know if any of you have seen the screenshots of Seagull (a GUI for
FreeDOS currently in development). This GUI is entirely ASCII/ANSI based
and it's incredible what they have been able to do. Check out the screenshots
on the FreeDOS website
Greg Haerr writes:
I'm not sure of the best way to fix this (some constants should
: be passed for the "dir" and "perm" arguments, I guess). Maybe
: someone more familiar with this code can offer the correct fix.
:
:
: Yep, definitly a bug, which might explain some of the bizare
Soete Joel writes:
Without knowing exactly to whom have I to send and or request
information, I submit you following remarks; hopping that it will be
helpful:
As I just recompile elks and elkscmd (together referenced -0.0.78) to
create a combine image to try on an old "portable" Toshiba
Thomas G. McWilliams writes:
Hello all,
In [elks 0.78] fs/select.c there is a problem in sys_select() at
lines 344 and 345:
timeout = ROUND_UP(get_user(tvp-tv_usec),(100L/HZ));
timeout += get_user(tvp-tv_sec) * (unsigned long) HZ;
Note that get_user() is a macro based
Greg Haerr writes:
: I am not quite sure whether this is the best way to proceed. It would make
: ELKS easier to find bugs in, but the -ansi option to bcc is not a very
: clean solution to wanting to convert the code to ANSI. The other thing is
: that it may make it harder to build the code
ELKS 0.0.79 has been released and is available from:-
ftp://ftp.ecs.soton.ac.uk/pub/elks/elks-0.0.79/
ftp://linux.mit.edu/pub/ELKS/kernel/elks-0.0.79/
This release consists of the following files
elks-0.0.79.tar.gz - Kernel source
elks-0.0.79.diff.gz - Differences from
Denis Brown writes:
Hello.
For what it's worth, I have been able to run ELKS 0.0.79 on an IBM PS/2
without any hassles. I seem to recall discussion on this list a while ago
suggesting that some oddities with the PS/2's keyboard or mouse port
created hassles. Happily that is not the
Louis P. Santillan writes:
Hello everyone,
Any word on someone trying to port ELKS to the new "upgradable" TI's, like
the 83 and 85/86 (not sure which)? That would be cool. They are called
the plus series I believe.
From TIs web site it looks as though these machines have Z80
Patrice Kadionik writes:
Hi all,
I intend to reuse very old pcs under linux and discovered ELKS :-)
I'm looking for a howto on ELKS installation more detailled than the FAQ on the
ELKS site ? Has anybody pointers on it (tutorial, howto, manual...) ?
I am afraid there is no more
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 entries
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... :)
snip 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 work.
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
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
(floppy, a
Greg Haerr writes:
: 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
Thomas Stewart writes:
hi
This many be a stupid idea,
As far as I know consoles on linux are seperate, ie each can run diffrent
proceses independent of each other?
Is this the same for ELKS? (using the f keys)
In my elks machine I have a vga card and a herc card, how can I use both.
Luke writes:
On Tue, 28 Sep 1999, Greg Haerr wrote:
: Or is there a better way to use the two cards together? DOS does not do this
: very well (appart from a few utills that switch the screen, and a few apps
: that support it (tcc).)
:
: There is no current support
Christopher Kovacs writes:
On Tue, Sep 28, 1999 at 10:22:00AM +0100, Alistair Riddoch wrote:
Thomas Stewart writes:
Or is there a better way to use the two cards together? DOS does not do this
very well (appart from a few utills that switch the screen, and a few apps
that support
Greg Haerr writes:
: Is it as simple as having a VGA card and a herc, and just writing to them
: both separatly? I would have thought there would be problems with
: initialising the hardware, and detecting which was present.
I think it's this easy. the bios in some location
Leonardo Sampaio Cardoso writes:
Hi guys! I am taking the microprocessors class at the
university. My professor wants us to build a small system using the
8086. I thought it would be real cool to get elks running on this
system. My question: Is it possible to get elks to fit in
Hi,
Recently I have become much more interested in the possibility of running
ELKS on actual embedded systems, rather than a Linux for old PCs. I have
no plans for cutting down development of Linux-8086, but would like to add
options to the kernel config to make it possible to build a system
to check a whole load of changes in at once, which I don't like
doing, but it was unavoidable in this case, so here is the CHANGELOG entry
for these changes:-
--
Tue Oct 26 14:24 BST 1999 Alistair Riddoch [EMAIL
David Given writes:
[...]
I have had to check a whole load of changes in at once, which I don't like
doing, but it was unavoidable in this case, so here is the CHANGELOG entry
for these changes:-
[...]
Excellent! So, how are we getting on on the stability front? Can you actually
do
Greg Haerr writes:
Also, on another note, in catching signals in Linux from the terminal
emulator, I attempt to send them to the process group with killpg().
This routine under ELKS causes an undefined symbol getgpid() when
linking. It appears there's an error in linux-8086 libc.
I have
[EMAIL PROTECTED] writes:
Hallo everyone,
I found a few problems installing/using ELKS on an Amstrad PPC640 and I could
not solve all of them. I also have some additional trouble in a xdos window
(dosemu 0.98-8).
Here is a description of what I did and which problems I encountered, I
Larry Howard Mittman writes:
I have an old ATT PC6300. It has 640Kb RAM and a 40Mb RLL Hard
drive. The processor is a NEC V20. I would like to use the machine
for something other than a oversized door-stop.
1) Will ELKS work on this machine?
Yes, almost certainly.
Larry Howard Mittman writes:
Taken from the ELKS web site - road map page
After 0.1 more elaborate features will be added, in particular
networking. At this stage it may be desirable to maintain a 0.1 stable
series, and do all new development in the 0.2 series. It may reduce
confusion
Greg Haerr writes:
5) I compiled elvis and it does run. well, this is a bit of an
exaggeration:
undo doesn't work and sometimes I have to kill the process from my root
session. after this, I get no more echo to the console where I was
running
elvis. I can do exit and login
Alan Cox writes:
The only reason I suggested using 0.1 as the stable tree is because we are
currently heading towards making 0.1.0 a stable version.
Well we've never applied any idea of stable/not before 1.0 to mainstream
Linux. I think tradition is 0.x = unfinished
The problem with
[EMAIL PROTECTED] writes:
I'm sorry for having caused this confusion: the correct version of my (7) is:
7) (this is specific to xdos (dosemu)) the cursor keeps blinking at one
position on the screen, around (0,19). I can do whatever I want, everything
works but the cursor stays there.
Greg Haerr writes:
On Thursday, October 28, 1999 10:33 PM, Scott Dudley [SMTP:[EMAIL PROTECTED]] wrote:
:
: I was unable to build Dev86 on Red Hat 6.0 and saw reference to same in the
: ELKS FAQ. Good news! If you install the following RPM's, you can set
: CC=i386-glibc20-linux-gcc and
Hi all,
I have uploaded the latest snapshot of the elksmcd package to:-
ftp://ftp.ecs.soton.ac.uk/pub/elks/elkscmd
ftp://linux.mit.edu/pub/ELKS/elkscmd
This is a minor update with two small bugfixes, and a change to the way the
root filesystem template is handled.
Al
Scott Dudley writes:
Well, as I've had no bites on my boot loader inquiry, I can only assume it's
not yet been done(?). To reiterate, I'm interested in being able to boot
ELKS from an MFM or RLL HD without having to boot from floppy. I'm not afraid
to roll up my sleeves and get dirty if
Thomas Stewart writes:
I have installed Ret Hat 6.0 with Gnome and KDE.
Thats what I use, did some one metion yesterday that dev86 is allready
installed with rh6?
That was 6.1
Al
[EMAIL PROTECTED] writes:
first of all, sorry for this awful mailer. Banyan BeyondMail at office.
then:
I'll try again with the comb-making-procedure. if you say it works, it has to
work here too! maybe I missed some error message.
to the points:
(1: init) maybe I could help somehow?
Scott Dudley writes:
Compiling with bcc, I'm getting the error "error: initializer too
complicated". It's in a function prototype. What should I look for?
bcc does not like function prototypes. Try specifying the -ansi flags
which tells bcc to remove the code through a prototype
ELKS 0.0.80 has been released and is available from the following sites:-
ftp://ftp.ecs.soton.ac.uk/pub/elks/elks-0.0.80
ftp://linux.mit.edu/pub/ELKS/kernel/elks-0.0.80
This is the first release for a while, and it contains a number of
significant bug fixes:-
The bug that meant that the floppy
kees writes:
Hi There,
I downloaded elks version 0.8. and the images.zip.
I wrote the comb file to a floppy, trying to boot it gave "Boot failed"
I build the Image file, wrote it to floppy. It boots but all ends after:
...:
Is there someone who can help me
1 - 100 of 161 matches
Mail list logo
