Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-29 Thread Warner Losh 
On Thu, Sep 28, 2017 at 11:54 PM, Kevin Oberman  wrote:

> On Thu, Sep 28, 2017 at 6:09 PM, Rodney W. Grimes <
> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
>
>> > On Thu, Sep 28, 2017 at 11:12 AM, Kevin Oberman 
>> wrote:
>> >
>> > > On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:
>> > >
>> > >> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma > >
>> > >> wrote:
>> > >>
>> > >> > I created a new kernel config file from scratch, wondered what the
>> > >> > GEOM_PART_MBR option and friends were doing, search for them,
>> didn't
>> > >> find
>> > >> > them in the tree, and deleted them from my config. But... de
>> resulting
>> > >> disk
>> > >> > image didn't boot, because of the fact that it didn't recognise
>> the MBR
>> > >> > partitions (it only had a single diskid entry on the mount-root
>> prompt).
>> > >> >
>> > >> > Can anyone explain to me how these kernel options work, as in:
>> they are
>> > >> > defined in kernel configs and as a consequence in opt_geom.h, but
>> how
>> > >> are
>> > >> > they actually used to select which geom_part_* modules/kernel
>> parts to
>> > >> > build? I thought these options were translated to stuff that cpp
>> would
>> > >> use,
>> > >> > but there are not uses of for example GEOM_PART_MBR anywhere for
>> > >> example!
>> > >> >
>> > >> >
>> > >> > The module always build them because they are listed in the
>> module's
>> > >> > Makefile.
>> > >> >
>> > >> > The kernel only sometimes does. Here's the key lines from
>> conf/files:
>> > >> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
>> > >> > files:geom/part/g_part_apm.c optional geom_part_apm
>> > >> > files:geom/part/g_part_bsd.c optional geom_part_bsd
>> > >> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
>> > >> > files:geom/part/g_part_ebr.c optional geom_part_ebr
>> > >> > files:geom/part/g_part_gpt.c optional geom_part_gpt
>> > >> > files:geom/part/g_part_ldm.c optional geom_part_ldm
>> > >> > files:geom/part/g_part_mbr.c optional geom_part_mbr
>> > >> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
>> > >> >
>> > >> > which turn on/off which files get included. config "helpfully"
>> converts
>> > >> the
>> > >> > upper case options to lower case for this.
>> > >> >
>> > >> > Warner
>> > >> >
>> > >> >
>> > >> > *slaps forehead* Goose chase!
>> > >> >
>> > >> > I actually knew that... and, at the time, thought it was weird
>> > >> behaviour.
>> > >> > ''grep" would not have failed me if those options would be
>> uppercase
>> > >> there
>> > >> > ...
>> > >> >
>> > >>
>> > >> I've been nibbled to death by these geese often enough to have a
>> PTSD-like
>> > >> reaction when someone mentions it and habitually add -i to my
>> greps...
>> > >>
>> > >> Warner
>> > >
>> > >
>> > > This horrid POLA violation seems to have been in FreeBSD configuration
>> > > since at least 3.0 and probably goes back to the creation of the
>> > > configuration process.
>> > >
>> > > Any idea why such a horrible POLA was ever introduced? Seems like an
>> > > obviously bad idea in an OS that is ALMOST always case sensitive.
>> > >
>> >
>> > It's received code from the old 4.3 BSD config program (or maybe the
>> net-2
>> > config program).
>>
>> We had best not have any code direct from 4.3 or net-2, it should be from
>> 4.4BSDLite, any code prior to that is subject of the lawsuit.
>>
>>
>> --
>> Rod Grimes
>> rgri...@freebsd.org
>>
>
> I believe any code in 4.3 BSD that was developed by CSRG was not subject
> of the suit. Copyright on that code by the Regents of UC, not AT&T. (So was
> any code I wrote.) Many utilities were from v8 or descended from AT&T code,
> but a great deal was not. It was what UC was getting paid for.
>

