Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Bug 204977] [PATCH] java/openjdk8: Use late in pkg-message's fstab entries

4 views
Skip to first unread message

bugzilla...@freebsd.org

unread,
Dec 2, 2015, 4:56:30 PM12/2/15
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204977

Bug ID: 204977
Summary: [PATCH] java/openjdk8: Use late in pkg-message's fstab
entries
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Keywords: patch
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ja...@FreeBSD.org
Reporter: t...@tobik.me
Assignee: ja...@FreeBSD.org
Flags: maintainer-feedback?(ja...@FreeBSD.org)
Keywords: patch

Created attachment 163784
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163784&action=edit
openjdk8.diff

The pkg-message for openjdk8 suggests adding two fstab entries. But when using
a separate boot partition (or boot pool with a standard ZFS configuration as
proposed by the installer when using encryption) adding them can lead to the
system booting to single user mode (see
https://forums.freebsd.org/threads/11-current-boots-to-single-user-with-fdescfs-linprocfs-in-fstab.53163/#post-298637).
Either loading fdescfs(5) (and procfs(5) but that is part of GENERIC) from
/boot/loader.conf or adding the late option fixes the problem for those systems
AFAICT (see attached patch).

This also affects the pkg-message of shells/bash.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebs...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-java
To unsubscribe, send any mail to "freebsd-java...@freebsd.org"

bugzilla...@freebsd.org

unread,
Dec 2, 2015, 5:14:41 PM12/2/15
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204977

Jung-uk Kim <jk...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jk...@FreeBSD.org

--- Comment #1 from Jung-uk Kim <jk...@FreeBSD.org> ---
These are almost direct copy-and-paste from fdescfs(5) and procfs(5).

https://www.freebsd.org/cgi/man.cgi?query=fdescfs&manpath=FreeBSD+10.2-RELEASE
https://www.freebsd.org/cgi/man.cgi?query=procfs&manpath=FreeBSD+10.2-RELEASE

I don't see any reason to change the message. :-/

bugzilla...@freebsd.org

unread,
May 18, 2016, 5:30:57 AM5/18/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204977

Andrew Smith <iamasmi...@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |iamasmi...@gmail.com

--- Comment #2 from Andrew Smith <iamasmi...@gmail.com> ---
(In reply to Jung-uk Kim from comment #1)

I'm not sure if you missed the significance of the 'late' flag and the very
good response to the post on the forum.

It sounds like a simple update to the mount option suggestions, either this or
a note about the particular issue experienced by the op on the thread could
save people a lot of fishing around for an answer.

bugzilla...@freebsd.org

unread,
Jul 10, 2016, 11:35:00 AM7/10/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204977

--- Comment #3 from Tobias Kortkamp <t...@tobik.me> ---
(In reply to Andrew Smith from comment #2)
> could save people a lot of fishing around for an answer
Yes, that was the reason for opening this PR.

(In reply to Jung-uk Kim from comment #1)
> These are almost direct copy-and-paste from fdescfs(5) and procfs(5).
So you're saying that fdescfs(5) and procfs(5) need an update too? ;-)

If nobody wants this please reject it and let's close this PR. Don't leave it
hanging around forever. I consider > 6 months too long for stuff like this.
The cost of changing it is so low. It's not like changing a pkg message will
break any functionality.

bugzilla...@freebsd.org

unread,
Jul 24, 2016, 9:17:03 AM7/24/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204977

Tobias Kortkamp <t...@tobik.me> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|New |Closed
Resolution|--- |Works As Intended
0 new messages