[Bug 230687] rmuser kill_procs kills processes in jails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230687 Bug ID: 230687 Summary: rmuser kill_procs kills processes in jails Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: si...@ikanobori.jp The usr.sbin/adduser/rmuser.sh script which ends up in /usr/sbin/rmuser when ran from a host system such as `rmuser user` will kill all processes owned by `user` in its kill_procs routine by identifying processes with `ps -U $USER`. This includes jailed processes which is not something to be expected (or is it?). I could submit a patch which would remove processes which have a J flag hidden behind an argument such as --no-jail / -F but don't know if this is desirable. It doesn't seem there are much better options here as we can't get the current JID as far as I'm aware. If that were possible we could add the -J $JID flag to ps. -- 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 230687] rmuser kill_procs kills processes in jails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230687 --- Comment #1 from si...@ikanobori.jp --- Reproduction: - create user user1 on host system - create jail1 with user1 - run process in jail1 as user1 - rmuser user1 on host system - process running in jail1 gets killed Expected: - jailed processes are not the same user as the host system and should not be killed -- 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 230635] [regression] Spam in console after r336593 (NFS mounted)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230635 --- Comment #6 from Colin Percival --- Created attachment 196280 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196280&action=edit Fix? Does this fix the problem? -- 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 229429] FIRST_MSI_INT is too low for large core count systems, panic on boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229429 John Baldwin changed: What|Removed |Added Blocks||228911 CC||j...@freebsd.org --- Comment #1 from John Baldwin --- Add this to the 12.0 list. I have a WIP patch not yet ready for review but that I hope to test shortly. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228911 [Bug 228911] FreeBSD 12.0 Release action items -- 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 229429] FIRST_MSI_INT is too low for large core count systems, panic on boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229429 John Baldwin changed: What|Removed |Added Assignee|b...@freebsd.org|j...@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 230704] All the memory eaten away by ZFS 'solaris' malloc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230704
Bug ID: 230704
Summary: All the memory eaten away by ZFS 'solaris' malloc
Product: Base System
Version: 11.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: mark.marti...@ijs.si
Affected: ZFS on 11.2-RELEASE and 11.1-RELEASE-p11 (but not on 10.3).
Running commands like 'zpool list', 'zpool status' or 'zpool iostat'
on a defunct pool (with broken underlying disks) leaks memory.
When such command runs frequently (like by a monitoring tool
'telegraf'), in a couple of days the system runs out of memory,
applications start swapping and eventually everything grinds
to a standstill, requiring a forced reboot.
In few days, shortly before a freeze, the vmstat -m shows
the 'solaris' malloc approaching the total size of the memory
(prior to that this number was steadily growing linearly):
$ vmstat -m :
Type InUse MemUse HighUse Requests Size(s)
solaris 39359484 2652696K - 234986296 ...
How to repeat:
# create a test pool on md
mdconfig -a -t swap -s 1Gb
gpart create -s gpt /dev/md0
gpart add -t freebsd-zfs -a 4k /dev/md0
zpool create test /dev/md0p1
# destroy the disk underneath the pool, making it "unavailable"
mdconfig -d -u 0 -o force
reboot now (before a reboot the trouble does not start yet)
Now run 'zpool list' periodically, monitoring the growth of
the 'solaris' malloc zone:
(while true; do zpool list >/dev/null; vmstat -m | \
fgrep solaris; sleep 0.5; done) | awk '{print $2-a; a=$2}'
12224540
2509
3121
5022
2507
1834
2508
2505
As suggested by Mark Johnston, here is a dtrace
https://www.ijs.si/usr/mark/tmp/dtrace-cmd.out.bz2
from the following command:
# dtrace -c "zpool list -Hp" -x temporal=off -n '
dtmalloc::solaris:malloc
/pid == $target/{@allocs[stack(), args[3]] = count()}
dtmalloc::solaris:free
/pid == $target/{@frees[stack(), args[3]] = count();}'
This will record all allocations and frees from a single instance
of "zpool list".
Andriy Gapon wrote on the mailing list:
I see one memory leak, not sure if it's the only one.
It looks like vdev_geom_read_config() leaks all parsed vdev nvlist-s but
the last. The problems seems to come from r316760. Before that commit
the function would return upon finding the first valid config, but now
it keeps iterating.
The memory leak should not be a problem when vdev-s are probed
sufficiently rarely, but it appears that with an unhealthy pool the
probing can happen much more frequently (e.g., every time pools are listed).
The whole discussion leading to the above findings is on
the sta...@freebsd.org mailing list, 2018-07-23 to 2018-08-14,
subject:
"All the memory eaten away by ZFS 'solaris' malloc - on 11.1-R amd64"
--
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 228669] CLOCK_PROCESS_CPUTIME_ID is unnecessarily inaccurate
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228669 Colin Percival changed: What|Removed |Added Resolution|--- |FIXED Status|New |Closed -- 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 183787] ping6(8) has no -t option, ping does have this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183787 Mike Appleby changed: What|Removed |Added CC||m...@app.leby.org --- Comment #2 from Mike Appleby --- I think that this PR can be closed. A timeout option (-X) was added to ping6(8) in base r273211. That change is in -current and stable/11, and was merged into stable/10 in base r285820. The patch was submitted as part of bug #151023. Here is an example shell session from a 12.0-ALPHA1 snapshot: $ uname -a FreeBSD fbsd-current 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #0 r337557: Fri Aug 10 02:02:48 UTC 2018 r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 $ time ping6 -X 1 fe80::1%lo0 PING6(56=40+8+8 bytes) fe80::1%lo0 --> fe80::1%lo0 16 bytes from fe80::1%lo0, icmp_seq=0 hlim=64 time=0.140 ms --- fe80::1%lo0 ping6 statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.140/0.140/0.140/0.000 ms real0m1.025s user0m0.001s sys 0m0.004s -- 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 230704] All the memory eaten away by ZFS 'solaris' malloc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230704 Mark Linimon changed: What|Removed |Added Keywords||regression Assignee|b...@freebsd.org|f...@freebsd.org --- Comment #1 from Mark Linimon --- Apparently a regression in ZFS vs. 10.x. -- 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 183787] ping6(8) has no -t option, ping does have this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183787 Mark Linimon changed: What|Removed |Added Resolution|--- |Overcome By Events Assignee|b...@freebsd.org|lini...@freebsd.org Status|Open|Closed -- 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 230715] sockstat does not aligns columns
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230715 Bug ID: 230715 Summary: sockstat does not aligns columns Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl Current output: # sockstat -l4 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS syncthing syncthing 4875 9 tcp4 10.0.0.100:22000 *:* syncthing syncthing 4875 10 udp4 10.0.0.100:20347 *:* syncthing syncthing 4875 11 udp4 10.0.0.100:21027 *:* syncthing syncthing 4875 15 tcp4 10.0.0.100:8384 *:* syncthing syncthing 4875 18 udp4 10.0.0.100:21820 *:* syncthing syncthing 4875 19 udp4 10.0.0.100:16107 *:* root sendmail 96174 3 tcp4 10.0.0.100:25 *:* root syslogd56080 6 udp4 10.0.0.100:514*:* How it should be: # sockstat -l4 USER COMMAND PID FD PROTO LOCAL ADDRESSFOREIGN ADDRESS syncthing syncthing 4875 9 tcp4 10.0.0.100:22000 *:* syncthing syncthing 4875 10 udp4 10.0.0.100:20347 *:* syncthing syncthing 4875 11 udp4 10.0.0.100:21027 *:* syncthing syncthing 4875 15 tcp4 10.0.0.100:8384 *:* syncthing syncthing 4875 18 udp4 10.0.0.100:21820 *:* syncthing syncthing 4875 19 udp4 10.0.0.100:16107 *:* root sendmail 96174 3 tcp4 10.0.0.100:25*:* root syslogd 56080 6 udp4 10.0.0.100:514 *:* -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 Bug ID: 230716 Summary: ls: compact columnts layout Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl How FreeBSD's ls(1) behaves: % ls bin/ etc/ mnt/ root/ usr/ boot/ lib/ net/ sbin/ var/ COPYRIGHT libexec/ proc/ sys dev/ media/ rescue/tmp/ How it should (GNU ls): % gls bin/ etc/ media/ proc/sbin/ var/ boot/ lib/ mnt/rescue/ tmp/ COPYRIGHT dev/ libexec/ net/root/usr/ sys -- 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 230717] ls: add option to group directories first
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230717 Bug ID: 230717 Summary: ls: add option to group directories first Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: verma...@interia.pl The GNU ls has --group-directories-first option which FreeBSD's ls(1) lacks. % gls bin COPYRIGHT etc libexec mnt procroot sys usr boot devlib medianet rescue sbin tmp var % gls --group-directories-first bin dev lib media net rescue sbin usr COPYRIGHT boot etc libexec mntproc roottmp var sys -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 --- Comment #1 from Mark Linimon --- Please, for heaven's sake, no. Please do not turn us into Linux. -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org --- Comment #2 from Conrad Meyer --- We separate columns with tabs rather than minimal spaces. Not sure it matters one way or the other. I don't understand why Mark has a strong opinion about it, but I also see no reason for the change. -- 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 230717] ls: add option to group directories first
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230717 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org --- Comment #1 from Conrad Meyer --- Is this option commonly used on Linux? Is it very helpful for anything? -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 --- Comment #3 from Mark Linimon --- (In reply to Conrad Meyer from comment #2) The sort order. Please, no. If people really want this let's get a gls port going. -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 --- Comment #5 from Conrad Meyer --- (In reply to Conrad Meyer from comment #4) s/affect/effect/, oops -- 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 230716] ls: compact columnts layout
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230716 --- Comment #4 from Conrad Meyer --- (In reply to Mark Linimon from comment #3) Hm, sort order looks more like a directory-first affect (see reporter's next PR) than a column width thing. We've got a gls port — it's part of "coreutils." -- 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 230720] strptime() conversion and validation issues
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230720 Bug ID: 230720 Summary: strptime() conversion and validation issues Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: rlit...@inetco.com Created attachment 196301 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196301&action=edit Patch file for strptime.c I've been running the FreeBSD strptime() function through a few tests and a few of things came up. 1) Some compile warnings were silenced by changing the type of len from int to size_t. Also some compiler-reported possibly uninitialized use, which I don't think are really bugs but best to be safe. 2) %k and %l should allow preceding blanks. The current version requires all digits and throws an error. I have put in a little fix to permit this. 3) %I and %l should generate an error on 0. A small check added for that. 4) %d should generate an error on 0. A small check added for that. Patch attached. -- 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 230720] strptime() conversion and validation issues
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230720 Mark Linimon changed: What|Removed |Added 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 230722] [nvme][resume] Delay and possible deadlock after resume
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230722 Bug ID: 230722 Summary: [nvme][resume] Delay and possible deadlock after resume Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: go...@freebsd.org CC: i...@freebsd.org, jimhar...@freebsd.org When resuming from S3 sleep any disk activity stops for around 30 seconds and kernel prints a bunch of error messages from NVME. Eventually, the system resumes normal operations. I also saw this scenario resulting in deadlock although can't reproduce it reliably anymore. Error messages printed by the kernel: nvme0: Resetting controller due to a timeout. nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: READ sqid:1 cid:111 nsid:1 lba:98381272 len:8 nvme0: ABORTED - BY REQUEST (00/07) sqid:1 cid:111 cdw0:0 nvme0: aborting outstanding i/o nvme0: READ sqid:1 cid:124 nsid:1 lba:626180072 len:8 nvme0: ABORTED - BY REQUEST (00/07) sqid:1 cid:124 cdw0:0 nvme0: aborting outstanding i/o nvme0: READ sqid:2 cid:121 nsid:1 lba:617174512 len:40 nvme0: ABORTED - BY REQUEST (00/07) sqid:2 cid:121 cdw0:0 nvme0: aborting outstanding i/o nvme0: DATASET MANAGEMENT sqid:4 cid:94 nsid:1 nvme0: ABORTED - BY REQUEST (00/07) sqid:4 cid:94 cdw0:0 nvme0: aborting outstanding i/o nvme0: WRITE sqid:4 cid:93 nsid:1 lba:46557808 len:16 nvme0: ABORTED - BY REQUEST (00/07) sqid:4 cid:93 cdw0:0 nvme0: Missing interrupt Controller information: Controller Capabilities/Features Vendor ID: 17aa Subsystem Vendor ID: 17aa Serial Number: 1150592304774 Model Number:LENSE20512GMSP34MEAT2TA Firmware Version:1.9.8341 Recommended Arb Burst: 2 IEEE OUI Identifier: 99 32 a0 Multi-Path I/O Capabilities: Not Supported Max Data Transfer Size: 131072 Controller ID: 0x01 Version: 0.0.0 Admin Command Set Attributes Security Send/Receive: Supported Format NVM: Supported Firmware Activate/Download: Supported Namespace Managment: Not Supported Device Self-test:Not Supported Directives: Not Supported NVMe-MI Send/Receive:Not Supported Virtualization Management: Not Supported Doorbell Buffer Config Not Supported Abort Command Limit: 4 Async Event Request Limit: 4 Number of Firmware Slots:1 Firmware Slot 1 Read-Only: No Per-Namespace SMART Log: No Error Log Page Entries: 4 Number of Power States: 5 NVM Command Set Attributes == Submission Queue Entry Size Max: 64 Min: 64 Completion Queue Entry Size Max: 16 Min: 16 Number of Namespaces:1 Compare Command: Not Supported Write Uncorrectable Command: Supported Dataset Management Command: Supported Write Zeroes Command:Not Supported Save Features: Supported Reservations:Not Supported Timestamp feature: Not Supported Fused Operation Support: Not Supported Format NVM Attributes: Crypto Erase, Per-NS Erase, Per-NS Format Volatile Write Cache:Present -- 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 95222] [cd9660] File sections on ISO9660 level 3 CDs ignored
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=95222 --- Comment #3 from Masachika ISHIZUKA --- mount_udf can mount iso9660 level 3 BD-R DL correctly. P.S. Although I want to write /etc/fstab, I can't specify charset in fstab. -- 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 95222] [cd9660] File sections on ISO9660 level 3 CDs ignored
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=95222 --- Comment #4 from Masachika ISHIZUKA --- (In reply to Masachika ISHIZUKA from comment #3) Sorry, I can specify charset in fstab as follows. /dev/cd0 /cdromudf ro,noauto,-C=UTF-8 0 0 -- 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 95222] [cd9660] File sections on ISO9660 level 3 CDs ignored
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=95222 Conrad Meyer changed: What|Removed |Added Status|Open|Closed Resolution|--- |Overcome By Events --- Comment #5 from Conrad Meyer --- There doesn't seem to be any obvious need for multi-extent 700 MB CD images, given cd9660 can reference 2^32-1 bytes (~4GB) in a single extent and the volume is limited by physical media to 700 MB. Meanwhile, DVD and larger media have UDF. I think we can close this, although it would be nice if documentation and/or automated detection were better. (Workaround: Use udf filesystem instead of cd9660.) Thanks Masachika ISHIZUKA for investigation. -- 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 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 Bug ID: 230725 Summary: [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: dmitry.wa...@ya.ru Created attachment 196309 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196309&action=edit +OLD_FILES+=usr/bin/kcc -- 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 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 Dmitry Wagin changed: What|Removed |Added Keywords||easy, install, patch, ||patch-ready -- 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 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 Dmitry Wagin changed: What|Removed |Added Attachment #196309|0 |1 is obsolete|| --- Comment #1 from Dmitry Wagin --- Created attachment 196310 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196310&action=edit patch-OptionalObsoleteFiles.inc -- 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 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 Dmitry Wagin changed: What|Removed |Added Attachment #196310|0 |1 is obsolete|| --- Comment #2 from Dmitry Wagin --- Created attachment 196311 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196311&action=edit patch-OptionalObsoleteFiles.inc -- 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 230727] [patch] NIS file missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230727 Bug ID: 230727 Summary: [patch] NIS file missing in tools/build/mk/OptionalObsoleteFiles.inc Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: dmitry.wa...@ya.ru Created attachment 196312 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196312&action=edit patch-OptionalObsoleteFiles.inc -- 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 230727] [patch] NIS file missing in tools/build/mk/OptionalObsoleteFiles.inc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230727 Dmitry Wagin changed: What|Removed |Added Keywords||easy, install, patch, ||patch-ready -- 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"
