paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 5ab9a875098f8011b9d094f1154756aea2349223
parent 5a5cbc33706fb3deb0328e195ae5ffb96ec0956a
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Sun, 10 May 2020 11:10:29 -0400

Publish new blog post

Diffstat:
Mpages/blog.md | 1+
Apages/blog/submitting-a-bug-report-to-freebsd.md | 55+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpages/home.md | 4++--
Mpublic/feeds/sitewide-feed.xml | 55+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpublic/sitemap.xml | 1+
5 files changed, 114 insertions(+), 2 deletions(-)

diff --git a/pages/blog.md b/pages/blog.md @@ -20,6 +20,7 @@ href="https://social.paritybit.ca/@jbauer">Mastodon</a>. ### 2020 <ul> + <li>2020-05-09 <a href="blog/submitting-a-bug-report-to-freebsd">Submitting a Bug Report to FreeBSD</a></li> <li>2020-05-08 <a href="blog/cat-v-considered-harmful">Cat -v Considered Harmful</a></li> <li>2020-05-07 <a href="blog/unsure-what-to-write">Unsure What To Write</a></li> <li>2020-05-07 <a href="blog/the-joys-of-old-tech">The Joys of Old Tech</a></li> diff --git a/pages/blog/submitting-a-bug-report-to-freebsd.md b/pages/blog/submitting-a-bug-report-to-freebsd.md @@ -0,0 +1,55 @@ +## Submitting a Bug Report to FreeBSD + +[//]: # "In which I detail my experience reporting a bug in FreeBSD." + +[//]: # "main.min.css" + +[//]: # + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-05-09 | + <b>Last Updated:</b> 2020-05-09 +</div> + +Today I installed and started using a FreeBSD system for the first time. I had +previously run through the installation and played around with it in a virtual +machine, but this time the plan is to keep it on the system for at least a +little while. + +On every system I own, I install either Vim or NeoVim depending on what is +available. On FreeBSD, when I went to `pkg install vim`, it reported that it +would use an extra 709MiB of space and would pull in a bunch of X and wayland +libraries! I then checked `pkg install neovim` and it reported that it would +only use an extra 29MiB of space. Being the FreeBSD newb that I am, I went ahead +and installed the `neovim` package and then [posted about my experience on +Mastodon](https://social.paritybit.ca/web/statuses/104139315294826147). + +Within a couple hours, it was pointed out to me that there is actually a +`vim-console` package which doesn't include the graphical libraries and is +packaged specifically for use in the console only. In hindsight, this makes +perfect sense, but coming from Linux where Vim is usually packaged as `vim` for +the console version and `vim-gtk` for the graphical version, this didn't even +cross my mind. Especially since neovim behaved as I expected it to. + +After some further discussion, it was suggested by @Evilham that I submit a bug +report about the difference in naming convention between the `vim` and `neovim` +packages. I thought this was a great idea and is exactly the right thing to do +when an issue such as this is identified. I created my account on +[bugs.freebsd.org](https://bugs.freebsd.org/bugzilla/) and [reported the +bug](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246343). + +It was, overall, a really painless process. Many people dislike when they have +to create an account for each project just to report bugs but, with a password +manager like KeepassXC, it's really easy to create and then store a lot of these +accounts. Reporting the bug was also super intuitive with the quick links +available on the front page of their Bugzilla instance. Plus, the suggestion +from @Evilham of what to write made me more confident that I was giving a +quality bug report. + +Will this be the start of my becoming a FreeBSD contributor? + +_This is my fifteenth post for the +[#100DaysToOffload](https://social.paritybit.ca/tags/100DaysToOffload) +challenge. You can learn more about this challenge over at +[https://100daystooffload.com](https://100daystooffload.com)._ diff --git a/pages/home.md b/pages/home.md @@ -17,6 +17,8 @@ rel="me" href="https://social.paritybit.ca/@jbauer">on Mastodon</a>. src="/img/feed-icon.png" width="15" height="15" alt="Click for RSS Feed"/> </a> </div> +2020-05-09 <a class="feed-item" href="blog/submitting-a-bug-report-to-freebsd">Submitting a Bug Report to FreeBSD</a> + 2020-05-08 <a class="feed-item" href="blog/cat-v-considered-harmful">Cat -v Considered Harmful</a> 2020-05-07 <a class="feed-item" href="blog/unsure-what-to-write">Unsure What To Write</a> @@ -35,8 +37,6 @@ rel="me" href="https://social.paritybit.ca/@jbauer">on Mastodon</a>. 2020-04-30 <a class="feed-item" href="blog/i-got-more-ram">I Got More RAM!</a> -2020-04-29 <a class="feed-item" href="blog/interesting-things-for-today">Some Interesting Things For Today</a> - ### What is a Parity Bit? It is a bit (in the 1's and 0's sense) used in checking for errors in digital diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,61 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>Submitting a Bug Report to FreeBSD</title> + <link>https://www.paritybit.ca/blog/submitting-a-bug-report-to-freebsd</link> + <guid>https://www.paritybit.ca/blog/submitting-a-bug-report-to-freebsd</guid> + <pubDate>Sat, 09 May 2020 22:51:40 -0400</pubDate> +<description><![CDATA[<h2>Submitting a Bug Report to FreeBSD</h2> + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2020-05-09 | + <b>Last Updated:</b> 2020-05-09 +</div> + +<p>Today I installed and started using a FreeBSD system for the first time. I had +previously run through the installation and played around with it in a virtual +machine, but this time the plan is to keep it on the system for at least a +little while.</p> + +<p>On every system I own, I install either Vim or NeoVim depending on what is +available. On FreeBSD, when I went to <code>pkg install vim</code>, it reported that it +would use an extra 709MiB of space and would pull in a bunch of X and wayland +libraries! I then checked <code>pkg install neovim</code> and it reported that it would +only use an extra 29MiB of space. Being the FreeBSD newb that I am, I went ahead +and installed the <code>neovim</code> package and then <a href="https://social.paritybit.ca/web/statuses/104139315294826147">posted about my experience on +Mastodon</a>.</p> + +<p>Within a couple hours, it was pointed out to me that there is actually a +<code>vim-console</code> package which doesn't include the graphical libraries and is +packaged specifically for use in the console only. In hindsight, this makes +perfect sense, but coming from Linux where Vim is usually packaged as <code>vim</code> for +the console version and <code>vim-gtk</code> for the graphical version, this didn't even +cross my mind. Especially since neovim behaved as I expected it to.</p> + +<p>After some further discussion, it was suggested by @Evilham that I submit a bug +report about the difference in naming convention between the <code>vim</code> and <code>neovim</code> +packages. I thought this was a great idea and is exactly the right thing to do +when an issue such as this is identified. I proceeded to creat my account on +<a href="https://bugs.freebsd.org/bugzilla/">bugs.freebsd.org</a> and <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246343">reported the +bug</a>.</p> + +<p>It was, overall, a really painless process. Many people dislike when they have +to create an account for each project just to report bugs but, with a password +manager like KeepassXC, it's really easy to create and then store a lot of these +accounts. Reporting the bug was also super intuitive with the quick links +available on the front page of their Bugzilla instance. Plus, the suggestion +from @Evilham of what to write made me more confident that I was giving a +quality bug report.</p> + +<p>Will this be the start of my becoming a FreeBSD contributor?</p> + +<p><em>This is my fifteenth post for the +<a href="https://social.paritybit.ca/tags/100DaysToOffload">#100DaysToOffload</a> +challenge. You can learn more about this challenge over at +<a href="https://100daystooffload.com">https://100daystooffload.com</a>.</em></p>]]></description> +</item> +<item> <title>Cat -v Considered Harmful</title> <link>https://www.paritybit.ca/blog/cat-v-considered-harmful</link> <guid>https://www.paritybit.ca/blog/cat-v-considered-harmful</guid> diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/submitting-a-bug-report-to-freebsd</loc></url> <url><loc>https://www.paritybit.ca/blog/cat-v-considered-harmful</loc></url> <url><loc>https://www.paritybit.ca/blog/unsure-what-to-write</loc></url> <url><loc>https://www.paritybit.ca/blog/the-joys-of-old-tech</loc></url>