From owner-freebsd-questions@FreeBSD.ORG Sat Jun 28 01:56:02 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A3A656E9 for ; Sat, 28 Jun 2014 01:56:02 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7107F240D for ; Sat, 28 Jun 2014 01:56:02 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id l13so2620699iga.1 for ; Fri, 27 Jun 2014 18:56:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=sGQwkr8qRVivxMhGvpi84ZMeONL7Qkg0oG/rHXFCGjY=; b=Au5E4F2uomihXjqyuJDi9AkkmChiX+RXgDFClSBdHoQ6uMf8NM2comirVHMIW2Sd81 b9EEPntjBV2wVb5d8DCQ1aLxmzYK36RRiCCfvcQv69+ADcUSeklJ9ATuzqKatAks7d6C KIcRSUnBvIjW51b7s+kr19xz8sZ0oHgJsHKbXxt1SFBTgGQd85xUDOKQttFBIYIT7fGT Hiwf8RY1/ltDDCrh3uYSR7EPmhedMJrvJ9IVCR3UkNM/IeeYqw2Ez7i53rXhVEGmS7fH SCX2xyXk7lB3etmxe7ar6xTKMjCI0lFVMW1dfz5qbm4XEmxUTQcdJMc0r13uurnFdji+ VFUA== MIME-Version: 1.0 X-Received: by 10.50.253.193 with SMTP id ac1mr16430829igd.35.1403920561789; Fri, 27 Jun 2014 18:56:01 -0700 (PDT) Received: by 10.64.225.194 with HTTP; Fri, 27 Jun 2014 18:56:01 -0700 (PDT) In-Reply-To: <44y4wi3v5x.fsf@be-well.ilk.org> References: <44lhsi5ugm.fsf@be-well.ilk.org> <20140627223650.25210a53.freebsd@edvax.de> <44y4wi3v5x.fsf@be-well.ilk.org> Date: Fri, 27 Jun 2014 18:56:01 -0700 Message-ID: Subject: Re: what should uname -v be telling me here? From: paul beard To: "questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 01:56:02 -0000 On Fri, Jun 27, 2014 at 2:22 PM, Lowell Gilbert wrote: > The boot procedure has to load and boot the kernel without having the > kernel available to create the device nomenclature. [Kind of obvious, > if you think about it.] So interrogating the firmware is the only way > the kernel *could* know where it was booted from. That's impossible > in the BIOS world, and even if there were a table indicating it in an > ACPI table, that would only tell you which disk the bootloader came > from, which isn't necessarily where the kernel came from. > I get that. It can sure mess things up if you boot from one and mount root et al from another. Just to add insult to injury, while cleaning out the dust and reseating cables, the plastic tab that backs up the pins on the SATA data connector broke off, leaving the pins exposed. So what was one a backup drive then a main drive is now possibly junk unless I can make the duct-tape arrangement that's in place while I run recoverdisk more durable. Lousy case for tight fitting components=E2=80=A6 --=20 Paul Beard / www.paulbeard.org/