Linux-Development-Sys Digest #413, Volume #8 Sat, 13 Jan 01 15:13:13 EST
Contents:
Re: Upgrading glibc using rpm (Karen Rosin)
Re: need help fixing a tcp kernel problem (Nix)
Re: Problems upgrading to glibc 2.2 (Nix)
Re: code language for Linux kernel (Nix)
Re: Maturity of Bonobo and CORBA (Nix)
2.4.0 on Athlon 1G / VIA KT 133 ([EMAIL PROTECTED])
Re: can libraries be made to load> 0x40000000 (Bob Hauck)
Re: need help fixing a tcp kernel problem ("Peter T. Breuer")
driver for Alcatel PC-NIC ("Jens")
Re: can libraries be made to load > 0x40000000 (Eric Taylor)
Re: need help fixing a tcp kernel problem (Eric Taylor)
Re: 2.2.18 & USB Does It or Doesn't It (Todd Knarr)
----------------------------------------------------------------------------
Date: Sat, 13 Jan 2001 15:23:25 +0200
From: Karen Rosin <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Upgrading glibc using rpm
Pete Lachall wrote:
>
> I'm upgrading glibc from 2.1.1 to 2.1.3 on Redhat 6.2 using the rpm.
> After running 'rpm -U xxx.rpm' I get a bunch of conflicts, all of them
> having to do with the 'localedata' package of my current glibc. Any
> ideas would be greatly appreciated.
>
> - Pete Lachall
Download Aduvizor from www.aduva.com
it will help you with the conflicts, resolve and download.
Karen
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: need help fixing a tcp kernel problem
Date: 13 Jan 2001 12:17:55 +0000
On Wed, 10 Jan 2001, Peter T. Breuer spake:
> though I'll mention vger.linux.org as being the list machine, with
ITYM `vger.kernel.org'. HTH. ;)
--
`Picture someone frothing at the mouth, waving a cleaver, and drawing
down death, destruction, fire, flood, pestilence, rape and looting
over SysV. This is perfectly normal reaction.' --- Andrew Vendryes
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: Problems upgrading to glibc 2.2
Date: 13 Jan 2001 12:24:07 +0000
On Tue, 09 Jan 2001, vadim yowled:
> First, please excuse my horrible English
It's not horrible at all.
> It seemed to be ok, at least the system was still running after
> reloading processes.
> I looked at the glibc howto and tried to do what it said. I added
The glibc howto is hugely outdated.
> /usr/i386-glibc21-linux/lib to /etc/ld.so.conf (for glibc 2.1
> compatibility) and run ldconfig -v.
>
> Again, it seemed to run fine.
> I tried dir.
> Segmentation fault.
That was a clue. A great big clue wrapt in neon with bells on.
Andreas Jaeger said in the glibc FAQ[1]:
,----
| 2.32. What has do be done when upgrading to glibc 2.2?
|
| {AJ} The upgrade to glibc 2.2 should run smoothly, there's in general no
| need to recompile programs or libraries. Nevertheless, some changes might
| be needed after upgrading:
| - The utmp daemon has been removed and is not supported by glibc anymore.
| If it has been in use, it should be switched off.
| - Programs using IPv6 have to be recompiled due to incompatible changes in
| sockaddr_in6 by the IPv6 working group.
| - The Berkeley db libraries have been removed (for details see ??nssdb).
| - The format of the locale files has changed, all locales should be
| regenerated with localedef. All statically linked applications which use
| i18n should be recompiled, otherwise they'll not be localized.
| - glibc comes with a number of new applications. For example ldconfig has
| been implemented for glibc, the libc5 version of ldconfig is not needed
| anymore.
| - There's no more K&R compatibility in the glibc headers. The GNU C library
| requires a C compiler that handles especially prototypes correctly.
| Especially gcc -traditional will not work with glibc headers.
|
| Please read also the NEWS file which is the authoritative source for this
| and gives more details for some topics.
`----
i.e. what you do is, do *not* move your old libraries away. Just install
the new glibc and everything should Just Work. The `move old libraries
into a new directory and point ld.so.conf at them' trick was exclusively
for going from libc5 to glibc2, as the two libraries were not binary
compatible.
In general if the major version number of two versions of the same
library are the same (e.g glibc-2.1.3.so and glibc-2.2.so), then they
*are* compatible and you only need to keep the one with the highest
version number accessible.
Hope this helps.
[1] I hope Mandrake provide this somewhere even with binary packages
of glibc; it is gold dust.
--
`Picture someone frothing at the mouth, waving a cleaver, and drawing
down death, destruction, fire, flood, pestilence, rape and looting
over SysV. This is perfectly normal reaction.' --- Andrew Vendryes
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: code language for Linux kernel
Date: 13 Jan 2001 02:17:25 +0000
On Tue, 09 Jan 2001, Kaz Kylheku stipulated:
> Unfortunately, the language forbids using longjmp to restart a
> function whose execution has already terminated.
*Real* languages, of course, have continuations... :)
--
`Picture someone frothing at the mouth, waving a cleaver, and drawing
down death, destruction, fire, flood, pestilence, rape and looting
over SysV. This is perfectly normal reaction.' --- Andrew Vendryes
------------------------------
From: Nix <$}xinix{[email protected]>
Subject: Re: Maturity of Bonobo and CORBA
Date: 13 Jan 2001 12:12:01 +0000
On 10 Jan 2001, Kaelin Colclasure said:
> If not, I recommend
> taking a close look at Orbacus <http://www.ooc.com/>. It's a very
> feature complete
That must be almost unique. IME, most CORBA servers implement the bare
minimum. (Of course, they always implement a *different* `bare minimum';
great for interoperability, oh yes.)
--
`Picture someone frothing at the mouth, waving a cleaver, and drawing
down death, destruction, fire, flood, pestilence, rape and looting
over SysV. This is perfectly normal reaction.' --- Andrew Vendryes
------------------------------
Date: Sat, 13 Jan 2001 15:14:32 +0000
From: [EMAIL PROTECTED]
Subject: 2.4.0 on Athlon 1G / VIA KT 133
Well I just had an unimpressive go with the 2.4.0 kernel.
This is on a very stable system that has been running Debian 2.2 r2 with
Linux Kernel 2.2.18 without any problems at all. To skip to the point, my
test drive ended when the system appeared to be suffering some kind of data
corruption. Here's the hardware...a plain vanilla configuration;
AMD Athlon Thunderbird 1000
Tyan Trinity KT main board (VIA KT 133 Chipset)
Voodoo 3 3000 AGP video card
3Com 3C905B-TXNM ethernet card
Sound Blaster 16 ISA (CT 4170) sound card.
Quantum Fireball lct 10, UDMA 66, 5.1G hard drive (on channel A)
Mitsumi 48x UDMA 33 CD Drive (on channel B)
USB is disabled in BIOS
Here's what happened.
Configured, built, and installed the kernel without incident.
Upon booting the system I received messages from the kernel about setting
idebus=XX to get the DMA 66 going. So I added the kernel option to
lilo.conf and ran lilo. The kernel seemed to accept that and indicated a
DMA 66 ide bus speed. But then the kernel went on to identify the disk as
UDMA 33. So I used hdparm -X66 to set the mode. Well I was highly
dissapointed to find out, using a disk benchmark, that there was absolutely
no difference in disk speed compared to the 2.2.18 kernel which I know is
running the disk at DMA 33. Based on my experience, DMA 66 does not work in
2.4.0 for my configuration.
What happened to the Soundblaster driver? With the 2.2.18 kernel, I just
set the IRQ, IO, and DMA in the kernel config and it works fine. Now it
tells me I have to enter the data as a kernel option and the driver doesn't
even provide any status during boot. Well, I did add the kernel options,
but no soundcard worky. The doc/Soundblaster said something about ISAPnP.
I don't need or want that software since my BIOS does a perfectly fine job
of configuring the card. So are they telling me that my Sound card has been
broken all this time? Works pretty good for a broken one.
Well, I gave up on the 2.4.0 kernel when, for no reason at all, it stopping
booting at init level 2 and started booting at init level 3. All I can say
to that one is ??????
You know, maybe its me and I'm just not doing something right, but I'm
fairly experienced at building and installing kernels. Its pretty routine
for me. This is sad. In my years of using Linux, geez, 6 or 7 years
now, I have never had such grave problems running a new kernel version.
Looks like its gonna be a long time before I upgrade from 2.2 And there's
been so much media hype over this thing...how pathetic. AFAIC, they should
have kept this one quiet.
==============================================================
Excerpts from .config
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set
#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_M686FXSR is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
# CONFIG_X86_UP_IOAPIC is not set
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_PM is not set
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Plug and Play configuration
#
# CONFIG_PNP is not set
#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
#
# Multi-device support (RAID and LVM)
##
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD7409 is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_BLK_DEV_OSB4 is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
#
# SCSI support
#
# CONFIG_SCSI is not set
# CONFIG_MD is not set
#
# Sound
#
CONFIG_SOUND=y
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
CONFIG_SOUND_OSS=y
# CONFIG_SOUND_TRACEINIT is not set
CONFIG_SOUND_DMAP=y
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
# CONFIG_SOUND_CS4232 is not set
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
CONFIG_SOUND_SB=y
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
CONFIG_SOUND_YM3812=y
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMPCI is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set
------------------------------
From: [EMAIL PROTECTED] (Bob Hauck)
Subject: Re: can libraries be made to load> 0x40000000
Reply-To: bobh{at}haucks{dot}org
Date: Sat, 13 Jan 2001 15:44:27 GMT
On Sat, 13 Jan 2001 02:59:28 GMT, Eric Taylor <[EMAIL PROTECTED]> wrote:
>I've got a app that needs more
>than 1 gig virtual address space.
>All the libraries load at 0x40000000,
Does the kernel compile option for max memory size change this? I don't
know, just wondering.
> I need all the dynamic memory to
> be contiguous so I can write it all out
> in one i/o.
Could you use writev() then?
--
-| Bob Hauck
-| To Whom You Are Speaking
-| http://www.haucks.org/
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: need help fixing a tcp kernel problem
Date: Sat, 13 Jan 2001 16:15:18 GMT
Nix <$}xinix{[email protected]> wrote:
> On Wed, 10 Jan 2001, Peter T. Breuer spake:
>> though I'll mention vger.linux.org as being the list machine, with
[ of linux-kernel@ ]
> ITYM `vger.kernel.org'. HTH. ;)
Errr, yes, sorry. I've yet to get used to rutgers being not where it's at.
Peter
------------------------------
From: "Jens" <[EMAIL PROTECTED]>
Subject: driver for Alcatel PC-NIC
Date: Sat, 13 Jan 2001 18:45:05 +0100
Is anyone currently trying to develop a driver for the (PCI) internal
DSL-modem of Alcatel?
------------------------------
From: Eric Taylor <[EMAIL PROTECTED]>
Subject: Re: can libraries be made to load > 0x40000000
Date: Sat, 13 Jan 2001 18:29:03 GMT
Bob Hauck wrote:
>
> On Sat, 13 Jan 2001 02:59:28 GMT, Eric Taylor <[EMAIL PROTECTED]> wrote:
>
> >I've got a app that needs more
> >than 1 gig virtual address space.
> >All the libraries load at 0x40000000,
>
> Does the kernel compile option for max memory size change this? I don't
> know, just wondering.
One piece of kernel code I saw surprised me. Is it true that
that if I want to have more than 1 gig of physical memory
then I have to give the kernel 2 gigs of address space, leaving
just 2 gigs for process space. And I need my own custom
kernel to do this.
In page.h:
* A __PAGE_OFFSET of 0xC0000000 means that the kernel has
* a virtual address space of one gigabyte, which limits the
* amount of physical memory you can use to about 950MB. If
* you want to use more physical memory, change this define.
*
* For example, if you have 2GB worth of physical memory, you
* could change this define to 0x80000000, which gives the
* kernel 2GB of virtual memory (enough to most of your physical memory
* as the kernel needs a bit extra for various io-memory mappings)
>
> > I need all the dynamic memory to
> > be contiguous so I can write it all out
> > in one i/o.
>
> Could you use writev() then?
I am working with an app that already has built in
checkpointing and its own mem allocation routines (uses sbrk).
If I could move the libraries up
I could get away w/o modifying this code. If I can't
I would need to figure out where to allocate more
memory (like at 0x5000000 on up - this app uses
very little stack) and use multiple writes or writev.
I was hoping for an easier solution :-)
thanks
eric
------------------------------
From: Eric Taylor <[EMAIL PROTECTED]>
Subject: Re: need help fixing a tcp kernel problem
Date: Sat, 13 Jan 2001 18:53:29 GMT
I've had to punt on this bug. It's just too difficult
to fix this problem, even with the source code. And
even with the help I've received here, I just can't find
anyone that can really help me fix this. I tried to post
in other forums, like deja (got rejected), and I even tried
to send Alan Cox a direct email (but it bounced).
Shame though, this simple but serious linux bug is proof to
my co-workers that argue that linux is just a toy o.s. and
is not reliable enough to use on a 1/4 billion dollar gov project.
They want to use NT instead of linux. I hope I can find
a workaround in time.
thanks for all your help
eric
------------------------------
From: Todd Knarr <[EMAIL PROTECTED]>
Subject: Re: 2.2.18 & USB Does It or Doesn't It
Date: 13 Jan 2001 19:21:16 GMT
In comp.os.linux.development.system
<3a5fcc28$0$15467$[EMAIL PROTECTED]> mpierce
<[EMAIL PROTECTED]> wrote:
> Does it support USB?
Yes it does.
> I've got a USB Zip250 configured as:
> /dev/sda4 /mnt/zip vfat noauto,user,rw 0 0
> I do:
> [root@localhost mpierce]# insmod ide-scsi
> Using /lib/modules/2.2.18/scsi/ide-scsi.o
> [root@localhost mpierce]# cd /dev
> [root@localhost /dev]# mount /mnt/zip
> mount: the kernel does not recognize /dev/sda4 as a block device
> (maybe `insmod driver'?)
> [root@localhost /dev]#
OK, the problem is likely that the ide-scsi.o module doesn't have anything
to do with USB. It's the SCSI emulation layer driver for the IDE interface.
You probably need one of the USB block storage drivers located under
/lib/modules/2.2.18/usb instead.
--
Collin was right. Never give a virus a missile launcher.
-- Erk, Reality Check #8
------------------------------
** 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 by posting to the
comp.os.linux.development.system newsgroup.
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
******************************
