Language Selection

English French German Italian Portuguese Spanish

Original Articles from 2005

  1. Stx 1.0rc3 - An update - Dec. 31, 2005
  2. Mandriva Linux 2006.1-0.3 - Dec. 27, 2005
  3. Return to Na Pali ...er ...Nepalinux - Dec. 25, 2005
  4. Linux XP 2006 - Dec. 24, 2005
  5. Top Distros of 2005 - Dec. 22, 2005
  6. Kororaa - Revisited - Dec. 18, 2005
  7. Kat Continues to Purrrr - Dec. 17, 2005
  8. SUSE 10.1 Alpha 4 Report - Dec. 17, 2005
  9. DSL 2.1r2 Report - Dec. 15, 2005
  10. Stx 1.0 r2: He Wanted Testers!... - Dec. 11, 2005
  11. A Taste of the Berry 0.65 - Dec. 10, 2005
  12. The Alpha-Male: Kenneth Granerud of Wolvix - Dec. 9, 2005
  13. KateOS 2.3: Kicking butt and taking names - Dec. 9, 2005
  14. DSL 2.1r1 on old Laptop - Dec. 6, 2005
  15. Wolvix 1.0.4, the adventure continues - Dec. 3, 2005
  16. grrrrrr-rr4 - Dec. 3, 2005
  17. Mutagenix 2.6.14.2-1 Reviewed - Nov. 27, 2005
  18. KDE 3.5 Unannounced - Nov. 26, 2005
  19. Kanotix 2005-04-RC17 - Nov. 24, 2005
  20. PCLOS .92 - It just works - Nov. 23, 2005
  21. Goodgoat - A shortcut to Gentoo? - Nov. 23, 2005
  22. Suse 10.1 alpha3 Report - Nov. 20, 2005
  23. Kurumin 5.1 Alpha 5 released - Nov. 19, 2005
  24. Kororaa - Close but no cigar... - Nov. 19, 2005
  25. KDE 3.5r1 Installed - Nov. 13, 2005
  26. Ubuntu 6.04 pre-beta (Dapper Drake) - Nov. 13, 2005
  27. Kurumin: From Brazil with Lov^H^H^HLinux - Nov. 12, 2005
  28. MitraX in the Matrix - Nov. 9, 2005
  29. MyahOS 1.1 - Moving on up - Nov. 5, 2005
  30. An Arabian Night - Nov. 2, 2005
  31. The Latest & Greatest from the Best of the Best - Oct. 28, 2005
  32. Act 3: Symphony OS Beta 1 PR1 - Oct. 26, 2005
  33. LG3D-Livecd 2.3 - Oct. 21, 2005
  34. Debian Pure 0.4 - Oct. 19, 2005
  35. Let's Take a Zenwalk - Oct. 16, 2005
  36. Going Live with Elive - Oct. 15, 2005
  37. Mandriva 2006 Final Look - Oct. 14, 2005
  38. All Hail! King of the Minis: DSL - Oct. 13, 2005
  39. Stuck on Stux - Oct. 12, 2005
  40. Come on in the Water's Fine - Oct. 8, 2005
  41. About SUSE Linux 10.0 - Oct. 7, 2005
  42. Gentoo User's Response to Slacker who tried Gentoo - Oct. 6, 2005
  43. Meet Komodo Linux - Oct. 5, 2005
  44. My Top 5 Distro Picks - Oct. 2, 2005
  45. SuSE 10.1 Alpha1 Report - Sept. 30, 2005
  46. Featherweight -> down for the count - Sept. 28, 2005
  47. My oh my, Myah - Sept. 25, 2005
  48. A Mini-Mandriva! - Sept. 23, 2005
  49. Taprobane GNU/Linux 0.4.1 - Sept. 23, 2005
  50. Wolvix: Leader of the Pack - Sept. 21, 2005
  51. Slackware 10.2 - Sept. 15, 2005
  52. MDV 2006 RC2 - In the Homestretch? - Sept. 15, 2005
  53. Education through Edubuntu - Sept. 13, 2005
  54. Your rPath to Conary - Sept. 11, 2005
  55. Is SUPER Superior? - Sept. 10, 2005
  56. OpenSuSE 10.0 RC1 is here too! - Sept. 9, 2005
  57. Ultima Linux: Ultimate Disappointment - Sept. 7, 2005
  58. Mandriva 2006 RC1 has arrived! - Sept. 7, 2005
  59. Beyond Beyond Linux from Scratch (lfs - part3) - Sept. 5, 2005
  60. Linux From Scratch 6.1 - Part 2 - BLFS - Sept. 2, 2005
  61. OSS 10.0b4 report - Sept. 1, 2005
  62. Get it while the Gettings Good - Sept. 1, 2005
  63. My Take On PocketLinux - August 29, 2005
  64. Beastie of an OS - August 27, 2005
  65. Keepin Ya Posted: SUSE Linux 10.0b3 - August 25, 2005
  66. Mandriva 2006 Beta 3 - August 23, 2005
  67. Quick Look-See at Freespire - August 23, 2005
  68. Exploring the outer limits - August 22, 2005
  69. SUSE Linux 10.0 Beta 2 Report - August 20, 2005
  70. Because Beauty is Basic - August 19, 2005
  71. Interview: Roberto Cappuccio of KAT - August 17, 2005
  72. Austrumi 0.9.7 Released - August 14, 2005
  73. Mandriva 2006 Beta 2 is Looking Goood - August 12, 2005
  74. The Lizard Blizzard Begins - August 10, 2005
  75. SymphonyOS - Act II (Alpha 4) - August 3, 2005
  76. Dark Water & Charlie & Choc Factory - July 24, 2005
  77. KDE 3.4.2: Just around the bend - July 23, 2005
  78. yum! raspBerry 0.60 - July 21, 2005
  79. Mandriva 2006 Beta1 - July 16, 2005
  80. Damn Small Look - July 15, 2005
  81. Linux From Scratch 6.1 (part 1?) - July 11, 2005
  82. Review: War of the Worlds - July 7, 2005
  83. Underground Desktop - July 5, 2005
  84. My Kinda Gal: KateOS 2.1 - July 4, 2005
  85. For the best in today's fashions: Frugalware - June 26, 2005
  86. Emerge Litrix-3.0 - June 19, 2005
  87. PCLinuxOS Preview-9 - June 14, 2005
  88. MiniSlack is no mini Slack - June 12, 2005
  89. Sneak Peek at PCLOS pre-9 - June 8, 2005
  90. Sneak Peek at Mandriva 2006 - June 6, 2005
  91. Helios Speaks out on Lobby4Linux - June 5, 2005
  92. Mini-Review of a Mini-Slack - June 3, 2005
  93. Venture into the Fox's Den - May 29, 2005
  94. KDE 3.4.1 is Coming Your Way - May 25, 2005
  95. An Austrumi Assessment - May 23, 2005
  96. Putting on my Tie & Tails - May 15, 2005
  97. Movietime: XXX: State of the Union - May 11, 2005
  98. My Mutagenix Monday - May 9, 2005
  99. A Damn Small Sunday - May 8, 2005
  100. Kickin the Tires: Taking PC-BSD for a Spin - May 2, 2005
  101. Movie Review: The Interpreter - April 25, 2005
  102. A Month With Fluxbox - Part 2 - April 22, 2005
  103. At the Movies: The Amityville Horror - April 20, 2005
  104. 411 on 2005 - April 17, 2005
  105. Your Very Own Mandriva - April 14, 2005
  106. Performance Tweaks & Tips - April 9, 2005
  107. Mini Distro Round-Up - April 4, 2005
  108. Origins of April Fool's Day - April 1, 2005
  109. Mandrake Thinking Name Change? - March 31, 2005
  110. A Month With Fluxbox - Part 1 - March 28, 2005
  111. This Week's Movies, part 2: The Ring Two - March 23, 2005
  112. This Week's Movies: The Jacket and The Pacifier" - March 21, 2005
  113. Computer Addiction or Healthy Enthusiam? - March 20, 2005
  114. KDE 3.4 Unleashed - March, 16, 2005
  115. KDE user's look at Gnome-2.10 - March 12, 2005.
  116. A Week with KDE 3.4rc1 - March 06, 2005
  117. Snapshots of KDE_3.4rc1 - February 27, 2005
  118. Slackware 10.1 - February 25, 2005
  119. Mdk 10.2 beta 3 - February 24, 2005
  120. This Week at the Movies: Million Dollar Baby & Constantine - February 22, 2005
  121. This Week at the Movies: Hitch & The Aviator - February 18, 2005
  122. A Week with KDE 3.4beta2 - February 17, 2005
  123. In Quest of Freedom - February 13, 2005
  124. This Week At the Movies: Boogeyman & Alone in the Dark & Hide and Seek - February 09, 2005
  125. Genesis of an Operating System - February 08, 2005