Yea, the suit quickly devolved into the short list of files...

v8 was from BSD that was reimported. That's clear from the TUHS archive. v8
is a big break from v7...

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Kevin Oberman 
On Thu, Sep 28, 2017 at 6:09 PM, Rodney W. Grimes <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:

> > On Thu, Sep 28, 2017 at 11:12 AM, Kevin Oberman 
> wrote:
> >
> > > On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:
> > >
> > >> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
> > >> wrote:
> > >>
> > >> > I created a new kernel config file from scratch, wondered what the
> > >> > GEOM_PART_MBR option and friends were doing, search for them, didn't
> > >> find
> > >> > them in the tree, and deleted them from my config. But... de
> resulting
> > >> disk
> > >> > image didn't boot, because of the fact that it didn't recognise the
> MBR
> > >> > partitions (it only had a single diskid entry on the mount-root
> prompt).
> > >> >
> > >> > Can anyone explain to me how these kernel options work, as in: they
> are
> > >> > defined in kernel configs and as a consequence in opt_geom.h, but
> how
> > >> are
> > >> > they actually used to select which geom_part_* modules/kernel parts
> to
> > >> > build? I thought these options were translated to stuff that cpp
> would
> > >> use,
> > >> > but there are not uses of for example GEOM_PART_MBR anywhere for
> > >> example!
> > >> >
> > >> >
> > >> > The module always build them because they are listed in the module's
> > >> > Makefile.
> > >> >
> > >> > The kernel only sometimes does. Here's the key lines from
> conf/files:
> > >> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> > >> > files:geom/part/g_part_apm.c optional geom_part_apm
> > >> > files:geom/part/g_part_bsd.c optional geom_part_bsd
> > >> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> > >> > files:geom/part/g_part_ebr.c optional geom_part_ebr
> > >> > files:geom/part/g_part_gpt.c optional geom_part_gpt
> > >> > files:geom/part/g_part_ldm.c optional geom_part_ldm
> > >> > files:geom/part/g_part_mbr.c optional geom_part_mbr
> > >> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> > >> >
> > >> > which turn on/off which files get included. config "helpfully"
> converts
> > >> the
> > >> > upper case options to lower case for this.
> > >> >
> > >> > Warner
> > >> >
> > >> >
> > >> > *slaps forehead* Goose chase!
> > >> >
> > >> > I actually knew that... and, at the time, thought it was weird
> > >> behaviour.
> > >> > ''grep" would not have failed me if those options would be uppercase
> > >> there
> > >> > ...
> > >> >
> > >>
> > >> I've been nibbled to death by these geese often enough to have a
> PTSD-like
> > >> reaction when someone mentions it and habitually add -i to my greps...
> > >>
> > >> Warner
> > >
> > >
> > > This horrid POLA violation seems to have been in FreeBSD configuration
> > > since at least 3.0 and probably goes back to the creation of the
> > > configuration process.
> > >
> > > Any idea why such a horrible POLA was ever introduced? Seems like an
> > > obviously bad idea in an OS that is ALMOST always case sensitive.
> > >
> >
> > It's received code from the old 4.3 BSD config program (or maybe the
> net-2
> > config program).
>
> We had best not have any code direct from 4.3 or net-2, it should be from
> 4.4BSDLite, any code prior to that is subject of the lawsuit.
>
>
> --
> Rod Grimes
> rgri...@freebsd.org
>

I believe any code in 4.3 BSD that was developed by CSRG was not subject of
the suit. Copyright on that code by the Regents of UC, not AT&T. (So was
any code I wrote.) Many utilities were from v8 or descended from AT&T code,
but a great deal was not. It was what UC was getting paid for.

