7z
e1000e-dkms-debian
7z | e1000e-dkms-debian | |
---|---|---|
5 | 3 | |
488 | 68 | |
- | - | |
2.4 | 0.0 | |
4 months ago | almost 2 years ago | |
C++ | C | |
GNU Lesser General Public License v3.0 only | 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.
7z
-
7-zip 22.00 – APFS, Posix TAR, high precision timestamps
Looking back at this version history [1], there was perviously a gap of 3.5 years between releases (2011-2014). Skimming through the discussion forums, the 2.5yr gap between 19.00 and 21.07 was filled with a number of alpha and beta releases, eg 20.02 [2]. Version numbering seems to follow a consistent yy.## format since 2015.
[1] https://sourceforge.net/projects/sevenzip/files/7-Zip/
[2] https://sourceforge.net/p/sevenzip/discussion/45797/thread/9...
-
And it's not like they're 60, they're twenty! I thought it was more known
Also, unlike WinRAR, 7zip is open-source. Code mirror here: https://github.com/kornelski/7z
-
7zip > winRAR change my mind
It's also open source.
- 7-zip official Linux version
-
How safe is 7Zip encryption?
AES is only as good as the KDF protecting the key. Looking at the github mirror of its code (updated march 2019), it seems to be using PBKDF2-SHA1 with 1,000 iterations. That's actually really bad because SHA1 is weak, and 1,000 iterations is very low.
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
What are some alternatives?
NanaZip - The 7-Zip derivative intended for the modern Windows experience
ntfs3 - ntfs3 Linux kernel module by Paragon Software
PeaZip - Free Zip / Unzip software and Rar file extractor. Cross-platform file and archive manager. Features volume spanning, compression, authenticated encryption. Supports 7Z, 7-Zip sfx, ACE, ARJ, Brotli, BZ2, CAB, CHM, CPIO, DEB, GZ, ISO, JAR, LHA/LZH, NSIS, OOo, PAQ/LPAQ, PEA, QUAD, RAR, RPM, split, TAR, Z, ZIP, ZIPX, Zstandard.
asus-fan - Kernel module to get/set (both) fan speed(s) on ASUS Zenbooks
7-Zip-zstd - 7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard
realtek-r8125-dkms - A DKMS package for easy use of Realtek r8125 driver, which supports 2.5 GbE.
libarchive - Multi-format archive and compression library
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.
p7zip - A new p7zip fork with additional codecs and improvements (forked from https://sourceforge.net/projects/sevenzip/ AND https://sourceforge.net/projects/p7zip/).
daemon - turns other processes into daemons
7zip.html - Browse 7z archives online in the web-browsers
bcm5719-fw - BCM5719 firmware reimplementation