> -Original Message-
> Does anyone know how to convert .pcf files to, say bdf?
> I've found bdftopcf, but I only know how to convert bdf files
> to micro-windows currently.
PCF files, like SNF files, are binary files, but the format is portable
across architectures. The data is stor
On Mon, 28 Jun 1999, Greg Haerr wrote:
> I'm trying to get some more non-copyrighted fonts for micro-windows
> use. I've found a good rom alternative, vga.pcf, which is part of the
> dosemu distribution.
> Does anyone know how to convert .pcf files to, say bdf?
> I've found bdftopcf, but
: I dunno about pcf -> bdf conversion, but if you'd like to use the wealth
: of Linux Console fonts out there, I've written a PSF/ROM font image -> BDF
: converter. It's at http://www.nmt.edu/~bsittler/convfont/convfont.c, and
: it's in the public domain.
Cool. I'll take a look at it,
On Monday, June 28, 1999 12:43 PM, Michael Hope [SMTP:[EMAIL PROTECTED]] wrote:
: > I'm trying to get some more non-copyrighted fonts for micro-windows
: > use. I've found a good rom alternative, vga.pcf, which is part of the
: > dosemu distribution.
:
: A PCF font is pretty much a compiled form
On Monday, June 28, 1999 12:25 PM, Chris Starling [SMTP:[EMAIL PROTECTED]] wrote:
: > This is interesting, I was just getting ready to do this myself. I'm
:running 2.2.5.
: > I would be interested in knowing whether you crash after loading the module, but
:never
: > having run an elks b
> I'm trying to get some more non-copyrighted fonts for micro-windows
> use. I've found a good rom alternative, vga.pcf, which is part of the
> dosemu distribution.
A PCF font is pretty much a compiled form of a BDF font. I have some
documentation on the file format and some code I wrote to con
> This is interesting, I was just getting ready to do this myself. I'm
>running 2.2.5.
> I would be interested in knowing whether you crash after loading the module, but
>never
> having run an elks binary. In other words, is it just the loading or rather the
>execution
> of the emulat
Has anyone else added the ELKS emulation to their Linux system and noticed any
stability problems?
I added the line to my rc.local file to echo "i-elks:" ..blah, blah..
"/proc/sys/fs/binfmt_misc/register" so I could try out the binaries I compile
with bcc. However, my machine doesn't seem to be
Simon Wood writes:
>
> Hello all and sundry,
>
> I'm still plugging away at the Psion port (this weekend didn't see much work
> as it took all of Saturday to put 2 IKEA shelves together, but I did get the
> kernel relocating itself to somewhere sensible).
>
> Next is the 'disk drives' and t
> Next is the 'disk drives' and this is where I'm a little lost. Current
> system uses the block drivers for disk access (presumably because the
> hardware is slow mechanical stuff) and registers interrupts for when data is
> ready (is this right?).
It doesn't have to
> The Psion SSD (memory
On Fri, 25 Jun 1999, Greg Haerr wrote:
> On Friday, June 25, 1999 2:12 PM, Alistair Riddoch [SMTP:[EMAIL PROTECTED]] wrote:
> : Greg Haerr writes:
> : Sounds good. Would be implemented by the compiler, or the pre-processor?
> :
> It would be implemented by the compiler, which would emit
>
Greg Haerr writes:
>
>
> : So form of stack check would be nice, every function call seems a little to
> : much for a lowly 8086. How about on task switch or even interrupt (or is
> : this too late)? If the chosen size for the stack is too small, it can be
> : cured by modifying the binary rathe
Joseph Dunn writes:
>
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_000A_01BEBF0C.5A754460
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> I have a interesting problem to solve. I'm going on a trip in
Greg Haerr writes:
>
>
> : > What exactly is being gained by making this modification? The stack
> : > is fixed size in both cases. Is it just that we currently pre-reserve the
>maximum
> : > combined heap/stack now, and in the future wouldn't require the heap size
> : > to be known?
> : >
: So form of stack check would be nice, every function call seems a little to
: much for a lowly 8086. How about on task switch or even interrupt (or is
: this too late)? If the chosen size for the stack is too small, it can be
: cured by modifying the binary rather than a full recompile.
:
: >
: > What exactly is being gained by making this modification? The stack
: > is fixed size in both cases. Is it just that we currently pre-reserve the maximum
: > combined heap/stack now, and in the future wouldn't require the heap size
: > to be known?
: >
:
: Thats it exactly. Currently
On Thursday, June 24, 1999 6:17 PM, Joseph Dunn [SMTP:[EMAIL PROTECTED]]
wrote:
: Hi,
:
: I just downloaded the latest ver. of Dev86 and Microwin. I built Dev86,
installed it, and then moved on to try out Microwin. I tried to compile it,
but I got an error complaining that two include files, li
On Thu, 24 Jun 1999, Jonathan Hall wrote:
> All MS-DOS machines I've ever used ask for the date and time upon boot.
> This includes all 808x machines I've ever used.
MS-DOS's default action when there is no config.sys or autoexec.bat is to
prompt for date and time.
> So, yes... they do have bui
Hi,
I have a interesting problem to solve. I'm going
on a trip in a few days, and I want to bring the source code to Microwin with my
to browse while I'm on the trip. I'm going to be taking my old 286 laptop.
Obviously the source code files are too big to put on the ELKS combo disk, so I
On Thu, 24 Jun 1999, Alistair Riddoch wrote:
> Luke writes:
> >
> >
> >
> >
> > On Wed, 23 Jun 1999, Greg Haerr wrote:
> > > :
> > > : Now it runs on ELKS, the screen flickers and it says Cannot open graphics.
> > > : This is on a 386 and a pentium.
> > >
> > > You must be using ELKS v
Joseph Dunn writes:
>
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_0020_01BEBE76.2F64B4E0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> I just downloaded the latest ver. of Dev86 and Microwin. I bui
Dan Olson writes:
>
> > > Aren't most of the legacy systems going to have trouble Y2K? I am very
> > > interested if you have a solution/answer because I have a ton of
> > > 8088-10/12MHz systems collecting dust. These systems may be not heading
> > > to dumpster if there such a solution.
> > >
Chad Page writes:
>
>
> There is (was?) some stack checking done at the system call level.
> However, it's not 100% foolproof - if the program gets sp above the
> low-water mark after dipping into bss before the next system call it won't
> be detected.
>
> Now, if you had a magic #
Bart Vandewoestyne writes:
>
> I have followed the instructions that are in the ELKS-FAQ but when I
> trie to compile a new kernel i get the following error message:
>
> ld86: text segment too large for 16bit
> make: *** [arch/i86/tools/system] Error 2
>
> What am I doing wrong here? I'm new a
On Fri, 25 Jun 1999, Simon Wood wrote:
> This E-Mail and any attachments hereto are strictly confidential and
> intended solely for the addressee. If you are not the intended addressee
> please notify the sender by return and delete the message. You must not
> disclose, forward or copy this E-mail
See below
Simon Wood
PS. Please only reply to the list OR to me personally... I only need 1 copy.
Hardware Engineer
Pace Micro Technology plc
Victoria Road, Saltaire, Shipley
West Yorkshire, BD18 3LF
Tel : +44(0)1274 532000 Fax: +44(0)1274 532029
This E-Mail and any attachments hereto are st
Greg Haerr writes:
>
>
> : The function stack_check() in arch/i86/kernel/process.c checks to see
> : whether the stack pointer is less then the brk pointer, and segfaults if it
> : is.
> :
> stack_check() is used by the kernel to see if the user process
> has run out of space, only during
Greg Haerr writes:
>
>
> : I am seriously considering adding this to the kernel, but I am not clear
> : why the linker needs to be tweaked. Surely the linker just deals with the
> : data and bss segments, and leaves the stack and heap to be sorted out at
> : load time?
> :
>
> Well one r
Greg Haerr writes:
>
> : The fixed size stack would probably be best placed just above the bss with
> : the heap above that. This would not require any mods to the linker or
> : binary format, just changes to the kernel.
> :
>
> What exactly is being gained by making this modification? T
>From my memories of a Toshiba 1500 (a desktop Toshiba...erk), a basic XT
clone, and a real IBM PC original release - and some early reviews of the
PC-AT - the only "real-time clock" a PC had was in the form of an add-on
card...either built-in in the case of things like Amstrads or a real card in
> All MS-DOS machines I've ever used ask for the date and time upon boot.
> This includes all 808x machines I've ever used.
My experience has been that any MS-DOS machine with no autoexec.bat will
prompt you for the time and date, of course any machine without a battery
powered clock will simply
Lynx is very large, and we also have no network stack yet.
All MS-DOS machines I've ever used ask for the date and time upon boot.
This includes all 808x machines I've ever used.
So, yes... they do have built-in clocks. They just don't have any battery
to store the time and date.
I imagine it would be more a software issue (OS issue) than a hardware
is
On Thursday, June 24, 1999 3:17 PM, Joseph Dunn [SMTP:[EMAIL PROTECTED]] wrote:
: Hi,
:
: I am wondering how hard it would be to port the lynx web browser to ELKS. Anyone
:have any opinions?
:
: Joseph Dunn
: << File: ATT8.htm >>
How big is it's text, data, bss, and stack, for st
On Thursday, June 24, 1999 4:24 PM, Chad Page [SMTP:[EMAIL PROTECTED]] wrote:
:
: There is (was?) some stack checking done at the system call level.
: However, it's not 100% foolproof - if the program gets sp above the
: low-water mark after dipping into bss before the next system call it
Hi,
I just downloaded the latest ver. of Dev86 and Microwin. I
built Dev86, installed it, and then moved on to try out Microwin. I tried to
compile it, but I got an error complaining that two include files,
linuxmt/time.h and linuxmt/posix_types.h could not be found. I went into
/usr/bcc/
> > Aren't most of the legacy systems going to have trouble Y2K? I am very
> > interested if you have a solution/answer because I have a ton of
> > 8088-10/12MHz systems collecting dust. These systems may be not heading
> > to dumpster if there such a solution.
> >
>
> I suspect the built in h
There is (was?) some stack checking done at the system call level.
However, it's not 100% foolproof - if the program gets sp above the
low-water mark after dipping into bss before the next system call it won't
be detected.
Now, if you had a magic # right after bss and checked th
> I am seriously considering adding this to the kernel, but I am not clear
> why the linker needs to be tweaked. Surely the linker just deals with the
> data and bss segments, and leaves the stack and heap to be sorted out at
> load time?
If you went data bss stack heap then yes it would work out
: The function stack_check() in arch/i86/kernel/process.c checks to see
: whether the stack pointer is less then the brk pointer, and segfaults if it
: is.
:
stack_check() is used by the kernel to see if the user process
has run out of space, only during a system call. If anyone really
Hi,
I am wondering how hard it would be to port the
lynx web browser to ELKS. Anyone have any opinions?
Joseph Dunn
: I am seriously considering adding this to the kernel, but I am not clear
: why the linker needs to be tweaked. Surely the linker just deals with the
: data and bss segments, and leaves the stack and heap to be sorted out at
: load time?
:
Well one reason would be that if the bss segme
: The fixed size stack would probably be best placed just above the bss with
: the heap above that. This would not require any mods to the linker or
: binary format, just changes to the kernel.
:
What exactly is being gained by making this modification? The stack
is fixed size in both c
Sorry - I forgot one other thing. Currently, Micro-Windows doesn't
keep update regions (sets of rectangles that show what portions of
a window need to be updated, and can be used for clipping.)
Because of this, whenever any portion of a window needs repainting,
*all* of it is repainted,
: Yeah Greg, why don't you use some sort of XORmap ? I understand it
: consumes lots of memory but it would allow faster screen refresh (try
: clicking on background window, do it once again and again and you'll
: notice flicker when former background window gets redrawn layer by
: layer). I gues
On Thursday, June 24, 1999 10:44 AM, Eric J. Korpela [SMTP:[EMAIL PROTECTED]]
wrote:
:
: > We also need a stack, and maybe some heap space:-
: > Where does this go and how is it allocated?
:
: Is there process stack overflow checking in ELKS? I'm pretty sure
: I saw checking of the kernel
: Is there any checking on the Stack Size (to prevent it over writing
: the stack)?
:
Not by bcc. Let me know if you'd like me to add stack overflow checking.
: Psion (on SIBO) seem to place a fixed stack at the bottom of the data
: segment (which grows down towards DS:),
I have followed the instructions that are in the ELKS-FAQ but when I
trie to compile a new kernel i get the following error message:
ld86: text segment too large for 16bit
make: *** [arch/i86/tools/system] Error 2
What am I doing wrong here? I'm new at all this, these are my first
compiling-exp
Alan Cox writes:
>
> > I know that the code sized is fixed when an application is compiled, as is
> > the initialised and un-initilised data.
> > This gives us minimum code and data segment sizes.
>
> Yes
>
> > We also need a stack, and maybe some heap space:-
> > Where does this go and how
Eric J. Korpela writes:
>
>
> > We also need a stack, and maybe some heap space:-
> > Where does this go and how is it allocated?
>
> Is there process stack overflow checking in ELKS? I'm pretty sure
> I saw checking of the kernel stack...
The function stack_check() in arch/i86/kernel/pr
Alan,
Sorry to post this to the list, but I am currently unable to mail you
directly because lxorguk.ukuu.org.uk is bouncing my mail.
This is because the mail server here is in the orbs database due to a
problem with the sendmail configuration of another server on the site.
We are currently doin
: I'm not sure about that, X is Pretty Damn Big. Several things in it are
: much more complicated than we want, and some are not the ideal model for
: what we want either (eg. the seperate font server instead of a simple bit
: of code in the server which can load font files from a fixed director
> We also need a stack, and maybe some heap space:-
> Where does this go and how is it allocated?
Is there process stack overflow checking in ELKS? I'm pretty sure
I saw checking of the kernel stack...
Eric
> I know that the code sized is fixed when an application is compiled, as is
> the initialised and un-initilised data.
> This gives us minimum code and data segment sizes.
Yes
> We also need a stack, and maybe some heap space:-
> Where does this go and how is it allocated?
Linux 8086 take
On Wed, 23 Jun 1999, Greg Haerr wrote:
> Sure, if you want to mirrow the Micro-Windows download area,
> use microwindows.censoft.com/pub/microwindows.
Done.
ftp:// or http://(www.,ftp.,)linuxhacker.org/pub/microwindows/
is a nightly mirror of microwindows.censoft.com/pub/microwindows.
It'
Greg Haerr writes:
>
>
> : undefined symbol: _select
> : ^^
> :
> : I cannot for the life of me find the _select symbol anywhere. Is it supposed to be
>in the
> :
> : libc that comes with bcc? If not, where is it? With my present setup, almost
>anything
> :
> : in el
Luke writes:
>
>
>
>
> On Wed, 23 Jun 1999, Greg Haerr wrote:
> > :
> > : Now it runs on ELKS, the screen flickers and it says Cannot open graphics.
> > : This is on a 386 and a pentium.
> >
> > You must be using ELKS version 0.77. Otherwise it won't work.
> > See mwin/server/drivers/sc
Simon Wood writes:
>
> Hi,
> I'm afraid I'm not understanding this.
>
> I know that the code sized is fixed when an application is compiled, as is
> the initialised and un-initilised data.
> This gives us minimum code and data segment sizes.
>
> We also need a stack, and maybe some heap sp
Greg Haerr writes:
>
> On Wednesday, June 23, 1999 1:02 PM, Joseph Dunn
> [SMTP:[EMAIL PROTECTED]] wrote:
> : Hi,
> :
> : I just downloaded ver. 0.0.77. I tried compiling, but got this error:
> :
> : make[1]: Entering directory `/home/jadunn/elks/arch/i86/drivers/char'
> : bcc -0 -I../../../../i
Hi,
I'm afraid I'm not understanding this.
I know that the code sized is fixed when an application is compiled, as is
the initialised and un-initilised data.
This gives us minimum code and data segment sizes.
We also need a stack, and maybe some heap space:-
Where does this go and h
> Try finding the kernel syscall number from the kernel source and then
> finding the syscall.dat file in the libc portion of the devkit. I had asked that
> Al include instructions for doing this with the 0.77 ELKS release, but I haven't
> looked at it yet.
I have to admit i didn't believe anyth
On Wed, 23 Jun 1999, Eric J. Korpela wrote:
> > That's a great idea. How can I get a screenshot of a linux framebuffer
> > system?
> I'm sure the smart-ass answer is 'cat /dev/fb >screenshot'
That grabs the current screen. You probably really want to do:
sleep 2; cat /dev/fb >screenshot
and
> That's a great idea. How can I get a screenshot of a linux framebuffer
> system?
I'm sure the smart-ass answer is 'cat /dev/fb >screenshot'
:)
Eric
: undefined symbol: _select
: ^^
:
: I cannot for the life of me find the _select symbol anywhere. Is it supposed to be
:in the
:
: libc that comes with bcc? If not, where is it? With my present setup, almost anything
:
: in elkscmd compiled OK, so there shouldn't be m
: > change the DEMO= line in Makefile. Micro-windows only has one
: > demo: demo.c. Nano-X has three demos, ../examples/demo.c, landmine.c, and world.c.
: > There are two different makefiles, and you must make clean and start from scratch:
: > Makefile.mwin, Makefile.nanox.
: >
: > Greg
:
On Wednesday, June 23, 1999 1:02 PM, Joseph Dunn
[SMTP:[EMAIL PROTECTED]] wrote:
: Hi,
:
: I just downloaded ver. 0.0.77. I tried compiling, but got this error:
:
: make[1]: Entering directory `/home/jadunn/elks/arch/i86/drivers/char'
: bcc -0 -I../../../../include -D__KERNEL__ -O \
: -0 -c -o bi
On Wednesday, June 23, 1999 3:09 PM, Darran D. Rimron [SMTP:[EMAIL PROTECTED]] wrote:
: > -Original Message-
: > That's a great idea. How can I get a screenshot of a
: > linux framebuffer system?
:
: `cat /dev/fb0 > /tmp/screen`
:
: you can display it by `cat /tmp/screen > /dev/fb0
: How about if you put that and other things like it in some directory on
: your server, and I'll set up a cron job to mirror it every night to
: ftp.linuxhacker.org/pub/microwindows/ ? I'm going to stay late tonight,
: get the CVS set up, and start integrating it.
Sure, if you want to m
On Wednesday, June 23, 1999 2:14 PM, Luke (boo) Farrar
[SMTP:[EMAIL PROTECTED]] wrote:
:
: I just tried nano-X-0.61.
: It compiles now.
:
: I changed the -I /home/greg/net.. blah to /usr/src/linux-86/elks/include
: and it compiled fine.
:
: It hadn't clicked that that was your main elks direct
On Wed, 23 Jun 1999, Greg Haerr wrote:
> :
> : Now it runs on ELKS, the screen flickers and it says Cannot open graphics.
> : This is on a 386 and a pentium.
>
> You must be using ELKS version 0.77. Otherwise it won't work.
> See mwin/server/drivers/scr_bios.c, function VGA_open(), and
On Wednesday, June 23, 1999 11:15 AM, Alex Holden [SMTP:[EMAIL PROTECTED]] wrote:
: On Wed, 23 Jun 1999, Greg Haerr wrote:
: > Attached is my latest cut of nano-X. This includes all the fixes
:
: I grabbed it from the ftp site and was about to mail you to say I'd got it
: immediately before
> -Original Message-
> That's a great idea. How can I get a screenshot of a
> linux framebuffer system?
`cat /dev/fb0 > /tmp/screen`
you can display it by `cat /tmp/screen > /dev/fb0`
How you then convert that to something else, no idea.
-Darran
On Wednesday, June 23, 1999 12:09 PM, Angel Martin Alganza [SMTP:[EMAIL PROTECTED]] wrote:
: On Wed, 23 Jun 1999, Greg Haerr wrote:
:
: > The Micro-Windows ftp site has been updated with
:
: Any screen-shots available? I'm curious to see how it looks like :)
:
: Angel
:
That's a great
Hi,
I just downloaded ver. 0.0.77. I tried
compiling, but got this error:
make[1]: Entering directory
`/home/jadunn/elks/arch/i86/drivers/char'bcc -0 -I../../../../include
-D__KERNEL__ -O \-0 -c -o bioscon.o bioscon.cbioscon.c:142.33 (macro
level 1): error: inode undeclaredbioscon.c:142.3
On Wed, 23 Jun 1999, Greg Haerr wrote:
> The Micro-Windows ftp site has been updated with
Any screen-shots available? I'm curious to see how it looks like :)
Angel
The Micro-Windows ftp site has been updated with
recent patches for ELKS. These fix some insidious
signed integer problems with the bcc compiler,
and include all the fixes from Al, the ELKS maintainer.
In addition, the Micro-Windows desktop wallpaper
pattern was changed (I removed the MS-Windows
All,
Thank you, I will investigate the microwindows information.
Regards,
Greg
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of James Tabor
Sent: Tuesday, June 22, 1999 10:39 PM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Subject: R
> The hw clocks will drop back to 1900 in most cases. Linux itself uses an
>
> if(year < 1970)
> year +=100
>
> rule to correct stuff like that
I've been astonished by how many clocks on old AT compatibles support
date past Y2K. Most won't roll over correcly, but many allow
> I suspect the built in hardware clocks of these machines will not survive
> the rollover, and may not work again afterwards, but assuming the machines
The hw clocks will drop back to 1900 in most cases. Linux itself uses an
if(year < 1970)
year +=100
rule to correct st
Matt Burleigh writes:
>
> Aren't most of the legacy systems going to have trouble Y2K? I am very
> interested if you have a solution/answer because I have a ton of
> 8088-10/12MHz systems collecting dust. These systems may be not heading
> to dumpster if there such a solution.
>
I suspect the
Greg,
Do you have a Web site, like www.
Thanks,
James
Greg Haerr wrote:
>
> I have received some reports that the Micro-Windows site
> isn't working with DNS too well and can't be accessed from certain
> areas. I'm working on this, but can't duplicate it yet.
>
> In any case, the IP addres
: P.S. I noticed that Greg had a 'bcc' directory on the ftp site. Maybe there's a
: new
: bcc version there?
:
There will be a new bcc there, but I've decided to make these
versions work with the existing bcc compiler. I want to make my ansi
advancements to bcc available to others. I'v
: CFLAGS = $(INC) -ansi -DELKS=1 -DUNIX=1 -0 -Dconst= -Dvolatile=
:
: Note also that in the include path there is something like
:
: INC = -I/home/greg/net/elks/include
:
: which is unlikely to be the same on your machine.
:
: With these changes I got quite a bit further, though I'm not yet
On Tuesday, June 22, 1999 1:18 PM, Alistair Riddoch [SMTP:[EMAIL PROTECTED]] wrote:
: Dennis Blazewicz writes:
: >
: > Hello all.
: >
: > I have observed from my (admittedly brief) fiddling that elks has a 14
: > character filename limit. Is there a reason that 14 chars was picked?
: > Big e
On Tue, 22 Jun 1999, Joseph Dunn wrote:
> -Original Message-
> From: Greg Haerr <[EMAIL PROTECTED]>
> To: 'Joseph Dunn' <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
> <[EMAIL PROTECTED]>
> Date: Tuesday, June 22, 1999 12:45 PM
> Subject: RE: Micro-Win Compiling Problems
>
>
> >On Tuesday,
>
>
> I read the install file, and I uncommented the ELKS=1 line in all three
> makefiles, so that's obviously not the problem. I've noticed that bcc gives
> me errors about missing semicolons when compiling other programs too. Is
> this possibly related to the fact that bcc does not understand an
On Tuesday, June 22, 1999 2:01 PM, Joseph Dunn [SMTP:[EMAIL PROTECTED]] wrote:
: -Original Message-
: From: Greg Haerr <[EMAIL PROTECTED]>
: To: 'Joseph Dunn' <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
: <[EMAIL PROTECTED]>
: Date: Tuesday, June 22, 1999 12:45 PM
: Subject: RE: Micro-Win Compi
-Original Message-
From: Dennis Blazewicz <[EMAIL PROTECTED]>
To: elks <[EMAIL PROTECTED]>
Date: Tuesday, June 22, 1999 3:55 PM
Subject: Brief observation from fiddling
>Hello all.
>
> I have observed from my (admittedly brief) fiddling that elks has a 14
>character filename limit. Is
-Original Message-
From: Greg Haerr <[EMAIL PROTECTED]>
To: 'Joseph Dunn' <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Tuesday, June 22, 1999 12:45 PM
Subject: RE: Micro-Win Compiling Problems
>On Tuesday, June 22, 1999 10:34 AM, Joseph Dunn [SMTP:[EMAIL PROTECTED]]
>
Alan Cox writes:
>
> > I have observed from my (admittedly brief) fiddling that elks has a 14
> > character filename limit. Is there a reason that 14 chars was picked?
>
> 14 is the old unix limit. Basically 16 bytes/file - 14 for the name 2 for
> the inode number.
>
> > Big enough to be de
Dennis Blazewicz writes:
>
> Hello all.
>
> I have observed from my (admittedly brief) fiddling that elks has a 14
> character filename limit. Is there a reason that 14 chars was picked?
> Big enough to be descriptive, but small enough for memory reasons?
This limit (which I thought was 15
On Tue, 22 Jun 1999, Dennis Blazewicz wrote:
> I have observed from my (admittedly brief) fiddling that elks has a 14
> character filename limit. Is there a reason that 14 chars was picked?
> Big enough to be descriptive, but small enough for memory reasons?
It was picked because ELKS uses t
On Tuesday, June 22, 1999 12:19 PM, Dennis Blazewicz [SMTP:[EMAIL PROTECTED]]
wrote:
: Hello all.
:
: I have observed from my (admittedly brief) fiddling that elks has a 14
: character filename limit. Is there a reason that 14 chars was picked?
: Big enough to be descriptive, but small enoug
> I have observed from my (admittedly brief) fiddling that elks has a 14
> character filename limit. Is there a reason that 14 chars was picked?
14 is the old unix limit. Basically 16 bytes/file - 14 for the name 2 for
the inode number.
> Big enough to be descriptive, but small enough for me
Hello all.
I have observed from my (admittedly brief) fiddling that elks has a 14
character filename limit. Is there a reason that 14 chars was picked?
Big enough to be descriptive, but small enough for memory reasons?
Also, I've found a strange quirk:
Take any file, we'll call it "test
: Greg - Are you likely to release a version with the changes I sent you, or
: shall I post the patch to the list so that others can give it a try?
:
I'll have a release tomorrow for both nano-X and microwindows that
will work. They will be called nano-X.0.61gh and microwindows-0.81.
Greg
On Tuesday, June 22, 1999 10:34 AM, Joseph Dunn [SMTP:[EMAIL PROTECTED]]
wrote:
: Hi,
:
: I'm not very experienced with compiling or writing C programs. I've
learned C out of a book. I downloaded the Micro-Win program and tried to
compile it with bcc. Bcc went on and on about some semicolon tha
: Each task has a kernel stack stored in its task entry which is 1024 bytes.
: The user space stack are a bit messy at the moment. When a chunk of memory
: is allocated for a process data segment the stack is placed at the top
: of this area of memory so it grows down towards the top of the heap w
Joseph Dunn writes:
>
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_000C_01BEBCA3.27FAEDC0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> I'm not very experienced with compiling or writing C programs.
ELKS 0.0.77 has been released and is available from the usual main sites:-
ftp://ftp.ecs.soton.ac.uk/pub/elks/elks-0.0.77/
ftp://linux.mit.edu/pub/ELKS/kernel/elks-0.0.77/
This release consists of the following files:
elks-0.0.77.tar.gz - Kernel source
elks-
1 - 100 of 126 matches
Mail list logo