My first Unix experience was with 4.2 BSD and I was not concerned with
copyrights as I was working for  UC (at least my paychecks said so) and we
had an AT&T license for Unix, so it was simply not an issue. The system was
a VAX-11/750 at the UC-Davis Department of Applied Science located at
Lawrence Livermore Lab.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Rodney W. Grimes 
> On Thu, Sep 28, 2017 at 11:12 AM, Kevin Oberman  wrote:
> 
> > On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:
> >
> >> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
> >> wrote:
> >>
> >> > I created a new kernel config file from scratch, wondered what the
> >> > GEOM_PART_MBR option and friends were doing, search for them, didn't
> >> find
> >> > them in the tree, and deleted them from my config. But... de resulting
> >> disk
> >> > image didn't boot, because of the fact that it didn't recognise the MBR
> >> > partitions (it only had a single diskid entry on the mount-root prompt).
> >> >
> >> > Can anyone explain to me how these kernel options work, as in: they are
> >> > defined in kernel configs and as a consequence in opt_geom.h, but how
> >> are
> >> > they actually used to select which geom_part_* modules/kernel parts to
> >> > build? I thought these options were translated to stuff that cpp would
> >> use,
> >> > but there are not uses of for example GEOM_PART_MBR anywhere for
> >> example!
> >> >
> >> >
> >> > The module always build them because they are listed in the module's
> >> > Makefile.
> >> >
> >> > The kernel only sometimes does. Here's the key lines from conf/files:
> >> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> >> > files:geom/part/g_part_apm.c optional geom_part_apm
> >> > files:geom/part/g_part_bsd.c optional geom_part_bsd
> >> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> >> > files:geom/part/g_part_ebr.c optional geom_part_ebr
> >> > files:geom/part/g_part_gpt.c optional geom_part_gpt
> >> > files:geom/part/g_part_ldm.c optional geom_part_ldm
> >> > files:geom/part/g_part_mbr.c optional geom_part_mbr
> >> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> >> >
> >> > which turn on/off which files get included. config "helpfully" converts
> >> the
> >> > upper case options to lower case for this.
> >> >
> >> > Warner
> >> >
> >> >
> >> > *slaps forehead* Goose chase!
> >> >
> >> > I actually knew that... and, at the time, thought it was weird
> >> behaviour.
> >> > ''grep" would not have failed me if those options would be uppercase
> >> there
> >> > ...
> >> >
> >>
> >> I've been nibbled to death by these geese often enough to have a PTSD-like
> >> reaction when someone mentions it and habitually add -i to my greps...
> >>
> >> Warner
> >
> >
> > This horrid POLA violation seems to have been in FreeBSD configuration
> > since at least 3.0 and probably goes back to the creation of the
> > configuration process.
> >
> > Any idea why such a horrible POLA was ever introduced? Seems like an
> > obviously bad idea in an OS that is ALMOST always case sensitive.
> >
> 
> It's received code from the old 4.3 BSD config program (or maybe the net-2
> config program).

We had best not have any code direct from 4.3 or net-2, it should be from
4.4BSDLite, any code prior to that is subject of the lawsuit.


-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Warner Losh 
On Sep 28, 2017 7:09 PM, "Rodney W. Grimes" <
freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:

