similar to: Appended 1 in fstab entries CentOS4.X installs

In my /etc/fstab here is just a snippet LABEL=/1 ....<rest of line> LABEL=/boot1 ....<rest of line> When i installed centOS-4.3 and it has appeared after starting to use any version of centOS4 was that the labels in my fstab were getting the "1" appended to each label... but if the all the labels for my partitions are appended with the "1" and i format and

I did a clean install of centos4.2 and i noticed on boot up that my mount points had a "1" added to each. For example here is a snippet of my /etc/fstab: /1 ...... /boot1 ...... /var1 ..... of course just what is pertinent to the problem is listed?

Hi, I've got a couple of servers that are running WBEL4 that I would like to upgrade to CentOS4. I noticed that there is a FAQ which explains how to upgrade WBEL3 to CentOS3, but haven't found anything similar for WBEL4. Are the instructions for the WBEL3 upgrade the same for WBEL4? Should I be doing something else instead? Any help would be greatly appreciated. Thanks, Eric

Are there any scripts available for rebuilding CentOS4 - or more specifically rebuilding a custom boot.iso? There is a /scripts directory on the download mirrors, but these scripts are specific to CentOS3/i386 Thanks James Pearson

I've done a test backup/restore on Centos3 with mondo, any one know if it works with Centos4? If so, same packages in from /mnt/cdrom/RPMS/RHE/3.0 I dont have a Ceontos4 test machine handy to mess around with

With Centos3, fedora1/2 I have been able to put /boot on a RAID1 partition and have it boot normally. Unlike earlier versions that used lilo as the default boot loader, these did not make the 2nd drive bootable but at least I was fairly confident that if the first drive failed I could use the install CD in rescue mode to fix up the 2nd one and go on. However, Centos4 won't boot at all with

With this we try to detect if the endianess switch works and assume LE if not. Suggested by Ben. Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") --- .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c

Dear R and S People: I have run across something very strange. Here is a function that I wrote for R: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y){n2 - pmax(x,y)})) return(a) } and here is the R output: > y1 [1] 9 8 7 3 6 > source("boot1.R") > boot1(y=y1,p=4) [,1] [,2]

Hello folks, Since I started using CentOS4, one thing has been bugging me: sshd's ipv6 logging as seen here: Failed password for root from ::ffff:83.220.130.10 port 43511 ssh2 Not a big deal, but I'd be really happy if I could get it to log in ipv4 format like on CentOS3. Any suggestion? Thanks, Francois

Hello, I want to redirect one local port to another. I am using the following: iptables -t nat -A PREROUTING -p tcp --dport 7003 -j REDIRECT --to-ports 80 and testing it by telneting to localhost on port 7003. It works on Centos3, not on Centos4. No luck with this either: iptables -t nat -A PREROUTING -p tcp --dport 7002 -j DNAT --to 127.0.0.1:80 Am I doing something wrong? Or did something

From: Gene Cumm <gene.cumm at gmail.com> alias.c: A simple COM32 module that allows the creation of an alias within the config for SYSLINUX, etc. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same

I am a relative newcomer to using extlinux. I am running Fedora 20 which means I am using syslinux 4.05. When I noticied that all of your documentation said that booting off ext234 and btrfs was supported, I gave it a try. Indeed, this does work with the boot files and the extlinux directory installed into the btrfs (root) volume. Has any thought been given to supporting supporting

I seem to have partitions on two different disks with the same UUID: [tim at helen ~]$ sudo blkid /dev/sda2 /dev/sda2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" [tim at helen ~]$ sudo blkid /dev/sdb2 /dev/sdb2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" This is

what is the turn around time from the time srpms are announced on redhat site to be available for centos3 for updating of systems

Hi,there, I am using R package "boot" to bootstrap. I have one question here: does anybody possibly know how the boot package generates the "indices" which is used in the statistic function? I thought "indices = sample(data, replace=TRUE)", but when I replaced "indices" with this command and used "boot", I got different results. Specifically,

I have been reading about software raid. I configured my first software raid system about a month ago. I have 4 500 Gig drives configured in RAID 5 configuration with a total of 1.5TB. Currently I configured the complete individual drivers as software raid, then created a /dev/md0 with the drives I then created a /file_storage partition on /dev/md0. I created my /boot / and swap partitions on

Hi everyone, My email server is running CentOS 3 and I can't upgrade it to CentOS 4 using the CD's. At first I thought it was the old Megaraid card (that's no longer supported), so I replaced that with a new card. I've tried ISO's from CentOS 4, 4.1 and now 4.2 which I've tested and booted in other machines. Just not this one. I've never had a problem like this

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

While in centos3, using vim and clicking the backspace I see the ^? character instead of it actually deleteing the previous character. In centos4 this was not a problem. I have rad about remapping keys and such, but can someone tell me what the difference between centos4 and centos3 is so I can make the change to make it work on centos3.

I am able to bring up a bonded NIC in Centos4 without requiring to bring up the bond0 with an ip address, but with CentOS-3 I must assign the NIC an address or eth0 and eth1 will not slave. I need to bring bond0 up without an ip address becuase I will be using tagged VLANs. ie. <snip /etc/sysconfig/network-scripts/ifcfg-bond0> DEVICE=bond0 BOOTPROTO=none ONBOOT=yes IPADDR=169.254.0.1