Linux-Development-Sys Digest #51, Volume #7 Fri, 13 Aug 99 16:14:33 EDT
Contents:
How to resolve the mismatch type definition ? ("Cute Panda")
Re: DRIVER for Toshiba DVD-RAM (only tested on kernel 2.0.36) (Christian Mund)
Best place in kernel for block encryption ? (R�khar�ur Egilsson)
Re: Stupid question re: sound config (root)
Seriel-programming ([EMAIL PROTECTED])
Re: RH 6.0 modprobe for lo (Robin Becker)
Re: DRIVER for Toshiba DVD-RAM (only tested on kernel 2.0.36) (Christian Mund)
Re: Stupid question re: sound config (Guilhem Tardy)
Re: Kernel upgrades... why? (Howard Mann)
Re: Best place in kernel for block encryption ? (R�khar�ur Egilsson)
Re: Broken Select ("Al Stanley")
Re: which mirror for Linux kernel (A Guy Called Tyketto)
Re: threads ("Bill Burris")
Re: How do I use source RPMs (David Fox)
Re: KDE for Redhat 6.0 (Guilhem Tardy)
----------------------------------------------------------------------------
From: "Cute Panda" <[EMAIL PROTECTED]>
Subject: How to resolve the mismatch type definition ?
Date: 13 Aug 1999 10:39:37 GMT
Dear All,
I'm using RedHat Linux 6.0 and MetroLink 1.2.4 Motif to do the porting of
our product, now I
come across a problem described as follows:
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/include/stddef.h:255:
conflicting types for `wchar_t'
/usr/X11R6/include/X11/Xlib.h:79: previous declaration of `wchar_t'
Anybody knows how to resolve it ? what directive should I define ?
please help, thanks a lot!
------------------------------
From: Christian Mund <[EMAIL PROTECTED]>
Subject: Re: DRIVER for Toshiba DVD-RAM (only tested on kernel 2.0.36)
Date: 13 Aug 1999 12:30:48 GMT
rdm wrote:
>
>
> Thanks to a clue in a post by Steve McIntyre in this group on 7/27/99
> that the Toshiba SD-W1101 DVD-RAM doesn't like 6-byte SCSI I/O commands
> (but DOES tolerate 10-byte commands), I was able to write a patch to get
> the Toshiba to work. I apologize for not having posted this sooner (I
> could have posted on Monday), but I was holding out in the hopes of
> testing on a more recent kernel than 2.0.36 (this is the latest kernel we
> have installed here right now). Having seen recent messages in this
group
> about the Toshiba, I figured I better post this now and wait on
confirming
> the patch with a newer kernel until a future date.
> This has ***ONLY*** been verified to work with the Tekram DC-390 SCSI
> controller card + Linux kernel 2.0.36. Certain other SCSI controller
> cards may need patching (basically, any card whose driver contains
> the words "WRITE_10", "WRITE_6", "READ_6", or "READ_10" is suspect.
> You can easily look to see if this applies to your card by doing a grep
> for these phrases in the drivers/scsi directory of your Linux source
> directory). Kernels newer than 2.0.36 *SHOULD* work, but again, I
haven't
> had an opportunity to verify any.
>
> Would anyone be kind enough to tell me who I should submit this patch
> to, to get it incorporated into the standard Linux kernel distributions?
> Please e-mail: [EMAIL PROTECTED] Thanks in advance!
>
> Good luck!!
>
> ---Reed Meyer
> [EMAIL PROTECTED]
Hello Reed,
Congratulations, it works !
I have tested it with Kernel 2.2.11 and the following Hardware :
Drive : TOSHIBA SD-1101 ,SCSI HA: Adaptec 3940AU.
The only patch i used was the sd.c_patch. You don�t need to modify scsi.c,
bcause the unpatched 2.2.x Kernel detects the SD-W1101 correctly as Device
Type Optical ( LUN 1 = Optical in 2-LUN Mode ).
With best regards,
Christian Mund
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED]�encroute.fr (R�khar�ur Egilsson)
Subject: Best place in kernel for block encryption ?
Date: 12 Aug 1999 15:17:19 GMT
Reply-To: =?iso-8859-1?Q?[EMAIL PROTECTED]=E9-en-croute.fr?=
Has there been any discussion here about where the most efficient
place is in the kernel is to put an encryption layer.
I would want it to work for all block devices. (i.e. all mountable
filesystems, both current and future).
I think one such place might be the cache buffers, any comments
on that ? "linux/fs/buffer.c"
--
RIKHARDUR EGILSSON
echo '[q]sa[ln0=aln80%Pln80/snlbx]16isb15CB32EF3AF9C0E5D7272C3AF4F2snlbxq'|dc
------------------------------
From: root <[EMAIL PROTECTED]>
Subject: Re: Stupid question re: sound config
Date: Fri, 13 Aug 1999 14:02:29 GMT
"Ashutosh S. Rajekar" wrote:
> Hello,
>
> On Fri, 13 Aug 1999, root wrote:
>
> > I'm a newbie, so to speak. Any help would be appreciated -- I can't
> > seem to get my sound card to work. It's a trident 4d PCI card. No
> > ideas.
> You will probably have the file 'sndconfig' installed on your box.
> At the shell prompt, type sndconfig, and it will probably autodetect your
> sound card. If it doesn't, then read the HOW-TO's in /usr/doc/HOWTO/***.
>
> > I tried Lothar - no help. Please help me, oh, the ignorant
> > one....
> >
> >
> >
> >
> >
>
> Thanks,
> --------------------
> Ashutosh S. Rajekar
Thank you for your response! After I posted this I looked through the other
messages and did those things. I have some ideas for follow-up now.
Troy
------------------------------
From: [EMAIL PROTECTED]
Subject: Seriel-programming
Date: Fri, 13 Aug 1999 08:05:50 +0200
I am going to write som programs that communicates trough the seriel
port.
Unfortunately I can't find any detaild and good-explaining documentation
on the subject (I don't think the Seriel.HOWTO and
Seriel-programming.HOWTO explains that part - it just showing examples).
I'm sure there exists some libraries of some kind. What are they called?
--
Rasmus Resen Amossen | http://w1.1444.telia.com/~u144400001
stud.mat.dat |
Steng�rdsv�nge 76, 2800 Lyngby | http://www.math.ku.dk/~moh
------------------------------
From: Robin Becker <[EMAIL PROTECTED]>
Subject: Re: RH 6.0 modprobe for lo
Date: Thu, 12 Aug 1999 17:33:22 +0100
In article <[EMAIL PROTECTED]>, Johan Kullstam
<[EMAIL PROTECTED]> writes
>Robin Becker <[EMAIL PROTECTED]> writes:
>
>> I'm getting some spurious boot messages about modprobe being unable to
>> find the lo device. I have inserted an 'alias lo off' line in
>> /etc/conf.modules and certainly attempts made after the boot to modprobe
>> for lo certainly don't cause errors. I have most of the net stuff in
>> modules, but can't figure this nonsense out.
>
>the redhat initscripts are trying to bring up ip aliases. go to
>/etc/sysconfig/network-scripts/ and find the ifup-aliases[1].
>
>you want to kill this script. in my case i inserted `exit 0' at the
>point right after the initial comments stop. this provides a nice
>short circuit but leaves the script in case i should want it.
>
I'll give that a go thanks
>this fixes the modprobe not finding lo:1 lo:2 ... lo:50 and similar
>eth: kvetching. however, i experience a significant delay at boot at
>the bringing up lo and eth spots, unless i use a init ramdisk
>(initrd).
>
I don't see that, but could it be related to searching for a nameserver.
I don't have any eth so my net is local+default through ppp0
>speaking of initrd, my disk access on kernel 2.2.x with x >= 7 on my
>scsi system is also hosed (very slow, but no corrupt data. bizarre.)
>unless i use an initrd. if have grovelled through many of the
>initscripts but i cannot figure out this initrd dependence. until
>then, i will just use initrd.
>
I'm using standard 2.2.11 without any noticeable slowness. Are you
fixing up the links in /boot as you go along?
>[1] i am not at my linux box. i think this is the name of the file.
> it ends in -aliases in any event.
>
--
Robin Becker
------------------------------
From: Christian Mund <[EMAIL PROTECTED]>
Subject: Re: DRIVER for Toshiba DVD-RAM (only tested on kernel 2.0.36)
Date: Fri, 13 Aug 1999 13:30:54 GMT
rdm wrote:
>
>
> Thanks to a clue in a post by Steve McIntyre in this group on 7/27/99
> that the Toshiba SD-W1101 DVD-RAM doesn't like 6-byte SCSI I/O commands
> (but DOES tolerate 10-byte commands), I was able to write a patch to get
> the Toshiba to work. I apologize for not having posted this sooner (I
> could have posted on Monday), but I was holding out in the hopes of
> testing on a more recent kernel than 2.0.36 (this is the latest kernel we
> have installed here right now). Having seen recent messages in this
group
> about the Toshiba, I figured I better post this now and wait on
confirming
> the patch with a newer kernel until a future date.
> This has ***ONLY*** been verified to work with the Tekram DC-390 SCSI
> controller card + Linux kernel 2.0.36. Certain other SCSI controller
> cards may need patching (basically, any card whose driver contains
> the words "WRITE_10", "WRITE_6", "READ_6", or "READ_10" is suspect.
> You can easily look to see if this applies to your card by doing a grep
> for these phrases in the drivers/scsi directory of your Linux source
> directory). Kernels newer than 2.0.36 *SHOULD* work, but again, I
haven't
> had an opportunity to verify any.
>
> Would anyone be kind enough to tell me who I should submit this patch
> to, to get it incorporated into the standard Linux kernel distributions?
> Please e-mail: [EMAIL PROTECTED] Thanks in advance!
>
> Good luck!!
>
> ---Reed Meyer
> [EMAIL PROTECTED]
Hello Reed,
Congratulations, it works !
I have tested it with Kernel 2.2.11 and the following Hardware :
Drive : TOSHIBA SD-1101 ,SCSI HA: Adaptec 3940AU.
The only patch i used was the sd.c_patch. You don�t need to modify scsi.c,
bcause the unpatched 2.2.x Kernel detects the SD-W1101 correctly as Device
Type Optical ( LUN 1 = Optical in 2-LUN Mode ).
With best regards,
Christian Mund
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: Guilhem Tardy <[EMAIL PROTECTED]>
Subject: Re: Stupid question re: sound config
Date: Fri, 13 Aug 1999 11:19:09 -0400
Hi!
I would like to setup my AWE64, too.
I use RH 6.0 upgraded with a stock kernel 2.2.11, sndconfig looks for a
module soundcore.o, which is not installed (there's awe_wave.o, sb.o,
sound.o and soundlow.o). Is it because I don't use the RH tree anymore?
Should I put one of these modules in conf.modules with the appropriate
settings and what is a typical /etc/sysconfig/sound file?
Guilhem.
------------------------------
From: Howard Mann <[EMAIL PROTECTED]>
Subject: Re: Kernel upgrades... why?
Date: 13 Aug 1999 15:30:44 GMT
bobrien wrote:
>
> I can understand making the jump from 1.x or 2.1 or 2.2 but it is really
a
> necessity or even useful to upgrade each release... 2.2.5-15, 2.2.5-20,
> 2.2.10, 2.2.11 ... etc... I'm still quite new to this and curious why
> everyone seems to jump right into each tiny upgrade.
You might get the _impression_ that "everyone" is doing this if you
read these newsgroups. This is certainly not the case.
There is no need to upgrade unless you _need_ something supplied by the
upgrade, like new hardware support, as you note in your post.
Some would recommend certain upgrades that "fix" security-related
problems.
I use Red Hat 5.0 with kernel version 2.0.36. I upgraded the kernel
to enable me to mount/read my FAT 32 partition. I have no current need to
upgrade to the 2.2.X versions.
I can't see a reason
> to upgrade until my soundcard has built in support in the kernel. Or I
can
> plug in a module for it.
>
> just curious,
> Blake
>
Cheers,
Howard Mann.
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED]�encroute.fr (R�khar�ur Egilsson)
Subject: Re: Best place in kernel for block encryption ?
Date: 13 Aug 1999 12:37:05 GMT
Reply-To: =?iso-8859-1?Q?[EMAIL PROTECTED]=E9-en-croute.fr?=
On Thu, 12 Aug 1999 16:53:35 GMT, Kaz Kylheku <[EMAIL PROTECTED]> wrote:
>On 12 Aug 1999 15:17:19 GMT, R�khar�ur Egilsson <[EMAIL PROTECTED]�encroute.fr>
>wrote:
>>Has there been any discussion here about where the most efficient
>>place is in the kernel is to put an encryption layer.
>>
>>I would want it to work for all block devices. (i.e. all mountable
>>filesystems, both current and future).
>
>The proper place might be in the block device loopback driver. I believe
>that this already exists.
If I understand correctly, the loopback driver sits on top of a character
"device" (file) that itself sits on top of a block device (disk). All
that the loopback devie does is to "simulate" a block device thru system
calls and buffering.
So when you have created a filesystem and put some files on this loopback
device you have FOUR (4) layers between the actual data on the disk and
your applications (f.ex sendmail)
This is hell for performance !
--
RIKHARDUR EGILSSON
echo '[q]sa[ln0=aln80%Pln80/snlbx]16isb15CB32EF3AF9C0E5D7272C3AF4F2snlbxq'|dc
------------------------------
From: "Al Stanley" <[EMAIL PROTECTED]>
Subject: Re: Broken Select
Date: Fri, 13 Aug 1999 09:54:41 -0500
Kaz Kylheku wrote in message ...
>On Thu, 12 Aug 1999 19:02:10 -0500, Al Stanley <[EMAIL PROTECTED]>
>wrote:
>>The select() functionality in the 2.2.9 kernel appears to be broken. If
>>there is nothing readable or writable when select() is initially called,
it
>>will not return until it times out. The man page says (and the way it is
>>normally used) that it will return when something int readfds becomes
>>readable or something in writefds becomes writable, and that the timeout
is
>>only an upper boundary. Our testing indicates that it will not return
until
>>the timeout expires. Anyone know of a workaround? Or has anyone else
>>noticed this problem yet?
>
>I've been using 2.2.9 since it came out, and I haven't seen any strange
>behaviors in any networking software. If what you are saying is true, than
it
>would probably follow that selects with a null struct timeval * argument
would
>block forever, resulting in a lot of catatonic applications. Have you
>investigated what happens if you make the wait infinite?
We tested with a NULL timeval * and the application did in fact go
catatonic. As near as I can tell the problem lies in the schedule_timeout
function in /usr/src/linux/kernel/sched.c, which is called from the bottom
of the loop in do_select in /usr/src/linux/fs/select.c. This function seems
to be setting up a timer to process the sleeping requests, via the
timer.function = process_timeout, however after setting up the timer struct
it does the following:
add_timer(&timer);
schedule();
del_timer(&timer);
The effect of this on an unloaded system is that schedule returns
immediately and the timer gets deleted, but regardless, since the
timer.expires = the select delay, the drivers poll() function does not get
checked again until the delay times out, because they are sleeping on the
wait queues and process_timeout is the only place that wake_up_process()
gets called. So rather than periodically checking the poll() status, the
current implementation only checks when select() is first called and when
the delay times out.
Ed Okerson
Quicknet Technologies, Inc.
------------------------------
From: [EMAIL PROTECTED] (A Guy Called Tyketto)
Subject: Re: which mirror for Linux kernel
Date: 13 Aug 1999 13:03:08 -0500
=====BEGIN PGP SIGNED MESSAGE=====
Hash: SHA1
Phil Howard ([EMAIL PROTECTED]) wrote:
> Can someone tell me which mirror site (in US) is most reliable, is
> mostly likely to stay around, and (this is important) keeps the
> timestamps consistent? I'm trying to make a continuing mirror of
> the kernel files, and because the mirror sites are inconsistent I
> have to mirror from a single site. I already have most files, so
> I don't want to download them all over again (which would happen
> where the timestamps are goofed).
>
> --
> Phil Howard KA9WGN
> [EMAIL PROTECTED] [EMAIL PROTECTED]
You may want to participate, in the Linux Kernel Archives Mirror
System. Since as you said, most mirrors are out of date, and
ftp.kernel.org is so bogged, the above system works wonderfully for when
kernels are released. if you do a nslookup on ftp.us.kernel.org, you'll
see the round-robin list of IP addresses that are for the site. (replace
.us with your fave 2 letter country code for your country, for similar
results out side the US). the URL for the LKAMS is
http://www.kernel.org/mirrors/. Give it a try.
BL.
- --
Brad Littlejohn | Email: [EMAIL PROTECTED]
Unix Systems Administrator, | [EMAIL PROTECTED]
WebMaster, NewsMaster.. Smeghead! :) | http://www.omnilinx.net/~tyketto
PGP: 1024/E9DF4D85 67 6B 33 D0 B9 95 F4 37 4B D1 CE BD 48 B0 06 93
=====BEGIN PGP SIGNATURE=====
Version: GnuPG v0.9.10 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3tB4+yBkZmuMZ8L8RAhsGAJ90QdSKeWPMxS+bFootYNVwhvYO1gCdHXC0
EU0UbvWOPyz6NPO/bY3kUH4=
=MExR
=====END PGP SIGNATURE=====
------------------------------
From: "Bill Burris" <[EMAIL PROTECTED]>
Subject: Re: threads
Date: Fri, 13 Aug 1999 11:58:57 -0600
Thanks for the comments, everyone.
Tim O'Reilly (http://www.oreilly.com/ask_tim/oss_com.html) has convinced me
that Linux is moving in interesting directions, so I am planning on putting
Linux back on my system after not using it for the last 3 years.
On Windows, muti-threading has become an important tool for me because of
the real-time and I/O intensive nature of my applications.
I was just reading a couple of win32 multi-threaded books
(http://www.icrossroads.com/~spider/sysbks.html). The one by Pham & Garg
talked about threads on other systems but failed to say anything about
Linux, therefore I posted my question here.
The O'Reilly book by Cohen & Woodring is top notch, now I need to find a
book like that for Threads on Linux.
Bill
--
http://www.icrossroads.com/~spider
------------------------------
From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Subject: Re: How do I use source RPMs
Date: 13 Aug 1999 09:56:35 -0700
[EMAIL PROTECTED] writes:
> No, it's because I also test and develop cutting edge code - and so my system
> is not always in a pristine state.
>
> BTW, another defect is that building source RPMS have to be done as
> root. That's a terrible idea. You can fix some of this by making the
> build dir writable, but I don't think that completely solves the
> problem.
Almost all RPMS now use a separate build root, so you don't have to be
root to build them. The only exceptions are packages that need to do
operations like mknode, and usually these can be performed by post
installation scripts.
--
David Fox http://hci.ucsd.edu/dsf xoF divaD
UCSD HCI Lab baL ICH DSCU
------------------------------
From: Guilhem Tardy <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,redhat.servers.general
Subject: Re: KDE for Redhat 6.0
Date: Fri, 13 Aug 1999 15:34:17 -0400
RedHat distributes both KDE and Gnome. You'll find KDE on the CD-ROM!
Sunil wrote:
>
> I am looking for KDE for linux head hat 6.0. I coundn't find any searching
> over the net. If you know the location where I can get it, I wouldly
> appretiate.
> I am abother concer
> I want other people access my Lunix box via FTP. who do I set up user
> account, rights and other things that I need to do. Thank you in advance
> for your help.
>
> ------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
--
Guilhem Tardy phone: (613) 993-8232
Communications Research Center email: [EMAIL PROTECTED]
Network Systems and Technologies web: http://www.crc.ca/
------------------------------
** 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
******************************