> On Thu, Sep 28, 2017 at 11:12 AM, Kevin Oberman 
wrote:
>
> > On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:
> >
> >> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
> >> wrote:
> >>
> >> > I created a new kernel config file from scratch, wondered what the
> >> > GEOM_PART_MBR option and friends were doing, search for them, didn't
> >> find
> >> > them in the tree, and deleted them from my config. But... de
resulting
> >> disk
> >> > image didn't boot, because of the fact that it didn't recognise the
MBR
> >> > partitions (it only had a single diskid entry on the mount-root
prompt).
> >> >
> >> > Can anyone explain to me how these kernel options work, as in: they
are
> >> > defined in kernel configs and as a consequence in opt_geom.h, but how
> >> are
> >> > they actually used to select which geom_part_* modules/kernel parts
to
> >> > build? I thought these options were translated to stuff that cpp
would
> >> use,
> >> > but there are not uses of for example GEOM_PART_MBR anywhere for
> >> example!
> >> >
> >> >
> >> > The module always build them because they are listed in the module's
> >> > Makefile.
> >> >
> >> > The kernel only sometimes does. Here's the key lines from conf/files:
> >> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> >> > files:geom/part/g_part_apm.c optional geom_part_apm
> >> > files:geom/part/g_part_bsd.c optional geom_part_bsd
> >> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> >> > files:geom/part/g_part_ebr.c optional geom_part_ebr
> >> > files:geom/part/g_part_gpt.c optional geom_part_gpt
> >> > files:geom/part/g_part_ldm.c optional geom_part_ldm
> >> > files:geom/part/g_part_mbr.c optional geom_part_mbr
> >> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> >> >
> >> > which turn on/off which files get included. config "helpfully"
converts
> >> the
> >> > upper case options to lower case for this.
> >> >
> >> > Warner
> >> >
> >> >
> >> > *slaps forehead* Goose chase!
> >> >
> >> > I actually knew that... and, at the time, thought it was weird
> >> behaviour.
> >> > ''grep" would not have failed me if those options would be uppercase
> >> there
> >> > ...
> >> >
> >>
> >> I've been nibbled to death by these geese often enough to have a
PTSD-like
> >> reaction when someone mentions it and habitually add -i to my greps...
> >>
> >> Warner
> >
> >
> > This horrid POLA violation seems to have been in FreeBSD configuration
> > since at least 3.0 and probably goes back to the creation of the
> > configuration process.
> >
> > Any idea why such a horrible POLA was ever introduced? Seems like an
> > obviously bad idea in an OS that is ALMOST always case sensitive.
> >
>
> It's received code from the old 4.3 BSD config program (or maybe the net-2
> config program).

We had best not have any code direct from 4.3 or net-2, it should be from
4.4BSDLite, any code prior to that is subject of the lawsuit.


The code is idental in both. There is also a newconfig in 4.4 we didn't
adopt...

Warner



--
Rod Grimes
rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Cy Schubert 
Changing grep to default to -i would be the POLA violation. Rather than mess 
with grep like RHEL has I suggest installing textproc/the_silver_searcher 
pkg/port. It does everything grep does and more. I've switched to ag (which by 
default does recursive case insensitive searches) while using grep in scripts 
and at times I need simply grep.


---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.

Cy Schubert
 or 

-Original Message-
From: Kevin Oberman
Sent: 28/09/2017 10:13
To: Warner Losh
Cc: Nick Hibma; FreeBSD Current Mailing List
Subject: Re: How do GEOM_PART_* options configure geom_part_* modules??

On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:

> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
> wrote:
>
> > I created a new kernel config file from scratch, wondered what the
> > GEOM_PART_MBR option and friends were doing, search for them, didn't find
> > them in the tree, and deleted them from my config. But... de resulting
> disk
> > image didn't boot, because of the fact that it didn't recognise the MBR
> > partitions (it only had a single diskid entry on the mount-root prompt).
> >
> > Can anyone explain to me how these kernel options work, as in: they are
> > defined in kernel configs and as a consequence in opt_geom.h, but how are
> > they actually used to select which geom_part_* modules/kernel parts to
> > build? I thought these options were translated to stuff that cpp would
> use,
> > but there are not uses of for example GEOM_PART_MBR anywhere for example!
> >
> >
> > The module always build them because they are listed in the module's
> > Makefile.
> >
> > The kernel only sometimes does. Here's the key lines from conf/files:
> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> > files:geom/part/g_part_apm.c optional geom_part_apm
> > files:geom/part/g_part_bsd.c optional geom_part_bsd
> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> > files:geom/part/g_part_ebr.c optional geom_part_ebr
> > files:geom/part/g_part_gpt.c optional geom_part_gpt
> > files:geom/part/g_part_ldm.c optional geom_part_ldm
> > files:geom/part/g_part_mbr.c optional geom_part_mbr
> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> >
> > which turn on/off which files get included. config "helpfully" converts
> the
> > upper case options to lower case for this.
> >
> > Warner
> >
> >
> > *slaps forehead* Goose chase!
> >
> > I actually knew that... and, at the time, thought it was weird behaviour.
> > ''grep" would not have failed me if those options would be uppercase
> there
> > ...
> >
>
> I've been nibbled to death by these geese often enough to have a PTSD-like
> reaction when someone mentions it and habitually add -i to my greps...
>
> Warner