Articles By Others

  1. Remastering: The undocumented process - Submitted by sennachie on Wed, 10/12/2005
  2. OnebaseGo 3.0 Review - Submitted by DJ Jackson on Fri, 08/19/2005
  3. Making a dual-boot RH9 and Fedora Core 3 computer - Submitted by TGodfrey on Thu, 07/07/2005
  4. Ubuntu 5.04 Review/Install - Submitted by TGodfrey on Fri, 07/01/2005
  5. Linux made workable, productive, and easy! - Submitted by TGodfrey on Tue, 06/28/2005
  6. Building a New Computer System for Linux - Submitted by gfranken on Thu, 06/16/2005
  7. You Want A WAR? I'll Give You A War! - Submitted by helios17 on Mon, 06/13/2005
  8. An Open Letter To Linux Developers - Submitted by helios17 on Wed, 04/27/2005
  9. Windows Users Test Linux Waters - Submitted by helios17 on Sun, 04/17/2005
  10. A Peak at MDK 10.2-b2 AMD64 - Submitted by Anonymous on Sat, 03/19/2005










More in Tux Machines

LWN: Spectre, Linux and Debian Development

  • Grand Schemozzle: Spectre continues to haunt

    The Spectre v1 hardware vulnerability is often characterized as allowing array bounds checks to be bypassed via speculative execution. While that is true, it is not the full extent of the shenanigans allowed by this particular class of vulnerabilities. For a demonstration of that fact, one need look no further than the "SWAPGS vulnerability" known as CVE-2019-1125 to the wider world or as "Grand Schemozzle" to the select group of developers who addressed it in the Linux kernel. Segments are mostly an architectural relic from the earliest days of x86; to a great extent, they did not survive into the 64-bit era. That said, a few segments still exist for specific tasks; these include FS and GS. The most common use for GS in current Linux systems is for thread-local or CPU-local storage; in the kernel, the GS segment points into the per-CPU data area. User space is allowed to make its own use of GS; the arch_prctl() system call can be used to change its value. As one might expect, the kernel needs to take care to use its own GS pointer rather than something that user space came up with. The x86 architecture obligingly provides an instruction, SWAPGS, to make that relatively easy. On entry into the kernel, a SWAPGS instruction will exchange the current GS segment pointer with a known value (which is kept in a model-specific register); executing SWAPGS again before returning to user space will restore the user-space value. Some carefully placed SWAPGS instructions will thus prevent the kernel from ever running with anything other than its own GS pointer. Or so one would think.

  • Long-term get_user_pages() and truncate(): solved at last?

    Technologies like RDMA benefit from the ability to map file-backed pages into memory. This benefit extends to persistent-memory devices, where the backing store for the file can be mapped directly without the need to go through the kernel's page cache. There is a fundamental conflict, though, between mapping a file's backing store directly and letting the filesystem code modify that file's on-disk layout, especially when the mapping is held in place for a long time (as RDMA is wont to do). The problem seems intractable, but there may yet be a solution in the form of this patch set (marked "V1,000,002") from Ira Weiny. The problems raised by the intersection of mapping a file (via get_user_pages()), persistent memory, and layout changes by the filesystem were the topic of a contentious session at the 2019 Linux Storage, Filesystem, and Memory-Management Summit. The core question can be reduced to this: what should happen if one process calls truncate() while another has an active get_user_pages() mapping that pins some or all of that file's pages? If the filesystem actually truncates the file while leaving the pages mapped, data corruption will certainly ensue. The options discussed in the session were to either fail the truncate() call or to revoke the mapping, causing the process that mapped the pages to receive a SIGBUS signal if it tries to access them afterward. There were passionate proponents for both options, and no conclusion was reached. Weiny's new patch set resolves the question by causing an operation like truncate() to fail if long-term mappings exist on the file in question. But it also requires user space to jump through some hoops before such mappings can be created in the first place. This approach comes from the conclusion that, in the real world, there is no rational use case where somebody might want to truncate a file that has been pinned into place for use with RDMA, so there is no reason to make that operation work. There is ample reason, though, for preventing filesystem corruption and for informing an application that gets into such a situation that it has done something wrong.

  • Hardening the "file" utility for Debian

    In addition, he had already encountered problems with file running in environments with non-standard libraries that were loaded using the LD_PRELOAD environment variable. Those libraries can (and do) make system calls that the regular file binary does not make; the system calls were disallowed by the seccomp() filter. Building a Debian package often uses FakeRoot (or fakeroot) to run commands in a way that appears that they have root privileges for filesystem operations—without actually granting any extra privileges. That is done so that tarballs and the like can be created containing files with owners other than the user ID running the Debian packaging tools, for example. Fakeroot maintains a mapping of the "changes" made to owners, groups, and permissions for files so that it can report those to other tools that access them. It does so by interposing a library ahead of the GNU C library (glibc) to intercept file operations. In order to do its job, fakeroot spawns a daemon (faked) that is used to maintain the state of the changes that programs make inside of the fakeroot. The libfakeroot library that is loaded with LD_PRELOAD will then communicate to the daemon via either System V (sysv) interprocess communication (IPC) calls or by using TCP/IP. Biedl referred to a bug report in his message, where Helmut Grohne had reported a problem with running file inside a fakeroot.

