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

2016-11-07 Thread Harry Schmalzbauer
Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime): > 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 >> regene

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

2016-11-07 Thread Patrick M. Hausen
Hi, > Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer : >> create the EFI boot volume like this? >> >> gpart add -t efi -l efi -a 512k -s 512k >> newfs_msdos /dev/gpt/efi >> mount_msdosfs /dev/gpt/efi /mnt >> mkdir -p /mnt/efi/boot >> cp /boot/boot1.efi /mnt/efi/boot/bootx64.efi > > You are m

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

2016-11-07 Thread Harry Schmalzbauer
Bezüglich Harry Schmalzbauer's Nachricht vom 07.11.2016 09:04 (localtime): > Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 08:10 (localtime): >> 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

Re: ath0 associated, wlan0 not associated

2016-11-07 Thread Lars Engels
On Sat, Nov 05, 2016 at 01:00:56PM -0400, George Mitchell wrote: > On 11/05/16 01:05, Adrian Chadd wrote: > > nope, sorry. There's a lot of work in the -11 wifi stack and drivers. > > > > > > -a > > > > [...] > > Okay, I downloaded and installed 11.0-RELEASE on a spare slice, and > dmesg tells

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

2016-11-07 Thread Harry Schmalzbauer
Bezüglich Patrick M. Hausen's Nachricht vom 07.11.2016 09:12 (localtime): > Hi, > >> Am 07.11.2016 um 09:04 schrieb Harry Schmalzbauer : >>> create the EFI boot volume like this? >>> >>> gpart add -t efi -l efi -a 512k -s 512k >>> newfs_msdos /dev/gpt/efi >>> mount_msdosfs /dev/gpt/efi /mnt >>> m

http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

2016-11-07 Thread Mark Millard
It looks like http://pkg.freebsd.org is still back as of head being 11-CURRENT: http://pkg.freebsd.org shows only • freebsd:11:aarch64:64 (as http://pkg.freebsd.org/freebsd%3A11%3Aaarch64%3A64 ). So on 12-CURRENT pkg bootstrapping gets: > # pkg > The package management tool is not yet

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-07 Thread Charles Swiger
On Nov 6, 2016, at 1:49 PM, Stefan Bethke wrote: > Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin : >> That works for POSIX locale aka C aka ASCII only world > > So what do I set my LANG and LC variables to? I do want UTF-8, but I do also > want my scripts to continue to work. Clearly, en_U

Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

2016-11-07 Thread Brad Davis
On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote: > It looks like http://pkg.freebsd.org is still back as of head being > 11-CURRENT: http://pkg.freebsd.org shows only Correct. I wrote up some details on how to use the 11 packages here: http://www.raspbsd.org/raspberrypi.html Rega

Re: Uppercase RE matching problems in FreeBSD 11

2016-11-07 Thread Mark Martinec
2016-11-06 22:49, Stefan Bethke wrote: So what do I set my LANG and LC variables to? I do want UTF-8, but I do also want my scripts to continue to work. Clearly, en_US.UTF-8 is not what I want. Is it C.UTF-8? Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C? Yes, that is the safest bet. The

Re: http://pkg.freebsd.org only has freebsd:11:aarch64:64 for aaarch64? How to boostrap aarch64 pkg for head (12-CURRENT)?

2016-11-07 Thread Mark Millard
On 2016-Nov-7, at 1:16 PM, Brad Davis wrote: > On Mon, Nov 07, 2016 at 12:19:24PM -0800, Mark Millard wrote: >> It looks like http://pkg.freebsd.org is still back as of head being >> 11-CURRENT: http://pkg.freebsd.org shows only > > Correct. I wrote up some details on how to use the 11 package