Linux-Development-Sys Digest #424, Volume #6     Tue, 23 Feb 99 14:13:48 EST

Contents:
  Re: Linux on old as400 machines? (Dave McKenzie)
  Re: Glibc-2.0.112 Problem. (Steve A)
  Re: How to I make a Screenshot in X. (Bandyopadhyay Rajarshi Dipak)
  How can I tell kernel processes in /proc? (R. Bernstein)
  Re: linux 2.2.1 with SMP power management problem. ("Robert Acklin")
  Re: Problems compiling linux-2.2.2 (PFENNIGER Daniel)
  ESS1688 sound chip and 2.2.x (Bow-Yaw Wang)
  Re: Problems compiling linux-2.2.2 (Mogens Kjaer)
  running from a cdrom (ie, a mostly read-only filesystem)? (BL)
  VGA handling ("Rangel Reale")
  Re: Problems compiling linux-2.2.2 (Aaron Hochwimmer)
  Re: NFS-client broken in 2.2.1 (was o.k. in 2.1.13x) ?? (Stefan Monnier)
  looking for a way to stuff keystrokes (Eric Fagerburg)
  Dont waste time and come and look here!! 28581 ([EMAIL PROTECTED])
  Re: PROOF: Jesus *is* Lord of the Sabbath! (Kirkus)
  Re: LINUX MERCED ("Ajay Khanna")
  Re: KDE 1.1 doesn't compile with glibc 2.1 (Thomas Esser)
  Re: threads (Marcus Sundberg)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Dave McKenzie)
Subject: Re: Linux on old as400 machines?
Date: Mon, 22 Feb 1999 01:11:48 GMT

On 11 Feb 1999 21:56:48 +0000, James Youngman
<[EMAIL PROTECTED]> wrote:

><[EMAIL PROTECTED]> writes:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> 
>> Hi,
>> 
>> I'm looking if there is any option to reuse old as400 machines with any
>> free Un*x OS. 
>> 
>> Any hint/link/suggestion/etc.. will be greatly appreciated
>> 
>> Thanks in advance,
>
>There is an AS/400 port under way but I have no idea of its status.
>You could help.


Where can I find info on this port?  I'm an AS/400 programmer with
fairly extensive internals experience (comparatively :-) and would
love to help.

--Dave

------------------------------

From: [EMAIL PROTECTED] (Steve A)
Crossposted-To: comp.os.linux.misc
Subject: Re: Glibc-2.0.112 Problem.
Date: Tue, 23 Feb 1999 10:06:27 GMT

On Sun, 14 Feb 1999 00:37:09 +0000, David Taylor
<[EMAIL PROTECTED]> wrote:

> I upgraded to glibc-2.0.112 and ended up (after 3 days) getting my
> computer to work again... However, I can't recompile the Linux kernel
> (2.2.1) [using egcs Feb08 snapshot] - it fails with undefined symbols in
> network.a
> 
> Output from make follows:
. 
. 
. 
> Now that is one hell of a lot of errors, but they are ALL referring to
> skb_put and skb_push...
> 
> Anyone have ANY clue what is going on?

I messed up a glibc2 installation, and it was the presence of the
glibc2 include files further up the path than the libc5 ones that
caused a lot of problems.

The only other time I've seen those skb_ errors is when I had the
wrong version of the pppd module code.



--
Warning: end of message imminent. Stop reading now.

We operate a zero-tolerance policy on UCE and spam.

------------------------------

From: [EMAIL PROTECTED] (Bandyopadhyay Rajarshi Dipak)
Subject: Re: How to I make a Screenshot in X.
Date: Tue, 23 Feb 1999 06:06:27 GMT

>
>How to I make a Screenshot in X.

Or use Xv. Its got this cute 'grab' button,  u know.

--Raj
-- 


================================================================
        Let me tonight look back at the span
                'Twixt dawn and dark & to my conscience say:
        "Because of some good act to beast or man,
                The world is better that I lived today."
                                
                                        ---Ella Wheeler Wilcox
=================================================================                      
                 

------------------------------

From: [EMAIL PROTECTED] (R. Bernstein)
Subject: How can I tell kernel processes in /proc?
Date: 21 Feb 1999 08:23:49 -0500

How do I find out using /proc whether a processes is a vital kernel
processes, which I assume should never be killed? For example, I
presume kflushd, kswapd, md_thread are in this category.  Looking in
/usr/include/linux/sched.h it seems to imply a process called
"swapper," but I don't see that in ps.

(It appears that ps shows kflush, kswapd, etc. as in parenthesis and
not containing any resident pages, but I suspect this is not the best
indication.)

