On Mon, 13 Dec 1999, Greg Lehey wrote:
> > Note: this fixes some recent problems (Hi Greg!) that I've been
> > having.
>
> Really? I thought they were more serious.
So did I. Although, I did a 'make world' after I saw the change go in,
so the fix could have come from a different commit.
In an
On Monday, 13 December 1999 at 18:18:14 -0500, Bill Fumerola wrote:
> On Sun, 12 Dec 1999, Peter Wemm wrote:
>
>>> -if (drive->vp->v_type != VBLK) { /* only consider bl
>> ock devices */
>>> +if (!vn_isdisk(drive->vp)) { /* only consider
On Sun, 12 Dec 1999, Peter Wemm wrote:
> > -if (drive->vp->v_type != VBLK) { /* only consider bl
> ock devices */
> > +if (!vn_isdisk(drive->vp)) { /* only consider bl
Note: this fixes some recent problems (Hi Greg!) that I've been
havi
> Jordan, I don't understand your answer. Using the new MAKEDEV is what
> causes vinum to fail. Won't -release be using the new MAKEDEV?
Sorry, I evidently didn't read the message the same way. If the
problem is indeed as you say then vinum has been broken; I thought
he was talking about using
At Sun, 12 Dec 1999 16:37:29 +0100,
Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> I think that between the two of us, Greg and I have lost a oneline
> patch on the floor, try this:
>
> Index: vinumio.c
This patch solved my problem, and I found it has already been
committed to the tree. :)
tha
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>I'm on the road now, and writing mail is like pulling teeth. phk
>supplied the correct patch. phk, could you commit it, please?
Done.
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run
I'm on the road now, and writing mail is like pulling teeth. phk
supplied the correct patch. phk, could you commit it, please?
Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Kevin Street writes:
>
> >Jordan, I don't understand your answer. Using the new MAKEDEV is what
> >causes vinum to fail. Won't -release be using the new MAKEDEV?
> >
> >Greg, is there a mechanism to transition an existing vinum
> >insta
In message <[EMAIL PROTECTED]>, Kevin Street writes:
>Jordan, I don't understand your answer. Using the new MAKEDEV is what
>causes vinum to fail. Won't -release be using the new MAKEDEV?
>
>Greg, is there a mechanism to transition an existing vinum
>installation to the new device nodes?
I th
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes:
> > Since the recent block device vanishment, MAKEDEV all and my vinum
> > volumes have failed to start.
>
> Please read /usr/src/UPDATING if you're going to track -current
> these days. The reason for this is clearly documented at the
> top of th
> Since the recent block device vanishment, MAKEDEV all and my vinum
> volumes have failed to start.
Please read /usr/src/UPDATING if you're going to track -current
these days. The reason for this is clearly documented at the
top of that file and won't be a problem in -release since the
correct
Hi Greg,
Since the recent block device vanishment, MAKEDEV all and my vinum
volumes have failed to start.
# ls -l da[01]s1h
crw-r- 1 root operator 13, 0x00020007 Dec 12 22:56 da0s1h
crw-r- 1 root operator 13, 0x0002000f Dec 12 22:56 da1s1h
# vinum start
** no drives found: No suc
12 matches
Mail list logo
