Source rpms and kernel compiling
I have been trying to learn more about how to customize an rpm package with features they did not compile with or to recompile a kernel. I went to linuxhomenetworking.com, linuxnewbie.org, and linuxnovice.org looking for help. I have read the man pages and I am still confused. I am trying to compile samba with acl support or for future just compile any package with an additional feature or to compile kernel 2.5.70. I have tried for about two and a half months and I am getting frustrated. I thought I was having a dependancy problem so I installed the complete installation of redhat 9, then I installed apt-get from freshrpms.net and did a apt-get update and then apt-get upgrade and it updated every package that was available for updating. When I was trying to compile a kernel from kernel.org I did these steps with no luck. I downloaded the kernel source into /usr/src and I extracted it. I then r! an make mrproper and ran successfully. Then I ran an make xconfig and chose all the things I wanted as well as those I wanted to remove. I chose to exit and save. I then ran make dep and it said it was unneccessary. I did this because all the guides that I have said to do that. I did a make clean even though I never recompiled a kernel because the manual said it wont hurt to do it anyway. I then ran a make bzImage. It always runs successfully. Then I ran a make modules and this is where it always fails. No matter what I chose while in the make xconfig it does not make a difference a driver of some sort fails the make modules. I went threw and took out everything I did not need, experimental, or even new. I did them all in different combinations and even just the default kernel straight and it does not seem to matter. It always fails. Any help would be appreciated.
hosts or named problem
I am not sure how to put this, but this is a first try, I am running a gateway program named NoCatAuth for my wireless network on a Compaq Proliant DL 320. This server has 2 embedded NIC cards. I must have been staring at it too long and it has all stopped making sense to me at this point. Within this app I need to refer to the server it is running on, it needs to be able to reference it from either interface. I know I cannot have 2 ip's with the same name in the hosts file, can I? -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
RE: SCSI Problem
First I have to say I don't really know. But I'm willing to take a couple of guesses. The messages refer to SCSI phases so this looks like a bus/driver issue to me. I don't think it is related to something like a kernel deadlock. The driver is reporting an error back to the kernel after timing out. In fact, it looks like the driver is complaining that the bus died meaning it isn't getting any responses from devices. Which leads me to think you might have a physical problem or perhaps the noise level has increased (new monitor?). It could also be that your devices are getting older. I suggest that you reseat your scsi card and check the cables to make sure they are all seated. Review the bus cabling. You should be using the proper cable type and layout. If you've kludged it anywhere, this is your system telling you its time to get the proper cables, layout and termination. Fast devices need fast cables. Use active termination. Make sure you don't have termination turned on any device if you are using a terminator. If you are using device termination on the last device, make sure it's the only device with termination turned on. Sanity check things, in other words. Some PC vendors ship 80 or 128 pin disks with a 68 pin adaptor which can slip loose, for example. The advice to split your bus into a dedicated disk bus and tape/cdrom bus is good advice. Disks are usually a faster SCSI type than tape and cdrom. When you mix device types, the bus slows down. Do not mix 8 bit and 16 bit bus devices (wide and narrow). The standard says this will work but implementation is spotty. Even on high end gear like a SUN $1200 SCSI card, I've seen problems. Sorry if this seems obvious. Hattie Rouge > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David I. Bell > Sent: Monday, June 02, 2003 11:45 PM > To: [EMAIL PROTECTED] > Subject: SCSI Problem > > > Kind Readers, > > Troubles recently started with my system. I'm running RH 8.0 > (2.4.18-26.8.0smp) on a dual CPU P-II/200Mhz system. It's > been up and running for 5 months or so. I just noticed that > the system periodically hangs for several seconds (sometimes > up to a minute or more) with the disk activity light solidy > on. The system usually unblocks itself if I wait > patiently. I've attached some text from /var/log/messages below. > > Does anyone know what the problem might be? I have a SCSI > disk at SCSI ID 0, a tape device at SCSI ID 3, and a CD-ROM > at SCSI ID 5. The tape and the CD-ROM were not in use at the > time of the error. Do you think this might be a failing SCSI > card or is it a failing disk drive? Could it be an O/S > induced hang -- deadlock of some kind related to SMP? > > == > Jun 2 14:14:59 igor kernel: scsi0:0:0:0: Attempting to queue > an ABORT message > Jun 2 14:14:59 igor kernel: scsi0: Dumping Card State in > Message-out phase, at SEQADDR 0x15f > Jun 2 14:14:59 igor kernel: ACCUM = 0xa0, SINDEX = 0x61, > DINDEX = 0xc0, ARG_2 = 0xf > Jun 2 14:14:59 igor kernel: HCNT = 0x0 SCBPTR = 0xf > Jun 2 14:14:59 igor kernel: SCSISEQ = 0x12, SBLKCTL = 0x0 > Jun 2 14:14:59 igor kernel: DFCNTRL = 0x4, DFSTATUS = 0x6d > Jun 2 14:14:59 igor kernel: LASTPHASE = 0xa0, SCSISIGI = > 0xb6, SXFRCTL0 = 0x88 > Jun 2 14:14:59 igor kernel: SSTAT0 = 0x7, SSTAT1 = 0x3 > Jun 2 14:14:59 igor kernel: STACK == 0xe4, 0xe4, 0x159, 0x189 > Jun 2 14:14:59 igor kernel: SCB count = 120 > Jun 2 14:14:59 igor kernel: Kernel NEXTQSCB = 43 > Jun 2 14:14:59 igor kernel: Card NEXTQSCB = 67 > Jun 2 14:14:59 igor kernel: QINFIFO entries: 67 51 > Jun 2 14:14:59 igor kernel: Waiting Queue entries: > Jun 2 14:14:59 igor kernel: Disconnected Queue entries: > Jun 2 14:14:59 igor kernel: QOUTFIFO entries: > Jun 2 14:14:59 igor kernel: Sequencer Free SCB List: 14 3 1 > 9 0 10 8 6 5 4 11 7 13 2 12 Jun 2 14:14:59 igor kernel: > Sequencer SCB Info: 0(c 0x68, s 0x7, l 0, t > 0xff) 1(c 0x68, s 0x7, l 0, t 0xff) 2(c 0x68, s 0x7, l 0, t > 0xff) 3(c 0x68, s 0x7, l 0, t 0xff) 4(c 0x68, s 0x7, l 0, t > 0xff) 5(c 0x68, s 0x7, l 0, t > 0xff) 6(c 0x68, s 0x7, l 0, t 0xff) 7(c 0x68, s 0x7, l 0, t > 0xff) 8(c 0x68, s 0x7, l 0, t 0xff) 9(c 0x68, s 0x7, l 0, t > 0xff) 10(c 0x68, s 0x7, l 0, t > 0xff) 11(c 0x68, s 0x7, l 0, t 0xff) 12(c 0x68, s 0x7, l 0, t > 0xff) 13(c 0x68, s 0x7, l 0, t 0xff) 14(c 0x0, s 0x57, l 0, t > 0xff) 15(c 0x0, s 0x57, l 0, t 0x3d) > Jun 2 14:14:59 igor kernel: Pending list: 51(c 0x68, s 0x7, > l 0), 67(c 0x68, s 0x7, l 0), 61(c 0x0, s 0x57, l 0) > Jun 2 14:14:59 igor kernel: Kernel Free SCB list: 31 49 59 > 10 8 33 11 9 20 1 24 41 16 3 5 35 25 39 46 4 48 0 26 38 58 45 > 44 22 17 21 15 29 40 6 55 12 14 30 28 32 7 54 19 56 42 62 37 > 34 13 18 52 63 50 53 119 27 36 23 60 57 2 47 112 113 114 115 > 108 109 110 111 104 105 106 107 100 101 102 103 96 97 98 99 > 92 93 94 95 88 89 90 91
Compiling kernels
I have been trying to learn more about how to customize an rpm package with features they did not compile with or to recompile a kernel. I went to linuxhomenetworking.com, linuxnewbie.org, and linuxnovice.org looking for help. I have read the man pages and I am still confused. I am trying to compile samba with acl support or for future just compile any package with an additional feature or to compile kernel 2.5.70. I have tried for about two and a half months and I am getting frustrated. I thought I was having a dependancy problem so I installed the complete installation of redhat 9, then I installed apt-get from freshrpms.net and did a apt-get update and then apt-get upgrade and it updated every package that was available for updating. When I was trying to compile a kernel from kernel.org I did these steps with no luck. I downloaded the kernel source into /usr/src and I extracted it. I then ran make mrproper and ran successfully. Then I ran an make xconfig and chose all the things I wanted as well as those I wanted to remove. I chose to exit and save. I then ran make dep and it said it was unneccessary. I did this because all the guides that I have said to do that. I did a make clean even though I never recompiled a kernel because the manual said it wont hurt to do it anyway. I then ran a make bzImage. It always runs successfully. Then I ran a make modules and this is where it always fails. No matter what I chose while in the make xconfig it does not make a difference a driver of some sort fails the make modules. I went threw and took out everything I did not need, experimental, or even new. I did them all in different combinations and even just the default kernel straight and it does not seem to matter. It always fails. Any help would be [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
RE: SCSI Problem
Hattie, Thanks for the advice. I will reseat and "sanity" check everything. I have another card which I will install and split the devices. My guess is that I have a drive that is on it's way toward failure. Do you have any advice on "cloning" the dying disk? It is my boot disk (of course). I'm familiar with dd but I'm not quite sure how to make a new boot disk from the old one when the new disk is of a different size. -- David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Hattie Rouge Sent: Tuesday, June 03, 2003 11:40 AM To: [EMAIL PROTECTED] Subject: RE: SCSI Problem First I have to say I don't really know. But I'm willing to take a couple of guesses. The messages refer to SCSI phases so this looks like a bus/driver issue to me. I don't think it is related to something like a kernel deadlock. The driver is reporting an error back to the kernel after timing out. In fact, it looks like the driver is complaining that the bus died meaning it isn't getting any responses from devices. Which leads me to think you might have a physical problem or perhaps the noise level has increased (new monitor?). It could also be that your devices are getting older. I suggest that you reseat your scsi card and check the cables to make sure they are all seated. Review the bus cabling. You should be using the proper cable type and layout. If you've kludged it anywhere, this is your system telling you its time to get the proper cables, layout and termination. Fast devices need fast cables. Use active termination. Make sure you don't have termination turned on any device if you are using a terminator. If you are using device termination on the last device, make sure it's the only device with termination turned on. Sanity check things, in other words. Some PC vendors ship 80 or 128 pin disks with a 68 pin adaptor which can slip loose, for example. The advice to split your bus into a dedicated disk bus and tape/cdrom bus is good advice. Disks are usually a faster SCSI type than tape and cdrom. When you mix device types, the bus slows down. Do not mix 8 bit and 16 bit bus devices (wide and narrow). The standard says this will work but implementation is spotty. Even on high end gear like a SUN $1200 SCSI card, I've seen problems. Sorry if this seems obvious. Hattie Rouge > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David I. Bell > Sent: Monday, June 02, 2003 11:45 PM > To: [EMAIL PROTECTED] > Subject: SCSI Problem > > > Kind Readers, > > Troubles recently started with my system. I'm running RH 8.0 > (2.4.18-26.8.0smp) on a dual CPU P-II/200Mhz system. It's > been up and running for 5 months or so. I just noticed that > the system periodically hangs for several seconds (sometimes > up to a minute or more) with the disk activity light solidy > on. The system usually unblocks itself if I wait > patiently. I've attached some text from /var/log/messages below. > > Does anyone know what the problem might be? I have a SCSI > disk at SCSI ID 0, a tape device at SCSI ID 3, and a CD-ROM > at SCSI ID 5. The tape and the CD-ROM were not in use at the > time of the error. Do you think this might be a failing SCSI > card or is it a failing disk drive? Could it be an O/S > induced hang -- deadlock of some kind related to SMP? > > == > Jun 2 14:14:59 igor kernel: scsi0:0:0:0: Attempting to queue > an ABORT message > Jun 2 14:14:59 igor kernel: scsi0: Dumping Card State in > Message-out phase, at SEQADDR 0x15f > Jun 2 14:14:59 igor kernel: ACCUM = 0xa0, SINDEX = 0x61, > DINDEX = 0xc0, ARG_2 = 0xf > Jun 2 14:14:59 igor kernel: HCNT = 0x0 SCBPTR = 0xf > Jun 2 14:14:59 igor kernel: SCSISEQ = 0x12, SBLKCTL = 0x0 > Jun 2 14:14:59 igor kernel: DFCNTRL = 0x4, DFSTATUS = 0x6d > Jun 2 14:14:59 igor kernel: LASTPHASE = 0xa0, SCSISIGI = > 0xb6, SXFRCTL0 = 0x88 > Jun 2 14:14:59 igor kernel: SSTAT0 = 0x7, SSTAT1 = 0x3 > Jun 2 14:14:59 igor kernel: STACK == 0xe4, 0xe4, 0x159, 0x189 > Jun 2 14:14:59 igor kernel: SCB count = 120 > Jun 2 14:14:59 igor kernel: Kernel NEXTQSCB = 43 > Jun 2 14:14:59 igor kernel: Card NEXTQSCB = 67 > Jun 2 14:14:59 igor kernel: QINFIFO entries: 67 51 > Jun 2 14:14:59 igor kernel: Waiting Queue entries: > Jun 2 14:14:59 igor kernel: Disconnected Queue entries: > Jun 2 14:14:59 igor kernel: QOUTFIFO entries: > Jun 2 14:14:59 igor kernel: Sequencer Free SCB List: 14 3 1 > 9 0 10 8 6 5 4 11 7 13 2 12 Jun 2 14:14:59 igor kernel: > Sequencer SCB Info: 0(c 0x68, s 0x7, l 0, t > 0xff) 1(c 0x68, s 0x7, l 0, t 0xff) 2(c 0x68, s 0x7, l 0, t > 0xff) 3(c 0x68, s 0x7, l 0, t 0xff) 4(c 0x68, s 0x7, l 0, t > 0xff) 5(c 0x68, s 0x7, l 0, t > 0xff) 6(c 0x68, s 0x7, l 0, t 0xff) 7(c 0x68, s 0x7, l 0, t > 0xff) 8(c 0x68, s 0x7, l 0, t 0xff) 9(c 0x68, s 0x7, l 0, t > 0xff) 10(c 0x68, s 0x7, l 0, t > 0xff) 11(c 0x68, s 0x7, l 0, t 0xff) 12(c 0x68,
iptables
Where is the best place for iptables help? Is there a mailing list? I've tried the one listed at netfilter.org, but that seems to be Tango Uniform (dead). Setting default policy doesn't seem to work with "REJECT" or "DENY". "ACCEPT" or "DROP" seem to work ok. I try adding rules based on interface device, but when I list the rules in use, I never see the interface listed. EX: This should or may be unnecessary, but this rule is attempting to stop someone outside from masquerading as an internal IP. iptables -A INPUT -p tcp -i eth0 -s 192.168.1.0/24 -j REJECT when I list the rules in effect: (partial display) #iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination REJECT tcp -- 192.168.1.0/24 anywhere reject-with icmp-port-unreachable it is rejecting anything from the non-routable address 192,168.1.X . I I want that to be rejected from eth0, but ok from eth1 . What am I missing? (a clue) Allan -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: iptables
Around Tue,Jun 03 2003, at 04:40, Allan M. Stewart, wrote: > > when I list the rules in effect: (partial display) > > #iptables -L Try iptables -L -v Should list interfaces. -- Roger Morris [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: iptables
www.netfilter.org works, I get about 20 messages a day from there ( in non-digest form of course) mailing list and lots of help hth john At 04:40 PM 6/3/2003 -0400, you wrote: Where is the best place for iptables help? Is there a mailing list? I've tried the one listed at netfilter.org, but that seems to be Tango Uniform (dead). Setting default policy doesn't seem to work with "REJECT" or "DENY". "ACCEPT" or "DROP" seem to work ok. I try adding rules based on interface device, but when I list the rules in use, I never see the interface listed. EX: This should or may be unnecessary, but this rule is attempting to stop someone outside from masquerading as an internal IP. iptables -A INPUT -p tcp -i eth0 -s 192.168.1.0/24 -j REJECT when I list the rules in effect: (partial display) #iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination REJECT tcp -- 192.168.1.0/24 anywhere reject-with icmp-port-unreachable it is rejecting anything from the non-routable address 192,168.1.X . I I want that to be rejected from eth0, but ok from eth1 . What am I missing? (a clue) Allan -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: Shrinking a disk partition
Am Die, 2003-06-03 um 14.15 schrieb Doug Wyatt: > But I'm somewhat confused - mostly by the differences in the > Start and End values indicated by parted, fdisk and sfdisk. The output of fdisk and sfdisk don_t differ. The first starts numbering with 0, the second with 1. Don't know about parted. > > Is what I want to do reasonable? And if so, can anyone shed > some light on why the values seem somewhat different and how > I should choose new values for parted and fdisk? I did this stuff several times. I shrinked the linux file system (on hdb2 in your case) as much as I could. Then I shrinked the partition using fdisk, deleting it first, then create a new partition with exactly the same starting point and choosing a different end point. Afterwards I extended the linux file system again to fill up completely the new partition size. I think you could use your existing /boot partition for both RHL versions. It should be large enough, even if the installation programm demands for a /boot partition of at least 70 mb. I never had any problems with my 50mb partition. Good luck. Peter -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
Re: Compiling kernels
Viestissä Tiistai 3. Kesäkuuta 2003 22:00, [EMAIL PROTECTED] kirjoitti: > When I was trying to compile a kernel from > kernel.org I did these steps with no luck. Was that a 2.5.* version? The kernel configuration/compilation system is changing and instructions for 2.4.* kernels don't necessarily apply. -- Markku Kolkka [EMAIL PROTECTED] -- Psyche-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/psyche-list