Background: I've written a program to dynamically display/update the
process tree in Motif/Lesstif, anounced recently in freshmeat.net.
For other platforms AIX and Netbsd, there are some one can toggle
showing these processes or not.

------------------------------

From: "Robert Acklin" <[EMAIL PROTECTED]>
Subject: Re: linux 2.2.1 with SMP power management problem.
Date: Sun, 21 Feb 1999 13:31:15 -0500


Account for using TIP wrote in message <[EMAIL PROTECTED]>...
>I have a dual processor and so was keep to use the new kernel. However I
>found that during bootup
>I got messages about APM not being compatible with SMP and after 20
>minutes my whole system
>hung. A reboot required a fsck of all partitions (i.e. slooooow) and
>then the same happened again 20 minutes later.
>
>I eventually guessed what was wrong and disabled APM in the BIOS. Now I
>can run as long
>as I like.
>
>The developers are only doing Linux a disfavour by doing tricks like
>this. It should be included as a caveat in the documentation and in the
>help during config.
>
>Auto powerdown after shutdown does not work. It did with SMP in 2.0.35
>so why not now?????
>
>
>

Why don't you write it up. Do Linux a favor!



------------------------------

From: PFENNIGER Daniel <[EMAIL PROTECTED]>
Subject: Re: Problems compiling linux-2.2.2
Date: Tue, 23 Feb 1999 12:03:07 +0100

Robert Schiele wrote:

> Friedhelm Hinrichs wrote:
> > Compiling the new kernel 2.2.2 ended with the following messages (I hope
> > this does make sense to somebody):
...
...
> > make[1]: Leaving directory `/usr/src/linux-2.2/drivers'
> > make: *** [_dir_drivers] Error 2
 
> Is it correct that you have a kernel version different from 2.2.2 in /usr/src/linux?
> If this is the fact, you should make sure that the following symlinks are changed to:
> /usr/include/asm --> /usr/src/linux-2.2/include/asm-i386
> /usr/include/linux --> /usr/src/linux-2.2/include/linux
> /usr/include/scsi --> /usr/src/linux-2.2/include/scsi

I have the same problem as Friedlhelm, yet my links 
/usr/include/asm, linux & scsi 
point toward the tar made original 2.2.2 directory (/usr/src/linux), i.e.

/usr/include/asm --> /usr/src/linux/include/asm
/usr/include/linux --> /usr/src/linux/include/linux
/usr/include/scsi --> /usr/src/linux/include/scsi

Perhaps a gcc version problem?  (I use gcc 2.7.2.3).

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Dr Daniel Pfenniger                      | [EMAIL PROTECTED]
 Geneva Observatory, University of Geneva | tel: +41 (22) 755 2611 
 CH-1290 Sauverny, Switzerland            | fax: +41 (22) 755 3983
__________________________________________________________________________

------------------------------

From: [EMAIL PROTECTED] (Bow-Yaw Wang)
Crossposted-To: comp.os.linux.portable
Subject: ESS1688 sound chip and 2.2.x
Date: 23 Feb 1999 11:24:06 GMT

Greetings,

I have an ESS1688 sound chip on my Dell Latitude XPi laptop. Ever
since I upgraded my box to 2.2.0, the sound chip doesn't work
properly. The mic device works fine. But /dev/dsp is broken. There's
no error message and /proc/sound looks fine to me. More interestingly,
if I load the sb module by setting the option esstype=1888 first,
unload it, and reload it with esstype=1688, /dev/dsp works as it
should. Does anyone have a similar problem? Thanks a lot.

Yaw

*** /proc/sound ***
OSS/Free:3.8s2++-971130
Load type: Driver loaded as a module
Kernel: Linux sylow 2.2.2 #1 Mon Feb 22 22:44:59 EST 1999 i586
Config options: 0

Installed drivers: 

Card config: 

Audio devices:
0: ESS ES1688 AudioDrive (rev 11) (3.1)

Synth devices:
0: Yamaha OPL3

Midi devices:
0: ESS ES1688

Timers:
0: System clock

Mixers:
0: Sound Blaster


*** /etc/conf.modules ***
post-install sb modprobe "-k" "opl3"
options sb io=0x230 irq=5 dma=1 dma16=5 mpu_io=0x330 esstype=1688
options opl3 io=0x388     # FM synthetiser
options mpu401 io=0x330 irq=7



--

------------------------------

From: Mogens Kjaer <[EMAIL PROTECTED]>
Subject: Re: Problems compiling linux-2.2.2
Date: Tue, 23 Feb 1999 12:33:05 +0100

Friedhelm Hinrichs wrote:
> 
> Compiling the new kernel 2.2.2 ended with the following messages (I hope
> this does make sense to somebody):
....

Try setting "Socket filtering" to No in Networking Options.

Mogens

-- 
Mogens Kjaer, Carlsberg Laboratory, Dept. of Chemistry
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: [EMAIL PROTECTED] Homepage: http://www.crc.dk

------------------------------

From: BL <[EMAIL PROTECTED]>
Subject: running from a cdrom (ie, a mostly read-only filesystem)?
Date: 23 Feb 1999 10:50:33 GMT
Reply-To: no.spambots.please

is there anything special I need to do to build a running linux system that
uses a cdrom as the primary filesystem?

I'm thinking of making links from the cdrom to a writable hard disk for
obvious areas that need write-access (like /var /dev /proc).  but I'd like
/etc /bin /sbin /usr/local (and other sensitive areas) to be HARD
write-locked.  I don't mind the speed decrease of using a cdrom for my main
filesystem but I'd like the safe-and-sound security of knowing that no hacker
could ever over-write /etc files and such.

also, how would I boot the system if the main file system was a cdrom?  could
lilo work?  or would I have to boot from a floppy?  cdroms are not usually
mounted as early as hard drives are (at boot time), so how would I boot?

anyone ever done anything like this before?

-- 
AntiSpam: For email, change all 'zero' chars to letter 'o' chars.

------------------------------

From: "Rangel Reale" <[EMAIL PROTECTED]>
Subject: VGA handling
Date: Tue, 23 Feb 1999 08:43:39 -0300

Hello.

I would like to write a video driver for my video board, but before that, I
would like to learn how can I do low-level access to the standard VGA board
under Linux.
I used to program VGA in DOS with interrupts, but I think that will not work
on Linux.

Is there any place where I can start looking for info, like how to change
video modes, write a pixel, basic stuff?

Thanks,
Rangel Reale




------------------------------

From: Aaron Hochwimmer <[EMAIL PROTECTED]>
Subject: Re: Problems compiling linux-2.2.2
Date: Tue, 23 Feb 1999 21:55:48 +0000

Well I got this instead :-) when doing a make bzImage after make mrproper,
make xconfig, make dep, make clean...

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -DEXPORT_SYMTAB -c
console.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -DEXPORT_SYMTAB -c
selection.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -DEXPORT_SYMTAB -c serial.c

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -c -o tty_io.o tty_io.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -c -o n_tty.o n_tty.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -c -o tty_ioctl.o
tty_ioctl.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
-malign-jumps=2 -malign-functions=2 -DCPU=686   -c -o mem.o mem.c
mem.c:18: linux/i2c.h: No such file or directory
make[3]: *** [mem.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.2.2/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.2.2/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory `/usr/src/linux-2.2.2/drivers'
make: *** [_dir_drivers] Error 2

