Date: Thu, 17 Sep 2015 07:47:08 +0000 From: Stefano Garzarella <stefanogarzarella@gmail.com> To: NGie Cooper <yaneurabeya@gmail.com>, Ryan Stone <rysto32@gmail.com> Cc: Julian Elischer <julian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: nanoBSD boot problem (on USB stick or as a HD) Message-ID: <CAO0mX5ZPEoE8_X=q6y1s9rpXKb9oMfZjg-TWyTq-0eUCSSm_DQ@mail.gmail.com> In-Reply-To: <CAGHfRMDQVOpp5Kk4ngabuPg7JQoSQi35W5_i3Qu8wWkvOX7OuQ@mail.gmail.com> References: <CAO0mX5YwFpUhcWfni8QeyOzesFmLpCQnkPT5zFOYU5PokYdiFw@mail.gmail.com> <55F8CBB2.1080109@freebsd.org> <CAFMmRNymd6jeZLepa1W_2m-5uYC5AO%2B9qyVyzZNnoYJpvibDSg@mail.gmail.com> <CAGHfRMDQVOpp5Kk4ngabuPg7JQoSQi35W5_i3Qu8wWkvOX7OuQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks to all!
as NGie says, I used the labeling through NANO_LABEL and it works very
well!
Now in the /etc/fstab I have the label and not the disk specific partition!
Maybe is better to set default label in the nanobsd.sh and not the driver
in according to NGie.
Cheers,
Stefano
Il giorno mer 16 set 2015 alle 04:26 NGie Cooper <yaneurabeya@gmail.com> ha
scritto:
> On Tue, Sep 15, 2015 at 7:18 PM, Ryan Stone <rysto32@gmail.com> wrote:
> > On Tue, Sep 15, 2015 at 9:53 PM, Julian Elischer <julian@freebsd.org>
> wrote:
> >
> >> one possibility is to use gpart label to describe the device.
> >> possibly it woudl hav ehte same result in both cases, but I don't know
> for
> >> sure that
> >> it works for root device.. you'd have to test.
> >>
> >>
> > I would recommend a UFS label instead. gpart labels are kind of fragile
> > and easy to mess up. My previous employer has been shipping systems
> where
> > the root fs is specified in fstab via a UFS label for years and it never
> > gave us a problems.
>
> +100
>
> And FWIW as Stefano discovered later, NANO_LABEL does just that (use
> UFS labels).
>
> The only unfortunate thing is that nanobsd uses a NUL string by default:
>
> grep NANO_LABEL tools/tools/nanobsd/defaults.sh
> tools/tools/nanobsd/defaults.sh:NANO_LABEL=""
> tools/tools/nanobsd/defaults.sh: echo newfs ${NANO_NEWFS}
> ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev}
> tools/tools/nanobsd/defaults.sh: newfs ${NANO_NEWFS}
> ${NANO_LABEL:+-L${NANO_LABEL}${lbl}} ${dev}
> tools/tools/nanobsd/defaults.sh: if [ ! -z ${NANO_LABEL} ];
> then
> tools/tools/nanobsd/defaults.sh: tunefs -L
> ${NANO_LABEL}"s2a" /dev/${MD}s2a
> tools/tools/nanobsd/defaults.sh: # Override user's NANO_DRIVE if
> they specified a NANO_LABEL
> tools/tools/nanobsd/defaults.sh: [ ! -z "${NANO_LABEL}" ] &&
> NANO_DRIVE="ufs/${NANO_LABEL}"
>
> The default NANO_DRIVE is useless though -- the old ata(4) stack is dead:
>
> 95 # The drive name of the media at runtime
> 96 NANO_DRIVE=ad0
>
> Cheers,
> -NGie
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAO0mX5ZPEoE8_X=q6y1s9rpXKb9oMfZjg-TWyTq-0eUCSSm_DQ>