On Sat, 2007-02-10 at 23:39 -0500, Mike Frysinger wrote:
> On Saturday 10 February 2007, Mike Doty wrote:
> > Do we have documentation on howto migrate? Thats the big thing holding
> > me back(afaik, I have to backup, wipe the disks and then do mdadm and
> > restore)
>
> erm, no ... you dont need
On Monday 12 February 2007, Chris Gianelloni wrote:
> If we're going to do this, should we do it before the 2007.0 snapshot,
> so people don't have raidtools disappear out from under them on their
> newly-installed system?
it's already been done
> Also, is mdadm.conf 100% compatible with /etc/rai
On Mon, 2007-02-12 at 08:58 -0500, Mike Frysinger wrote:
> On Monday 12 February 2007, Chris Gianelloni wrote:
> > If we're going to do this, should we do it before the 2007.0 snapshot,
> > so people don't have raidtools disappear out from under them on their
> > newly-installed system?
>
> it's a
On Monday 12 February 2007, Chris Gianelloni wrote:
> Then what is the migration path? You made it sound like copying the
> file was the solution.
if the default mdadm scan does not automatically detect their raid devices,
then the user needs to manually define their raid devices in /etc/mdadm.c
Hi all,
Due to the newest media-lib/gd the current graphviz won't build
anymore. Could someone who actually uses it, bump it to the latest
version and have a look at the keywording status. Thanks.
V-Li
signature.asc
Description: PGP signature
Christian Faulhammer wrote:
> Hi all,
> Due to the newest media-lib/gd the current graphviz won't build
> anymore. Could someone who actually uses it, bump it to the latest
> version and have a look at the keywording status. Thanks.
Will do.
> V-Li
signature.asc
Description: OpenPGP digita
On Mon, 2007-02-12 at 11:13 -0500, Mike Frysinger wrote:
> On Monday 12 February 2007, Chris Gianelloni wrote:
> > Then what is the migration path? You made it sound like copying the
> > file was the solution.
>
> if the default mdadm scan does not automatically detect their raid devices,
> then
William L. Thomson Jr. wrote:
> Migration is from my experience painless. Even if detecting does not
> work, the mdadm.conf syntax is easier IMHO.
>
> However a nice little guide or doc on it, should cover and address most
> all user issues stemming from migration. If such a document does not
> al
On Monday 12 February 2007, William L. Thomson Jr. wrote:
> Migration is from my experience painless. Even if detecting does not
> work, the mdadm.conf syntax is easier IMHO.
and the comments in mdadm.conf explain the most common cases pretty clearly
> However a nice little guide or doc on it, sh
Both sides have valid points:
1) we should remove vulnerable cruft from the tree
2) we should not break dependencies for any arch, regardless of their
response time
I believe some communication adjustments could avoid unnecessary conflict.
If a package cannot be removed because a newer version
10 matches
Mail list logo
