>> [I think] 4.3 did not have on-disk disklabels.
> Just checked my copy of the 4.3-Tahoe
The 4.3 I used was pre-Tahoe, pre-Lite, pre-Reno, pre-everything. We
started with 4.1c, then, successively, 4.2, 4.3, and mtXinu's 4.3+NFS,
then SunOS. (This was at a university with the relevant license;
mo...@rodents-montreal.org writes:
> 4.3 did not have on-disk disklabels. Partition tables were built into
> the drivers; changing partitioning required recompiling the relevant
> driver. (I'm reasonably sure it worked that way for the disks we
> actually had on our 4.3 machine(s), at least.)
On Tue, Dec 27, 2016 at 06:02:01AM +, Michael van Elst wrote:
> >> I'm not sure wether disks without labels could be used at all in
> >> 4.3bsd.
>
> >Those memories are pretty fuzzy, but I _think_ it worked this way:
>
> >4.3 did not have on-disk disklabels.
>
> 4.3tahoe added the
mo...@rodents-montreal.org (Mouse) writes:
>> I'm not sure wether disks without labels could be used at all in
>> 4.3bsd.
>Those memories are pretty fuzzy, but I _think_ it worked this way:
>4.3 did not have on-disk disklabels.
4.3tahoe added the on-disk disklabels for some drivers.
--
--
> I'm not sure wether disks without labels could be used at all in
> 4.3bsd.
Those memories are pretty fuzzy, but I _think_ it worked this way:
4.3 did not have on-disk disklabels. Partition tables were built into
the drivers; changing partitioning required recompiling the relevant
driver.
g...@lexort.com (Greg Troxel) writes:
>I think it's wrong to print out messages like that because DIAGNOSTIC is
>defined. DIAGNOSTIC is supposed to just add KASSERT (was panic, long
>ago) about conditions that must be true unless the kernel is buggy.
The specific disklabel warnings are printed
I think it's wrong to print out messages like that because DIAGNOSTIC is
defined. DIAGNOSTIC is supposed to just add KASSERT (was panic, long
ago) about conditions that must be true unless the kernel is buggy.
Separately, given that there's no rule that all disks must have labels,
it seems
mar...@duskware.de (Martin Husemann) writes:
># mount -o async,discard /dev/dk1 /mnt
>wd0: no disk label
>wd0: no disk label
>wd0: no disk label
>#
>It is not clear to me why we call dk_getlabel that often and whether this
>message would make any sense ever more than once (or in my use case ever
On a sparc64 machine (so using dev/sun/sunlabel.c) but using GPT on anything
but the boot device I get spurious kernel messages that I would like to
avoid:
# mount -o async,discard /dev/dk1 /mnt
wd0: no disk label
wd0: no disk label
wd0: no disk label
#
The wedge dk1 lives on wd0, wd0 only has a
