1
0
This commit is contained in:
dtb 2022-05-20 19:34:34 -04:00
parent 9242512a16
commit 034799c033
3 changed files with 46 additions and 84 deletions

View File

@ -84,9 +84,7 @@ I'm vaccinated against COVID-19. Are you?
<A HREF="thegame" >/thegame</A>; <A HREF="thegame" >/thegame</A>;
<B>knowledge</B>: <B>knowledge</B>:
<A HREF="knowledge/cat/" >cat(1)</A>, <A HREF="knowledge/cat/" >cat(1)</A>,
<A HREF="knowledge/cryptography">cryptography</A>, <A HREF="knowledge/software">software</A>,
<A HREF="knowledge/linux" >linux</A>,
<A HREF="knowledge/netbsd/" >NetBSD</A>,
<A HREF="knowledge/true" >true(1)</A>, <A HREF="knowledge/true" >true(1)</A>,
<A HREF="knowledge/x200t" >X200T</A>; <A HREF="knowledge/x200t" >X200T</A>;
<B>shilling</B>: <B>shilling</B>:

View File

@ -1,74 +0,0 @@
<!DOCTYPE html>
<HTML LANG="en">
<HEAD>
<LINK HREF="http://www.trinity.moe/FILL_IN" REL="canonical" />
<LINK HREF="https://raw.githubusercontent.com/devenblake/homepage/main/favicon.ico" REL="shortcut icon" TYPE="image/x-icon" />
<LINK HREF="/css/blank.css" ID="styling" REL="stylesheet" />
<META CHARSET="UTF-8" />
<META CONTENT="noindex" NAME="googlebot" /> <!-- FUCK GOOGLE -->
<META CONTENT="interest-cohort=()" HTTP-EQUIV="Permissions-Policy" /> <!-- FUCK GOOGLE -->
<META NAME="viewport" CONTENT="width=device-width, initial-scale=1" />
<TITLE>knowledge/NetBSD</TITLE>
</HEAD>
<BODY>
<P><A HREF="/">~ Return to the rest of the site</A></P>
<SCRIPT SRC="/js/cookies.js" TYPE="application/javascript"></SCRIPT>
<SCRIPT SRC="/js/sheets.js" TYPE="application/javascript"></SCRIPT>
<SCRIPT TYPE="application/javascript">window.onload = window.initializesheets;</SCRIPT>
<H1>NetBSD</H1>
<H3>updated 2021-07-23</H3>
<HR ALIGN="left" SIZE="1" WIDTH="25%" />
<P>
From <A HREF="http://netbsd.org/">netbsd.org</A>: <I>NetBSD is a free, fast, secure, and highly portable Unix-like Open Source operating system</I>.
Of course, I run NetBSD, and this page serves as documentation of weird error fixes and miscellaneous tutorials that I think can be helpful.
</P>
<P>
Before diving into NetBSD you should really read the bits that look interesting of <A HREF="https://www.netbsd.org/docs/guide/en/">the NetBSD Guide</A> and (if you intend to use it) all of <A HREF="https://www.netbsd.org/docs/pkgsrc/">the pkgsrc guide</A>.
They're well written and detailed guides to NetBSD and the package manager typically used with NetBSD, and for the sake of you and anyone who finds your forum questions you should always consult them first if you have any questions.
</P>
<P>
Also, thank you to all the forum posters and chatroom hackers that help with my frequent n00b questions (see sources on each section).
If you like this page please consider donating to the <A HREF="http://netbsd.org/">NetBSD Foundation</A> using the hyperlinks on their website.
</P>
<H2>Fix <CODE>SSL certificate problem: unable to get local issuer certificate</CODE></H2>
<P>Install <CODE>security/mozilla-rootcerts-openssl</CODE>.</P>
<P>Sources:</P>
<UL>
<LI><A HREF="https://www.cambus.net/installing-ca-certificates-on-netbsd/">Frederic Cambus</A></LI>
<LI><A HREF="https://github.com/ohmyzsh/ohmyzsh/issues/8321#issuecomment-863493503">ohmyzsh/ohmyzsh#8321</A></LI>
</UL>
<P>
<I>Do not</I> use SSL workarounds like (in the case of git) <CODE>GIT_SSL_NO_VERIFY</CODE>.
These leave your system open to man-in-the-middle attacks.
</P>
<P>Related: <A HREF="http://mail-index.netbsd.org/pkgsrc-users/2021/07/19/msg034147.html">Depending on security/ca-certificates?</A></P>
<H2>Mounting ext4 partitions with FUSE</H2>
<P>
I don't know that this is documented in either the NetBSD guide or wiki.
If you have edit access to either and see this, please, add this in with any necessary edits!
This page is public domain (as is the rest of my site); don't worry about copyright (I can confirm anything by e-mail if needed).
</P>
<OL>
<LI>Install <CODE>filesystems/fuse</CODE> and <CODE>filesystems/fuse-ext2</CODE>.</LI>
<LI>Connect the drive with the ext4 partition you want to access.</LI>
<LI>Use <CODE>dmesg(8)</CODE> to determine the location in <CODE>/dev/</CODE> of the disk.</LI>
<LI>Use <CODE>disklabel(8)</CODE> to determine which partition on the disk you want to access (<CODE>disklabel /dev/<I>disk</I></CODE>)
- it will be listed with the partition type "Linux Ext2" even though the partition may be ext4.</LI>
<LI>Use <CODE>fuse-ext2(1)</CODE> to mount the partition (<CODE>fuse-ext2 /dev/<I>disk with partition letter</I> <I>mountpoint</I></CODE>
- for example, <CODE>fuse-ext2 /dev/sd1e /mnt/sd1</CODE> to mount partition <I>e</I> of device <I>sd1</I> to the mountpoint <I>/mnt/sd1</I>).</LI>
<LI>This mountpoint can be unmounted with <CODE>umount(8)</CODE> as normal.</LI>
</OL>
<H2>System logging</H2>
<P>See <CODE>syslogd(8)</CODE> and <CODE>syslog.conf(5)</CODE>, which pertain to system logging.</P>
<P>Setting <CODE>DDB_ONPANIC</CODE> (see <CODE>options(4)</CODE> and <CODE>sysctl(8)</CODE>) will save a crash dump at <CODE>/var/crash</CODE> on kernel panic (<A HREF="https://www.unitedbsd.com/d/548-system-instability-on-unstable-version-how-do-i-get-logs/7">source</A>).</P>
<H2>TOR Browser</H2>
<P>
On a ThinkPad X200T (current NetBSD amd64) the <CODE>start-tor-browser.desktop</CODE> script in the pre-compiled amd64 Linux tarball errors out with <CODE>Tor Browser requires a CPU with SSE2 support. Exiting.</CODE>.
This is on a Core2 Duo SL9600 CPU, which does indeed support SSE2 (<CODE>grep flags</CODE> on <CODE>dd &lt;/proc/cpuinfo</CODE> to check your own CPU).
</P>
<P>
TOR Browser is available through pkgsrc at <CODE>security/tor-browser</CODE>.
Because TOR is typically used in environments where very strong security is necessary, it's recommended that you audit the pkgsrc Makefile and distinfo before installation.
</P>
</BODY>
</HTML>

