Linux-Development-Sys Digest #44, Volume #8 Tue, 25 Jul 00 04:13:20 EDT
Contents:
Re: How to read BIOS info in Linux? (bill davidsen)
Re: kernel compile issues (bill davidsen)
Re: Can i get a MAC address ? (Michael Meissner)
Info on a segmentation fault... (Chris Quinn)
Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC ([EMAIL PROTECTED])
Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC (Kaz Kylheku)
Re: How to wait for TCP data to be ack'ed? (Grant Edwards)
[Question]gdb remote debugging on arm-based system (Krik Lee)
Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC ([EMAIL PROTECTED])
Port Emulator.... (8623805)
Re: SCO emulation mode??? (Lew Pitcher)
Re: How to read BIOS info in Linux? (Tim Roberts)
Re: Linking against libstdc++.so (Markus Pietrek)
Re: How to read BIOS info in Linux? (Marco van de Voort)
Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC (Marco van de Voort)
Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC (Marco van de Voort)
Re: Question about after upgrading kernel (Marco van de Voort)
Re: A good IDE (cLIeNUX user)
orainst not running ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: How to read BIOS info in Linux?
Date: 24 Jul 2000 23:13:14 GMT
In article <[EMAIL PROTECTED]>,
Jay Miller <[EMAIL PROTECTED]> wrote:
| Hi there. I was hoping there was some standard way to read BIOS
| information through Linux - any nonstandard ways are fine, too.
|
| If anyone has any ideas, I'd be very grateful. Thanks in advance!
The only info you can get easily is the CMOS contents, there's a
kernel option for that. Since Linux doesn't use the BIOS after boot
there's little useful stuff to read.
--
bill davidsen <[EMAIL PROTECTED]> CTO, TMR Associates, Inc
There are those who make things happen, those who watch things happen,
and those who wonder what happened.
-- idea from _Pickles_
------------------------------
From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: kernel compile issues
Date: 24 Jul 2000 23:22:43 GMT
In article <8lfsj7$hig$[EMAIL PROTECTED]>,
J. Roe <[EMAIL PROTECTED]> wrote:
| I have Red Hat 6.2 and kernel version 2.2.14-5.0.
| The kernel that is set from the initial install loads fine for me.
| However when I try to recompile the kernel I get major problems with
| things failing to startup or the kernel just freezes up all together.
| So, for example if I'm trying to compile support for my zip drive, then
| things like my eth0 fails to load, and my sound module fails to load.
| And I didn't touch these options when running the xconfig.
If you got your source from the Redhat CD that's passing strange. If
you downloaded a kernel that's no surprise.
| I was assuming that when I run make xconfig the options are ones that
| are set for my already working kernel. However, is it correct to say
| that this isn't the case? That these are arbirtrary values rather?
Depends on where you got them. The original configs are in the
something/config directory. Note that in the past Redhat has shipped a
Redhat kernel, not a Linux kernel, meaning that they have applied
patches to the released source from kernel.org.
| My problem is I'm not having any luck recompiling the kernel to suit my
| computers needs. And I really don't know enough to go through every
| option in the xconfig and set it correctly for my system. Is there a
| way to determine the settings for the kernel that works for me now and
| then when I run xconfig to set all those values the same and then work
| from there?
If this is the RH source, get the config from CD or config directory.
If this is an upgrade kernel, copy the RH config to .config in the linux
base directory and 'make oldconfig' which will ask only about stuff you
didn't set before. Then run make menuconfig and change what you must.
I think you really need to get the RH config, you don't sound ready to
do every option from scratch, and may never need to be.
--
bill davidsen <[EMAIL PROTECTED]> CTO, TMR Associates, Inc
There are those who make things happen, those who watch things happen,
and those who wonder what happened.
-- idea from _Pickles_
------------------------------
Subject: Re: Can i get a MAC address ?
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 24 Jul 2000 20:13:36 -0400
[EMAIL PROTECTED] (Chris J/#6) writes:
> To my knowledge some advanced cards as well as some UNIX workstations
> allow a user to change the MAC through software. Dunno the reason for
> this, but in the case of where some software uses the MAC as part of its
> licensing, it saves you having to relicense if the card is replaced :)
As I recall, in the days of yore, DECNET required the Mac address to be in a
range reserved by DEC, and you had to change the ethernet adapter address. As
I understand it, there was a 1-to-1 translation between the Mac address and the
DECNET id.
Nowadays, a reason why people might want to change the MAC address is to change
which ethernet card your cable modem talks to (on some of the systems, it will
only talk to the registered ethernet board), or to get a specific static IP
address from a dhcp server administered by a BOFH (bastard operator from hell).
--
Michael Meissner, Red Hat, Inc.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: Chris Quinn <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Info on a segmentation fault...
Date: Tue, 25 Jul 2000 01:22:55 +0100
Hello folks,
I'd like to use mprotect(PROT_READ) on mmap()'ed pages so that when they are first
written to and cause a SIGSEGV, I can catch the signal and find out which memory
location the attempt was made on. I would imagine that such information would be at
hand for the kernel but I do not know of any appropriate system call. Does anyone know
if the info is available and whether it is accessible?
Thanks,
Chris Quinn
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.powerpc
Subject: Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC
Date: Mon, 24 Jul 2000 19:48:52 -0500
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Marco van de Voort) wrote:
>[EMAIL PROTECTED] (MWRon) wrote:
>> Again I apologize if I offended anyone it was not meant to be any
>> commercial posting.
> I'm generally easily offended, and I wasn't offended by yours.
>
> However IMHO, if it just had been the announcement, and not the
> demand for beta-testers(which makes it of interest for the development
> flock), it would have been offensive
As you say, you are easily offended.
Is it your opinion that anyone and everyone who works with Linux should
be kept in ignorance of any and all commercial products for all time? A
single announcement, even of a previously announced product's new
version, does not a spam make.
--
__ _____________ __
\ \_\ \__ __/ /_/ / <http://www.war-of-the-worlds.org/>
.\ __ \ | | / __ /----------------------------------------------------
^ \_\ \_\|_|/_/ /_/ Don't mail me, I'll mail you.
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Crossposted-To: comp.os.linux.powerpc
Subject: Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC
Reply-To: [EMAIL PROTECTED]
Date: Tue, 25 Jul 2000 01:08:28 GMT
On Mon, 24 Jul 2000 19:48:52 -0500, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>Is it your opinion that anyone and everyone who works with Linux should
>be kept in ignorance of any and all commercial products for all time?
It's my opinion that people who are interested about announcements
related to Linux, such as product releases and whatnot, can read
comp.os.linux.announce. That is where announcements belong, not in
a discussion newsgroup.
--
Any hyperlinks appearing in this article were inserted by the unscrupulous
operators of a Usenet-to-web gateway, without obtaining the proper permission
of the author, who does not endorse any of the linked-to products or services.
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: How to wait for TCP data to be ack'ed?
Date: Tue, 25 Jul 2000 01:45:26 GMT
In article <8liib8$2j4c$[EMAIL PROTECTED]>, bill davidsen wrote:
>| How do I find out if all data in a TCP stream has been ACK'ed
>| before proceeding?
>
>1 - have the application send an ACK
Can't -- the other end is in ROM, in the field, and it doesn't send
application-level acks.
>2 - close the socket
Can't -- got to send a series of commands via a single connection.
One of the downsides of using Linux for actual production work is that
you've only got control over part of the problem domain and you you've got
to deal with all sorts of brokeness. It's sort of like trying to talk to MS
Exchange Server. We all know the _right_ way to do things, but the
requirement isn't to do it the right way, the requirement is to talk to a
particular widget.
>3 - look in /proc/net/tcp, I can't remember if the queue is cleared when
> the data are sent or acked.
Acked.
That was the answer (sort of). I used a snippet of code I copied from the
routine that generates /proc/net/tcp. Works like charm.
--
Grant Edwards grante Yow! I'm in direct contact
at with many advanced fun
visi.com CONCEPTS.
------------------------------
From: Krik Lee <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.arm,comp.os.linux.development,linux.dev.kernel
Subject: [Question]gdb remote debugging on arm-based system
Date: Tue, 25 Jul 2000 11:10:27 +0800
Dear All:
I want to use gdb to remote debug an arm-based system.
The target is Assabet running arm-linux.
I have very poor experience with gdb, so I am not sure what should I
do.
Could any one tell me how to do it or give me some hints to search
related information about using gdb to remote debug an arm-based
system?
TIA
kirk
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.powerpc
Subject: Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC
Date: Mon, 24 Jul 2000 23:06:12 -0500
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> It's my opinion that people who are interested about announcements
> related to Linux, such as product releases and whatnot, can read
> comp.os.linux.announce. That is where announcements belong, not in
> a discussion newsgroup.
Ah. Point taken. (With followups set to an appropriate discussion
group I hope. Even announcements are worthy of discussion.)
--
__ _____________ __
\ \_\ \__ __/ /_/ / <http://www.war-of-the-worlds.org/>
.\ __ \ | | / __ /----------------------------------------------------
^ \_\ \_\|_|/_/ /_/ Don't mail me, I'll mail you.
------------------------------
From: [EMAIL PROTECTED] (8623805)
Subject: Port Emulator....
Date: 25 Jul 2000 06:00:46 GMT
Hello, all:
I want to implement a virtual COM port emulator which is
similar to 'VCOMM' in Windows platforms.
I found the source code of IrCOMM ( i.e.
a layer of the IrDA protocol stack).
However, it is said that the IrCOMM is not stable and
may causes the system to crash.
Does anyone know where to get source
code of a stable virtual COM port emulator
(in any UNIX-like platforms) ?
Or, could anyone tell me why the IrComm is not stable ?
Thanks very much !
--
==========================================================
David Chang
Operating System Laboratory
CIS Department, NCTU, Taiwan
Email Address: [EMAIL PROTECTED]
==========================================================
------------------------------
From: Lew Pitcher <[EMAIL PROTECTED]>
Subject: Re: SCO emulation mode???
Date: Mon, 24 Jul 2000 19:13:14 -0400
Pizzamaxsw wrote:
>
> Is there any way to run programs for SCO Unix under Linux such a emulation to
> run my programs in Linux
Run the iBCS daemon. It'll run SCO Unix programs
>From the iBCS2 README
iBCS Emulation for Linux
The Intel Binary Compatibility Specification, or iBCS, specifies the
interfaces between application programs and the surrounding operating
system environment for i386 based systems. There are however several
flavours of iBCS in use - SVR4, SVR3 plus several vendor specific
extensions to SVR3 which are slightly different and incompatible. The
iBCS emulator for Linux supports all flavours known so far.
SUPPORTED CPU ARCHITECTURES
* Intel 386/486/Pentium and compatibles
* Sparc
SUPPORTED BINARY FORMATS
* A.OUT (using standard Linux loader unless using BSD support)
* ELF (using standard Linux loader)
* COFF
* XOUT
SUPPORTED OS EMULATIONS
* Sparc Solaris
* i386 BSD (386BSD, FreeBSD, NetBSD, BSDI/386)
- very alpha, very old.
* SVR4 (Interactive, Unixware, USL, Dell etc.)
* SVR3 generic
* SCO (SVR3 with extensions for symlinks and long filenames)
* SCO OpenServer 5
* Wyse V/386 (SVR3 with extensions for symlinks)
* Xenix V/386 (386 small model binaries only)
* Xenix 286 (not currently supported, not built by default)
Unrecognised binaries will default to the Linux personality for ELF or
the SVR3 personality for COFF binaries. COFF binaries which have had
their .comment section completely removed will default to the SCO
personality. If there are non-standard extensions which require
handling
a new personality may need creating in the emulator.
--
Lew Pitcher
Master Codewright and JOAT-in-training
------------------------------
From: Tim Roberts <[EMAIL PROTECTED]>
Subject: Re: How to read BIOS info in Linux?
Date: Mon, 24 Jul 2000 23:37:10 -0700
[EMAIL PROTECTED] (bill davidsen) wrote:
>Jay Miller <[EMAIL PROTECTED]> wrote:
>| Hi there. I was hoping there was some standard way to read BIOS
>| information through Linux - any nonstandard ways are fine, too.
>|
>| If anyone has any ideas, I'd be very grateful. Thanks in advance!
>
> The only info you can get easily is the CMOS contents, there's a
>kernel option for that. Since Linux doesn't use the BIOS after boot
>there's little useful stuff to read.
Depends on what you you're trying to do. It is useful and possible to read
the contents of and even invoke the video BIOS. There is a package called
lrmi (Linux Real-Mode Interface)that is a wrapper around the vm86 kernel
interface. It includes a sample program which queries the video BIOS for
all available modes, allows you to choose one, switches to that mode,
displays a pretty splash screen, and switches back.
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
------------------------------
Date: Tue, 25 Jul 2000 08:28:09 +0200
From: Markus Pietrek <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,gnu.g++.help
Subject: Re: Linking against libstdc++.so
Timo Volkmer wrote:
>
> Hi everyone,
>
> I am having a problem linking one of my programs against libstdc++.so
>
> I am linking the program under SuSE-Linux 6.4 using gcc 2.95.2
> The link to libstc++.so exists in /usr/lib/gcc-lib/i486-suse-linux/2.95.2
> When I now link the program, the linker tells me the following:
>
> /usr/i486-suse-linux/bin/ld -m elf_i386 -dynamic-linker /lib/ld-linux.so.2 -
> .....
> ..... -L /usr/lib -L/usr/lib/gcc-lib/i486-suse-linux/2.95.2 .....
> ..... -Bdynamic -ldl -lnsl -lstdc++ .....
>
> After linking the program I check what the linker did with "ldd programname"
> and see:
>
> libclntsh.so.1.0 => /usr/oracle/V8.0.5.1/lib/libclntsh.so.1.0
> (0x40015000)
> libdl.so.2 => /lib/libdl.so.2 (0x40395000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x40399000)
> libstdc++-libc6.1-2.so.3 => /usr/lib/libstdc++-libc6.1-2.so.3
> (0x403b0000)
> libm.so.6 => /lib/libm.so.6 (0x403f8000)
> libc.so.6 => /lib/libc.so.6 (0x40416000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> The problem here is, that the linker links directly against
> "libstdc++-libc6.1-2.so.3"
> Should not the linker link agains libstc++.so, so that the program can work
> on a different system, too??
> When I try to run the program on a SuSE-6.2 machine the loader can't find
Is Suse 6.2 a glibc 2.1 or glibc 2.0 system? If it is a 2.1, than you
have to install libstdc++-libc6.1*.
--
Markus Pietrek
Tel: +49-761-47094-13
Fax: +49-761-47094-29
Web: http://www.concept.de
Concept Engineering GmbH
Boetzinger Strasse 29
D-79111 Freiburg/Germany
------------------------------
From: [EMAIL PROTECTED] (Marco van de Voort)
Subject: Re: How to read BIOS info in Linux?
Date: 25 Jul 2000 07:12:28 GMT
>>| If anyone has any ideas, I'd be very grateful. Thanks in advance!
>>
>> The only info you can get easily is the CMOS contents, there's a
>>kernel option for that. Since Linux doesn't use the BIOS after boot
>>there's little useful stuff to read.
>
>Depends on what you you're trying to do. It is useful and possible to read
>the contents of and even invoke the video BIOS. There is a package called
>lrmi (Linux Real-Mode Interface)that is a wrapper around the vm86 kernel
>interface. It includes a sample program which queries the video BIOS for
>all available modes, allows you to choose one, switches to that mode,
>displays a pretty splash screen, and switches back.
Sounds like you are writing something like dosemu. So I guess the proper
place to look how to access the bios is DosEMU?
------------------------------
From: [EMAIL PROTECTED] (Marco van de Voort)
Crossposted-To: comp.os.linux.powerpc
Subject: Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC
Date: 25 Jul 2000 07:20:05 GMT
>> demand for beta-testers(which makes it of interest for the development
>> flock), it would have been offensive
>
>As you say, you are easily offended.
>
>Is it your opinion that anyone and everyone who works with Linux should
>be kept in ignorance of any and all commercial products for all time? A
>single announcement, even of a previously announced product's new
>version, does not a spam make.
No, but they should be using channels dedicated to that kind of
advertisements, and this isn't one of them. This is
comp.os.linux.DEVELOPMENT not comp.os.linux.announces
Just that I don't mind (and even encourage) people to create businesses
all over the world. Just don't stuff all their info in my mailbox.
------------------------------
From: [EMAIL PROTECTED] (Marco van de Voort)
Crossposted-To: comp.os.linux.powerpc
Subject: Re: [ANN] Beta testing of CW for Linux on Intel and PowerPC
Date: 25 Jul 2000 07:21:43 GMT
>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>> (Marco van de Voort) wrote:
>>
>> >Or mklinux (another Mac Linux distribution). I use Slackware on PC, and
>> >want to use mklinux on the PowerMac (since LinuxPPC doesn't support
>> >nubus).
>> >Neither of them are supported.
>>
>> send me a request and you might want to send a note to the Linux
>> distributor as well we are trying to cooperate with everyone possible.
>
>That would be ... Apple. Or Prime Time Freeware (the distributors).
>it's exactly two years since the last release mentioned on the ptf.com
>website, so I don't know if there's anything happening there...
I'm on the MkLinux list, and people are finally working on the Nubus
systems, something LinuxPPC always failed to do.
They hope to have something working end this summer.
------------------------------
From: [EMAIL PROTECTED] (Marco van de Voort)
Subject: Re: Question about after upgrading kernel
Date: 25 Jul 2000 07:37:19 GMT
>On Wed, 19 Jul 2000 21:30:08 GMT, Wesley Wong <[EMAIL PROTECTED]> wrote:
>>1. After kernel is compiled (bzImage is out), will all the .o files be
>>deleted automatically? Or I have to do it myself?
>
>No, for that you do a make clean.
If you want to remove all but the source, do a make mrproper
This also removes the kernel configuration (so you have to
load it from a saved file or reconfigure), and files used in creating the
kernel configuration.
------------------------------
From: [EMAIL PROTECTED] (cLIeNUX user)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.hardware
Subject: Re: A good IDE
Date: 25 Jul 2000 08:07:55 GMT
[EMAIL PROTECTED]
>In comp.os.linux.development.apps cLIeNUX user <[EMAIL PROTECTED]> wrote:
>> Didn't the term IDE in this context come from somewhere other than unix?
>
>> The "IDE" feature I use the most is "+", which is supported by Pico and
>> the "most" pager. When gcc says
>
>If by '+' you mean compile, parse errors and edit, then joe can do that
>quite easily.
No, I mean
pico +210 bletch.c
where 210 was the line gcc reported a fatal error on.
I noodled around briefly with vim's nascent IDE stuff, but even at that
level the problem I have with such things is they very strongly tend to
enforce a style. I'm sure emacs is great for writing gdb.
The only two "IDEs" I know of that don't make any un-toward assumptions
are Unix itself and Forth. Depends on how unique your code is as to how
much of a problem that is.
Rick Hohensee
[EMAIL PROTECTED]
>
>--
>______________________________________________________________________________
>| [EMAIL PROTECTED] | |
>|Andrew Halliwell BSc(hons)| "The day Microsoft makes something that doesn't |
>| in | suck is probably the day they start making |
>| Computer science | vacuum cleaners" - Ernst Jan Plugge |
>------------------------------------------------------------------------------
------------------------------
From: [EMAIL PROTECTED]
Subject: orainst not running
Date: Tue, 25 Jul 2000 07:33:31 GMT
Recently I read a HOWTO called oracle howto.
This how to provides guidelines on how to install oracle 7.3.3 for Sco
Unix on Linux machine. It requires iBCS package.
Now I tried to uncompress the the files from Oracle 7.3-for-SCo
OPenserver CD using a program called orainst which comes with the CD.
This programme simply does not run. A message is displayed "cannot
execute the binary executable".
My computer has kernel-ibcs installed. Now I want to know what is the
difference between kernel-iBCs and iBCS. Why programmes compiled on SCO
Unix (binary files) can not run on on Redhat 6.1?
What is the emulator I have to obtain for making this program run?
Please help if this question belongs to this group. If it does'nt kindly
suggest the appropriate group.
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
