Date: Tue, 23 Oct 2007 08:58:37 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Kip Macy" <kip.macy@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: Should Xen be a sub-arch or a build option? Message-ID: <86sl42mi5e.fsf@ds4.des.no> In-Reply-To: <b1fa29170710221130o21d8d8a1yb9f69d0dbc5c35c9@mail.gmail.com> (Kip Macy's message of "Mon\, 22 Oct 2007 11\:30\:42 -0700") References: <b1fa29170710212056x5649a858n5202b78fc3e55589@mail.gmail.com> <86lk9ve5bx.fsf@ds4.des.no> <b1fa29170710221130o21d8d8a1yb9f69d0dbc5c35c9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Kip Macy" <kip.macy@gmail.com> writes: > What if, rather than putting ifndef XEN in 10 or 15 files, I instead > added "native" to options.i386 and marked all those files as "native" > in files.i386 and then put "native" in DEFAULTS. That would allow me > to simply add "nooption native" in a XEN kernel config and disable > their compilation without touching the files themselves. or "legacy" perhaps, rather than "native". It would also be useful for anyone trying to run FreeBSD on a so-called "legacy-free" machine that doesn't have a PC-compatible BIOS (many thin clients for instance) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86sl42mi5e.fsf>