View File

@ -15,8 +15,8 @@
<SCRIPT SRC="/js/cookies.js" TYPE="application/javascript"></SCRIPT> <SCRIPT SRC="/js/cookies.js" TYPE="application/javascript"></SCRIPT>
<SCRIPT SRC="/js/sheets.js" TYPE="application/javascript"></SCRIPT> <SCRIPT SRC="/js/sheets.js" TYPE="application/javascript"></SCRIPT>
<SCRIPT TYPE="application/javascript">window.onload = window.initializesheets;</SCRIPT> <SCRIPT TYPE="application/javascript">window.onload = window.initializesheets;</SCRIPT>
<H1>linux</H1> <H1>software</H1>
<H3>updated 2022-05-17</H3> <H3>updated 2022-05-20</H3>
<HR ALIGN="left" SIZE="1" WIDTH="25%" /> <HR ALIGN="left" SIZE="1" WIDTH="25%" />
<H2>ACPI client</H2> <H2>ACPI client</H2>
<P> <P>
@ -212,6 +212,40 @@ Configuration is in <CODE>/etc/conf.d/dmcrypt</CODE> and further configuration s
<CODE>dm-crypt</CODE> will need the UUID of the <I>physical</I> block device while fstab (if being configured with UUIDs will need the UUID of the decrypted block device in the device mapper. <CODE>dm-crypt</CODE> will need the UUID of the <I>physical</I> block device while fstab (if being configured with UUIDs will need the UUID of the decrypted block device in the device mapper.
</P> </P>
<H2>NetBSD</H2>
<UL>
<LI><A HREF="http://netbsd.org/">netbsd.org</A></LI>
<LI><A HREF="https://www.netbsd.org/docs/guide/en/">NetBSD Guide</A></LI>
<LI><A HREF="https://www.netbsd.org/docs/pkgsrc/">pkgsrc Guide</A></LI>
</UL>
<H3>Mounting ext4 partitions with FUSE</H3>
<OL>
<LI>Install <CODE>filesystems/fuse</CODE> and <CODE>filesystems/fuse-ext2</CODE>.</LI>
<LI>Connect the drive with the ext4 partition you want to access.</LI>
<LI>Use <CODE>dmesg(8)</CODE> to determine the location in <CODE>/dev/</CODE> of the disk.</LI>
<LI>Use <CODE>disklabel(8)</CODE> to determine which partition on the disk you want to access (<CODE>disklabel /dev/<I>disk</I></CODE>)
- it will be listed with the partition type "Linux Ext2" even though the partition may be ext4.</LI>
<LI>Use <CODE>fuse-ext2(1)</CODE> to mount the partition (<CODE>fuse-ext2 /dev/<I>disk with partition letter</I> <I>mountpoint</I></CODE>
- for example, <CODE>fuse-ext2 /dev/sd1e /mnt/sd1</CODE> to mount partition <I>e</I> of device <I>sd1</I> to the mountpoint <I>/mnt/sd1</I>).</LI>
<LI>This mountpoint can be unmounted with <CODE>umount(8)</CODE> as normal.</LI>
</OL>
<H3>Fix <CODE>SSL certificate problem: unable to get local issuer certificate</CODE></H3>
<UL>
<LI><A HREF="http://mail-index.netbsd.org/pkgsrc-users/2021/07/19/msg034147.html">Depending on security/ca-certificates?</A></LI>
<LI><A HREF="https://www.cambus.net/installing-ca-certificates-on-netbsd/">Installing CA certificates on NetBSD</A></LI>
<LI><A HREF="https://github.com/ohmyzsh/ohmyzsh/issues/8321#issuecomment-863493503">SSL Certificate Problem</A> (ohmyzsh/ohmyzsh#8321)</LI>
</UL>
<P>Install <CODE>security/mozilla-rootcerts-openssl</CODE>.</P>
<P>
<I>Do not</I> use SSL workarounds like (in the case of git) <CODE>GIT_SSL_NO_VERIFY</CODE>.
These leave your system open to man-in-the-middle attacks.
</P>
<H3>System logging</H3>
<UL>
<LI><A HREF="https://www.unitedbsd.com/d/548-system-instability-on-unstable-version-how-do-i-get-logs/7">System instability on unstable version - how do I get logs?</A></LI>
</UL>
<P>See <CODE>syslogd(8)</CODE> and <CODE>syslog.conf(5)</CODE>, which pertain to system logging.</P>
<P>Setting <CODE>DDB_ONPANIC</CODE> (see <CODE>options(4)</CODE> and <CODE>sysctl(8)</CODE>) will save a crash dump at <CODE>/var/crash</CODE> on kernel panic.
<H2>postmarketOS</H2> <H2>postmarketOS</H2>
<P> <P>
@ -388,7 +422,11 @@ Start <CODE>pulseaudio(1)</CODE> when you want audio, ideally in your <CODE>.xin
<CODE>mpv(1)</CODE> and <CODE>vlc(1)</CODE> are good options. <CODE>mpv(1)</CODE> and <CODE>vlc(1)</CODE> are good options.
</P> </P>
</BODY> <H3>Web Browsing</H3>
</HTML> <H4>TOR Browser</H4>
<P>
TOR Browser is available through pkgsrc at <CODE>security/tor-browser</CODE>.
</P>
</BODY> </BODY>
</HTML> </HTML>