Alistair Riddoch wrote:
> On Wed, Feb 09, 2000 at 09:11:08PM +0100, Mario Frasca wrote:
>
> > By the way, I tried to modify exec.c in order to have it look at the suid
> > bit (I don't want to become root to run mount), but my modifications didn't
> > cause any change. There is surely a mistake
Shadow Daemon wrote:
> Personally, I think it would be more to ELKS's benefit, as far as
> filesystem support goes, to concentrate on MSDOS FAT16 compatibility.
is anyone working on this? It shouldn't be that difficult, that file system
is extremely simple and rather well documented.
As far as
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
: Basically, its simply a binary format handler, which simply processes the
: exe header from a file, and claims that its valid or not. It was more an
: excercise for me learning how to parse exe headers.
Yes. I'm quite familiar with MSDOS EXE format and the current
code doesn't do anything nea
be used for putting an EXE header on a binary.
> How compatible and with what versions of DOS?
I dont think its compatible at all. I dont think it even works.
> What is its current status and where is it going? Who is doing it?
I dont think it was ever really seriously going. Feel fre
I'd be interested in any information/documentation on the MSDOS binary compatibility
in ELKS. What purpose does it serve in the project? How is it being accomplished?
What could it be used for? How compatible and with what versions of DOS? What is its
current status and where is it
Personally, I think it would be more to ELKS's benefit, as far as
filesystem support goes, to concentrate on MSDOS FAT16 compatibility.
Perhaps even a UMSDOS-like approach would be in order.
Who is working on DOS binary compatibility? Is that still an active
project?
-matt balaun
- - - - - -
A while ago someone, (I can't remember who) copied off the minixfs code into
the elksfs directory to develop a new filesystem. Nothing has happened with
this code for a while now, and as far as I am aware it currently doesn't do
that minixfs does not do. It has also fallen behind the rest of the c
On Fri, 03 Dec 1999, Alistair Riddoch wrote:
>> Is the linux-8086 list up?
>
>Seems to work fine as far as I can see. How long since you have had
>anything from the list?
About a week(?)...
>
>Al
--
Regards,
Scott Dudley
Scott Dudley writes:
>
>
> Is the linux-8086 list up?
Seems to work fine as far as I can see. How long since you have had
anything from the list?
Al
Is the linux-8086 list up?
--
Regards,
Scott Dudley
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!)
>
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 f
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?
>
The CVS server is on elks.doa.org, which is not currently available at that
add
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?
Simon Wood
Hardware Engineer
Pace Micro Technology plc
Victoria Road, Saltaire, Shipley
West Yorkshire, BD18 3LF
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-t
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
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. I'll work on that very soon.
M
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
Hi,
how is the status of the project ? What is the latest version ?
The home page: http://www.uk.linux.org/ELKS-Home/index.html is outdated.
Isaque.
I am new to the Elks Project. I have an AT&T PC6300 (8086 clone machine) that I
would like to eventually network with my Linux machine. What is the current
status of ELKs, how useful is it, and what do I need to do to implement it? I
assume I have to at least compile the kernel, but what
21 matches
Mail list logo