Making sense out of SUSE's delta releases

With a cold on one side and a complete Internet connection meltdown on the other, I've been having a heck of a time keeping up with my email. Still, before my ISP, Bell South, hosed my DSL connection and my cold medicine knocked me out, I got a message asking: "What's the deal with those 'delta' releases for SUSE 10.1? I can't get them to work."
After a little back and forth with him, I saw what his problem was. He thought the delta was the complete distribution. Nope.
A "delta" to a program, in and of itself, is no good to man or beast. It's simply the code of the changes between one version of a program and another. To make use of a SUSE 10.1 delta, you first have to have a copy of the original code. You then apply the delta to that code to create the complete new version of the program, or in this case, the latest version of SUSE 10.1
-
- Login or register to post comments
Printer-friendly version
- 725 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Events: Video Conferences, Code.gov, and LibreOffice
| GitLab Web IDE
|
Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
| Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
|
Recent comments
3 hours 55 min ago
3 hours 55 min ago
3 hours 57 min ago
7 hours 3 min ago
7 hours 15 min ago
14 hours 7 min ago
1 day 16 hours ago
1 day 17 hours ago
1 day 22 hours ago
2 days 23 hours ago