Linux-Misc Digest #862, Volume #25 Mon, 25 Sep 00 01:13:02 EDT
Contents:
Re: Error on "make bzImage"... (Markus Kossmann)
Re: Error on "make bzImage"... ("Rinaldi J. Montessi")
Li..... (Seiler)
Re: Li..... ("David ..")
Re: Error on "make bzImage"... (Dances With Crows)
Re: Li..... (Leonard Evens)
Re: Li..... (jeff)
Re: BIND ACL Workarounds (was: Re: been hacked...have a question) (Bryan Packer)
Re: Error on "make bzImage"... (MH)
Re: Error on "make bzImage"... (MH)
Help, Pcmcia Card Reader (futurebots)
Re: Error on "make bzImage"... (MH)
----------------------------------------------------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: Error on "make bzImage"...
Date: Mon, 25 Sep 2000 04:35:07 +0200
MH wrote:
>
> Recently, while trying to compile a new kernel, I did "make bzImage" and
> everything proceeded normally until the very end. I got the following
> error:
>
> make[1]: as86: command not found
> make[1]: *** [bbootsect.o] Error 127"
> make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
> make: *** [bzImage] Error 2
>
> I remembered having this error before and resolved it by installing an
> RPM package that contained some utilities. It took me awhile to locate
> the right package, since it was not part of the ISO. The package is
> called "bin86*****" and had I not remembered the "bin" part, I never
> would have found it.
>
> In any case, it seems very odd that this package is not part of the ISO,
> since it is REQUIRED to compile a new kernel. Even stranger, it is
> apparently not part of the GNU utilities, nor even a GPL application,
> since it is listed as "contrib" on RedHat's site. Does anyone else find
> this disturbing given that GNU/Linux is supposed to be "free" i.e.
> licensed under the GPL? Am I missing something here?
Well, the kernel needs some real mode code in the early boot stage
before switching to protected mode. Not so long ago, gnu binutils
weren't able to produce real mode code. So you did have to use another
tool to build that part of the kernel.
BTW. Kernel 2.4 will switch to use GNU binutils only.
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: "Rinaldi J. Montessi" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Error on "make bzImage"...
Date: Sun, 24 Sep 2000 23:22:44 -0400
MH wrote:
>
> "Rinaldi J. Montessi" wrote:
>
> > MH wrote:
> > >
> > > Recently, while trying to compile a new kernel, I did "make bzImage" and
> > > everything proceeded normally until the very end. I got the following
> > > error:
> > >
> > > make[1]: as86: command not found
> > > make[1]: *** [bbootsect.o] Error 127"
> > > make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
> > > make: *** [bzImage] Error 2
> > >
> > > I remembered having this error before and resolved it by installing an
> > > RPM package that contained some utilities. It took me awhile to locate
> > > the right package, since it was not part of the ISO. The package is
> > > called "bin86*****" and had I not remembered the "bin" part, I never
> > > would have found it.
> > >
> > > In any case, it seems very odd that this package is not part of the ISO,
> > > since it is REQUIRED to compile a new kernel. Even stranger, it is
> > > apparently not part of the GNU utilities, nor even a GPL application,
> > > since it is listed as "contrib" on RedHat's site. Does anyone else find
> > > this disturbing given that GNU/Linux is supposed to be "free" i.e.
> > > licensed under the GPL? Am I missing something here?
> >
> > I've compiled probably a dozen kernels; some even worked when I finished
> > - and never choked on the bzImage make. All were from kernel org
> > tarballs with various and sundry patches applied. I'd look elsewhere
> > for your problem.
> >
>
> You don't seem to read very well do you.
Possibly. But my point stands. I've never had to go fetch another
utility in order to compile a kernel or make a bzImage.
>From the man page:
as86(1) as86(1)
NAME
as86 - Assembler for 8086..80386 processors
It appears you have a 686 - but that may be irrelevant.
locate produces the following
/usr/bin/as86
/usr/bin/as86_encap
/usr/man/man1/as86.1.gz
Although rpm -qa | grep bin86 returns nothing.
And http://rpmfind.net/linux/RPM/redhat/6.0/i386/bin86-0.4-7.i386.html
indicates it's a development tool.
So my not so well read conclusion still stands. Perhaps the packages
weren't installed during the install process? But it should be on your
distro cd if you have one.
--
Rinaldi]$
"The federal government has taken too much tax money from the people,
too much authority from the states, and too much liberty with the
Constitution." --Ronald Reagan
------------------------------
From: Seiler <SN Is [EMAIL PROTECTED]>
Subject: Li.....
Date: Mon, 25 Sep 2000 03:30:03 -0000
i had linux but my hard drive was gettin low so i deleted just deleted the
partition not thinking... anyway i had red hat linux and when i deleted
teh partition when i rebooted it booted off of the hard drive and then at
the point where it goes to what normally says "lilo:" it says "Li" and
then just freezes, i can get into dos through my boot disk and i don't
feel like reformating and losing my files. when i reinstalled windows
without reformating the problem was still there.
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Li.....
Date: Sun, 24 Sep 2000 22:41:47 -0500
Seiler wrote:
>
> i had linux but my hard drive was gettin low so i deleted just deleted the
> partition not thinking... anyway i had red hat linux and when i deleted
> teh partition when i rebooted it booted off of the hard drive and then at
> the point where it goes to what normally says "lilo:" it says "Li" and
> then just freezes, i can get into dos through my boot disk and i don't
> feel like reformating and losing my files. when i reinstalled windows
> without reformating the problem was still there.
Boot with DOS bootdisk and run "fdisk /MBR"
--
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Error on "make bzImage"...
Date: 25 Sep 2000 03:59:28 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 24 Sep 2000 19:49:56 -0700, MH wrote:
>[EMAIL PROTECTED] wrote:
[snippage]
>> From the README in /usr/doc/dev86-0.15.0
>> This is based on the as86 and ld86 distribution written by Bruce Evans.
>> Bruce has released this under the GPL and the changes I've made are
>> also under the same license
>Interesting. Any idea why RedHat is listing it as "distributable" rather
>than "GPL"?
>Also, I have another question if it's not a bother. Excuse my ignorance,
>but what is an "assembler and linker"--
Assembler: A program that takes assembly language and outputs machine
language. Assembly language looks like so--
LDA #$7F % load 0x7f into accumulator
LDX #$10 % load 0x10 into X register
STA $0400,X % do something stupid
DEX % decrement X
BEQ -04 % equal to 0? If so, go back to "do something stupid"
RTS % return
...and is rather hideous to code in. A compiler like gcc takes C code,
outputs assembly language, and generally pipes that to an assembler like
"as". Use the -S option with gcc to see machine code!
Linker: Modern OSes don't just execute random blocks of machine code,
and modern assemblers don't generate random blocks of machine code.
Machine code (with header information telling a linker what goes where)
is generally stored in .o files, and a linker takes these .o files and
puts them together into a coherent executable, with appropriate
executable header information, shared libraries needed for execution,
and so forth.
There are two different assemblers generally used here: as, the
standard GNU assembler, and as86, an assembler that's specifically for
putting together x86 real-mode code. Real-mode crud does not run under
Linux and the only reason as86 is required for a kernel compile is that
an x86 machine starts up in real mode, so the first thing the kernel
must do is load itself into memory and uncompress itself, using only
real-mode services. Then it switches to protected mode.
>(I'm not a programmer, though I have dabbled a bit with BASIC and VBA.)
Yep. Get yourself a good book on C or C++ and learn a Real Language :-]
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Those who do not understand Unix are
http://www.brainbench.com / condemned to reinvent it, poorly.
=============================/ ==Henry Spencer
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Li.....
Date: Sun, 24 Sep 2000 23:04:42 -0500
Seiler wrote:
>
> i had linux but my hard drive was gettin low so i deleted just deleted the
> partition not thinking... anyway i had red hat linux and when i deleted
> teh partition when i rebooted it booted off of the hard drive and then at
> the point where it goes to what normally says "lilo:" it says "Li" and
> then just freezes, i can get into dos through my boot disk and i don't
> feel like reformating and losing my files. when i reinstalled windows
> without reformating the problem was still there.
>
> --
> Posted via CNET Help.com
> http://www.help.com/
Boot from a DOS boot floppy and run the command
fdisk/mbr
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: [EMAIL PROTECTED] (jeff)
Subject: Re: Li.....
Date: 25 Sep 2000 04:13:25 GMT
Reply-To: [EMAIL PROTECTED]
On Mon, 25 Sep 2000 03:30:03 -0000, Seiler <[EMAIL PROTECTED]> wrote:
> i had linux but my hard drive was gettin low so i deleted just deleted the
> partition not thinking... anyway i had red hat linux and when i deleted
> teh partition when i rebooted it booted off of the hard drive and then at
> the point where it goes to what normally says "lilo:" it says "Li" and
> then just freezes, i can get into dos through my boot disk and i don't
> feel like reformating and losing my files. when i reinstalled windows
> without reformating the problem was still there.
>
> --
> Posted via CNET Help.com
> http://www.help.com/
Just boot from DOS diskette and run: fdisk /mbr
-jeff
------------------------------
From: Bryan Packer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.security
Subject: Re: BIND ACL Workarounds (was: Re: been hacked...have a question)
Date: Sun, 24 Sep 2000 23:17:10 -0500
If your situation allows you to be selective in which addresses can
query your server, my vote is use packet filtering as well as the ACL's.
The more layers of security you can put between you and the big bad
world the better...
my .02 cents,
bryan
Grega Bremec wrote:
>
> Are there any known exploits that can get around BIND ACLs or is it OK
> for me consider opening up UDP port 53 after having my way with
> named.conf? CERT says nothing about ACL exploits so far.
================================================================
Before you criticize someone, walk a mile in his shoes.
That way, if he gets angry, he'll be a mile away and barefoot.
================================================================
------------------------------
From: MH <[EMAIL PROTECTED]>
Subject: Re: Error on "make bzImage"...
Date: Sun, 24 Sep 2000 21:21:06 -0700
Dances With Crows wrote:
> On Sun, 24 Sep 2000 19:49:56 -0700, MH wrote:
> >[EMAIL PROTECTED] wrote:
> [snippage]
> >> From the README in /usr/doc/dev86-0.15.0
> >> This is based on the as86 and ld86 distribution written by Bruce Evans.
> >> Bruce has released this under the GPL and the changes I've made are
> >> also under the same license
> >Interesting. Any idea why RedHat is listing it as "distributable" rather
> >than "GPL"?
> >Also, I have another question if it's not a bother. Excuse my ignorance,
> >but what is an "assembler and linker"--
>
> Assembler: A program that takes assembly language and outputs machine
> language. Assembly language looks like so--
> LDA #$7F % load 0x7f into accumulator
> LDX #$10 % load 0x10 into X register
> STA $0400,X % do something stupid
> DEX % decrement X
> BEQ -04 % equal to 0? If so, go back to "do something stupid"
> RTS % return
> ...and is rather hideous to code in. A compiler like gcc takes C code,
> outputs assembly language, and generally pipes that to an assembler like
> "as". Use the -S option with gcc to see machine code!
>
> Linker: Modern OSes don't just execute random blocks of machine code,
> and modern assemblers don't generate random blocks of machine code.
> Machine code (with header information telling a linker what goes where)
> is generally stored in .o files, and a linker takes these .o files and
> puts them together into a coherent executable, with appropriate
> executable header information, shared libraries needed for execution,
> and so forth.
>
> There are two different assemblers generally used here: as, the
> standard GNU assembler, and as86, an assembler that's specifically for
> putting together x86 real-mode code. Real-mode crud does not run under
> Linux and the only reason as86 is required for a kernel compile is that
> an x86 machine starts up in real mode, so the first thing the kernel
> must do is load itself into memory and uncompress itself, using only
> real-mode services. Then it switches to protected mode.
>
> >(I'm not a programmer, though I have dabbled a bit with BASIC and VBA.)
>
> Yep. Get yourself a good book on C or C++ and learn a Real Language :-]
>
Thanks for the great response! I actually "poked" around in assembler once.
;-) But I was always under the impression that "assembler" and "machine code"
were the same thing. Not sure I'd actually like being a "real" programmer, as
it generally seems exceedingly tedious--though I do enjoy working with
databases (VBA, SQL). Would probably go for one of the "scripting" languages
like Python or Perl if pushed. Anyway, thanks again! Much appreciated.
------------------------------
From: MH <[EMAIL PROTECTED]>
Subject: Re: Error on "make bzImage"...
Date: Sun, 24 Sep 2000 21:29:12 -0700
Markus Kossmann wrote:
> MH wrote:
> >
> > Recently, while trying to compile a new kernel, I did "make bzImage" and
> > everything proceeded normally until the very end. I got the following
> > error:
> >
> > make[1]: as86: command not found
> > make[1]: *** [bbootsect.o] Error 127"
> > make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
> > make: *** [bzImage] Error 2
> >
> > I remembered having this error before and resolved it by installing an
> > RPM package that contained some utilities. It took me awhile to locate
> > the right package, since it was not part of the ISO. The package is
> > called "bin86*****" and had I not remembered the "bin" part, I never
> > would have found it.
> >
> > In any case, it seems very odd that this package is not part of the ISO,
> > since it is REQUIRED to compile a new kernel. Even stranger, it is
> > apparently not part of the GNU utilities, nor even a GPL application,
> > since it is listed as "contrib" on RedHat's site. Does anyone else find
> > this disturbing given that GNU/Linux is supposed to be "free" i.e.
> > licensed under the GPL? Am I missing something here?
> Well, the kernel needs some real mode code in the early boot stage
> before switching to protected mode. Not so long ago, gnu binutils
> weren't able to produce real mode code. So you did have to use another
> tool to build that part of the kernel.
> BTW. Kernel 2.4 will switch to use GNU binutils only.
>
Yeah, first time I went through this I assumed that the binutils package was
what I needed, but that turned out not to be the case. Has binutils been
updated so that the new kernel no longer requires bin86? Or is it the other
way around? Any idea why bin86 isn't currently package with ISOs? Seems
very odd, especially since I've been informed that bin86 is indeed GPLed (How
would one confirm that? Is the GPL license located in source, as opposed to a
file included with RPM?).
------------------------------
From: futurebots <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Help, Pcmcia Card Reader
Date: Sun, 24 Sep 2000 23:36:53 -0700
Hello,
I have a DataBook Card reader Part # 9453002, this is a 2 slot unit that
fits a ISA slot, how do I read and write to the
cards? Is there software for this reader?
Thanks !!
Dan Mathias
==========================
Future-Bot Components Web: http://www.futurebots.com
106 Commerce way, A8 Email: [EMAIL PROTECTED]
Jupiter, Fl. 33458 USA Phone/Fax (561) 575-1487
=======================================================================
Robotic and Electronic Components for the Hobbyist and Professional..
We have Motors, IC Chips, PC-Parts, Sensors, Robotic items......
------------------------------
From: MH <[EMAIL PROTECTED]>
Subject: Re: Error on "make bzImage"...
Date: Sun, 24 Sep 2000 21:45:49 -0700
"Rinaldi J. Montessi" wrote:
> MH wrote:
> >
> > "Rinaldi J. Montessi" wrote:
> >
> > > MH wrote:
> > > >
> > > > Recently, while trying to compile a new kernel, I did "make bzImage" and
> > > > everything proceeded normally until the very end. I got the following
> > > > error:
> > > >
> > > > make[1]: as86: command not found
> > > > make[1]: *** [bbootsect.o] Error 127"
> > > > make[1]: Leaving directory `/usr/src/linux/arch/i386/boot'
> > > > make: *** [bzImage] Error 2
> > > >
> > > > I remembered having this error before and resolved it by installing an
> > > > RPM package that contained some utilities. It took me awhile to locate
> > > > the right package, since it was not part of the ISO. The package is
> > > > called "bin86*****" and had I not remembered the "bin" part, I never
> > > > would have found it.
> > > >
> > > > In any case, it seems very odd that this package is not part of the ISO,
> > > > since it is REQUIRED to compile a new kernel. Even stranger, it is
> > > > apparently not part of the GNU utilities, nor even a GPL application,
> > > > since it is listed as "contrib" on RedHat's site. Does anyone else find
> > > > this disturbing given that GNU/Linux is supposed to be "free" i.e.
> > > > licensed under the GPL? Am I missing something here?
> > >
> > > I've compiled probably a dozen kernels; some even worked when I finished
> > > - and never choked on the bzImage make. All were from kernel org
> > > tarballs with various and sundry patches applied. I'd look elsewhere
> > > for your problem.
> > >
> >
> > You don't seem to read very well do you.
>
> Possibly. But my point stands. I've never had to go fetch another
> utility in order to compile a kernel or make a bzImage.
>
> From the man page:
> as86(1) as86(1)
>
> NAME
> as86 - Assembler for 8086..80386 processors
>
> It appears you have a 686 - but that may be irrelevant.
>
> locate produces the following
> /usr/bin/as86
> /usr/bin/as86_encap
> /usr/man/man1/as86.1.gz
>
> Although rpm -qa | grep bin86 returns nothing.
>
> And http://rpmfind.net/linux/RPM/redhat/6.0/i386/bin86-0.4-7.i386.html
> indicates it's a development tool.
>
> So my not so well read conclusion still stands. Perhaps the packages
> weren't installed during the install process? But it should be on your
> distro cd if you have one.
>
Most likely you got lucky, or you went with the "pre-packaged" installs. I've
had this happen twice, once with RH 6.0 and once with RH 6.2. Both installations
were "custom", so it's likely I left out the package containing bin86. There
are no dependencies apparently (except for building bzImage!!). My most recent
installation was done using an ISO image, which DID NOT contain bin86. If the
relevant programs are in another package, I'll be damned if I could find it.
As for your conclusion, it's dead wrong. I was unable to compile the kernel
UNTIL I installed the bin86 package at which time the kernel compiled perfectly.
The logic is unassailable, which is why I accused you of not reading very well.
On the other hand, you are right about not needing "bin86", as it is the programs
WITHIN that particular package that are necessary.
------------------------------
** 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.misc) 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-Misc Digest
******************************
