RE: OS development
There is another book, called "Linux Kernel Internals", this was may start point on the wonderfull world of Linux. There are two editions: an about kernel version 1 (that's what I get) and another about kernel version 2. /H\j[EMAIL PROTECTED] (=U=) 55-11-3741-3510 '-'Sistema Empresa / SIAL 2000 -Original Message- From: Rod Boyce [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, September 07, 1999 5:00 PM To: [EMAIL PROTECTED] Subject: RE: OS development What about uCOSII book search on any technical book site and you will find the book describing uCOSII. The book and OS was written by a chap called Jean Laprose ( sorry for the misspelling of his name I am doing this from memory). Regards, Rod Boyce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Tracy Camp (Hurrah) Sent: Wednesday, 8 September 1999 03:29 To: Matthew Kirkwood Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: OS development Also a facinating book called the "developement of the BSD 4.4 operating system" not much around that talks about non-unix OSes though. On Tue, 7 Sep 1999, Matthew Kirkwood wrote: 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 on OS/kernel development in general. The Minix book[0] is probably as good a place to start as any. It's quite heavily microkernel-oriented, but that's probably an advantage - otherwise it's very easy to forget that all the world isn't monolithic Unix. After that, you might get some more information from looking at the LDP's "The Linux Kernel"[1] which wil show you how a lot of the stuff in the Minix book is anchored to Linux, and introduce some of the more modern bits which the Minix book omits. Matthew. [0] "Operating Systems: Design and Implementation" by A S Tanenbaum [1] http://www.linuxdoc.org/LDP/tlk/tlk.html Tracy Camp 503.380.3218 Hurrah Internet Services [EMAIL PROTECTED] Consultants to the Networked World http://www.hurrah.com/
Re: get compile error compiling objdump85
Basically, the time-honored FILE * constants stdin, stdout, and stderr are no longer constant. The offending line is: They've never been constants in all cases. done this? It's going to screw up alot of old programs. only broken ones as far as standards believe
Re: ELKS 0.0.79 released
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 case here. The problem with PS/2s is with older version like the 35. I ran elks on a model 50 for over a year as my main test machine without problems. Brief summary: IBM PS/2 model 50Z, MCA bus, 80286 @ 10MHz, 9 megs memory, 40 meg hard disk, VGA display, IBM keyboard and mouse connected, Artisoft network card installed all file i/o is floppy based so far boot and root floppies from the image.zip file (have not compiled my own kernel) boot and root floppies created with the rawrite2 programme from big-linux (Debian) the "please insert root disk" wait works correctly virtual consoles appear to work correctly (Alt-F1, F2, F3) commands ls, ps, cd and so on appear to work correctly lpt port recognised during boot up printing not yet attempted don't recall seeing the serial port mentioned on boot up hard disk recognised during boot up hard disk not yet elks-partitioned or used, but existing dos partitioning is recognised don't recall the network card being mentioned in the startup (not surprised!) No, no network yet. Serial port should have been detected though. What can I do to help with testing? If I have the time, I'll try booting ELKS on an Epson '286 system with a CGA display. However the Epson has 720K floppies so I'll have to get some low density ones with which to experiment :-) Might try to get term.c running before that, on the PS/2. There is loads of code in the elkscmd package most of which compiles, but hasn't really been tested. The most important is fsck, which is going to be essential. I have got it to run fine on clean filesystems under elksemu, but it needs to be tested under elks, and on actual dirty filesystems. Al
missin timezone, and a bcc-cc1 error
Hello I got past the FILE *in =sdtin; problem as a result from the input from this list. I've gotten a bit further. When compiling elksemu/elks_sys.c I get an error in line 557 (and 580?) about the tz size is unknown. I figured the problem was with the struct timezone. So I copied the /usr/include/time.h to the directory edited the file and added the struct from the elks/include/time.h and removed the reference to extern long int timezone. This helped. 1) What have I done wrong in my installation since I had to do this. 2) Wont there be a conflict at link time when there exist a 'struct timezone' and a 'long int timezone' ? After doing a 'make all' from linux-86, I tried doing an /elks/make (after doing make config; make dep; make clean.) But I get the error bcc: 'exec of bcc-cc1 failed' bcc -D__KERNEL__ -O -I../include \ -0 -c -o sched.o sched.c bcc: exec of bcc-cc1 failed bcc: error unlinking /tmp/bcc2248 3) Is this a result of my tampering with time.h ? Or have I gone avry somewhere else ? Thanks Henrik Signup for your FREE ZenSearch E-MAIL account at http://www.zensearch.net and win a Notebook PC
