Page MenuHomeFreeBSD

lang/rust*: Advise users to mount procfs
ClosedPublic

Authored by asomers on Feb 28 2017, 5:26 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 6 2024, 12:46 PM
Unknown Object (File)
Feb 8 2024, 2:11 PM
Unknown Object (File)
Feb 5 2024, 2:32 PM
Unknown Object (File)
Jan 15 2024, 1:07 PM
Unknown Object (File)
Dec 30 2023, 4:48 PM
Unknown Object (File)
Dec 20 2023, 1:36 AM
Unknown Object (File)
Nov 20 2023, 3:39 AM
Unknown Object (File)
Nov 20 2023, 2:58 AM
Subscribers

Details

Summary

lang/rust*: Advise users to mount procfs

Add a pkg-message to these ports advising users to mount procfs to see
backtraces.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

asomers retitled this revision from to lang/rust*: Advise users to mount procfs.
asomers updated this object.
asomers edited the test plan for this revision. (Show Details)
asomers added reviewers: riggs, dumbbell.
lang/rust-nightly/pkg-message
3 ↗(On Diff #25804)

Please use "Rust" (with a capital 'R'), that's what we use eslewhere in the ports.

Also, perhaps that sentence and the next should be merged in a single paragraph so it's shorter.

lang/rust/pkg-message
13 ↗(On Diff #25804)

Can we point the port to lang/rust/pkg-message instead of duplicating the file? Or perhaps it's not recommended to do that?

lang/rust-nightly/pkg-message
4 ↗(On Diff #25804)

I'd keep this as short as possible, we don't need to repeat procfs(5).
Why not simply something like:

Debugging Rust programs and printing backtraces requires procfs(5) mounted on /proc,
see "man 5 procfs".

lang/rust/pkg-message
13 ↗(On Diff #25804)

That's fine. We don't need duplication as long as the content applies to both ports.

share pkg-message file between both ports, and capitalize Rust

Why not add support for KERN_PROC_PATHNAME to libbacktrace? The sysctl is available on FreeBSD, DragonFly and NetBSD.

Why not add support for KERN_PROC_PATHNAME to libbacktrace? The sysctl is available on FreeBSD, DragonFly and NetBSD.

That would be a good thing to do. But it would be at least several more Rust versions before it would be available. So in the meantime, we should still make this change to the ports tree.

lang/rust-nightly/pkg-message
4 ↗(On Diff #25804)

I for one think it's convenient when a pkg-message shows me exactly what I need to copy and paste. I pretty much do that on every new machine I install right after I "pkg install bash".

lang/rust/pkg-message
13 ↗(On Diff #25804)

Yes, I can and will. I'll upload it as soon as Poudriere finishes.

I agree with @asomers regarding the explicit commands in pkg-message. Yes, it is something the user could learn from the manpages, but it makes it very straightforward and quick to finish the setup. Personnaly, I find that commands stand out in all pkg-messages displayed at the end of a pkg install and it has a better chance of getting my attention.

lang/rust/pkg-message
3 ↗(On Diff #25821)

I would finish this sentence with a '.' too.

10 ↗(On Diff #25821)

That's really minor but you could use the same name for the procfs "device" on the command line and the fstab line (proc vs. procfs currently).

asomers edited edge metadata.

s/procfs/proc

dumbbell edited edge metadata.

Thank you!

This revision is now accepted and ready to land.Mar 1 2017, 11:24 PM
This revision was automatically updated to reflect the committed changes.