This horrid POLA violation seems to have been in FreeBSD configuration
since at least 3.0 and probably goes back to the creation of the
configuration process.

Any idea why such a horrible POLA was ever introduced? Seems like an
obviously bad idea in an OS that is ALMOST always case sensitive.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Warner Losh 
On Thu, Sep 28, 2017 at 11:12 AM, Kevin Oberman  wrote:

> On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:
>
>> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
>> wrote:
>>
>> > I created a new kernel config file from scratch, wondered what the
>> > GEOM_PART_MBR option and friends were doing, search for them, didn't
>> find
>> > them in the tree, and deleted them from my config. But... de resulting
>> disk
>> > image didn't boot, because of the fact that it didn't recognise the MBR
>> > partitions (it only had a single diskid entry on the mount-root prompt).
>> >
>> > Can anyone explain to me how these kernel options work, as in: they are
>> > defined in kernel configs and as a consequence in opt_geom.h, but how
>> are
>> > they actually used to select which geom_part_* modules/kernel parts to
>> > build? I thought these options were translated to stuff that cpp would
>> use,
>> > but there are not uses of for example GEOM_PART_MBR anywhere for
>> example!
>> >
>> >
>> > The module always build them because they are listed in the module's
>> > Makefile.
>> >
>> > The kernel only sometimes does. Here's the key lines from conf/files:
>> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
>> > files:geom/part/g_part_apm.c optional geom_part_apm
>> > files:geom/part/g_part_bsd.c optional geom_part_bsd
>> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
>> > files:geom/part/g_part_ebr.c optional geom_part_ebr
>> > files:geom/part/g_part_gpt.c optional geom_part_gpt
>> > files:geom/part/g_part_ldm.c optional geom_part_ldm
>> > files:geom/part/g_part_mbr.c optional geom_part_mbr
>> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
>> >
>> > which turn on/off which files get included. config "helpfully" converts
>> the
>> > upper case options to lower case for this.
>> >
>> > Warner
>> >
>> >
>> > *slaps forehead* Goose chase!
>> >
>> > I actually knew that... and, at the time, thought it was weird
>> behaviour.
>> > ''grep" would not have failed me if those options would be uppercase
>> there
>> > ...
>> >
>>
>> I've been nibbled to death by these geese often enough to have a PTSD-like
>> reaction when someone mentions it and habitually add -i to my greps...
>>
>> Warner
>
>
> This horrid POLA violation seems to have been in FreeBSD configuration
> since at least 3.0 and probably goes back to the creation of the
> configuration process.
>
> Any idea why such a horrible POLA was ever introduced? Seems like an
> obviously bad idea in an OS that is ALMOST always case sensitive.
>

It's received code from the old 4.3 BSD config program (or maybe the net-2
config program).

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Kevin Oberman 
On Thu, Sep 28, 2017 at 9:13 AM, Warner Losh  wrote:

