Open-source News

How to Create a Cool Photo Mosaic on Linux With Polyfoto  MUO - MakeUseOf

KDE neon is Now Based on Ubuntu 22.04 ‘Jammy Jellyfish’  OMG! Ubuntu!

Linux Operating System Market Size, Share, Trend, Register Exponential Growth, Business Opportunity, Regional Data, Demand, Key Players Throughout 2022-2029  Digital Journal

AMD Per-Thread CPU Microcode Loading Fix Submitted For Linux 6.1-rc2  Phoronix

A set of "x86/urgent" patches were sent out this morning for pulling into the Linux kernel ahead of today's 6.1-rc2 release...

There has long been a debate over an "accelerator" subsystem for the Linux kernel given the increasing number of AI/accelerator devices coming to market. Currently there are accelerator drivers living within the catch-all "char/misc" area of the kernel while some driver efforts have been focused on Direct Rendering Manager (DRM) subsystem integration given the commonality with GPUs and some of the core infrastructure and APIs being relevant for both GPUs and these dedicated accelerator ASICs. There finally seems to be some agreement over the future of the accelerator subsystem and some initial patches were mailed out this weekend...

Patches Posted For Preparing New Linux "Accel" Subsystem - Builds Off DRM Code  Phoronix

A new Linux driver introduced by Intel earlier this year was the In-Field Scan for making use of new silicon failure testing functionality with upcoming Intel server CPUs. The IFS driver and associated hardware capability is for detecting potential problems not caught by parity or ECC checks on systems in production. In-Field Scan was merged in Linux 5.19 but then shortly thereafter the driver was marked "broken" due to some driver design issues coming to light. New patches for IFS have been posted to improve the driver's design and remove that "broken" tag...

Intel In-Field Scan (IFS) Driver Improved - Will Remove Its "Broken" Tag  Phoronix

Linus Torvalds has backed the idea of possibly removing Intel 486 (i486) processor support from the Linux kernel...

The Linux Kernel May Finally Phase Out Intel i486 CPU Support  Phoronix

How to Use the wc Command in Linux  MUO - MakeUseOf

After being worked on the past year, Mesa 22.3 has landed support for Wayland's DMA-BUF Feedback extension for use by the Mesa Vulkan drivers with the Vulkan windowing system integration (WSI) code...

In addition to GCC landing patches this week in preparing for Grand Ridge and Sierra Forest, the LLVM/Clang open-source compiler stack has also been seeing patches to prepare for future Intel server processors...

Valve put up a few more fixes in the new Steam Deck Beta  GamingOnLinux

Intel earlier this year more formally announced DAOS as its distributed parallel file-system designed for NVMe storage and aims to be more efficient than other parallel file-systems. Yesterday marked the release of DAOS 2.2 as the newest step forward for Distributed Application Object Storage...

FreeBSD had a busy Friday with releasing their first beta of the upcoming FreeBSD 12.4 as well as publishing their third quarter development summary...

Last week saw the release of Plasma 5.26 while this week KDE developers moved on to more feature work for Plasma 5.27 while also addressing some fall-out and fixes for Plasma 5.26...

How to Create Custom Linux Mint or Ubuntu ISO  It's FOSS

Use open source commands in Powershell Alan Smithee Sat, 10/22/2022 - 03:00

When you launch an application on an operating system, there are certain code libraries and utility applications that your OS needs to use for that app to run. Your OS knows how to find these libraries and utilities because it has a system path, a map to common shared data that lots of apps need. Every OS has this, but users aren’t usually aware of it because they don’t usually need to care about it. However, when you start coding or using special network utilities or commands, you might care about your own PATH variable.

More great content Free online course: RHEL technical overview Learn advanced Linux commands Download cheat sheets Find an open source alternative Explore open source resources

The PATH variable makes it so that you can save commands to a consistent location, and use them from anywhere on your system using the command prompt or the more powerful (and open source) Powershell.

For instance, say you want to install the open source application pscp.exe, a command-line interface to the famous PuTTY OpenSSH client on Windows. You can download it to your hard drive, but how does your command-line know that it exists? Well at first, it doesn’t:
 

PS> pscp
pscp: The term 'pscp' is not recognized as the name of a cmdlet, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

If you’re using an open source command line, such as Powershell or Cmder, you get a useful error hinting that this might be a problem with your path (or the lack thereof). Here’s how to solve that problem.

Setting a PATH

1. First, create a folder called App on your Desktop.

2. Next, right-click on the Windows menu in the bottom left corner of your screen, and select System.

Image by:

(Alan Smithee, CC BY-SA 4.0)

3. In the System window that appears, click the link to Advanced system settings on the left of the window.

4. In the System properties window that appears, click the Environment variables button at the bottom of the window.

Image by:

(Alan Smithee, CC BY-SA 4.0)

5. In the Environment variables window, click the New button under the User variables panel.

Image by:

(Alan Smithee, CC BY-SA 4.0)

6. In the dialog box that appears, enter PATH for the Variable name field, and %USERPROFILE\Desktop\App for the Variable value field. Click the OK button to save your changes.

Image by:

(Alan Smithee, CC BY-SA 4.0)

Place commands and applications you want to have access to from a command prompt in Desktop\Apps and Powershell, Cmder, and even Cmd will find them:
 

PS> pscp –version
pscp: Release 0.XY
Build platform: 64-bit x86 Windows
PS> Automatic PATH settings

Many applications get automatically added to the system path during installation. However, not all of them do, either because you missed a check box during the install process, or because the application developer expects you to add it yourself. When automatic paths fail, you now know how to forge your own path.

Set your path on Windows so you can use open source commands.

Image by:

Opensource.com

Command line Windows What to read next This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.