steeb/home_network_notes
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add Software Notes

steeb 2024-11-15 19:30:42 -07:00
parent bbe958f95f
commit 74b3888095
1 changed files with 43 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
Software-Notes.md Normal file

@ -0,0 +1,43 @@
### Software Notes
These probably do not belong in the network notes wiki, but then again, I'm using this entire Git incorrectly by using it for exclusively the wiki functionality. Oops.
## Debian
# Installing the unstable kernel on a stable installation
A plain Debian installation did not see the Intel i226-v NIC, so this is a *possible* workaround for that. Untested until this weekend when I have time to sit down with it.
First, edit `/etc/apt/sources.list` to add the lines for the Debian unstable repo
```
deb http://deb.debian.org/debian unstable main contrib non-free
deb-src http://deb.debian.org/debian unstable main contrib non-free
```
**Do not update at this point or you will upgrade the entire system.**
Next, modify `/etc/apt/preferences` - this file likely does not exist on your system, currently.
```
nano /etc/apt/preferences
````
Contents:
```
Package: *
Pin: release a=bookworm
Pin-Priority: 500
Package: linux-image-amd64
Pin:release a=unstable
Pin-Priority: 1000
Package: linux-headers
Pin:release a=unstable
Pin-Priority: 1000
Package: *
Pin: release a=unstable
Pin-Priority: 100
```
Keep in mind, this will fix the installation onto `bookworm` and will need to be modified to upgrade to `trixie` when it is released. The first section pins all packages to `bookworm`, the second and third section pin the `linux-kernel-amd64` and `linux-headers` packages to unstable, the last section simply de-prioritizes the `unstable` repo so that it is not automatically upgraded from for any other packages.