> On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma 
> wrote:
>
> > I created a new kernel config file from scratch, wondered what the
> > GEOM_PART_MBR option and friends were doing, search for them, didn't find
> > them in the tree, and deleted them from my config. But... de resulting
> disk
> > image didn't boot, because of the fact that it didn't recognise the MBR
> > partitions (it only had a single diskid entry on the mount-root prompt).
> >
> > Can anyone explain to me how these kernel options work, as in: they are
> > defined in kernel configs and as a consequence in opt_geom.h, but how are
> > they actually used to select which geom_part_* modules/kernel parts to
> > build? I thought these options were translated to stuff that cpp would
> use,
> > but there are not uses of for example GEOM_PART_MBR anywhere for example!
> >
> >
> > The module always build them because they are listed in the module's
> > Makefile.
> >
> > The kernel only sometimes does. Here's the key lines from conf/files:
> > files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> > files:geom/part/g_part_apm.c optional geom_part_apm
> > files:geom/part/g_part_bsd.c optional geom_part_bsd
> > files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> > files:geom/part/g_part_ebr.c optional geom_part_ebr
> > files:geom/part/g_part_gpt.c optional geom_part_gpt
> > files:geom/part/g_part_ldm.c optional geom_part_ldm
> > files:geom/part/g_part_mbr.c optional geom_part_mbr
> > files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> >
> > which turn on/off which files get included. config "helpfully" converts
> the
> > upper case options to lower case for this.
> >
> > Warner
> >
> >
> > *slaps forehead* Goose chase!
> >
> > I actually knew that... and, at the time, thought it was weird behaviour.
> > ''grep" would not have failed me if those options would be uppercase
> there
> > ...
> >
>
> I've been nibbled to death by these geese often enough to have a PTSD-like
> reaction when someone mentions it and habitually add -i to my greps...
>
> Warner


This horrid POLA violation seems to have been in FreeBSD configuration
since at least 3.0 and probably goes back to the creation of the
configuration process.

Any idea why such a horrible POLA was ever introduced? Seems like an
obviously bad idea in an OS that is ALMOST always case sensitive.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Ian Lepore 
On Thu, 2017-09-28 at 17:31 +0200, Nick Hibma wrote:
> I created a new kernel config file from scratch, wondered what the
> GEOM_PART_MBR option and friends were doing, search for them, didn't
> find them in the tree, and deleted them from my config. But... de
> resulting disk image didn't boot, because of the fact that it didn't
> recognise the MBR partitions (it only had a single diskid entry on
> the mount-root prompt).
> 
> Can anyone explain to me how these kernel options work, as in: they
> are defined in kernel configs and as a consequence in opt_geom.h, but
> how are they actually used to select which geom_part_* modules/kernel
> parts to build? I thought these options were translated to stuff that
> cpp would use, but there are not uses of for example GEOM_PART_MBR
> anywhere for example!
> 
> The only thing I was able to come up with, but could not figure out,
> was FEATURE() doing some magic.
> 
> Thanks in advance for any pointers!
> 
> Nick Hibma
> n...@van-laarhoven.org 
> 
> -- Open Source: We stand on the shoulders of giants.
> 
> 
> % grep -r GEOM_PART_ /usr/src/sys/ | grep -Ev '/conf/.*options'
> /usr/src/sys/geom/part/g_part_mbr.c:"GEOM_PART_MBR Master Boot
> Record");
> /usr/src/sys/geom/part/g_part_ldm.c:"GEOM_PART_LDM Logical Disk
> Manager");
> /usr/src/sys/geom/part/g_part_ldm.c:   * XXX: We use some
> knowledge about GEOM_PART_GPT internal
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part.h:#ifndef _GEOM_PART_H_
> /usr/src/sys/geom/part/g_part.h:#define   _GEOM_PART_H_
> /usr/src/sys/geom/part/g_part.h:#endif /* !_GEOM_PART_H_ */

If you had added '-i' to your grep command you would have found the
missing piece in sys/conf/files.  config(8) turns uppercase OPTION_NAME
into lowercase option_name for purposes of configuring which files to
compile.

-- Ian

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Warner Losh 
On Thu, Sep 28, 2017 at 10:00 AM, Nick Hibma  wrote:

