On 15/09/11 10:02, John Doe wrote:
What about using multilib_policy=best instead?
JD
This is what I do as well and it's worked well on many different
machines now. i386/i686 packages are not automatically pulled in
anymore, it automatically selects the right arch (x86_64).
On 19/07/2011 08:14, James Hogarth wrote:
I built a CentOS 6 machine to host several CentOS 6 guest servers.
As all guests will be Internet facing I set up the host with two
bridged NICs and assigned an Internet facing IP address to br0 and a
local IP address to br1.
Each guest was
On 06/28/2011 07:17 PM, Robert Heller wrote:
At Tue, 28 Jun 2011 18:13:13 +0100 (BST) CentOS mailing
listcentos@centos.org wrote:
Maybe that's because my machine is running generally 24/7,
and I do quite often leave FF running on 2-3 desktops, with
several tabs open at once. Then yum runs
I've found that if I'm on an Ubuntu machine and SSHing to a Centos 5.4
machine, it does the same thing, i.e. it sort of hangs for a while then
comes back after about 10-15 secs with a login prompt.
I've found that editing the /etc/ssh/ssh_config (note ssh_config, NOT
sshd_config) file on the
Hi,
I just got an Android phone last week and wanted something similar, i.e. an app
that will automatically check for new feeds of a podcast and download them for
me.
The app I'm trying right now is BeyondPod and it does a nice job. However it's
a 7-day trial app and i'm not sure which
Thanks to all of you for your help, and especially Tim Shubitz who faced the
same problem and his solution worked perfectly for me.
However, now that I have properly created a GPT partition of size 2.7TB, which
filesystem is best on it? This filesystem will be used to
store backups of various
On 8 Mar 2010, at 16:09, Alan Hoffmeister wrote:
JFS.
http://www.debian-administration.org/articles/388
The article you linked to suggests XFS though? I'm also now thinking about EXT3
with a mkfs.ext3 -T news for example so that I get more inodes?
Yes. Absolutely yes. One day you'll reboot and your partition table (and
all your data) will be gone and unrecoverable. Trust me.
And that reason is that it *will* die horribly and eat your data. Set up
the small logical drive in the RAID BIOS as another poster detailed so
nicely.
On 23 Feb 2010, at 18:02, Robert Heller wrote:
I guessing one of these things is going on:
A) Ubuntu has *patched* versions of parted and fdisk that disable their
error checking (!).
B) Ubuntu has new versions of parted and fdisk that are more liberal
than the (older) versions shipped
On 23 Feb 2010, at 23:41, Robert Nichols wrote:
You realize that you're utilizing just 2TiB of that 2.7TiB drive, right?
It looks like the tools in Ubuntu simply partitioned as much of the drive
as they could handle with an msdos label and let the rest go to waste.
Yes I'll fix this the
Hello, sorry for the long email, it's a little hard to explain this issue. The
gist of it is that the Ubuntu version of parted allowed me to do something
which perhaps should not be allowed i.e. creating partitions on a 2.7TB drive
when the partition table is not *gpt* but *msdos*.
I am trying
Thanks for your replies, just to clear things up, here is what I am seeing.
If I reboot server A with the Ubuntu LiveCD, I get:
# parted /dev/sda p
Model: DELL PERC 5/i (scsi)
Disk /dev/sda: 2998GB
Sector size (logical/physical): 512B/512B
Partition
12 matches
Mail list logo