similar to: Sendmail logs?

On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > And after picking this back up this morning .... still no dice. I have > now > blacklisted the one module that would enumerate the add-in ethernet port > so > that is no longer an issue during the kickstart process, however the > following is now happening: > > - kickstart

On Wed, 25 Feb 2015 17:11:02 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file. >> > > Trying that next. It'll have to wait till tomorrow as we're under a > serious > blizzard/snow event right now and I'd like to get home before all of hell > freezes over.

Hi folks, I have a production server that's currently running 5.0 with all updates. What's the easiest, or perhaps best way to upgrade it to 5.1, with minimal down time? The downtime is critical, so I need to have it be a short as possible. I can live with an hour or two, but larger is going to be a pain. Suggestions? -- W | It's not a bug - it's an undocumented

I just installed CentOS 4 on a new server and now I'm looking for updates that have been released. I like to keep a local mirror of all the updates so I can apply them to other machines easier/faster (this of course assuming I end up installing CentOS on more servers.) So, where are those updates mirrored? With RH/FC, I can hit any mirror and rsync the updates folders. Is there an

I installed CentOS 5 on a server today (wiping clean the drive which had 4.4 on it). During installation I picked the correct timezone, location and all. Yet, upon booting the machine, it seems to think that it's 6 hours earlier than it really is. The BIOS has the correct time and date on it. /etc/locatime was originally what /usr/share/zoneinfo/America/Denver would've

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

Care to explain those two. direct versus indirect mapping? On Wed, Jun 17, 2015 at 12:13 PM, Akemi Yagi <amyagi at gmail.com> wrote: > On Wed, Jun 17, 2015 at 11:06 AM, Ashley M. Kirchner <ashley at pcraft.com> > wrote: > > Nope, that completely takes over '/mnt' and everything else that's in > there > > becomes invisible. However, I do believe

Hello folks, I'm about to install Centos on a new server and this will be my first "exposure" if you will to Centos. I come from an RH/Fedora background. Anyway, is there a list somewhere that will tell me what UPS batteries are compatible with Centos 4 (brand/model)? I figured before I go out and buy something I better check to see what's supported. Thanks.

Nope, that completely takes over '/mnt' and everything else that's in there becomes invisible. However, I do believe you're on to something here. Looking back at the other, working setup, I do realize now that I did the same, where the path was '/mnt/<something>' and the autofs mounts are within that, so they became '/mnt/<something>/<mount-point>'

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

I'm in the process of upgrading an old server which is running uw-imap to a new one running Dovecot. With the old machine, unfortunately, my users had the opportunity to store their e-mails in various locations. For example, some have their mail boxes stored in ~/mail/[various mbox files], others ALSO have a ~/mail/clients/[various mbox files] and yet others simply stored them in their

I have a Dell server that has two built-in ethernet devices. When I kickstart the machine, they are correctly identified as eth0 and eth1 (correctly meaning they correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

So I'm in a bit of a pickle ... I have a machine that needs to be repurposed from WinXP to CentOS. I downloaded the CentOS DVD and all then realized ... I don't have a keyboard/mouse for the machine. It only has USB ports on it, and I don't have a single available USB keyboard that I can plug in. Bit of a problem. Usually what I do is install via VNC anyway, but that is contingent

Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel

Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would that be correct? On Thu, May 14, 2015 at 6:21 PM, Kahlil Hodgson < kahlil.hodgson at

Hi folks, After some more trial and error, I was able to get a bit further in the game with the permission issues I had (previous message was titled 'Samba permissions...) Now I'm able to get onto the system, browse and read/copy/delete files off of the shares. What I can't do is put stuff on because I get a locking error. The setup is as follows: Server 1 -->

Do you think I'd break a lot of people's filters if I removed the prefix? :) Anyone strongly for/against removing it? It seems kind of annoying to me whenever I happen to think about it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL:

I have a machine that's been configured as follows using its BIOS tools: SATA-0 is a 160 GiB drive used as boot SATA-1 and SATA-2 are both 500 GiB drives and were configured as a RAID-1 in BIOS. When the system boots up, BIOS reports 1 160 GiB SATA drive, and 1 Logical volume as RAID-1 ID#0 500 GiB, which is what I would expect it to report, as the two drives are now raided

I need a second pair of eyes here, please. I have a CentOS 6.6 server (let's call it 'S1") that has a Samba share on it that is currently working. We can mount that drive on our Windows work stations and transfer/delete from it just fine. It's setup as a "guest" config so no user specific passwords or any other restrictions like that. I'm trying to setup another