[CentOS-announce] CESA-2013:0714 Moderate CentOS 6 stunnel Update
CentOS Errata and Security Advisory 2013:0714 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0714.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
134f6e3d27d4b52f58a537f6949978df01aaf92ff1bd354647d0d617bff4985f
stunnel-4.29-3.el6_4.i686.rpm
x86_64:
091e1b3670042f45f0ff0a7f5da18ee1987b5f9ae803ce92d089778c79f95c45
stunnel-4.29-3.el6_4.x86_64.rpm
Source:
2670221d4b06c1c9fba776235560512a0f1ad21f55ed39cb68e255bbd5b56602
stunnel-4.29-3.el6_4.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] floppy drives
Le 08/04/2013 02:23, mark a écrit : On 04/07/13 19:53, John R. Dennison wrote: On Sun, Apr 07, 2013 at 07:35:17PM -0400, mark wrote: ls -l /dev/fd? What do you see? lrwxrwxrwx 1 root root 13 Apr 7 15:03 /dev/fd - /proc/self/fd/ Interesting as that doesn't match the pattern /dev/fd? fd0 should have been shown by the ls -l /dev/fd? pattern so is that a broken link? Ok, ll /dev/fd - which is a directory - shows it pointing to /proc/self/fd/. Under tghat is 0-3, where 0-2 are links to /dev/pts/0, *all* the same. 3 is a link to /proc/5038/fd/, which does not exist. you were asked to type ls -l /dev/fd? the question mark is part of what you have to type... another poster explained that /dev/fd/ has nothing to do with floppies. If this still fails ensure that the device is enabled in the system's bios. Speaking of that, is the device seen at boot time? dmesg | grep ^Floppy or grep ^Floppy /var/log/dmesg should show fd0 and a size. Is it time to try MAKEDEV? maybe first try ls -l /dev/fd? and then dmesg Note that I've had a lot of old floppies that were dead when I tried to read them after many years. For me, 3/3 isn't conclusive. I would try to read at least 10 or 20 floppies before deciding that it's a drive or driver issue. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 04/08/13 04:43, Nicolas Thierry-Mieg wrote: Le 08/04/2013 02:23, mark a écrit : On 04/07/13 19:53, John R. Dennison wrote: On Sun, Apr 07, 2013 at 07:35:17PM -0400, mark wrote: ls -l /dev/fd? What do you see? lrwxrwxrwx 1 root root 13 Apr 7 15:03 /dev/fd - /proc/self/fd/ Interesting as that doesn't match the pattern /dev/fd? fd0 should have been shown by the ls -l /dev/fd? pattern so is that a broken link? Ok, ll /dev/fd - which is a directory - shows it pointing to /proc/self/fd/. Under tghat is 0-3, where 0-2 are links to /dev/pts/0, *all* the same. 3 is a link to /proc/5038/fd/, which does not exist. you were asked to type ls -l /dev/fd? the question mark is part of what you have to type... Perhaps you didn't understand what I wrote in the paragraph that you cut out. ** If ls -l /dev/fd0* does not show a series of device nodes try: It does - /dev/fd0, along with all 14 sizes of floppies, of a patter /dev/fd0udisk capacity ** Now, if that's not clear enough for you, let me rephrase: /dev/fd0 exists, as does the related ones, as far as I know (note that ll for me is aliased to ls -laF). brw-rw 1 mark floppy 2, 0 Apr 7 15:03 /dev/fd0 brw-rw 1 mark floppy 2, 84 Apr 7 15:03 /dev/fd0u1040 brw-rw 1 mark floppy 2, 88 Apr 7 15:03 /dev/fd0u1120 brw-rw 1 mark floppy 2, 28 Apr 7 15:03 /dev/fd0u1440 brw-rw 1 mark floppy 2, 44 Apr 7 15:03 /dev/fd0u1680 brw-rw 1 mark floppy 2, 60 Apr 7 15:03 /dev/fd0u1722 brw-rw 1 mark floppy 2, 76 Apr 7 15:03 /dev/fd0u1743 brw-rw 1 mark floppy 2, 96 Apr 7 15:03 /dev/fd0u1760 brw-rw 1 mark floppy 2, 116 Apr 7 15:03 /dev/fd0u1840 brw-rw 1 mark floppy 2, 100 Apr 7 15:03 /dev/fd0u1920 brw-rw 1 mark floppy 2, 12 Apr 7 15:03 /dev/fd0u360 brw-rw 1 mark floppy 2, 16 Apr 7 15:03 /dev/fd0u720 brw-rw 1 mark floppy 2, 120 Apr 7 15:03 /dev/fd0u800 brw-rw 1 mark floppy 2, 52 Apr 7 15:03 /dev/fd0u820 brw-rw 1 mark floppy 2, 68 Apr 7 15:03 /dev/fd0u830 Is that clear enough? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Sun, 2013-04-07 at 15:45 -0400, mark wrote: Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25 and a 3.5 drive, both are plugged in, but in the BIOS, all I see is the 3.5. Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor mount nor fdisk works - the latter telling me that /dev/fd0 is not a valid block device. After some googling, I tried modprobe floppy, which installed it, but still no joy. Anyone have a clue? mark Mark, you said that both floppy drives are connected. Could it be that both are wired to fd0? One drive could be malfunctioning Try with only one drive connected at a time at the end of the cable and see if that helps... Louis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 04/07/2013 07:26 PM, mark wrote: On 04/07/13 19:53, John R. Dennison wrote: On Sun, Apr 07, 2013 at 07:35:17PM -0400, mark wrote: ls -l /dev/fd? What do you see? lrwxrwxrwx 1 root root 13 Apr 7 15:03 /dev/fd - /proc/self/fd/ Interesting as that doesn't match the pattern /dev/fd? And, while we're at it, ll of /dev/floppy shows lrwxrwxrwx 1 root root 3 Apr 7 15:03 /dev/floppy - fd0 fd0 should have been shown by the ls -l /dev/fd? pattern so is that a broken link? lsmod | grep floppy - does it show the floppy module loaded? If ls -l /dev/fd0* does not show a series of device nodes try: It does - /dev/fd0, along with all 14 sizes of floppies, of a patter /dev/fd0udisk capacity snip I saw in an earlier part of the thread, you were trying to do things to A: ... A: is a windows device, not a Linux device Make sure you are trying to do things to /dev/fd0 and not A: signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Sun, Apr 7, 2013 at 2:45 PM, mark m.r...@5-cent.us wrote: Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25 and a 3.5 drive, both are plugged in, but in the BIOS, all I see is the 3.5. Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor mount nor fdisk works - the latter telling me that /dev/fd0 is not a valid block device. After some googling, I tried modprobe floppy, which installed it, but still no joy. Anyone have a clue? To debug this, I'd do the following: 1. Remove both USB plugs (I assume that these floppies are USB connected) 2. Reboot 3. Plug just one in, then do lsusb and get the end of /var/log/messages One of these might tell you where the floppy is connected in /dev. It might not be /dev/fd0 4. If it doesn't show up immediately, try putting in a floppy disk and do 3 again. 5. If it doesn't show up again, then it's probably dead. 6. If it does show, perhaps at /dev/sdb1, then create a file .mtoolsrc: # USB drive drive u: file=/dev/sdb1 Then do mdir u: Of course, it will probably show up at /dev/fdn. Just my pre-tax 2 cents. -- Dale Dellutri ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
Johnny Hughes wrote: snip I saw in an earlier part of the thread, you were trying to do things to A: ... A: is a windows device, not a Linux device Make sure you are trying to do things to /dev/fd0 and not A: Oh, of course. I was trying mdir, I think - that's an mtools thing - they use a: internally to represent /dev/fd0. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Mon, Apr 8, 2013 at 10:19 AM, Johnny Hughes joh...@centos.org wrote: If ls -l /dev/fd0* does not show a series of device nodes try: It does - /dev/fd0, along with all 14 sizes of floppies, of a patter /dev/fd0udisk capacity snip I saw in an earlier part of the thread, you were trying to do things to A: ... A: is a windows device, not a Linux device Make sure you are trying to do things to /dev/fd0 and not A: That was in the context of the 'mtools' programs - which do map the devices to dos-like letters but failed in the same way with a problem with the underlying device. But as someone else mentioned, if 2 drives are plugged in, it may be trying the wrong device. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
Hi, Louis, Louis Lagendijk wrote: On Sun, 2013-04-07 at 15:45 -0400, mark wrote: Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25 and a 3.5 drive, both are plugged in, but in the BIOS, all I see is the 3.5. Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor mount nor fdisk works - the latter telling me that /dev/fd0 is not a valid block device. After some googling, I tried modprobe floppy, which installed it, but still no joy. Anyone have a clue? Mark, you said that both floppy drives are connected. Could it be that both are wired to fd0? One drive could be malfunctioning Try with only one drive connected at a time at the end of the cable and see if that helps... Good thought... but I think I had one of them disconnected before I took my system down yesterday and connected both. I will note that the 5.25 one's light does seem to stay on, regardless. I was speaking about it to my manager this morning, and he pulls out a 3.5 USB drive I can borrow, so I'll take my system down, pull the 3.5, and see what I see. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
mark m.roth@... writes: On 04/07/13 16:22, Frank Cox wrote: On Sun, 07 Apr 2013 16:18:29 -0400 mark wrote: All of 'em are old DOS. Just tried mdir a:, and the same: can't open, can't initials A:. I really doubt the drives themselves are dead, but Floppy disks have a finite usable life. Depending on where and how you have been storing them, they may be shot. Yeah, but I tried three of 'em, three different OEM, and three ages, and they all give me fdisk saying it's not a valid block device. Is it possibly that there's some driver missing? Floppy drives also have a limited lifetime. Are you sure the drive itself (not the disk) is good? I also have a bunch of old floppies and try to keep at least one system with a working floppy drive. I see: [dave@waste ~]# ls /dev/fd* /dev/fd@ /dev/fd0u1120 /dev/fd0u1722 /dev/fd0u1840 /dev/fd0u720 /dev/fd0u830 /dev/fd0 /dev/fd0u1440 /dev/fd0u1743 /dev/fd0u1920 /dev/fd0u800 /dev/fd0u1040 /dev/fd0u1680 /dev/fd0u1760 /dev/fd0u360 /dev/fd0u820 [dave@waste ~]# ls -l /dev/floppy lrwxrwxrwx 1 root root 3 Apr 3 17:17 /dev/floppy - fd0 [dave@waste ~]# lsmod | grep floppy floppy 57125 0 on that system and it reads and writes floppies. Cheers, Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Mon, 8 Apr 2013, David G. Miller wrote: mark m.roth@... writes: On 04/07/13 16:22, Frank Cox wrote: On Sun, 07 Apr 2013 16:18:29 -0400 mark wrote: All of 'em are old DOS. Just tried mdir a:, and the same: can't open, can't initials A:. I really doubt the drives themselves are dead, but Floppy disks have a finite usable life. Depending on where and how you have been storing them, they may be shot. Yeah, but I tried three of 'em, three different OEM, and three ages, and they all give me fdisk saying it's not a valid block device. Is it possibly that there's some driver missing? Floppy drives also have a limited lifetime. Are you sure the drive itself (not the disk) is good? I also have a bunch of old floppies and try to keep at least one system with a working floppy drive. I see: [dave@waste ~]# ls /dev/fd* /dev/fd@ /dev/fd0u1120 /dev/fd0u1722 /dev/fd0u1840 /dev/fd0u720 /dev/fd0u830 /dev/fd0 /dev/fd0u1440 /dev/fd0u1743 /dev/fd0u1920 /dev/fd0u800 /dev/fd0u1040 /dev/fd0u1680 /dev/fd0u1760 /dev/fd0u360 /dev/fd0u820 [dave@waste ~]# ls -l /dev/floppy lrwxrwxrwx 1 root root 3 Apr 3 17:17 /dev/floppy - fd0 [dave@waste ~]# lsmod | grep floppy floppy 57125 0 on that system and it reads and writes floppies. Any chance that we could see your /etc/fstab, at least those lines regarding floppies? Or is that personal? Cheers, Dave Max Pyziur p...@brama.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
Max Pyziur wrote: On Mon, 8 Apr 2013, David G. Miller wrote: mark m.roth@... writes: On 04/07/13 16:22, Frank Cox wrote: On Sun, 07 Apr 2013 16:18:29 -0400 mark wrote: All of 'em are old DOS. Just tried mdir a:, and the same: can't open, can't initials A:. I really doubt the drives themselves are dead, but Floppy disks have a finite usable life. Depending on where and how you have been storing them, they may be shot. *shrug* In houses, apts, where I live, not in storage (except possibly for a couple months, and that was all climate-controlled storage). snip Is it possibly that there's some driver missing? Floppy drives also have a limited lifetime. Are you sure the drive itself (not the disk) is good? That I don't know, and was trying to think of a way to test it. As I noted in another post, the 5.25 light seems to stay on, and I *think* that was the one I had disconnected before. I also think I mentioned that after bringing it down, connecting, and rebooting, I looked at the BIOS, and it told me it *only* saw the 3.5 drive. snip Any chance that we could see your /etc/fstab, at least those lines regarding floppies? Or is that personal? a) Not at home. b) Not really relevant, since I don't have a floppy entry in it, just my h/d partitions. It *looks* like udev knows about it, since it created /dev/fd0 and the related devices. Btw, I updated before I brought it down, so it's on current 5.9. mark mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 4/8/2013 9:00 AM, Les Mikesell wrote: That was in the context of the 'mtools' programs - which do map the devices to dos-like letters but failed in the same way with a problem with the underlying device. But as someone else mentioned, if 2 drives are plugged in, it may be trying the wrong device. if I remember correctly, PC floppies require a cable with a twisted bit in it. both drives are jumpered for disk1, and the flip makes the end drive disk0 if you used a straight through ribbon cable and both drives were jumpered for the default, then they would have collided and not worked. its been 10 years since I've hooked one up, so this is from old memories. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 4/8/2013 7:58 AM, m.r...@5-cent.us wrote: Good thought... but I think I had one of them disconnected before I took my system down yesterday and connected both. I will note that the 5.25 one's light does seem to stay on, regardless. OH. another rusty old memory. if you plugged a floppy cable in upside down (only possible if the cable wasn't keyed, but I remember quite a few that werent), it grounded both drive select and write select, and the drive would write nulls (or something) all over any track that was seeked to, without even sector formatting. this would, of course, erase any disk you inserted. also, the LED would stay on. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Mon, 2013-04-08 at 12:21 -0400, m.r...@5-cent.us wrote: That I don't know, and was trying to think of a way to test it. As I noted in another post, the 5.25 light seems to stay on, and I *think* that was the one I had disconnected before. I also think I mentioned that after bringing it down, connecting, and rebooting, I looked at the BIOS, and it told me it *only* saw the 3.5 drive. snip That is why I thought of the cable/drive issue. Please keep in mind that the bios versions I recall did not detect a drive unless it was told that there was one (you had to even specify the type/ format of the drive) Any chance that It *looks* like udev knows about it, since it created /dev/fd0 and the related devices. From what I recall, the OS gets the information on what is there from the bios. Look around in the bios and check if you can specify the format of the floppy drives somewhere... And the comment about checking if the cable has been put on upside down (on either side). Please note tat the twist in the cable sits between drive a and b. Still 4 possibilities to try. Louis ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
John R Pierce wrote: On 4/8/2013 7:58 AM, m.r...@5-cent.us wrote: Good thought... but I think I had one of them disconnected before I took my system down yesterday and connected both. I will note that the 5.25 one's light does seem to stay on, regardless. OH. another rusty old memory. if you plugged a floppy cable in upside down (only possible if the cable wasn't keyed, but I remember quite a few that werent), it grounded both drive select and write select, and the drive would write nulls (or something) all over any track that was seeked to, without even sector formatting. this would, of course, erase any disk you inserted. also, the LED would stay on. I *think* these cables are keyed - they're relatively new, but I'll check. I still think I had the 5.25 power on, but not the cable Something to check this evening. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
Louis Lagendijk wrote: On Mon, 2013-04-08 at 12:21 -0400, m.r...@5-cent.us wrote: That I don't know, and was trying to think of a way to test it. As I noted in another post, the 5.25 light seems to stay on, and I *think* that was the one I had disconnected before. I also think I mentioned that after bringing it down, connecting, and rebooting, I looked at the BIOS, and it told me it *only* saw the 3.5 drive. snip That is why I thought of the cable/drive issue. Please keep in mind that the bios versions I recall did not detect a drive unless it was told that there was one (you had to even specify the type/ format of the drive) Any chance that It *looks* like udev knows about it, since it created /dev/fd0 and the related devices. From what I recall, the OS gets the information on what is there from the bios. Look around in the bios and check if you can specify the format of the floppy drives somewhere... And the comment about checking if the cable has been put on upside down (on either side). Please note tat the twist in the cable sits between drive a and b. Still 4 possibilities to try. OH! I thought, since the m/b is from '05 or '06, that it would detect the floppy drives, but *that* I need to look at. Thanks! mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 4/8/2013 9:57 AM, m.r...@5-cent.us wrote: OH! I thought, since the m/b is from '05 or '06, that it would detect the floppy drives, but*that* I need to look at. Thanks! the floppy interface was really low level.all parallel signals, like select drive, step, direction, head select, serial data, clock, write enable, and a status line for home, and index (the hole in the disk that said its at sector 0). the ONLY way to detect a drive is connected was to STEP outwards 100 times, checking for the 'home' status each time, this takes several seconds per drive. AFAIK, there was no way electrically to tell the difference between drive types, unless there's a reliable disk in the drive. so the BIOS's pretty much stopped doing the auto-home-and-detect thing early on when floppies became optional because it was /so/ slow and added significant time to POST. and even from the very beginning, you have to configure the BIOS for the drive types (heck, early hard disks had to be configured in the BIOS too) -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Hostname question
CentOS 6.4, clean install. Zimbra 8.0.3 I am behind a PfSense box using a virtual IP. So the IP of the box is 192.168.1.27 I entered this in /etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.27 mail mail.meowbox.me meowbox.me but `hostname -f` says: $ hostname -f hostname: Unknown host Do I need to put the public IP for where this record resolves? Since PFSense is forwarding traffic from it to the virtual IP? Jason ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
John R Pierce wrote: On 4/8/2013 9:57 AM, m.r...@5-cent.us wrote: OH! I thought, since the m/b is from '05 or '06, that it would detect the floppy drives, but*that* I need to look at. Thanks! the floppy interface was really low level.all parallel signals, like select drive, step, direction, head select, serial data, clock, write enable, and a status line for home, and index (the hole in the disk that said its at sector 0). snip drive. so the BIOS's pretty much stopped doing the auto-home-and-detect thing early on when floppies became optional because it was /so/ slow and added significant time to POST. and even snip But post, if memory check is enabled, *does* take a long time... oh, that's right, that was on the server with -256G- mark and my mind SEGV's whenever I say that ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
Jason T. Slack-Moehrle wrote: CentOS 6.4, clean install. Zimbra 8.0.3 I am behind a PfSense box using a virtual IP. So the IP of the box is 192.168.1.27 I entered this in /etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.27 mail mail.meowbox.me meowbox.me but `hostname -f` says: $ hostname -f hostname: Unknown host Do I need to put the public IP for where this record resolves? Since PFSense is forwarding traffic from it to the virtual IP? Quick check: is the hostname showing in /var/log/messages? If not, did you either reboot the box, or set the hostname manually, or restart the network? It won't take effect until you do one of those. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
Hi Mark, I did a reboot and not `hostname -f` says: mail. But I think that will still be wrong in terms of what Zimbra is looking for. When I did the install I set the hostname to `webserver.localdomain`, so I see in /var/log/messages: `Apr 7 12:35:48 webserver kernel: SRAT: PXM 0 - APIC 0 - Node 0` I think I might need to trick Zimbra bu changing: 192.168.1.27 mail mail.meowbox.me meowbox.me to 192.168.1.27 mail.meowbox.me mail.meowbox.me meowbox.me Jason On Mon, Apr 8, 2013 at 11:26 AM, m.r...@5-cent.us wrote: Jason T. Slack-Moehrle wrote: CentOS 6.4, clean install. Zimbra 8.0.3 I am behind a PfSense box using a virtual IP. So the IP of the box is 192.168.1.27 I entered this in /etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.27 mail mail.meowbox.me meowbox.me but `hostname -f` says: $ hostname -f hostname: Unknown host Do I need to put the public IP for where this record resolves? Since PFSense is forwarding traffic from it to the virtual IP? Quick check: is the hostname showing in /var/log/messages? If not, did you either reboot the box, or set the hostname manually, or restart the network? It won't take effect until you do one of those. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
On 04/08/2013 01:35 PM, Jason T. Slack-Moehrle wrote: Hi Mark, I did a reboot and not `hostname -f` says: mail. But I think that will still be wrong in terms of what Zimbra is looking for. When I did the install I set the hostname to `webserver.localdomain`, so I see in /var/log/messages: `Apr 7 12:35:48 webserver kernel: SRAT: PXM 0 - APIC 0 - Node 0` I think I might need to trick Zimbra bu changing: 192.168.1.27 mail mail.meowbox.me meowbox.me to 192.168.1.27 mail.meowbox.me mail.meowbox.me meowbox.me Jason On Mon, Apr 8, 2013 at 11:26 AM, m.r...@5-cent.us wrote: Jason T. Slack-Moehrle wrote: CentOS 6.4, clean install. Zimbra 8.0.3 I am behind a PfSense box using a virtual IP. So the IP of the box is 192.168.1.27 I entered this in /etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.27 mail mail.meowbox.me meowbox.me but `hostname -f` says: $ hostname -f hostname: Unknown host Do I need to put the public IP for where this record resolves? Since PFSense is forwarding traffic from it to the virtual IP? Quick check: is the hostname showing in /var/log/messages? If not, did you either reboot the box, or set the hostname manually, or restart the network? It won't take effect until you do one of those. What is the hostname listed in /etc/sysconfig/network ? signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
On 4/8/2013 11:17 AM, Jason T. Slack-Moehrle wrote: but `hostname -f` says: $ hostname -f hostname: Unknown host put the hostname in /etc/sysconfig/network, as .. HOSTNAME=full.domain.name.com example... $ more /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=hostname.mydomain.com GATEWAY=x.y.w.x -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
Hi Johnny: # cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=mail.meowbox.me Jason On Mon, Apr 8, 2013 at 11:45 AM, Johnny Hughes joh...@centos.org wrote: On 04/08/2013 01:35 PM, Jason T. Slack-Moehrle wrote: Hi Mark, I did a reboot and not `hostname -f` says: mail. But I think that will still be wrong in terms of what Zimbra is looking for. When I did the install I set the hostname to `webserver.localdomain`, so I see in /var/log/messages: `Apr 7 12:35:48 webserver kernel: SRAT: PXM 0 - APIC 0 - Node 0` I think I might need to trick Zimbra bu changing: 192.168.1.27 mail mail.meowbox.me meowbox.me to 192.168.1.27 mail.meowbox.me mail.meowbox.me meowbox.me Jason On Mon, Apr 8, 2013 at 11:26 AM, m.r...@5-cent.us wrote: Jason T. Slack-Moehrle wrote: CentOS 6.4, clean install. Zimbra 8.0.3 I am behind a PfSense box using a virtual IP. So the IP of the box is 192.168.1.27 I entered this in /etc/hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.27 mail mail.meowbox.me meowbox.me but `hostname -f` says: $ hostname -f hostname: Unknown host Do I need to put the public IP for where this record resolves? Since PFSense is forwarding traffic from it to the virtual IP? Quick check: is the hostname showing in /var/log/messages? If not, did you either reboot the box, or set the hostname manually, or restart the network? It won't take effect until you do one of those. What is the hostname listed in /etc/sysconfig/network ? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
John, Weird question, but if web and e-mail are going to be on the same box. Do I need to do mail.hostname.tld or can I just to hostname.tld? For the MeowBox.me domain. for DNS A-record: @ is the public IP A-record mail is the public IP. Mx record is 0 mail mail.meowbox.me On Mon, Apr 8, 2013 at 11:46 AM, John R Pierce pie...@hogranch.com wrote: On 4/8/2013 11:17 AM, Jason T. Slack-Moehrle wrote: but `hostname -f` says: $ hostname -f hostname: Unknown host put the hostname in /etc/sysconfig/network, as .. HOSTNAME=full.domain.name.com example... $ more /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=hostname.mydomain.com GATEWAY=x.y.w.x -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
On 4/8/2013 11:52 AM, Jason T. Slack-Moehrle wrote: Weird question, but if web and e-mail are going to be on the same box. Do I need to do mail.hostname.tld or can I just to hostname.tld? For the MeowBox.me domain. for DNS A-record: @ is the public IP A-record mail is the public IP. Mx record is 0 mail mail.meowbox.me the FQDN hostname can be whatever. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Hostname question
Thanks everyone for all of the help, I appreciate it. On Mon, Apr 8, 2013 at 12:09 PM, John R Pierce pie...@hogranch.com wrote: On 4/8/2013 11:52 AM, Jason T. Slack-Moehrle wrote: Weird question, but if web and e-mail are going to be on the same box. Do I need to do mail.hostname.tld or can I just to hostname.tld? For the MeowBox.me domain. for DNS A-record: @ is the public IP A-record mail is the public IP. Mx record is 0 mail mail.meowbox.me the FQDN hostname can be whatever. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
Dale Dellutri wrote: On Sun, Apr 7, 2013 at 2:45 PM, mark m.r...@5-cent.us wrote: Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25 and a 3.5 drive, both are plugged in, but in the BIOS, all I see is the 3.5. Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor mount nor fdisk works - the latter telling me that /dev/fd0 is not a valid block device. After some googling, I tried modprobe floppy, which installed it, but still no joy. Anyone have a clue? To debug this, I'd do the following: 1. Remove both USB plugs (I assume that these floppies are USB connected) Wrong assumption. They're on the FD cable to the m/b. I've got some *old* hardware snip Of course, it will probably show up at /dev/fdn. Just my pre-tax 2 cents. I'll tell my wife, who's working on the taxes, to include that as income g mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] 5.9 update error messages
Just updated one of our servers, and see a bunch of udevd-event[8735]: run_program: ressize 256 too short Along with Apr 8 14:57:48 servername kernel: Breaking affinity for irq 209 Apr 8 14:57:48 servername kernel: CPU 8 is now offline Apr 8 14:57:49 servername kernel: CPU 8 offline: Remove Rx thread Apr 8 14:57:49 servername kernel: CPU 9 is now offline Apr 8 14:57:49 servername kernel: CPU 9 offline: Remove Rx thread Apr 8 14:57:49 servername kernel: CPU 10 is now offline Apr 8 14:57:49 servername kernel: CPU a offline: Remove Rx thread Apr 8 14:57:49 servername kdump: kexec: failed to unload kdump kernel Apr 8 14:57:49 servername kdump: failed to stop Apr 8 14:57:49 servername kernel: CPU 11 is now offline Apr 8 14:57:49 servername kernel: CPU b offline: Remove Rx thread Apr 8 14:57:49 servername kernel: CPU 12 is now offline Apr 8 14:57:49 servername kernel: CPU c offline: Remove Rx thread Apr 8 14:57:49 servername kernel: CPU 13 is now offline Apr 8 14:57:49 servername kernel: CPU d offline: Remove Rx thread Apr 8 14:57:49 servername kernel: Breaking affinity for irq 209 Apr 8 14:57:49 servername kernel: CPU 14 is now offline Apr 8 14:57:49 servername kernel: CPU e offline: Remove Rx thread Apr 8 14:57:49 servername kdump: kexec: failed to unload kdump kernel This is a Sun X4640. I see, in a quick google, some posts about this from '08 or '09, with no resolution. Any ideas out there? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On Mon, 8 Apr 2013, Louis Lagendijk wrote: On Sun, 2013-04-07 at 15:45 -0400, mark wrote: Yes, really. I've got hundreds of the damn things here at home, and I want to go through them and get rid of them all. But... to do that I want to read them. I have both a 5.25 and a 3.5 drive, both are plugged in, but in the BIOS, all I see is the 3.5. Fine, I figure I'll take care of those. Nope. I see /dev/fd0 once I've booted up, but neither konqueror nor mount nor fdisk works - the latter telling me that /dev/fd0 is not a valid block device. After some googling, I tried modprobe floppy, which installed it, but still no joy. Anyone have a clue? mark Mark, you said that both floppy drives are connected. Could it be that both are wired to fd0? One drive could be malfunctioning Try with only one drive connected at a time at the end of the cable and see if that helps... Louis Separately, on some Ubuntu boards there has been discussion about a program called udisks for disk-related issues. It is available for CentOS 6, not for CentOS 5. Where mount commands have failed, udisks for these Ubuntu users has come through. Ironically, this discussion got me interested in whether or not the floppy drive on a home server running CentOS 5 is accessible via CentOS5. It isn't; no heartbreak, just a mild annoyance. Max Pyziur p...@brama.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] floppy drives
On 04/08/13 12:55, Louis Lagendijk wrote: On Mon, 2013-04-08 at 12:21 -0400, m.r...@5-cent.us wrote: That I don't know, and was trying to think of a way to test it. As I noted in another post, the 5.25 light seems to stay on, and I *think* that was the one I had disconnected before. I also think I mentioned that after bringing it down, connecting, and rebooting, I looked at the BIOS, and it told me it *only* saw the 3.5 drive. snip That is why I thought of the cable/drive issue. Please keep in mind that the bios versions I recall did not detect a drive unless it was told that there was one (you had to even specify the type/ format of the drive) Any chance that snip You gents nailed it. I brought my machine down again, and set the BIOS to see the 1.2M as a, and the 1.44 as b: while it was down, before I did that, I looked... I'm sure the cable was on, but it's really hard to see the open side of the case still covers about a third of the board, and with all the cables Pulling out my trusty minimag, and moving cables... and it was upside down. I don't know how it got on that way, certainly I wouldn't have forced it, but flipped it over, and played with the BIOS... the 3.5 drive still doesn't work... but the 1.2M floppy, as b: *does* work - light goes on only when I try to read it, and not otherwise. Now I don't know if I have a drive cleaner, since I can't believe none of the first 10 or so disks I tried to look at was readable. But I'm over the first hump. Now I'm playing with /dev/fd1 and /dev/floppy-fd1 (and why is it trying to read a superblock when I try to mount it, when I've said -t msdos? Oh, well, onward in the fight.) mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
