[Bug 204674] [PATCH] boot1.efi remove consolecontrol as it's not in the UEFI specs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674 Bug ID: 204674 Summary: [PATCH] boot1.efi remove consolecontrol as it's not in the UEFI specs Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: m...@bidouilliste.com Keywords: patch Created attachment 163324 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163324&action=edit boot1.efi remove ConsoleControl Hello, The ConsoleControl->SetMode in boot1.efi breaks booting freebsd correctly on my machines (HP 840G1 and HP 840G2). The console during boot1.efi and loader.efi isn't setup correctly, neither is the framebuffer which means when kernel starts, display is garbage. After some research I've found that ConsoleControl isn't part of the UEFI specs but was only on the EDK implementation (there is a bug on grub about this). I suspect that HP firmware incorrectly implement it. i.e.: The LocateProtocol works but the SetMode screw things up. With this patch I can correctly boot FreeBSD on my HP 840 machines and also on my Samsung 870Z. Cheers, -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204676] pw groupshow 0 does not work and gives unknown group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204676
Bug ID: 204676
Summary: pw groupshow 0 does not work and gives unknown group
Product: Base System
Version: 10.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: bin
Assignee: freebsd-bugs@FreeBSD.org
Reporter: longw...@incore.de
On FreeBSD 10.2-STABLE #0 r287473 the command 'pw groupshow 0' gives 'pw:
unknown group `0' instead of 'wheel:*:0:root'. The reason for this is an
uninitialized variable in pw_group.c.
The following patch solves this problem for me:
--- usr/src/usr.sbin/pw/pw_group.c.orig 2015-09-05 21:22:44.0 +0200
+++ usr/src/usr.sbin/pw/pw_group.c 2015-11-19 12:00:04.23391 +0100
@@ -296,6 +296,7 @@
NULL
};
+ name = NULL;
if (arg1 != NULL) {
if (arg1[strspn(arg1, "0123456789")] == '\0')
id = pw_checkid(arg1, GID_MAX);
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204651] ls --libxo html -l crashes in xo_format_string_direct() after r285734
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204651 Jan Beich changed: What|Removed |Added Summary|ls --libxo html -l crashes |ls --libxo html -l crashes |in |in |xo_format_string_direct() |xo_format_string_direct() ||after r285734 Keywords||regression CC||allanj...@freebsd.org --- Comment #1 from Jan Beich --- The version before base r285734 doesn't crash. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204679] imposible instalar HP Proliant DL120 gen9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204679 Bug ID: 204679 Summary: imposible instalar HP Proliant DL120 gen9 Product: Base System Version: 10.0-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ven...@sistemas1.com.ar Created attachment 163331 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163331&action=edit error en HP Proliant Al intentar instalar en un servidor HP Proliant DL120 Gen9 E5 2603 V3 LFF el sistema se bloquea y no se instala Adjunto Imagen -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204676] pw groupshow 0 does not work and gives unknown group
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204676 Mark Linimon changed: What|Removed |Added CC||b...@freebsd.org Keywords||patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 Mark Linimon changed: What|Removed |Added Keywords||patch -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204643] [msdosfs] [panic] Crash while accessing files with large, non-english names
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204643 Mark Linimon changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1418 ||97 Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204674] [PATCH] boot1.efi remove consolecontrol as it's not in the UEFI specs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from Ed Maste --- Thank you for your contribution! Unfortunately just removing the SetMode is no good, because with other UEFI implementations the display is not set up correctly for us at boot and the loader output does not work w/o it. As you point out we should handle the case that ConsoleControl is not implemented (we just skip the SetMode if LocateProtocol fails), so this suggests that the failing systems here implement a broken ConsoleControl. It looks like we may need a blacklist of broken systems (or a whitelist of systems that implement & require ConsoleControl). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204674] [PATCH] boot1.efi remove consolecontrol as it's not in the UEFI specs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674 Ed Maste changed: What|Removed |Added Status|New |Open Keywords||uefi -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204674] [PATCH] boot1.efi remove consolecontrol as it's not in the UEFI specs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674 --- Comment #2 from Emmanuel Vadot --- Hi, I've noticed that after. I've sent a mail to hacker@ (https://lists.freebsd.org/pipermail/freebsd-hackers/2015-November/048639.html). As said on my second mail, removing the mode selection and the reset of the conout resolves the problem. I had another idea of what could be wrong, it could be that setting the mode to text strictly disable the graphical mode so I tested to set the mode to graphical just before calling ExitBootService but this doesn't change anything. Maybe we can just remove the reset/mode change ? The console is cleared after and since the number of lines are hardcoded to 24 by default maybe it's sane to leave the text mode to 80x25 for now ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204684] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204684 Bug ID: 204684 Summary: panic: mp_setmaxid: one CPU but mp_maxid is not zero Product: Base System Version: 11.0-CURRENT Hardware: sparc64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: tr...@freebsd.org Trying to boot 11-CURRENT on Sun Blade 2000 (which for some reason reports as SUNW,Sun-Blade-1000), 2 x UltraSPARC-III+, results in the following panic: panic: mp_setmaxid: one CPU but mp_maxid is not zero FreeBSD 10.1-RELASE works with no problems. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204685] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204685 Bug ID: 204685 Summary: panic: mp_setmaxid: one CPU but mp_maxid is not zero Product: Base System Version: 11.0-CURRENT Hardware: sparc64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: tr...@freebsd.org Trying to boot 11-CURRENT on Sun Blade 2000 (which for some reason reports as SUNW,Sun-Blade-1000), 2 x UltraSPARC-III+, results in the following panic: panic: mp_setmaxid: one CPU but mp_maxid is not zero FreeBSD 10.1-RELASE works with no problems. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204684] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204684 Edward Tomasz Napierala changed: What|Removed |Added Status|New |Closed Resolution|--- |DUPLICATE --- Comment #1 from Edward Tomasz Napierala --- *** This bug has been marked as a duplicate of bug 204685 *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204685] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204685 --- Comment #2 from Edward Tomasz Napierala --- Works fine on 10-STABLE too. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204685] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204685 --- Comment #1 from Edward Tomasz Napierala --- *** Bug 204684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204686] panic: critical_exit: td_critnest == 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204686 Andrew Turner changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|and...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204686] panic: critical_exit: td_critnest == 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204686 Bug ID: 204686 Summary: panic: critical_exit: td_critnest == 0 Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: and...@freebsd.org Related to pmc, was running "pmcstat -S INST_RETIRED -O sample.out" while ld was running. root@cavium:~ # hwpmc: SOFT/16/64/0x67 ARMV8/6/32/0x1ff panic: critical_exit: td_critnest == 0 cpuid = 15 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc = 0xff80004d6434 lr = 0xff86d888 sp = 0xff87cc0c4590 fp = 0xff87cc0c46b0 db_trace_self_wrapper() at vpanic+0x170 pc = 0xff86d888 lr = 0xff800025ad54 sp = 0xff87cc0c46c0 fp = 0xff87cc0c4740 vpanic() at kassert_panic+0x160 pc = 0xff800025ad54 lr = 0xff800025abe0 sp = 0xff87cc0c4750 fp = 0xff87cc0c4810 kassert_panic() at critical_exit+0xc8 pc = 0xff800025abe0 lr = 0xff8000261510 sp = 0xff87cc0c4820 fp = 0xff87cc0c4830 critical_exit() at spinlock_exit+0x10 pc = 0xff8000261510 lr = 0xff80004ddf10 sp = 0xff87cc0c4840 fp = 0xff87cc0c4850 spinlock_exit() at pmc_select_cpu+0x80 pc = 0xff80004ddf10 lr = 0xff8047a5ba0c sp = 0xff87cc0c4860 fp = 0xff87cc0c4870 pmc_select_cpu() at pmc_syscall_handler+0x15f8 pc = 0xff8047a5ba0c lr = 0xff8047a5f824 sp = 0xff87cc0c4880 fp = 0xff87cc0c49e0 pmc_syscall_handler() at do_el0_sync+0x478 pc = 0xff8047a5f824 lr = 0xff80004e7e5c sp = 0xff87cc0c49f0 fp = 0xff87cc0c4aa0 do_el0_sync() at handle_el0_sync+0x58 pc = 0xff80004e7e5c lr = 0xff80004d79d4 sp = 0xff87cc0c4ab0 fp = 0x007ff500 KDB: enter: panic [ thread pid 8261 tid 100471 ] Stopped at kdb_enter+0x40: db> -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204340] [panic] nfsd, em, msix, fatal trap 9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204340 --- Comment #11 from g_amana...@yahoo.com --- I am currently testing with the three last patches applied as I do have NFSv4.1 clients running on Linux. Give me a couple of days and I will provide feedback. Thank you for the insight. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204688] out of swap space due to intensive disk IO
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204688 Bug ID: 204688 Summary: out of swap space due to intensive disk IO Product: Base System Version: 10.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: b...@zurbagan.org Created attachment 163344 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163344&action=edit dmesg.boot + vmstat of testted systems Intensive disk IO leads to "out of swap space" at system without configured swap. Test system: 8Gb RAM, i7 CPU, 500G SSD (dmesg boot, vmstat outputs attached), NO SWAP, UFS filesystems (softupdates+trim flags enabled), fdisk+disklabel partitionig amd64 10.2-STABLE r290985M userland+kernel amd64 10.2 release kernel compiled from sources 10.2-STABLE r290985M userland + 10.2-STABLE r290985M userland How to reproduce: 1. Prepare files with total size more than RAM for i in `jot 16 101` do bs=1m count=1024 if=/dev/zero of=file_$i.bin done ls -la *bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:21 file_101.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_102.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_103.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_104.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_105.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_106.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_107.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_108.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_109.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_110.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_111.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_112.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_113.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_114.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_115.bin -rw-r--r-- 1 bag bag 1073741824 Nov 19 21:22 file_116.bin 2. Reboot to test system then run test script for i in file*.bin do dd bs=1m if=$i of=/dev/null done 3 amd64 10.2 release kernel: no problems 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.085321 secs (514904828 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.135202 secs (502876008 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.131729 secs (503695301 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.137902 secs (502240895 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.136251 secs (502629063 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.137830 secs (502257866 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.133230 secs (503340867 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.166784 secs (495546357 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.136592 secs (502548858 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.142595 secs (501140812 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.154938 secs (498270406 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.126926 secs (504832726 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.147977 secs (499885132 bytes/sec) 1024+0 records in 1024+0 records out 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.138070 secs (502201411 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.154765 secs (498310432 bytes/sec) 4 Reboot to amd64 10.2-STABLE r290985M then run test script 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.086252 secs (514675043 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.135337 secs (502844172 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.132365 secs (503545045 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.137970 secs (502224932 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.136101 secs (502664350 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.137171 secs (502412680 bytes/sec) 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 2.133041 secs (503385482 bytes/sec) https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204688] out of swap space due to intensive disk IO
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204688 --- Comment #1 from Andrey Blochintsev --- FreeBSD 11.0-CURRENT #0 r290865M is affected -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204394] usr.bin/tr: ASCII collation passthrough doesn't work on Unicode-aware locales
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204394
Jan Beich changed:
What|Removed |Added
Keywords||regression
Summary|www/firefox: configure: |usr.bin/tr: ASCII collation
|error: |passthrough doesn't work on
|--enable-chrome-format must |Unicode-aware locales
|be set to either jar, flat, |
|or omni |
Flags|maintainer-feedback?(gecko@ |maintainer-feedback+
|FreeBSD.org)|
Assignee|ge...@freebsd.org |freebsd-bugs@FreeBSD.org
Version|Latest |11.0-CURRENT
Product|Ports & Packages|Base System
CC||b...@freebsd.org,
||mar...@freebsd.org
Component|Individual Port(s) |bin
--- Comment #5 from Jan Beich ---
Cutting down configure I've found
# NLS nuisances.
# Only set these to C if already set. These must not be set unconditionally
# because not all systems understand e.g. LANG=C (notably SCO).
# Fixing LC_MESSAGES prevents Solaris sh from translating var values in
`set'!
# Non-C LC_CTYPE values break the ctype check.
if test "${LANG+set}" = set; then LANG=C; export LANG; fi
if test "${LC_ALL+set}" = set; then LC_ALL=C; export LC_ALL; fi
if test "${LC_MESSAGES+set}" = set; then LC_MESSAGES=C; export LC_MESSAGES;
fi
if test "${LC_CTYPE+set}"= set; then LC_CTYPE=C;export LC_CTYPE;
fi
which breaks tr(1) on a mixed locale (LANG unset)
$ env -i LC_COLLATE=en_US.UTF-8 LC_CTYPE=C sh
$ echo FooBar | tr A-Z a-z
aq
$ echo FooBar | tr '[:upper:]' '[:lower:]'
foobar
GNU tr (coreutils) works fine but doesn't support UTF-8 at all.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204394] usr.bin/tr: ASCII collation passthrough doesn't work on Unicode-aware locales
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204394 Baptiste Daroussin changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|b...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204685] panic: mp_setmaxid: one CPU but mp_maxid is not zero
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204685 Mark Linimon changed: What|Removed |Added CC||lini...@freebsd.org, ||mar...@freebsd.org --- Comment #3 from Mark Linimon --- Same on a v245. Per marius I am going to attempt to revert sys/kern/subr_smp.c via: https://svnweb.freebsd.org/base/head/sys/kern/subr_smp.c?r1=285771&r2=290547&pathrev=290547 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