I am currently running (a locally compiled) version 2.2.1.


Friedhelm Hinrichs wrote:

> Compiling the new kernel 2.2.2 ended with the following messages (I hope
> this does make sense to somebody):
>
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2
> -malign-jumps=2 -malign-functions=2 -DCPU=586   -c -o loopback.o
> loopback.c
> /usr/src/linux/include/net/sock.h: In function `sk_filter':
> In file included from loopback.c:51:
> /usr/src/linux/include/net/sock.h:796: dereferencing pointer to
> incomplete type
> /usr/src/linux/include/net/sock.h:796: dereferencing pointer to
> incomplete type
> /usr/src/linux/include/net/sock.h:796: warning: passing arg 1 of
> `sk_run_filter' from incompatible pointer type
> /usr/src/linux/include/net/sock.h:796: too few arguments to function
> `sk_run_filter'
> /usr/src/linux/include/net/sock.h: In function `sk_filter_release':
> /usr/src/linux/include/net/sock.h:807: warning: implicit declaration of
> function `sk_filter_len'
> /usr/src/linux/include/net/sock.h:811: dereferencing pointer to
> incomplete type
> /usr/src/linux/include/net/sock.h: In function `sk_filter_charge':
> /usr/src/linux/include/net/sock.h:817: dereferencing pointer to
> incomplete type
> make[3]: *** [loopback.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.2/drivers/net'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.2/drivers/net'
> make[1]: *** [_subdir_net] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.2/drivers'
> make: *** [_dir_drivers] Error 2
>
> --

--
"Microsoft OS's are bad, and their morals are even worse..."  - Linus Torvalds
----
Aaron Hochwimmer | Geothermal Group, Eng. Science, Auckland University
[EMAIL PROTECTED] | TEL: +64-9-373-7599 xtn 7490
http://www.esc.auckland.ac.nz/People/Students/Hochwimmer
PB Power (GENZL Div) | [EMAIL PROTECTED] | Ph: +64-9-375-3758 (DDI)




------------------------------

From: Stefan Monnier 
<[EMAIL PROTECTED]>
Subject: Re: NFS-client broken in 2.2.1 (was o.k. in 2.1.13x) ??
Date: 23 Feb 1999 09:00:35 -0500

>> As I said, this happens with SUN-servers. If the sources are on a linux

I seem to remember similar stories and some of them at least were due to recent
kernels triggering a bug in Sun's nfs server (fixed by a patch whose number I
never tried to remember).


        Stefan

