Hi all. I'm currently having a following problem: I have only ssh connection to a CentOS 5.2 system, there are two harddiscs on it. One stores the system (/ filesystem) and the other should be used to help restore the system in case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots limited to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the system from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with the machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
With regards, R.
2009/6/21 Rafał Radecki radecki.rafal@gmail.com
Hi all. I'm currently having a following problem: I have only ssh connection to a CentOS 5.2 system, there are two harddiscs on it. One stores the system (/ filesystem) and the other should be used to help restore the system in case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots limited to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the system from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with the machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
With regards, R.
rsync will probably be your best bet. You'll be able to make an exact copy of the / root system, regardless of what filesystem it uses.
Furthermore, you can choose to exclude certain stuff from being copied over to the backup HDD, and all the files will be accesabile like they are on the first HDD. The advantage of this, is that the HDD could be put into another machine, without having to figure out how to restore it. And, you could run a cronob to sync the files every night.
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list centos@centos.org wrote:
Hi all. I'm currently having a following problem: I have only ssh connection to a CentOS 5.2 system, there are two harddiscs on it. One stores the system (/ filesystem) and the other should be used to help restore the system in case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files that will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots limited to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the system from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with the machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think about using dd instead of dump? Is this an acceptable idea?
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list centos@centos.org wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the system in case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files that will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Without snapshots there is some risk to get inconsistent set of files when you make a backup of live file system. In general this is a problem but I'm not sure about your case. Actually there is another solution to this problem shutdown the system and take the backup using bootable CD/DVD (or booting from another OS installation).
You should unmount a file system before backing up with dd. You can also take a look at Clonezilla which is an open-source image-backup software.
2009/6/21 Rafał Radecki radecki.rafal@gmail.com
I think about using dd instead of dump? Is this an acceptable idea?
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list centos@centos.org
wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the system
in
case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files that will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
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
At Sun, 21 Jun 2009 19:58:41 +0300 CentOS mailing list centos@centos.org wrote:
Without snapshots there is some risk to get inconsistent set of files when you make a backup of live file system. In general this is a problem but I'm not sure about your case. Actually there is another solution to this problem shutdown the system and take the backup using bootable CD/DVD (or booting from another OS installation).
You should unmount a file system before backing up with dd. You can also take a look at Clonezilla which is an open-source image-backup software.
The OP has no physical access to the machine, so unmounting the root file system is not possible. This pretty much rules out dd. dump and rsync WILL work just fine. Yes, the second disk won't be an exact mirror -- short of creating a software RAID 1 (mirroring) set it is not going to be possible to do that. I outlined (in another message) a reasonable procedure to create an up-to-date (within 24 hours) backup disk that will generally be an acceptable replacement system disk should the original disk die.
The 'inconsistenies' caused by a backup of a live file system are generally small are are not going to be fatal using proper backup tools (like dump, tar, cpio, and rsync). Mostly you will lose the last 24 hours worth of log files and stuff like that (assuming a once-a-day use of rsync). Nothing critical to the operation of the system.
2009/6/21 Rafał Radecki radecki.rafal@gmail.com
I think about using dd instead of dump? Is this an acceptable idea?
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list centos@centos.org
wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the system
in
case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files that will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
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
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At Sun, 21 Jun 2009 15:06:35 +0200 CentOS mailing list centos@centos.org wrote:
I think about using dd instead of dump? Is this an acceptable idea?
*NO!*. dd is NOT a proper backup tool... I don't know where the idea that it is comes from (probably some really old UNIX sys admin book or something). dd has many uses, but it is not normally considered a backup tool. Dump is a perfectly acceptable backup tool. Dump was *designed* as the backup tool of choice. And it works just fine on a read-write file system, with the *standard* disclaimer that if used on a file system that is 'active', it (*like all backup tools*) will miss files that are being created/writen to during the backup. Generally, the missed files will be gotten on a later backup. On a normal, typical system, one would run the full backup at a 'quiet' time (a time frame of low activity, with the idea of avoiding having the backup interfere with normal activities and of normal activities interfering with the backup. On a typical normal system, the missed files will likely be things like the tail end of log files or various trasienent files (like mail queue files and the like).
If you want a non-live mirror on the second does do this:
Pick a 'quiet' time (say on a quiet Sunday morning) and do this:
(Assume that /dev/sdb1 is the sole partition on the second disk):
# mkfs.ext3 -L SecondDisk /dev/sdb1 # mkdir /seconddisk # mount -v -t ext3 LABEL=SecondDisk /seconddisk # dump 0f - / | (cd /seconddisk; restore -rf -)
At this point pick out a good book to read and get comfortable and read a chapter or three or you can do whatever you would do to kill some time -- ie go for a walk (or walk the dog), play a game of hoops or go for a swim or whatever. I am assuming that the disk is probably good sized, so full dump may take some time. You could stare at the screen for an hour, if that floats your boat... Dump will display a progress report every 5 minutes.
# umount -v /seconddisk
Now create a script (Let's call it '/usr/local/sbin/dailybackup'):
#!/bin/sh /sbin/e2fsck -C -T -a LABEL=SecondDisk mount -v -t ext3 LABEL=SecondDisk /seconddisk rsync -v -a -x -H --delete --delete-after --exclude=lost+found/ / /seconddisk umount -v /seconddisk
# chmod +x /usr/local/sbin/dailybackup
Now create a daily cron job:
# crontab -e
Add the line:
10 0 * * * /usr/local/sbin/dailybackup
And you are all set. Once a day an 10 past midnight, the backup disk will be sync'ed to the live system disk. Every morning you will get a message from cron with the output.
If you really want to, you can change the '0' above to '0,6,12,18' and the sync'ing will happen every 6 hours. This is *probably* overkill.
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list centos@centos.org wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the system in case of first disks' failure. I thought that maybe dump would be a good utility to make it. But in only works on read-only filesystems. In one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files that will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up the entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Could You please explain what exactly that line means:
# dump 0f - / | (cd /seconddisk; restore -rf -)
You are very helpful.
With regards, R.
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 15:06:35 +0200 CentOS mailing list centos@centos.org wrote:
I think about using dd instead of dump? Is this an acceptable idea?
*NO!*. dd is NOT a proper backup tool... I don't know where the idea that it is comes from (probably some really old UNIX sys admin book or something). dd has many uses, but it is not normally considered a backup tool. Dump is a perfectly acceptable backup tool. Dump was *designed* as the backup tool of choice. And it works just fine on a read-write file system, with the *standard* disclaimer that if used on a file system that is 'active', it (*like all backup tools*) will miss files that are being created/writen to during the backup. Generally, the missed files will be gotten on a later backup. On a normal, typical system, one would run the full backup at a 'quiet' time (a time frame of low activity, with the idea of avoiding having the backup interfere with normal activities and of normal activities interfering with the backup. On a typical normal system, the missed files will likely be things like the tail end of log files or various trasienent files (like mail queue files and the like).
If you want a non-live mirror on the second does do this:
Pick a 'quiet' time (say on a quiet Sunday morning) and do this:
(Assume that /dev/sdb1 is the sole partition on the second disk):
# mkfs.ext3 -L SecondDisk /dev/sdb1 # mkdir /seconddisk # mount -v -t ext3 LABEL=SecondDisk /seconddisk # dump 0f - / | (cd /seconddisk; restore -rf -)
At this point pick out a good book to read and get comfortable and read a chapter or three or you can do whatever you would do to kill some time -- ie go for a walk (or walk the dog), play a game of hoops or go for a swim or whatever. I am assuming that the disk is probably good sized, so full dump may take some time. You could stare at the screen for an hour, if that floats your boat... Dump will display a progress report every 5 minutes.
# umount -v /seconddisk
Now create a script (Let's call it '/usr/local/sbin/dailybackup'):
#!/bin/sh /sbin/e2fsck -C -T -a LABEL=SecondDisk mount -v -t ext3 LABEL=SecondDisk /seconddisk rsync -v -a -x -H --delete --delete-after --exclude=lost+found/ / /seconddisk umount -v /seconddisk
# chmod +x /usr/local/sbin/dailybackup
Now create a daily cron job:
# crontab -e
Add the line:
10 0 * * * /usr/local/sbin/dailybackup
And you are all set. Once a day an 10 past midnight, the backup disk will be sync'ed to the live system disk. Every morning you will get a message from cron with the output.
If you really want to, you can change the '0' above to '0,6,12,18' and the sync'ing will happen every 6 hours. This is *probably* overkill.
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list <
centos@centos.org>
wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the
system in
case of first disks' failure. I thought that maybe dump would be a
good
utility to make it. But in only works on read-only filesystems. In
one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files
that
will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up
the
entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact
with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com --
http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Rafał Radecki wrote:
Could You please explain what exactly that line means:
# dump 0f - / | (cd /seconddisk; restore -rf -)
As root, do a level 0 (or full) backup of the root / filesystem. Rather than write the backup output to a regular file, send it to standard out.
Pipe the standard output to a new process. For the new process, change your working location to be another directory where you have another filesystem mounted. It will be best if this second filesystem was formatted prior to running this command.
Run a restore of the dump results in a non-interactive mode taking as input the output of the dump command.
- -- David Goldsmith
At Mon, 22 Jun 2009 08:26:22 +0200 CentOS mailing list centos@centos.org wrote:
Could You please explain what exactly that line means:
# dump 0f - / | (cd /seconddisk; restore -rf -)
This does a full dump of the file system mounted as '/' and sends it down a pipe to a shell process that first changes its working directory to /seconddisk and then runs the restore program to restore the dump coming on on stdin (from the other end of the pipe).
This does a disk-to-disk backup from / to /seconddisk.
Useful reading:
man dump man restore man bash
You are very helpful.
With regards, R.
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 15:06:35 +0200 CentOS mailing list centos@centos.org wrote:
I think about using dd instead of dump? Is this an acceptable idea?
*NO!*. dd is NOT a proper backup tool... I don't know where the idea that it is comes from (probably some really old UNIX sys admin book or something). dd has many uses, but it is not normally considered a backup tool. Dump is a perfectly acceptable backup tool. Dump was *designed* as the backup tool of choice. And it works just fine on a read-write file system, with the *standard* disclaimer that if used on a file system that is 'active', it (*like all backup tools*) will miss files that are being created/writen to during the backup. Generally, the missed files will be gotten on a later backup. On a normal, typical system, one would run the full backup at a 'quiet' time (a time frame of low activity, with the idea of avoiding having the backup interfere with normal activities and of normal activities interfering with the backup. On a typical normal system, the missed files will likely be things like the tail end of log files or various trasienent files (like mail queue files and the like).
If you want a non-live mirror on the second does do this:
Pick a 'quiet' time (say on a quiet Sunday morning) and do this:
(Assume that /dev/sdb1 is the sole partition on the second disk):
# mkfs.ext3 -L SecondDisk /dev/sdb1 # mkdir /seconddisk # mount -v -t ext3 LABEL=SecondDisk /seconddisk # dump 0f - / | (cd /seconddisk; restore -rf -)
At this point pick out a good book to read and get comfortable and read a chapter or three or you can do whatever you would do to kill some time -- ie go for a walk (or walk the dog), play a game of hoops or go for a swim or whatever. I am assuming that the disk is probably good sized, so full dump may take some time. You could stare at the screen for an hour, if that floats your boat... Dump will display a progress report every 5 minutes.
# umount -v /seconddisk
Now create a script (Let's call it '/usr/local/sbin/dailybackup'):
#!/bin/sh /sbin/e2fsck -C -T -a LABEL=SecondDisk mount -v -t ext3 LABEL=SecondDisk /seconddisk rsync -v -a -x -H --delete --delete-after --exclude=lost+found/ / /seconddisk umount -v /seconddisk
# chmod +x /usr/local/sbin/dailybackup
Now create a daily cron job:
# crontab -e
Add the line:
10 0 * * * /usr/local/sbin/dailybackup
And you are all set. Once a day an 10 past midnight, the backup disk will be sync'ed to the live system disk. Every morning you will get a message from cron with the output.
If you really want to, you can change the '0' above to '0,6,12,18' and the sync'ing will happen every 6 hours. This is *probably* overkill.
2009/6/21 Robert Heller heller@deepsoft.com
At Sun, 21 Jun 2009 11:49:09 +0200 CentOS mailing list <
centos@centos.org>
wrote:
Hi all. I'm currently having a following problem: I have only ssh
connection
to a CentOS 5.2 system, there are two harddiscs on it. One stores the
system
(/ filesystem) and the other should be used to help restore the
system in
case of first disks' failure. I thought that maybe dump would be a
good
utility to make it. But in only works on read-only filesystems. In
one
Dump works just fine on a read-write file system. There is the pretty much standard limitation (that applies to *all* backup methods) that when backing up an 'active' file system: there will always be files
that
will miss the backup because they were being written during the backup process.
article I've read that making a snapshot of the / filesystem (then it wouldbe read-only) and backing it could help. But aren't snapshots
limited
to logical volumes (LVM)? My friend told me to use rsync to back up
the
entire / filesystem to the second disk and then in case o failure the
system
from the copy should boot ok.
Could anyone provide any suggestions? I don't have physical contact
with
the
machine so for example RAID 1 isn't a possible option/
Any help will be very kindly appreciated.
Make an initial dump to get the base system copied, then set up a cron job to sync the disks once a day (or more frequently) with rsync.
With regards, R.
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com --
http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller@deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
MIME-Version: 1.0
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
David Goldsmith -
Javor Nikolov -
Rafał Radecki -
Robert Heller -
Rudi Ahlers