Flameshot is a brilliant screenshot tool for Linux

The default screenshot tool in Ubuntu is alright for basic snips but if you want a really good one you need to install a third-party screenshot app. Shutter is probably my favorite, but I decided to give Flameshot a try. Packages are available for various distributions including Ubuntu, Arch, openSuse and Debian. You find installation instructions on the official project website. Read more

Android Leftovers

IBM/Red Hat and Intel Leftovers

  • Troubleshooting Red Hat OpenShift applications with throwaway containers

    Imagine this scenario: Your cool microservice works fine from your local machine but fails when deployed into your Red Hat OpenShift cluster. You cannot see anything wrong with the code or anything wrong in your services, configuration maps, secrets, and other resources. But, you know something is not right. How do you look at things from the same perspective as your containerized application? How do you compare the runtime environment from your local application with the one from your container? If you performed your due diligence, you wrote unit tests. There are no hard-coded configurations or hidden assumptions about the runtime environment. The cause should be related to the configuration your application receives inside OpenShift. Is it time to run your app under a step-by-step debugger or add tons of logging statements to your code? We’ll show how two features of the OpenShift command-line client can help: the oc run and oc debug commands.

  • What piece of advice had the greatest impact on your career?

    I love learning the what, why, and how of new open source projects, especially when they gain popularity in the DevOps space. Classification as a "DevOps technology" tends to mean scalable, collaborative systems that go across a broad range of challenges—from message bus to monitoring and back again. There is always something new to explore, install, spin up, and explore.

  • How DevOps is like auto racing

    When I talk about desired outcomes or answer a question about where to get started with any part of a DevOps initiative, I like to mention NASCAR or Formula 1 racing. Crew chiefs for these race teams have a goal: finish in the best place possible with the resources available while overcoming the adversity thrown at you. If the team feels capable, the goal gets moved up a series of levels to holding a trophy at the end of the race. To achieve their goals, race teams don’t think from start to finish; they flip the table to look at the race from the end goal to the beginning. They set a goal, a stretch goal, and then work backward from that goal to determine how to get there. Work is delegated to team members to push toward the objectives that will get the team to the desired outcome. [...] Race teams practice pit stops all week before the race. They do weight training and cardio programs to stay physically ready for the grueling conditions of race day. They are continually collaborating to address any issue that comes up. Software teams should also practice software releases often. If safety systems are in place and practice runs have been going well, they can release to production more frequently. Speed makes things safer in this mindset. It’s not about doing the “right” thing; it’s about addressing as many blockers to the desired outcome (goal) as possible and then collaborating and adjusting based on the real-time feedback that’s observed. Expecting anomalies and working to improve quality and minimize the impact of those anomalies is the expectation of everyone in a DevOps world.

  • Deep Learning Reference Stack v4.0 Now Available

    Artificial Intelligence (AI) continues to represent one of the biggest transformations underway, promising to impact everything from the devices we use to cloud technologies, and reshape infrastructure, even entire industries. Intel is committed to advancing the Deep Learning (DL) workloads that power AI by accelerating enterprise and ecosystem development. From our extensive work developing AI solutions, Intel understands how complex it is to create and deploy applications for deep learning workloads. That?s why we developed an integrated Deep Learning Reference Stack, optimized for Intel Xeon Scalable processor and released the companion Data Analytics Reference Stack. Today, we?re proud to announce the next Deep Learning Reference Stack release, incorporating customer feedback and delivering an enhanced user experience with support for expanded use cases.

  • Clear Linux Releases Deep Learning Reference Stack 4.0 For Better AI Performance

    Intel's Clear Linux team on Wednesday announced their Deep Learning Reference Stack 4.0 during the Linux Foundation's Open-Source Summit North America event taking place in San Diego. Clear Linux's Deep Learning Reference Stack continues to be engineered for showing off the most features and maximum performance for those interested in AI / deep learning and running on Intel Xeon Scalable CPUs. This optimized stack allows developers to more easily get going with a tuned deep learning stack that should already be offering near optimal performance.