Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

2016-11-06 Thread Patrick M. Hausen
Hi, all, > Am 06.11.2016 um 18:14 schrieb Dimitry Andric : > > Please do, so it is not forgotten. It is relatively easy to change the > volume label, by editing sys/boot/efi/boot1/generate-fat.sh, and then > regenerating the FAT templates. Why use the pre-generated image at

Re: Use of env SRC_ENV_CONF=. . . for buildworld does not override/avoid use of /etc/src.conf : Intentional?

2016-11-06 Thread Mark Millard
[The original of this message was not delivered to two of the places it was sent to. This retries sending to just those places.] On 2016-Nov-4, at 9:40 AM, Bryan Drewery wrote: > On 11/3/2016 5:28 PM, Mark Millard wrote: >> I just had a case of "odd" command text in a buildworld that was based

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Stefan Bethke
Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin : > >> But under what circumstances would [A-Z] mean anything other than a >> character whose Unicode codepoint is between U+0041 and U+005A, inclusive? >> Especially given the locale in the example is en_US.UTF-8. Or, put

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Andriy Gapon
On 06/11/2016 23:30, Stefan Bethke wrote: > Although with en_US.UTF-8 on other systems, I have not had that experience. > A quick check on stuff I have immediate access to: > > macOS 10.12: > $ echo 'abcdABCD' | sed 's/[A-Z]/X/g’ > abcd > > Ubuntu 14.04.5 > $ echo 'abcdABCD' | sed

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Stefan Bethke
> Am 06.11.2016 um 22:14 schrieb Stefan Ehmann : > >> That is rather surprising. Is there a normative reference for the >> treatment of bracket expressions and character classes when using >> locales other than C and/or encodings like UTF-8? > > I found an interesting article

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Baptiste Daroussin
On Sun, Nov 06, 2016 at 10:20:54PM +0100, Stefan Bethke wrote: > > > Am 06.11.2016 um 22:06 schrieb Baptiste Daroussin : > > > > On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote: > >> > >>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin : >

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Stefan Bethke
> Am 06.11.2016 um 22:06 schrieb Baptiste Daroussin : > > On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote: >> >>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin : >>> >>> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote: I

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Stefan Ehmann
On 06.11.2016 21:57, Stefan Bethke wrote: > >> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin >> : >> >> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote: >>> I happened to run an old script today that uses sed(1) to extract >>> the system boot time from the

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Baptiste Daroussin
On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote: > > > Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin : > > > > On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote: > >> I happened to run an old script today that uses sed(1) to extract the > >> system

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Stefan Bethke
> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin : > > On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote: >> I happened to run an old script today that uses sed(1) to extract the system >> boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works as

Re: boot1.efifat's FAT12 volume label prevents booting (some systems)

2016-11-06 Thread Dimitry Andric
On 06 Nov 2016, at 16:07, Harry Schmalzbauer wrote: > > Recently I played with bsdinstall and UEFI setup, which left the system > unbootable (11.0-Release). > The culprit is the MS-DOS volume lable "EFI" of the EFI partition. > At least on Intel Single-Socket Servers

how to download freebsd

2016-11-06 Thread fery rahmat
feryputrasulun...@gmail.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

boot1.efifat's FAT12 volume label prevents booting (some systems)

2016-11-06 Thread Harry Schmalzbauer
Recently I played with bsdinstall and UEFI setup, which left the system unbootable (11.0-Release). The culprit is the MS-DOS volume lable "EFI" of the EFI partition. At least on Intel Single-Socket Servers (for Xeon E3 IvyBridge/BearToot + Haswell/RainbowPass), the UEFI firmware can't

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Baptiste Daroussin
On Sun, Nov 06, 2016 at 01:26:51PM +0100, Mark Martinec wrote: > 2016-11-06 12:07, Baptiste Daroussin wrote: > > Yes A-Z only means uppercase in an ASCII only world in a unicode world > > it means > > AaBb... Z because there are way more characters that simple A-Z. In > > FreeBSD 11 > > we have a

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Mark Martinec
2016-11-06 12:07, Baptiste Daroussin wrote: Yes A-Z only means uppercase in an ASCII only world in a unicode world it means AaBb... Z because there are way more characters that simple A-Z. In FreeBSD 11 we have a unicode collation instead of falling back in on LC_COLLATE=C which means ascii

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-06 Thread Baptiste Daroussin
On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote: > I happened to run an old script today that uses sed(1) to extract the system > boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works as > expected: > > $ sysctl kern.boottime > kern.boottime: { sec = 1478380714,