Page MenuHomeFreeBSD

Suggest upload of dmesg in login fortune file
ClosedPublic

Authored by bcr on Oct 25 2018, 7:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Oct 13, 9:40 PM
Unknown Object (File)
Sat, Oct 4, 5:36 AM
Unknown Object (File)
Sat, Sep 20, 11:36 PM
Unknown Object (File)
Sat, Sep 20, 1:30 PM
Unknown Object (File)
Sep 11 2025, 11:23 PM
Unknown Object (File)
Sep 7 2025, 4:34 PM
Unknown Object (File)
Aug 19 2025, 1:06 PM
Unknown Object (File)
Aug 15 2025, 3:48 AM

Details

Summary

We should encourage users to upload their dmesg to the NYCBUG database to get a better feel on which hardware FreeBSD is run on. This patch is a first attempt at adding such an entry to the fortune file.
The command I used is the one posted on this thread:
http://lists.nycbug.org:8080/pipermail/talk/2018-October/017729.html

Question: How do we best reference where the data is going (NYCBUG)? Do we add a note that users might upload potentially sensitive information about their systems like serial numbers this way?

Note: I chose not to add a name to the fortune, not all of them have one. I'm also not opposed to adding a name to it. The command did not originate from me, so attribution should go to the proper author.

Suggestions welcome.

Test Plan
  1. Apply the attached patch to head/usr.bin/fortune/datfiles/freebsd-tips
  2. run make in that directory
  3. To view the fortune, run: fortune -m curl freebsd-tips

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

head/usr.bin/fortune/datfiles/freebsd-tips
558

Maybe "the curl package"?

559

Does it make sense to wrap this with backslashes at <80 columns due to the potential for terminal damage?

Update with suggestions from Brooks:

  • use "the curl package"
  • use \ to wrap long lines

ping? I think we can add it and see how it works out regarding the data collection we are trying to do.

I don't think we need email= anymore.

Removed the email= part.

bcr marked 2 inline comments as done.Nov 16 2018, 5:54 PM

Belatedly mark comments as done.

This revision is now accepted and ready to land.Nov 19 2018, 8:31 PM
This revision was automatically updated to reflect the committed changes.