Re: Apt-get update question
On 5 Jun 2003, Stephen Liu wrote: > Hi Panu, > > Thanks for your advice. > > I download following RPMs > > apt-0.5.4cnc6-0.1.i686.rpm > apt-0.5.4cnc7-fr0.62.1.i386.rpm > apt-0.5.5cnc5-fr2.i386.rpm > (apt-devel-0.5.4cnc6-0.1.i686.rpm > apt-devel-0.5.4cnc7-fr0.62.1.i386.rpm > apt-devel-0.5.5cnc5-fr2.i386.rpm) > > I tested rpm all of them and found them not suitable for RH 8.0 because > of many dependencies not available or updated. > > $ rpm -qa|grep apt > apt-0.3.19cnc55-fr8 > > $ rpm -qa|grep librpm > librpm404-devel-4.0.4-8x.27 > librpm404-4.0.4-8x.27 > > $ rpm -qa|grep libbz*.* > libbonobo-2.0.0-4 > libbonoboui-2.0.1-2 > > $ rpm -qa|grep ORBit*.* > ORBit-devel-0.5.13-5 > ORBit2-2.4.1-1 > ORBit-0.5.13-5 > > $ rpm -qa|grep bonobo-activation*.* > bonobo-activation-1.0.3-2 Uhhh.. and what on *earth* have these various Gnome libraries got to do with apt?!? Download the apt built for RH 8.0, for example from http://ftp.freshrpms.net/pub/freshrpms/redhat/8.0/apt/ and it'll "just fit in" if the box you're running on is indeed RH 8.0. - Panu - -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: [edlug] RedHat kernel versions
On 04 Jun 2003 17:39:54 +0100 "Stephen C. Tweedie" <[EMAIL PROTECTED]> wrote: > Hi, > > On Wed, 2003-06-04 at 15:28, Ross Macintyre wrote: > > I'm a bit confused about the updated kernels that Redhat supplies. > > For example they've just released these for RedHat 8.0: > > 2.4.18-27.8.0 (on Monday) > > 2.4.20-18.8(on Tuesday) > > It's a bit complicated --- the Monday push did not not include any i386 > kernels at all. It was just an update to an existing errata to add the > same fixes for ia64, backported to the last ia64 kernel for Red Hat > 7.2. The errata page at > > https://rhn.redhat.com/errata/RHSA-2003-098.html > > shows all --- the x86 kernels listed there have all been superceded by > the Tuesday push of 2.4.20-18.*, but the ia64 kernels are still valid. > > You just need to pay a lot of attention to the fine print in the > advisory notices when an old advisory gets updated. :-) Thanks for this useful bit of advice Stephen. I must admit that I don't read ALL of the advisory notice that comes in the email. I tend to have a quick scan of the Problem description and also look at the first line in the Topic, and if it said that "Updated kernel packages for Red Hat Linux 7.1, 7.2, 7.3, and 8.0 are now available" I thought that meant all kernels had been updated, but I now see that I should read on and it is the "Updated" bit that is important!! But now I've got your attention, you could help me with one more thing: could you tell me what the side effects of running a generic i686 kernel on an athlon processor would be? Up till now I have tended to run all my lab machines with generic 386 kernels and my servers with 686 kernels and this has been fine. But my latest server is a dual athlon machine and I must admit I just assumed I should use a 686-smp kernel as usual and it seems to be working ok! saying that I will now install the athlon kernel and use that instead. Cheers, Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Some questions on use of CD-ROMs
Hi, some question: 1) How to read from command line the label of cd-rom (IDE/SCSI) inserted into device? 2) How to eject the cd-rom simply press the eject button of device when: o the cd-rom is mounted. o the cd-rom is mounted and the users use the files on it. 3) I have 7 cdrom SCSI connecto to channel 2 of a SCSI adapter on a system whit kernel 2.4.18-27.8.0 and when I mount and use the cd-rom I get in /var/log/message the attached error: what means? Thanks for your reply... --- Dario Lesca ([EMAIL PROTECTED]) ---[attach]--- Jun 5 12:37:36 server kernel: scsi1:0:4:0: Attempting to queue an ABORT message Jun 5 12:37:36 server kernel: scsi1: Dumping Card State while idle, at SEQADDR 0x8 Jun 5 12:37:36 server kernel: ACCUM = 0x4, SINDEX = 0x47, DINDEX = 0x25, ARG_2 = 0x0 Jun 5 12:37:36 server kernel: HCNT = 0x0 SCBPTR = 0x0 Jun 5 12:37:36 server kernel: SCSISEQ = 0x12, SBLKCTL = 0x6 Jun 5 12:37:36 server kernel: DFCNTRL = 0x0, DFSTATUS = 0x89 Jun 5 12:37:36 server kernel: LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80 Jun 5 12:37:36 server kernel: SSTAT0 = 0x0, SSTAT1 = 0x8 Jun 5 12:37:36 server kernel: SCSIPHASE = 0x0 Jun 5 12:37:36 server kernel: STACK == 0xe7, 0x160, 0x175, 0x3 Jun 5 12:37:36 server kernel: SCB count = 4 Jun 5 12:37:36 server kernel: Kernel NEXTQSCB = 3 Jun 5 12:37:36 server kernel: Card NEXTQSCB = 3 Jun 5 12:37:36 server kernel: QINFIFO entries: Jun 5 12:37:36 server kernel: Waiting Queue entries: Jun 5 12:37:36 server kernel: Disconnected Queue entries: 0:2 Jun 5 12:37:36 server kernel: QOUTFIFO entries: Jun 5 12:37:36 server kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Jun 5 12:37:36 server kernel: Sequencer SCB Info: 0(c 0x44, s 0x47, l 0, t 0x2) 1(c 0x0, s 0xff, l 255, t 0xff) 2(c 0x0, s 0xff, l 255, t 0xff) 3(c 0x0, s 0xff , l 255, t 0xff) 4(c 0x0, s 0xff, l 255, t 0xff) 5(c 0x0, s 0xff, l 255, t 0xff) 6(c 0x0, s 0xff, l 255, t 0xff) 7(c 0x0, s 0xff, l 255, t 0xff) 8(c 0x0, s 0xff , l 255, t 0xff) 9(c 0x0, s 0xff, l 255, t 0xff) 10(c 0x0, s 0xff, l 255, t 0xff ) 11(c 0x0, s 0xff, l 255, t 0xff) 12(c 0x0, s 0xff, l 255, t 0xff) 13(c 0x0, s 0xff, l 255, t 0xff) 14(c 0x0, s 0xff, l 255, t 0xff) 15(c 0x0, s 0xff, l 255, t 0xff) 16(c 0x0, s 0xff, l 255, t 0xff) 17(c 0x0, s 0xff, l 255, t 0xff) 18(c 0x 0, s 0xff, l 255, t 0xff) 19(c 0x0, s 0xff, l 255, t 0xff) 20(c 0x0, s 0xff, l 2 55, t 0xff) 21(c 0x0, s 0xff, l 255, t 0xff) 22(c 0x0, s 0xff, l 255, t 0xff) 23 (c 0x0, s 0xff, l 255, t 0xff) 24(c 0x0, s 0xff, l 255, t 0xff) 25(c 0x0, s 0xff , l 255, t 0xff) 26(c 0x0, s 0xff, l 255, t 0xff) 27(c 0x0, s 0xff, l 255, t 0xf f) 28(c 0x0, s 0xff, l 255, t 0xff) 29(c 0x0, s 0xff, l 255, t 0xf Jun 5 12:37:37 server kernel: ) 30(c 0x0, s 0xff, l 255, t 0xff) 31(c 0x0, s 0x ff, l 255, t 0xff) Jun 5 12:37:37 server kernel: Pending list: 2(c 0x40, s 0x47, l 0) Jun 5 12:37:37 server kernel: Kernel Free SCB list: 1 0 Jun 5 12:37:37 server kernel: Untagged Q(4): 2 Jun 5 12:37:37 server kernel: DevQ(0:0:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:1:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:2:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:3:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:4:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:5:0): 0 waiting Jun 5 12:37:37 server kernel: DevQ(0:6:0): 0 waiting Jun 5 12:37:37 server kernel: (scsi1:A:4:0): Queuing a recovery SCB Jun 5 12:37:37 server kernel: scsi1:0:4:0: Device is disconnected, re-queuing S CB Jun 5 12:37:37 server login(pam_unix)[1954]: session closed for user sispac Jun 5 12:37:37 server kernel: (scsi1:A:4:0): Abort Message Sent Jun 5 12:37:37 server kernel: Recovery code sleeping Jun 5 12:37:37 server kernel: (scsi1:A:4:0): SCB 2 - Abort Completed. Jun 5 12:37:37 server kernel: Recovery SCB completes Jun 5 12:37:37 server kernel: Recovery code awake Jun 5 12:37:37 server kernel: aic7xxx_abort returns 0x2002 -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: [edlug] RedHat kernel versions
On 05 Jun 2003 12:29:57 +0100 "Stephen C. Tweedie" <[EMAIL PROTECTED]> wrote: > > Hi, > > On Thu, 2003-06-05 at 10:41, Ross Macintyre wrote: > > > But now I've got your attention, you could help me with one more thing: > > could you tell me what the side effects of running a generic i686 > > kernel on an athlon processor would be? > > A few bits and pieces relating to improved performance for those CPUs. > It enables cache-bypass streaming page clear/copy, but not much else; > and without the athlon kernel, you still get MMX-based page operations > (not quite as fast as the athlon-dedicated ones, but still > accelerated.) It also results in a kernel compiled with gcc optimising > its instruction scheduling and function alignment for athlon. So it's a > bit of a performance boost. Thanks for that information Stephen. I'm now in the difficult position of wondering whether to use the athlon up-to-date kernel(2.4.20-18.8smp) or the i686 older kernel(2.4.18-27.8.0smp) [or recompile my own]? (I prefer to use generic kernels and not bother recompiling). The reason I'm considering the older kernel is that the newer kernel seems to break the 2 bits of software that I want to run to manage my raid configuration, that is megamgr and /etc/init.d/raidmon[MegaCtrl/MegaServ] to manage an LSILogic Megaraid SCSI 320-2. Maybe I need to use the older athlon kernel but I'm not sure if RedHat makes these available? I only have the i686 version of the older kernel. Could you advise please? Do Ineed to wait for LSILogic to update their software or wait for a RedHat kernel that runs megaserv and megamgr? Thanks aagain, Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
RedHat kernel versions
I'm a bit confused about the updated kernels that Redhat supplies. For example they've just released these for RedHat 8.0: 2.4.18-27.8.0 (on Monday) 2.4.20-18.8(on Tuesday) Well I thought I had already put on the 2.4.18-27.8.0 version a while ago, and right enough when I look more closely, it says: Issue date:2003-03-17 Updated on:2003-06-02 It looks like there are two kernels being developed and supported, that is, 2.4.18 kernels AND 2.4.20 kernels. Is this correct? Are these 2 issued about the same time because similar bugs have been found in each? Also why is the new 2.4.18-27.8.0 kernel not got a different number, like 2.4.18-28.8.0?? Normally I would keep 2 kernels on my servers and these would be the the 2 most recent kernels, like 2.4.20-13.8 and 2.4.20-18.8, but since I recently discovered that the 2.4.20-13.8 broke my raid management software, I am now thinking that I should keep the 2.4.18 type kernels as well as the 2.4.20 ones, though my feeling is that I should be using the 2.4.20 kernels rather than the 2.4.18 ones. Thanks in advance for any useful information on this. Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: RedHat kernel versions
On Wednesday 04 June 2003 07:28, Ross Macintyre wrote: > I'm a bit confused about the updated kernels that Redhat supplies. > For example they've just released these for RedHat 8.0: > 2.4.18-27.8.0 (on Monday) > 2.4.20-18.8(on Tuesday) > Well I thought I had already put on the 2.4.18-27.8.0 version a while > ago, and right enough when I look more closely, it says: > Issue date:2003-03-17 > Updated on:2003-06-02 The errata text might have been updated, but 2.4.18-27 is much older than Monday. The newest kernel is 2.4.20-18.8. Just shortly before that there was a 2.4.20-13.8, but it introduced some bugs that are fixed with the -18 release for it. Red Hat would not make changes to the kernel without bumping the kernel version number. -- Jesse Keating RHCE MCSE http://geek.j2solutions.net Mondo DevTeam (www.mondorescue.org) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: RedHat kernel versions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Jun 2003 15:28:12 +0100 (GMT Daylight Time), Ross Macintyre wrote: > I'm a bit confused about the updated kernels that Redhat supplies. > For example they've just released these for RedHat 8.0: > 2.4.18-27.8.0 (on Monday) > 2.4.20-18.8(on Tuesday) > Well I thought I had already put on the 2.4.18-27.8.0 version a while > ago, and right enough when I look more closely, it says: > Issue date:2003-03-17 > Updated on:2003-06-02 Read the corresponding security advisory text in section 1 closely. - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+3hAy0iMVcrivHFQRAim6AJwJMaW8ngQNEuI6dAj3CelHDiJqaACfdqmY 7fZio9uS4leP/5/Omdgl74I= =JMzb -END PGP SIGNATURE- -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: Compiling kernels
If the kernel instructions are different. Do you know where to find the new instructions because I searched all over kernel.org and google.com for newer instructions? -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
rpm vs rpmbuild with kernel
Title: rpm vs rpmbuild with kernel Are there any advantages in using "rpmbuild --rebuild kernel-#.#.#-#.#.src.rpm" instead of "rpm -i kernel-#.#.#.#.rpm" when installing a new kernel version? -Channon
Re: rpm vs rpmbuild with kernel
On Wed, 2003-06-04 at 23:57, Quillen, Channon wrote: > Are there any advantages in using "rpmbuild --rebuild > kernel-#.#.#-#.#.src.rpm" instead of "rpm -i kernel-#.#.#.#.rpm" when > installing a new kernel version? If you aren't modifying the kernel source rpm in any way then no, unless you live in a cold country and want to produce some extra heat from your CPU :) - Panu - -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: Apt-get update question
Hi Panu, Thanks for your advice. I download following RPMs apt-0.5.4cnc6-0.1.i686.rpm apt-0.5.4cnc7-fr0.62.1.i386.rpm apt-0.5.5cnc5-fr2.i386.rpm (apt-devel-0.5.4cnc6-0.1.i686.rpm apt-devel-0.5.4cnc7-fr0.62.1.i386.rpm apt-devel-0.5.5cnc5-fr2.i386.rpm) I tested rpm all of them and found them not suitable for RH 8.0 because of many dependencies not available or updated. $ rpm -qa|grep apt apt-0.3.19cnc55-fr8 $ rpm -qa|grep librpm librpm404-devel-4.0.4-8x.27 librpm404-4.0.4-8x.27 $ rpm -qa|grep libbz*.* libbonobo-2.0.0-4 libbonoboui-2.0.1-2 $ rpm -qa|grep ORBit*.* ORBit-devel-0.5.13-5 ORBit2-2.4.1-1 ORBit-0.5.13-5 $ rpm -qa|grep bonobo-activation*.* bonobo-activation-1.0.3-2 etc. If to install either of them I need to update/install many new packages. Maybe they are suitable for RH 9.0 only. In such circumstance I have to keep running apt-0.3.19cnc55-fr8 B.Regards Stephen On Tue, 2003-06-03 at 20:16, Panu Matilainen wrote: > On 3 Jun 2003, Stephen Liu wrote: > > > Hi all folks, > > > > Each time after running "apt-get update" following lines appearing at > > end of the processing script; > > > > > > . > > Fetched 502kB in 33s (15.1kB/s) > > Processing File Dependencies... Done > > apt-get: rpm/rpmlistparser.cc:240: string rpmListParser::Architecture > > (): Assertion `res' failed. > > Aborted > > > > Kindly advise what does it mean "Assertion `res' failed". Is my update > > successful. > > This would appear to be an oldish version of apt, such assert is not > present in 0.5.5cnc5 which is the latest version of apt-rpm. I suggest you > upgrade to that and if the problem persists report to > [EMAIL PROTECTED], RH doesn't distribute apt -> they don't > support it either. > > - Panu - -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
