Re: [Fwd: syntax doc. about as86]
Personally I think if as86 code were converted this way, you keep the as86 users happy. There's another advantage with this means of conversion that I forgot to mention. By using macros to retain compatibility with as86, it's easy to do regression tests to ensure the semantics of the code have not changed. As I convert the code to use my macros, I periodically run this make rule: first: first.S gcc -DUSE_AS86 -E -traditional -o first.s first.S as86 -0 -b first first.s cmp first first.ref where first.ref is a binary saved from a pristine assembly.
Re: corruption of /usr with cfdisk
Put your partition table back exactly as it was before you can delete partitons and re-create them but don't mkfs, dont anything else. Does the fs check ? If so you're saved, you may have to re-run lilo from your panic boot. If you don't know the exact positions you can experiment, you don't normally have to reboot between fdisks. But beware there will be may setups where you get it "almost right", ie it looks like it works but you'll have mysterious corruption. While you're fiddling run e2fsck in read only mode (with -n). If you do 'fix' it you should probably only use it to backup files changed since your last backup and do a full restore afterward. The chances of you getting this right are rather small, you may already have corrupted something serious so if it doesn't fix quite quickly you may as well do "dd bs=1024k if=/dev/zero of=/dev/hda" to clean the disk for a restore from tape. ... Don't tell me; You bought an overpriced graphics card in a nice colourfull box instead of a tape drive ... FX: These people never learn; bye now, I've gotta go change my backup tape. -- Rob. (Robert de Bath http://poboxes.com/rdebath) rdebath @ poboxes.com http://www.cix.co.uk/~mayday On Sun, 5 Sep 1999, Adam C. Siepel wrote: I seem to have managed to corrupt my /usr partition with cfdisk, by impetuously trying to maximize its space (without really understanding what I was doing). Here's what I did. Breathless with excitement to upgrade to RedHat 6.0 on my Compaq Presario 1621 (laptop), which is currently running 5.1, and dismayed that I seemed not to have enough space on my /usr and / partitions for even a minimal upgrade (I'm using a partition that takes up approximately half of a 2 GB drive; other half is Win95), I started poking around for ways of making even just A LITTLE more space. I came across the "m" (maximize) option in cfdisk, which apparently recovers unused space between the partition table and the beginning of a partition, the only cost being a loss of compatibility with OS/2 and Windows. I didn't know how much space I might recover, and I didn't really understand the process, but I rashly went ahead with it anyway. I chose "m", then "w" (for write to disk). Sure enough, something went wrong. I don't remember exactly the message I got from cfdisk, but I went ahead and rebooted, recalling that the cfdisk man page suggested doing so in most cases after adjusting a partition. The system wouldn't boot -- couldn't mount /usr (/dev/hda6 on my system). I dug out my emergency boot floppy, brought it up in emergency mode, and ran fsck. Fsck told me that I had a bad "magic number" in the superblock for /dev/hda6, and recommended running e2fsck -b 8193, to attempt to get to some kind of backed-up version of the superblock (I didn't really understand this). E2fsck (-b 8193) gave me the exact same message, including the recommendation to run itself with the same option. Sensing the possibility of an infinite recursion, I decided to bail. At this point, it is evident to me that I probably could sort of reformat /dev/hda6 (perhaps using mke2fs?), and then reinstall its contents, but of course, I'd rather not do that. I'm in the middle of a big development project (what kind of bozo tries to upgrade the OS at a time like this?), and would like to get my system back up as quickly as possible. At this point, I don't even care about the upgrade to RedHat 6.0 -- I can deal with that later (probably need to get Partition Magic and do some resizing of partitions). I just want Linux running! Anyone know of a way to recover my corrupted partition? Many thanks to anyone who can help! Adam Siepel P.S. /dev/hda6 is a logical partition, in case that makes a difference. --- Adam Siepel phone: (505)982-7840 Software Development Group Leader fax:(505)995-4432 National Center for Genome Resources WWW:http://www.ncgr.org 1800-A Old Pecos Traile-mail: [EMAIL PROTECTED] Santa Fe, NM 87505
Re: [Fwd: syntax doc. about as86]
On Tue, 7 Sep 1999, Thierry DELHAISE wrote: I'm translatting the assembler source code of Linux (as86) to Nasm syntax. I need to understand the syntax of as86 wich is (very??) different from Nasm's one, in particular : movb4(di),*36; (What mean the * prefix of value 36) ; does 4(di) means [di+4] ??? Do you know where I can find any documentation. If not may be I can reach Bruce Evans himself. Hi all, Like part of my previous message will show you, I will apreciate any documentation on as86 syntax, I mean, may be a document where stuff like previous 'movb 4(di),*36' will be explain. The only 'real' documentation is the man page, it a lot better than it used to be but it's slanted to _using_ not decoding somebody else's mess! movb4(di),*36; (What mean the * prefix of value 36) ; does 4(di) means [di+4] ??? Both of these 'features' come from the old minix assembler. The '*' is just like the '#' in normal assemblers except the '*' is supposed to flag a signed as opposed to an unsigned value; as86 does not check this. The '#' flags an immediate value like in every microprocessor assembler before Microsoft spewed out MASM. Are you sure it's round brackets? As86 will not accept () for indirection without the '-a' flag. This flag exchanges the interpretation of the round and square brackets. So the MASMised version is: mov byte ptr 4[DI],36 -- Rob. (Robert de Bath http://poboxes.com/rdebath) rdebath @ poboxes.com http://www.cix.co.uk/~mayday
Re: [Fwd: syntax doc. about as86]
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
OS development
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. Matthew Fredrickson
Re: OS development
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. I know at the university here, they offer a course in OS development. It's a 3 year course I believe, and it covers all the aspects of development, from the theories to actually writing the system/apps. I've been told that it's possible to sit in on some of the lectures of this course, so you might find a university/college near you has similar courses which you may be able to sit in on. Failing that, simply look at ELKS from the very beginning (ELKS 0.0.10 is available, and linux-86 before that), and look at how things have been implemented since then. Davey
Re: OS development
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
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: 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/
Q: get compile error compiling objdump85
Hello I'm just starting into the ELKS system. I'm atempting a make in linux-8086, and I encounter the following error in the ld directory 'objdump86.c:19: initializer element is not constant' I'm running on a Linux Red Hat 6.0 2.2.5-15 #1 Mon Apr 19 22:21:09 EDT 1999 i686 using GCC gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release). I'm using it out the box so to speak. Any idea of what I'm doing wrong ? Or where I should go look ? Where are the gcc error codes explained ? Sincerely Henrik Signup for your FREE ZenSearch E-MAIL account at http://www.zensearch.net and win a Notebook PC
RE: [Fwd: syntax doc. about as86]
: There's another advantage with this means of conversion that I forgot : to mention. By using macros to retain compatibility with as86, it's : easy to do regression tests to ensure the semantics of the code have not : changed. As I convert the code to use my macros, I periodically run this : make rule: : : first:first.S : gcc -DUSE_AS86 -E -traditional -o first.s first.S : as86 -0 -b first first.s : cmp first first.ref : Ken - quite cute. I'm glad you posted this, as I have found myself wondering how to cope with the myrad of idiotic assembler source formats, and how to make sure that as I change continually one to another, when to know I've screwed up. God I wish that the NASM guys would have at least allowed some of the more obtuse forms of source input, so at least we could have used a single assembler, then worked on changing source formats... Greg
Re: ELKS 0.0.79 released
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. 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!) 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. Regards, Denis
