e1000e-dkms-debian
p7zip
e1000e-dkms-debian | p7zip | |
---|---|---|
3 | 13 | |
68 | 737 | |
- | 1.1% | |
0.0 | 0.0 | |
almost 2 years ago | 7 months ago | |
C | C | |
GNU General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
e1000e-dkms-debian
-
PXE provisioning issues with new hardware that requires specific drivers!
Hello, Our hardware vendor stopped selling the previous models of our standard desktops and laptops and possess sent the newest models in our latest purchase. Unfortunately, when installing Ubuntu on these machines the NICs are not recognized by the OS and need manual intervention to be updated, which I was able to get going by downloading the appropriate e1000e driver onto a USB and installing from that. Our standard workflow was provisioning the system with Foreman, and configuring it with ansible after the OS was installed. The manual steps now required between these steps have caused delays in setting up new equipment. Getting this hardware to allow PXE in the first place was a pain, I had to take the initrd.gz that foreman provides for the PXE environment, unpack it and replace the e1000e network driver with the very latest one to even allow the PXE process to start. But because the archive foreman uses for Ubuntu is the standard Canonical hosted Ubuntu archive, the OS is again missing that version of the driver and it needs to get updated again. Does anyone have recommendations on how to get around this? * I tried using HWE but it seems to not include this very latest version of e1000e so had no luck there * Could this process be included in the preseed file/provisioning template to handle the driver? * Our foreman install has Katello, but I have been having a hell of a time getting deb repos hosted. Even if that gets set up properly, it seems pretty hacky again to insert a kernel with the correct driver version. (GPG issues? idk) * Foreman/Katello docs are lackluster and havent seen anything related to this kind of problem * FYI the desktop is a Dell Precision Tower 3650 and installing Ubuntu 18.04 I was hired as a Junior Sys Admin 2 years and now find myself as the sole IT in the company, this has been driving me nuts as my previous provisioning workflow was pretty solid but dont have anyone internal to turn to for advice. Would really appreciate any thoughts or ideas you all have or any resources you know of I can look into. Thanks! EDIT: Thanks for the replies everyone, I ended up getting this resolved by using DKMS. https://github.com/koljah-de/e1000e-dkms-debian was a good starting point, I built a deb from that and placed it on my tftp server. Then in Foreman's finish template I included the following lines: tftp -m binary tftp.example.com -c get e1000e-dkms.deb dpkg -i e1000e-dkms.deb That worked for me, after the installation process the NIC was usable. Plus this has the added benefit of not needing to tweak the drivers after upgrading the kernel at a later date.
-
7-zip 22.00 – APFS, Posix TAR, high precision timestamps
Intel out-of-tree NIC drivers too; https://sourceforge.net/projects/e1000/ - But there are not many!
-
Intel NIC drivers confusion
[1] qemu/hw/net/e1000.c [2] Devices supported by Linux's e1000 [3] e1000 from Intel
p7zip
-
Ubuntu 23.04 (Lunar Lobster)
nearly every main distro I am aware of has both available. The reason you still see p7zip is because the CLI incompatibilities vs the newer 7z/7zip executables and the general licensing issues. Most users of "old p7zip" are actually using the actively maintained https://github.com/p7zip-project/p7zip which is updated, supporting unix permissions and zstd and so on.
-
7-zip 22.00 – APFS, Posix TAR, high precision timestamps
Thank you for pointing this out! This is the source of much confusion. Although Arch for example uses https://github.com/jinfeihan57/p7zip which seems to be reasonably maintained?
- Ark and 7-zip
-
Replace p7zip with upstream 7-Zip
Then you can compile p7zip from source: $ mkdir p7zip-git $ cd p7zip-git $ git clone https://github.com/jinfeihan57/p7zip .
- Don't Use RAR
- TIL there's a fork of the unmaintained p7zip port of 7-Zip
- I can't compress in 7zip with Ark and p7zip
-
will arch replace p7zip with normal 7-zip?
April 4th was the latest release. Had some commits in May. I think it is active.
-
Why is 7z so outdated?
I think the point is, the '7z' at 17.04 available in Arch Linux's repo is actually p7zip, the development of which is independent of 7-zip. So comparison of the version number is meaningless (if I am right). Also, p7zip 17.04 is released in April this year, not 2017, according to its release page
-
7-Zip 21.0 alpha introduces native Linux support
this comment might clarify that.
What are some alternatives?
ntfs3 - ntfs3 Linux kernel module by Paragon Software
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
asus-fan - Kernel module to get/set (both) fan speed(s) on ASUS Zenbooks
NanaZip - The 7-Zip derivative intended for the modern Windows experience
realtek-r8125-dkms - A DKMS package for easy use of Realtek r8125 driver, which supports 2.5 GbE.
7z - Because 7-zip source code was in a 7z archive [mirror]
rapiddisk - An Advanced Linux RAM Drive and Caching kernel modules. Dynamically allocate RAM as block devices. Use them as stand alone drives or even map them as caching nodes to slower local disk drives. Access those volumes locally or export them across an NVMe Target network. Manage it all from a web API.
libarchive - Multi-format archive and compression library
daemon - turns other processes into daemons
engrampa - A file archiver for MATE
bcm5719-fw - BCM5719 firmware reimplementation
fast-lzma2 - Fast LZMA2 Library