Linux-Development-Sys Digest #21, Volume #7 Thu, 5 Aug 99 00:13:59 EDT
Contents:
Re: does egcs 1.1.2 produce stable kernels? (Erik de Castro Lopo)
bzip2 compressed kernel (Matthias Kilian)
Re: Problem with compiling vfat in 2.3 kernel (Marcin Romaszewicz)
Re: g++ (Juergen Heinzl)
2.2.x(?) problem with SO_LINGER... (cirrus)
Re: Port 6000 Process (Juergen Heinzl)
Re: Help! Cannot set thread's priority under Linux, even not as root! (Nix)
Re: Lecture N� carte ETHERNET (Nix)
Re: Port 6000 Process ("Marc Marais")
Re: Problem with compiling vfat in 2.3 kernel (Tristan Wibberley)
refs on building/accessing shared libraries??? ("Dan Miller")
Re: when will Linux support > 2GB file size??? (Christopher Browne)
Re: java compiler ([EMAIL PROTECTED])
I/O problem ("J. Escalante")
no-lilo problem ("J. Escalante")
Re: g++ (Horst von Brand)
Re: bzip2 compressed kernel (Horst von Brand)
Re: /proc & lm_sensor kernel Oops... feature or bug? :-) (Brian Hall)
Re: Port 6000 Process (John McKown)
----------------------------------------------------------------------------
From: Erik de Castro Lopo <[EMAIL PROTECTED]>
Subject: Re: does egcs 1.1.2 produce stable kernels?
Date: Thu, 05 Aug 1999 06:48:48 +1000
Arnoud de Geus wrote:
>
> Hello
>
> Does the egcs 1.1.2 compiler produce stable
> kernels? Just recently, there were problems
> using egcs for kernel build.
Only use EGCS for 2.2.0 and later kernels. The problems
with using EGCS were specific to earlier kernels.
Erik
--
+-------------------------------------------------+
Erik de Castro Lopo [EMAIL PROTECTED]
+-------------------------------------------------+
The word "Windows" is a word out of an old dialect of the
Apaches. It means: "White man staring through glass-screen
onto an hourglass..."
------------------------------
From: [EMAIL PROTECTED] (Matthias Kilian)
Subject: bzip2 compressed kernel
Date: 4 Aug 1999 19:01:54 GMT
Is there anyone who has the time to patch the kernel to use bzip2 instead of
gzip compression algorithms? This would be a nice feature for building
one-floppy rescue systems.
Are there any tradeoffs using bzip2 (apart from compression/decompression
time)?
Kili
------------------------------
From: Marcin Romaszewicz <[EMAIL PROTECTED]>
Subject: Re: Problem with compiling vfat in 2.3 kernel
Date: Wed, 04 Aug 1999 14:29:52 -0700
Tristan Wibberley wrote:
>
> Marcin Romaszewicz wrote:
>
> > I am compiling fat/vfat directly into the kernel and not as a module.
> > The problem is that when linking, there is an undefined symbol which is
> > used in:
> >
> > <linuxroot>/fs/fat/file.c, line 440:
> > update_vm_cache(inode, *ppos, bh->b_data + (*ppos & (SECTOR_SIZE-1)),
> > written);
> >
> > Which feature/module must I compile in addition to fat/vfat to define
> > this
> > symbol?
>
> Oh! How many times! This has been repeated so much it is not funny
> anymore. Go look on the WWW for devel kernel information, search
> archives of this newsgroup. It is *very* easy to find.
Very easy to find, huh? Have you actually tried? Dejanews was returning
crap on searches such as "update_vm_cache", which should return
something,
imho. Generally, it's easy to find stuff in the archives, I agree, but
many
searches on this topic did not retrieve anything useful, and I really
don't
have the bandwidth (or the will) to read through each month's archive
one
by one. Hmm, interesting, dejanews returns a lot of hits now. In any
case,
at the time I searched, I was not getting hits, so my argument is valid
:).
Sorry that this question annoyed you, but in such a high volume
newsgroup,
it is inevitable that certain topics get pounded to death. It certainly
happens in some of the graphics newsgroups I participate in a lot. I'm
not surprised that a lot of questions are asked about this, since it's
not
mentioned anywhere in the documentation which comes with 2.3, which I
imagine most people read.
I realize that I've thrown wood into the fire, so I'll shut up now.
-- Marcin
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Subject: Re: g++
Date: Wed, 04 Aug 1999 22:27:53 GMT
In article <[EMAIL PROTECTED]>,
Horst von Brand wrote:
>On Mon, 02 Aug 1999 19:45:08 GMT,
> Juergen Heinzl <[EMAIL PROTECTED]> wrote:
>>In article <[EMAIL PROTECTED]>, Billy Donahue wrote:
>
>[...]
>
>>>It's not just bad if you're root...
>>>You should NEVER put . in your path.
>
>[...]
>
>>>If you happen to visit my directory and type 'ls',
>>>then you're screwed.. I could also put my 'ls' in
>>>/tmp, and if you 'cd /tmp' and 'ls', you're doomed.
>
>>PATH=$PATH:. ... . ought to be the last entry, then
>>you can type ls until the cows come home 8)
>
>But you'd type 'sl' once in a while... dystypia can be deadly.
I must admit this sounds either like a straw man or like
Latin to me now.
>>Minor note, only root can create a programme so it
>>is setuid JoeSixpack, say you're screwed already, you
>
>What gave you that idea? I certainly have the permission to make programs
>SUID myself, or SGID a group to which I belong.
Sure, but then it is suid "You", not suid "Him" or "Her" and if ls
is a trojan horse that hides a "rm -rf *" you're going to make a clown
of yourself.
In that case suid is the last thing you want.
Never mind, but while I am in security I think too one should
not overdo it. You cannot avoid a break in (assuming you're a
target) but you had better be able to handle it. Some guy I know
once said something like "People who say they've never been cracked
are either fools or liers".
You saw that I said "root does not need ." and yes, make this
stronger, "root must not have . in PATH". For "normal" users though
this is mostly more an inconvenience than anything else, but sure
thing, depending on what is up and running a trojan horse can become
an issue and then I'd rather modify .profile, adding a much less
unconspicuous hash entry so "my" ls or application wrapper is run,
even if PATH changes.
Ta'
Juergen
--
\ Real name : J�rgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
------------------------------
From: cirrus <[EMAIL PROTECTED]>
Subject: 2.2.x(?) problem with SO_LINGER...
Date: 4 Aug 1999 22:04:30 GMT
I'm not sure if this is the correct place to post something like this. Actually I've
never posted here before, but here goes..
While doing some socket programming with a 2.2.6 kernel, I noticed that when
one sets the SO_LINGER socket option with a corresponding linger struct set as
linger_struct.l_onoff = 1;
linger_struct.l_linger = 0;
the packets sent upon close()ing the socket are not what is expected.
setting the l_onoff to a nonzero and a the l_linger to zero is supposed to
force the sending of a RST packet to the connected peer upon a close(), thus
avoiding the TIME_WAIT state. However on kernels 2.2.5, 2.2.6, and 2.2.10
(the only ones I have tested) the packet sent on closing is a FIN, which begins
the 4 way FIN/ACK close and takes the end doing the active close into the
TIME_WAIT state. sorry, for being so verbose, but I wanted to make it clear what was
happening. tcpdump verifies that the packet sent upon close is a FIN.
I tested the same code on kernel 2.0.37 and everything went as it is supposed
to. (sent a RST, no time_wait)
If there is someone else or somewhere else to which this should be said then
let me know.
thanks,
James ([EMAIL PROTECTED])
------------------------------
From: [EMAIL PROTECTED] (Juergen Heinzl)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Port 6000 Process
Date: Wed, 04 Aug 1999 22:27:56 GMT
In article <[EMAIL PROTECTED]>,
Matthew Carl Schumaker wrote:
>Does anybody know a process that uses Port 6000, I was writing an app that
The X server.
[...]
Ta',
Juergen
--
\ Real name : J�rgen Heinzl \ no flames /
\ EMail Private : [EMAIL PROTECTED] \ send money instead /
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: Help! Cannot set thread's priority under Linux, even not as root!
Date: 04 Aug 1999 22:39:26 +0100
Andreas Jaeger <[EMAIL PROTECTED]> writes:
> glibc 2.1 has better thread support than glibc 2.0 -
Is this another way to say `aio_*()'?
--
`The plague, dirt, lack of running water, illiteracy, ignorance, and
oppressive political and social systems are what made the dark ages what
they were.' --- Gus Hartmann in the Monastery
------------------------------
From: Nix <$}xinix{[email protected]>
Crossposted-To: comp.os.linux.development
Subject: Re: Lecture N� carte ETHERNET
Date: 04 Aug 1999 22:25:36 +0100
Vincent <[EMAIL PROTECTED]> writes:
> Hi.
> I'll like to know how I can read my ID ethernet on my network card in
> language C.
>
> Moreover, I'm looking for schemes for protect my own software.
You're on a hiding to nothing doing this in Linux.
(The kernel can always be modified to lie to your program about the
Ethernet MAC address, or, indeed, anything else.)
--
`The plague, dirt, lack of running water, illiteracy, ignorance, and
oppressive political and social systems are what made the dark ages what
they were.' --- Gus Hartmann in the Monastery
------------------------------
From: "Marc Marais" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Port 6000 Process
Date: Wed, 4 Aug 1999 16:11:00 -0700
Matthew Carl Schumaker wrote in message ...
>Does anybody know a process that uses Port 6000, I was writing an app that
>used that port and I could never get it, I tried telneting to it and I
>connect but that was about it. I'm running RedHat 6.0. I looked in the
>services file but there was nothing listed for that port. I even tried to
>reboot in case a previous process somehow didn't release it but it was
>there when I rebooted which leads me to believe that its some sort of
>system process, however my 2.0.36 machine has that port open. Its not
>that important since I can use any other port, Its just a little
>disconcerning knowing that there is an app running on that port and I have
>no idea what it is.
>
>Thanks in advance
>matt
>
>Matthew Carl Schumaker
>UPAC Lights Administrative Chairperson
>[EMAIL PROTECTED]
>veni, vedi, velcro
>I came, I saw, I stuck around
>
You can use 'lsof -i' to see which ports belong to which processes.
Marc
------------------------------
From: Tristan Wibberley <[EMAIL PROTECTED]>
Subject: Re: Problem with compiling vfat in 2.3 kernel
Date: Tue, 03 Aug 1999 22:32:32 +0100
Reply-To: [EMAIL PROTECTED]
Marcin Romaszewicz wrote:
> I'm
> not surprised that a lot of questions are asked about this, since it's
> not
> mentioned anywhere in the documentation which comes with 2.3, which I
> imagine most people read.
>
> I realize that I've thrown wood into the fire, so I'll shut up now.
You should see what happened the last time someone asked this here ;)
Regarding your trouble finding this information, it can be found by
starting at www.linux.com and using a bit of intelligence, and it will
not take more than 2-3 minutes. If you already know where to find info
on devel kernels, it can be found even quicker :)
--
Tristan Wibberley
------------------------------
From: "Dan Miller" <[EMAIL PROTECTED]>
Subject: refs on building/accessing shared libraries???
Date: Wed, 4 Aug 1999 16:52:22 -0700
I've suddenly discovered that I have to write a shared library of functions
for someone else to call functions in. I've never written a shared library,
nor have I even called one (I don't think), and none of my books say
anything about it.
Is there anyplace that I can find a tutorial on this process, maybe with
some simple example code so I can try it out?? Alternately, what
books are good for learning about this?? I have extensive experience
with C, I just have never written shared libraries or DLLs before.
Thanks for any assistance that you can provide...
1 desperate Dan Miller
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Crossposted-To: comp.os.linux.advocacy
Subject: Re: when will Linux support > 2GB file size???
Reply-To: [EMAIL PROTECTED]
Date: Thu, 05 Aug 1999 01:36:18 GMT
On Tue, 27 Jul 1999 05:49:25 GMT, Bloody Viking <[EMAIL PROTECTED]> wrote:
>In comp.os.linux.advocacy Philip Brown <[EMAIL PROTECTED]> wrote:
>
>: Umm.... a low-end alpha was affordable 2 years ago.
>
>Depends on your definition of "affordable", which is of course a function
>of your take-home pay. For a professional making $80K/yr, you're right.
>For a postal worker, no. Becuse I'm a postal worker, the Y2K-3 DEC Alphas
>were not affordable. :( When Intel starts shipping millions of 64-bit
>CPUs, then it will meet my income's definition of "affordable".
>
>Not every Linux fan is a computer professional. A few of us use it becuse
>the price is right: Affordable like nothing else. :)
If it is "affordable" according to the definitions used by enough
people, then its use can become fairly widespread.
If that doesn't meet *everyone's* definition of "affordable," that may
be unfortunate, but still acceptable for the purpose of increasing its
proliferation. After all, $5000 might be too much for you to pay, but
if that's a better value than the $6000 that people pay for other
systems, $5K < $6K, and that can turn into a sale, albeit not to
you...
I picked up an Alpha box a couple of years ago for $850, which was
fairly comparable to the pretty-much-constant pricing of Intel boxes
over the years where the "box you want" costs about $1500.
--
"NT 5.0 is the last nail in the Unix coffin. Interestingly, Unix isn't
in the coffin... It's wondering what the heck is sealing itself into a
wooden box 6 feet underground..." -- Jason McMullan
[EMAIL PROTECTED] <http://www.hex.net/~cbbrowne/alpha.html>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: java compiler
Date: Thu, 05 Aug 1999 02:21:15 GMT
kl <[EMAIL PROTECTED]> wrote:
: Is there a java compiler on RH6.0? I can't seem to find it.
gcj (free, comes w/ gcc 2.95+) or TowerJ (http://www.towerj.com/).
Both compile Java bytecode to native code.
TowerJ runs great under Linux, and happens to be fastest Java available
for any platform. (plug plug I used to work there)
I don't know of any Java compiler that supports AWT; but most apps that
can benefit from being compiled as native code are server-based
applications. (For GUI stuff, selective speedups via JNI should work
just fine)
Jeff
--
Sounds suspiciously like a contest I run everyday when I bike
to work. It's called "break the bike lock and keep the bike!".
-SirSlud, commenting on LinuxPPC contest
"Crack this box, and keep it"
------------------------------
Date: Wed, 04 Aug 1999 22:32:33 -0400
From: "J. Escalante" <[EMAIL PROTECTED]>
Subject: I/O problem
I am running LINUX slackware 4 at home, my problem is that I don't get
any output on the screen, cout << "Name" << endl; does not output
anything and neither does prontf("Name");
If you know what the problem could be I would appreciate an email at
[EMAIL PROTECTED]
Thanks in advance
------------------------------
Date: Wed, 04 Aug 1999 22:10:45 -0400
From: "J. Escalante" <[EMAIL PROTECTED]>
Subject: no-lilo problem
Since I don't have any other OS than Linux Slackware running in my
computer, what I want is not to
have lilo at boot up time.
The small partition where DOS resided, I made it the swap partition and
the rest is all Linux.
Using fdisk, I toggled the boot switch in the big partition, now that I
rebooted my machine, I got a
message saying that there was not operating system.
I really don't know what the problem could be, but I want to get rid of
LILO and any other OS, but
LINUX.
Hey!! if you know what I can do to solve this problem, I would
appreciate an email at
[EMAIL PROTECTED]
Thanks in advance
------------------------------
From: [EMAIL PROTECTED] (Horst von Brand)
Subject: Re: g++
Date: 5 Aug 1999 02:46:53 GMT
On Wed, 04 Aug 1999 22:27:53 GMT,
Juergen Heinzl <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>,
>Horst von Brand wrote:
>>On Mon, 02 Aug 1999 19:45:08 GMT,
>> Juergen Heinzl <[EMAIL PROTECTED]> wrote:
>>>In article <[EMAIL PROTECTED]>, Billy Donahue wrote:
[...]
>>>>If you happen to visit my directory and type 'ls',
>>>>then you're screwed.. I could also put my 'ls' in
>>>>/tmp, and if you 'cd /tmp' and 'ls', you're doomed.
>>>PATH=$PATH:. ... . ought to be the last entry, then
>>>you can type ls until the cows come home 8)
>>But you'd type 'sl' once in a while... dystypia can be deadly.
>I must admit this sounds either like a straw man or like
>Latin to me now.
OK, so you _never_ type 'sl' for 'ls'? What I was hinting at is that placing
'.' last can't save you from this kind of attack.
>>>Minor note, only root can create a programme so it
>>>is setuid JoeSixpack, say you're screwed already, you
>>What gave you that idea? I certainly have the permission to make programs
>>SUID myself, or SGID a group to which I belong.
>Sure, but then it is suid "You", not suid "Him" or "Her" and if ls
>is a trojan horse that hides a "rm -rf *" you're going to make a clown
>of yourself.
If I get JSP to run some code I wrote, he does as JSP, and can then create a
SUID JSP executable. I can stash that away and run it later at leisure. But
to just do "rm -rf $HOME" I don't even need a SUID JSP executable.
>In that case suid is the last thing you want.
>
>Never mind, but while I am in security I think too one should
>not overdo it. You cannot avoid a break in (assuming you're a
>target) but you had better be able to handle it. Some guy I know
>once said something like "People who say they've never been cracked
>are either fools or liers".
>
>You saw that I said "root does not need ." and yes, make this
>stronger, "root must not have . in PATH". For "normal" users though
>this is mostly more an inconvenience than anything else, but sure
>thing, depending on what is up and running a trojan horse can become
>an issue and then I'd rather modify .profile, adding a much less
>unconspicuous hash entry so "my" ls or application wrapper is run,
>even if PATH changes.
IMVHO, if anybody can screw innocent Joe SixPack because of an "for
convenience" default setup, the one doing the setting up should be shot.
This _is_ security. Perhaps not for the system as a whole, but for its
users. May I remaind you that the _users_ are the reason for the existence of
the system in the first place?
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vi�a del Mar, Chile +56 32 672616
------------------------------
From: [EMAIL PROTECTED] (Horst von Brand)
Subject: Re: bzip2 compressed kernel
Date: 5 Aug 1999 02:46:51 GMT
On 4 Aug 1999 19:01:54 GMT, Matthias Kilian <[EMAIL PROTECTED]> wrote:
>Is there anyone who has the time to patch the kernel to use bzip2 instead of
>gzip compression algorithms? This would be a nice feature for building
>one-floppy rescue systems.
Noone. bzip2 needs _at least_ 900Kb to uncompress, and when booting you've
got the fabled 640Kb to work with, minus whatever BIOS uses, and the memory
for the bootloader, etc.
I believe somebody did the exercise and it turned out that what you win by
compressing the kernel you loose by larger uncompressing code :-)
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vi�a del Mar, Chile +56 32 672616
------------------------------
From: [EMAIL PROTECTED] (Brian Hall)
Subject: Re: /proc & lm_sensor kernel Oops... feature or bug? :-)
Date: Thu, 05 Aug 1999 03:23:08 GMT
Reply-To: [EMAIL PROTECTED]
Is there an equivalent to "ksymoops" for RedHat ?
In article <[EMAIL PROTECTED]>, Paolo Pedaletti
wrote:
>Ciao Alexander Viro,
>
> > Bug, indeed, but you've omitted very interesting piece of data: version
of the
> > kerenl ;-)
>
>2.2.10 .... sorry :-)
>
> > Results of ksymoops on your kern.log would be also useful
>
>Jul 30 14:50:09 niels kernel: Unable to handle kernel NULL pointer derefer
>Jul 30 14:50:09 niels kernel: current->tss.cr3 = 07095000, %cr3 = 07095000
>Jul 30 14:50:09 niels kernel: *pde = 00000000
>Jul 30 14:50:09 niels kernel: Oops: 0000
>Jul 30 14:50:09 niels kernel: CPU: 0
>Jul 30 15:11:30 niels kernel: klogd 1.3-3#32, log source = /proc/kmsg started.
>Jul 30 15:11:30 niels kernel: Cannot find map file.
>Jul 30 15:11:30 niels kernel: Loaded 304 symbols from 39 modules.
>Jul 30 15:11:30 niels kernel: Unable to handle kernel NULL pointer derefer
>Jul 30 15:11:30 niels kernel: current->tss.cr3 = 028fb000, %cr3 = 028fb000
>Jul 30 15:11:30 niels kernel: *pde = 00000000
>Jul 30 15:11:30 niels kernel: Oops: 0000
>Jul 30 15:11:30 niels kernel: CPU: 0
>Jul 30 15:16:15 niels kernel: klogd 1.3-3#32, log source = /proc/kmsg started.
>Jul 30 15:16:15 niels kernel: Cannot find map file.
>Jul 30 15:16:15 niels kernel: Loaded 300 symbols from 24 modules.
>Jul 30 15:16:15 niels kernel: Linux version 2.2.10 (root@niels) (gcc versi
>Jul 30 15:16:15 niels kernel: Detected 350810353 Hz processor.
>Jul 30 15:16:15 niels kernel: Console: colour VGA+ 132x44
>Jul 30 15:16:15 niels kernel: Calibrating delay loop... 699.60 BogoMIPS
>Jul 30 15:16:15 niels kernel: Memory: 128228k/131008k available (820k kern
>Jul 30 15:16:15 niels kernel: CPU: AMD AMD-K6(tm) 3D processor stepping 0c
>
>--
>
>Paolo Pedaletti, Como, ITALYa < paolo . pedaletti @ flashnet . it >
------------------------------
From: [EMAIL PROTECTED] (John McKown)
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Port 6000 Process
Date: 5 Aug 1999 02:56:48 GMT
On Wed, 4 Aug 1999 15:55:51 -0400, Matthew Carl Schumaker
<[EMAIL PROTECTED]> wrote:
>Does anybody know a process that uses Port 6000, I was writing an app that
[snip]
>
>Thanks in advance
>matt
>
>Matthew Carl Schumaker
>UPAC Lights Administrative Chairperson
>[EMAIL PROTECTED]
I did a "netstat -a -p" on my RedHat 6.0 system. Port 6000 showed up as
in use by my X Window server. I don't know if this is a normal part of
X or if it is Gnome. I just found something in the XFree86 docs, but
I don't really understand it. It says:
XFree86 listens on port htons(6000+n) where "n" is the display number.
I guess this is for non-local X clients to display on this system's
X display. Just my guess.
John
------------------------------
** 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
******************************