> I created a new kernel config file from scratch, wondered what the
> GEOM_PART_MBR option and friends were doing, search for them, didn't find
> them in the tree, and deleted them from my config. But... de resulting disk
> image didn't boot, because of the fact that it didn't recognise the MBR
> partitions (it only had a single diskid entry on the mount-root prompt).
>
> Can anyone explain to me how these kernel options work, as in: they are
> defined in kernel configs and as a consequence in opt_geom.h, but how are
> they actually used to select which geom_part_* modules/kernel parts to
> build? I thought these options were translated to stuff that cpp would use,
> but there are not uses of for example GEOM_PART_MBR anywhere for example!
>
>
> The module always build them because they are listed in the module's
> Makefile.
>
> The kernel only sometimes does. Here's the key lines from conf/files:
> files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> files:geom/part/g_part_apm.c optional geom_part_apm
> files:geom/part/g_part_bsd.c optional geom_part_bsd
> files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> files:geom/part/g_part_ebr.c optional geom_part_ebr
> files:geom/part/g_part_gpt.c optional geom_part_gpt
> files:geom/part/g_part_ldm.c optional geom_part_ldm
> files:geom/part/g_part_mbr.c optional geom_part_mbr
> files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
>
> which turn on/off which files get included. config "helpfully" converts the
> upper case options to lower case for this.
>
> Warner
>
>
> *slaps forehead* Goose chase!
>
> I actually knew that... and, at the time, thought it was weird behaviour.
> ''grep" would not have failed me if those options would be uppercase there
> ...
>

I've been nibbled to death by these geese often enough to have a PTSD-like
reaction when someone mentions it and habitually add -i to my greps...

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Nick Hibma 
>> I created a new kernel config file from scratch, wondered what the
>> GEOM_PART_MBR option and friends were doing, search for them, didn't find
>> them in the tree, and deleted them from my config. But... de resulting disk
>> image didn't boot, because of the fact that it didn't recognise the MBR
>> partitions (it only had a single diskid entry on the mount-root prompt).
>> 
>> Can anyone explain to me how these kernel options work, as in: they are
>> defined in kernel configs and as a consequence in opt_geom.h, but how are
>> they actually used to select which geom_part_* modules/kernel parts to
>> build? I thought these options were translated to stuff that cpp would use,
>> but there are not uses of for example GEOM_PART_MBR anywhere for example!
>> 
> 
> The module always build them because they are listed in the module's
> Makefile.
> 
> The kernel only sometimes does. Here's the key lines from conf/files:
> files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
> files:geom/part/g_part_apm.c optional geom_part_apm
> files:geom/part/g_part_bsd.c optional geom_part_bsd
> files:geom/part/g_part_bsd64.c optional geom_part_bsd64
> files:geom/part/g_part_ebr.c optional geom_part_ebr
> files:geom/part/g_part_gpt.c optional geom_part_gpt
> files:geom/part/g_part_ldm.c optional geom_part_ldm
> files:geom/part/g_part_mbr.c optional geom_part_mbr
> files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8
> 
> which turn on/off which files get included. config "helpfully" converts the
> upper case options to lower case for this.
> 
> Warner

*slaps forehead* Goose chase!

I actually knew that... and, at the time, thought it was weird behaviour. 
''grep" would not have failed me if those options would be uppercase there ...

Thanks, Warner.

Nick


signature.asc
Description: Message signed with OpenPGP

Re: How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Warner Losh 
On Thu, Sep 28, 2017 at 9:31 AM, Nick Hibma  wrote:

> I created a new kernel config file from scratch, wondered what the
> GEOM_PART_MBR option and friends were doing, search for them, didn't find
> them in the tree, and deleted them from my config. But... de resulting disk
> image didn't boot, because of the fact that it didn't recognise the MBR
> partitions (it only had a single diskid entry on the mount-root prompt).
>
> Can anyone explain to me how these kernel options work, as in: they are
> defined in kernel configs and as a consequence in opt_geom.h, but how are
> they actually used to select which geom_part_* modules/kernel parts to
> build? I thought these options were translated to stuff that cpp would use,
> but there are not uses of for example GEOM_PART_MBR anywhere for example!
>

The module always build them because they are listed in the module's
Makefile.

