Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 06 Feb 2001 11:25:58 +0100
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        chris@aims.com.au
Cc:        sheldonh@uunet.co.za, current@freebsd.org
Subject:   Re: md, current and stable 
Message-ID:  <33052.981455158@critter>
In-Reply-To: Your message of "Tue, 06 Feb 2001 21:23:59 %2B1100." <004a01c09026$ec0261f0$020aa8c0@aims.private> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <004a01c09026$ec0261f0$020aa8c0@aims.private>, "Chris Knight" writes:
>Howdy,
>
>> -----Original Message-----
>> From: Sheldon Hearn [mailto:sheldonh@uunet.co.za]
>> Sent: Tuesday, 6 February 2001 20:38
>> To: chris@aims.com.au
>> Cc: phk@freebsd.org; current@freebsd.org
>> Subject: Re: md, current and stable
>>
>>
>> On Tue, 06 Feb 2001 16:34:39 +1100, "Chris Knight" wrote:
>>
>> > Since the new md was introduced, it is not possible to
>> build a -current
>> > snapshot on a -stable box. Are there any plans to MFC this soon?
>>
>> Woah, what's the problem?  This sounds like something that should be
>> fixed, not covered up with an MFC.
>>
>When -current's release scripts were cut over to use mdconfig due to PHK's
>death warrant notice of vn, vnconfig and MFS, release builds stopped working
>on -stable due to -stable's md driver not having a handler for /dev/mdctl.
>As vn + friends are disappearing, it makes sense for md to be MFCed, thus
>fixing the problem.

Somebody with a stable machine: try it and send patches.

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33052.981455158>