------------------------------

From: Eric Fagerburg <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: looking for a way to stuff keystrokes
Date: Tue, 23 Feb 1999 07:36:44 -0700

I can read from a virtual console by opening /dev/vcs? or /dev/vcsa? but
I can't figure out how to get keystrokes back in.  I'd love to be able
to do it in a user mode app running as root but if it's only possible
from kernel mode I'll take it at this point.

Thanks in advance for any help anyone can give me.

Eric Fagerburg
[EMAIL PROTECTED]

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: 
comp.publish.electronic.developer,comp.society.development,demon.ip.developers,intel.managedpc.developer_support,it.comp.linux.development,linux.redhat.development,microsoft.public.access.developers.toolkitode,microsoft.public.accessibility.developer,microsoft.public.enable.developer
Subject: Dont waste time and come and look here!! 28581
Date: Tuesday, 23 Feb 1999 14:41:13 -0600

Yeah here it his Sorry about before wasnt quite finished but check it out now .
youll find my service here.
Http://members.xoom.com/entertainni/
or the mirror
http://members.tripod.com/entertainni/
thanks
Phil
Cyberactive



zb

------------------------------

From: gkirk@*nospam*comp.uark.edu (Kirkus)
Crossposted-To: 
alt.society.underwear,comp.sys.mac.misc,comp.sys.amiga.hardware,fr.rec.voyages
Subject: Re: PROOF: Jesus *is* Lord of the Sabbath!
Date: Tue, 23 Feb 1999 01:21:34 -0600

I thought Ozzy Osbourne was the lord of Sabbath...Or maybe it was Tony Iommi???

------------------------------

From: "Ajay Khanna" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: LINUX MERCED
Date: Sat, 20 Feb 1999 21:50:01 -0600


Christopher B. Browne <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...

>I saw a Gartner Group research paper a while back indicating:
...
>In short, I suggest that you not hold your breath...

well, don't underestimate the people who are interested in Linux under a new
architecture, regardless of what the Gartner group says, just for the thrill
and challenge of it.  What do you think Gartner group has to say about Linux
on the Amiga?  I fully expect Linux hackers to swarm to IA-64 en masse and
quickly adopt the new architecture.

Ajay Khanna




------------------------------

From: Thomas Esser <[EMAIL PROTECTED]>
Subject: Re: KDE 1.1 doesn't compile with glibc 2.1
Date: 23 Feb 1999 15:27:20 GMT

T. J. Domsalla <[EMAIL PROTECTED]> wrote:
: I did it before with glibc 2.0.7 and it worked fine. Now I get the message
: cross compiling=yes (from the c++ compilier, egcs 1.1.1) and "don't know

Normally, this just means that you compiler cannot compile+run an simple
test program. That it is not KDE's fault. You have somehow managed to
screw up your system.

Thomas

-- 
Thomas Esser                http://www-b.informatik.uni-hannover.de/~te/
University of Hannover, Germany
Informatics Institute (Databases and Information Systems Group)

------------------------------

From: [EMAIL PROTECTED] (Marcus Sundberg)
Subject: Re: threads
Date: 23 Feb 1999 18:12:01 GMT

In article <[EMAIL PROTECTED]>,
        Jim Cromie <[EMAIL PROTECTED]> writes:
> J.H.M. Dassen (Ray) wrote:
> 
>> AFAIK, the pthread functions are implemented by a library (an add-on for
>> glibc); they're not in the kernel, so you can't use them in kernel source.
>> What you can do is use the kernel code through which pthread is implemented,
>> like clone().
> 
> As I read it, glibc2.0.7 is thread safe, no add-ons (presumably you mean
> patches)
> are needed.

Thread safety has nothing to do with threads.
To use pthreads you need libpthread.so, which is an add-on (not a patch!)
for glibc. (Well, there are other pthread libraries for Linux, but
the one which comes with glibc is more or less the "standard"
implementation.)

//Marcus
-- 
===============================+====================================
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: [EMAIL PROTECTED]

------------------------------


** 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
******************************

Reply via email to