The kernel only sometimes does. Here's the key lines from conf/files:
files:geom/geom_bsd_enc.c optional geom_bsd | geom_part_bsd
files:geom/part/g_part_apm.c optional geom_part_apm
files:geom/part/g_part_bsd.c optional geom_part_bsd
files:geom/part/g_part_bsd64.c optional geom_part_bsd64
files:geom/part/g_part_ebr.c optional geom_part_ebr
files:geom/part/g_part_gpt.c optional geom_part_gpt
files:geom/part/g_part_ldm.c optional geom_part_ldm
files:geom/part/g_part_mbr.c optional geom_part_mbr
files:geom/part/g_part_vtoc8.c optional geom_part_vtoc8

which turn on/off which files get included. config "helpfully" convers the
upper case options to lower case for this.

Warner

Warner


> The only thing I was able to come up with, but could not figure out, was
> FEATURE() doing some magic.
>
> Thanks in advance for any pointers!
>
> Nick Hibma
> n...@van-laarhoven.org 
>
> -- Open Source: We stand on the shoulders of giants.
>
>
> % grep -r GEOM_PART_ /usr/src/sys/ | grep -Ev '/conf/.*options'
> /usr/src/sys/geom/part/g_part_mbr.c:"GEOM_PART_MBR Master Boot
> Record");
> /usr/src/sys/geom/part/g_part_ldm.c:"GEOM_PART_LDM Logical Disk
> Manager");
> /usr/src/sys/geom/part/g_part_ldm.c: * XXX: We use some knowledge
> about GEOM_PART_GPT internal
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
> /usr/src/sys/geom/part/g_part.h:#ifndef _GEOM_PART_H_
> /usr/src/sys/geom/part/g_part.h:#define _GEOM_PART_H_
> /usr/src/sys/geom/part/g_part.h:#endif /* !_GEOM_PART_H_ */
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

How do GEOM_PART_* options configure geom_part_* modules??

2017-09-28 Thread Nick Hibma 
I created a new kernel config file from scratch, wondered what the 
GEOM_PART_MBR option and friends were doing, search for them, didn't find them 
in the tree, and deleted them from my config. But... de resulting disk image 
didn't boot, because of the fact that it didn't recognise the MBR partitions 
(it only had a single diskid entry on the mount-root prompt).

Can anyone explain to me how these kernel options work, as in: they are defined 
in kernel configs and as a consequence in opt_geom.h, but how are they actually 
used to select which geom_part_* modules/kernel parts to build? I thought these 
options were translated to stuff that cpp would use, but there are not uses of 
for example GEOM_PART_MBR anywhere for example!

The only thing I was able to come up with, but could not figure out, was 
FEATURE() doing some magic.

Thanks in advance for any pointers!

Nick Hibma
n...@van-laarhoven.org 

-- Open Source: We stand on the shoulders of giants.


% grep -r GEOM_PART_ /usr/src/sys/ | grep -Ev '/conf/.*options'
/usr/src/sys/geom/part/g_part_mbr.c:"GEOM_PART_MBR Master Boot Record");
/usr/src/sys/geom/part/g_part_ldm.c:"GEOM_PART_LDM Logical Disk Manager");
/usr/src/sys/geom/part/g_part_ldm.c: * XXX: We use some knowledge about 
GEOM_PART_GPT internal
/usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
/usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
/usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
/usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
/usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
/usr/src/sys/geom/part/g_part_ebr.c:#if defined(GEOM_PART_EBR_COMPAT)
/usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
/usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
/usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
/usr/src/sys/geom/part/g_part_ebr.c:#ifndef GEOM_PART_EBR_COMPAT
/usr/src/sys/geom/part/g_part.h:#ifndef _GEOM_PART_H_
/usr/src/sys/geom/part/g_part.h:#define _GEOM_PART_H_
/usr/src/sys/geom/part/g_part.h:#endif /* !_GEOM_PART_H_ */


signature.asc
Description: Message signed with OpenPGP