Language Selection

English French German Italian Portuguese Spanish

Reiser

Awkward History of Linux and Latest of Reiser5

Filed under
Linux
Reiser
  • Linux in 2020 [Ed: This is clearly conflating the kernel (Linux) with GNU, which predates it by almost one decade. It also perpetuates the myth that only Ubuntu brought GNU/Linux to the masses.]

    Hello. Today I would like to share with you, my perspective of Linux. Please take note that this is all my opinions and the way I see it. If you feel that I missed something very important or have a fact or two wrong, please let me know.

    So Linux was announced for the first time, on the 25 of August 1991 by a Finnish student, called Linus Torvalds. Little did he know, and the world knows that 30 years later the world would be using it on a daily basis.

    So From 1991, Linux has been maturing several Linux Distros (operating systems) came and went away, with a few of the first ones still around today. But it was mainly/only for those who are computer "geeks" and not for everyday users. But that all changed in October 2004, when the first version of Ubuntu was released.

  • Reiser5 Logical Volume Management - Updates
      Reiser5 Logical Volume Management - Updates
    
    
    I am happy to inform, that Logical Volumes stuff has become more
    stable. Also we introduce the following changes, which make logical
    volumes administration more flexible and simple:
    
    
                      1. No balancing by default
    
    
    Now all volume operations except brick removal don't invoke balancing
    by default. Instead, they mark volume as "unbalanced". To complete any
    operation with balancing specify option -B (--with-balance), or run
    volume.reiser4(8) utility with the option -b (--balance) later.
    
    This allows to speed up more than one operations over logical volume
    being performed at once. For example, if you want to add more than one
    brick to your volume at once, first add all the bricks, then run
    balancing. There is no need to balance a volume between the addition
    operations.
    
    
                        2. Removal completion
    
    
    Operation of brick removal always includes balancing procedure as its
    part. This procedure moves out all data block from the brick to be
    removed to remaining bricks of the volume. Thus, brick removal is
    usually a long operation, which may be interrupted for various reasons
    In such cases the volume is automatically marked with an "incomplete
    removal" flag.
    
    It is not allowed to perform essential volume operations on a volume
    marked as "with incomplete removal": first, user should complete
    removal by running volume.reiser4 utility with option
    -R (--finish-removal). Otherwise, the operation will return error
    (-EBUSY).
    
    There is no other restrictions: you are allowed to add a brick to
    unbalanced volume, and even remove a brick from an unbalanced volume
    (assuming it is not incomplete removal).
    
    Comment. "--finish-removal" is a temporary option. In the future the
    file system will detect incomplete removal and automatically perform
    removal completion by itself.
    
    
                    3. Balancing is always defined
    
    
    Operation of volume balancing (regardless of its balanced status) is
    always defined, and can be launched at any moment. If the volume is
    balanced, then the balancing procedure just scans the volume without
    any useful work.
    
    It is allowed to run more than one balancing threads on the same
    volume, however currently it will be inefficient: other threads will
    be always going after the single leader without doing useful work.
    Efficient volume balancing by many threads (true parallelism) is not a
    trivial task. We estimate its complexity as 2/5.
    
    
              4. Restore regular distribution on the volume
    
    
    Custom (defined by user) file migration can break fairness of data
    distribution among the bricks. To restore regular (fair) distribution
    on the volume, run volume.reiser4 utility with the option -S
    (--restore-regular). It launches a balancing procedure, which performs
    mandatory data migration of all files (including the ones marked as
    "immobile") in accordance with regular distribution policy on the
    volume. Moreover, when the balancing procedure encounters a file
    marked as "immobile", its "immobile" flag is cleared up.
    
    
                             5. How to test
    
    
    The new functionality is available starting with the kernel patch
    reiser4-for-linux-5.10-rc3 and reiser4progs-2.0.4 (Software Framework
    Release number of both is 5.1.3).
    
  • Reiser5 Stabilizing Its Logical Volume Functionality - Phoronix

    This New Year's Eve will mark one year since the announcement of the in-development Reiser5 file-system. While the outlook for getting Reiser5 upstreamed into the mainline kernel remains murky given the out-of-tree status of Reiser4, Edward Shishkin does continue advancing this latest Reiser file-system iteration.

    Since last year's initial Reiser5 announcement, more features continue to be ironed out for this evolution of Reiser4. The latest Reiser5 functionality hitting a point of stability is its logical volume management.

Reiser4/Reiser5 Updated For Linux 5.8

Filed under
Reiser

Edward Shishkin continues pushing ahead with not only maintaining the existing out-of-tree Reiser4 file-system code but also developing Reiser5 seemingly without any major corporate support. Reiser4 and the experimental Reiser5 file-system code were updated on Monday for Linux 5.8 kernel compatibility.

The Reiser4 kernel driver along with the unstable Reiser5 kernel code saw new patch releases for supporting them on the Linux 5.8 stable kernel (Linux 5.8.1 target to be exact).

Read more

Reiser4/Reiser5 Updated For Linux 5.7 Kernel Compatibility

Filed under
Reiser

It was just over a week ago that Reiser4 was updated for Linux 5.6 support while now it's been updated for the newly-minted Linux 5.7 stable kernel along with updating the experimental Reiser5 file-system for this latest kernel series.

Uploaded today by Edward Shishkin was Reiser4 for Linux 5.7.1. Though given the minimal changes with 5.7.1 compared to last week's 5.7 release, the patch presumably should apply cleanly there as well. There are no reports of any other functional Reiser4 changes besides re-basing to the new kernel series.

Read more

Reiser5 Updates For Linux 5.5 Along With Reiser4

Filed under
Reiser

The out-of-tree Reiser4 and Reiser5 (Reiser4 v5) patches have been updated against the recently stabilized Linux 5.5 kernel.

Main Reiser4 developer Edward Shishkin re-based the Reiser4 file-system patch against Linux 5.5.1 along with the experimental Reiser5.

At the end of 2019 is when Shishkin announced Reiser5 file-system development with introducing the concepts of local volumes capable of parallel scaling out and other key iterations over the current Reiser4 design.

Read more

Reiser4 File-System Is Still Ticking In 2019 - Now Updated For Linux 5.3 Compatibility

Filed under
Linux
Reiser

Edward Shishkin continues near single-handedly maintaining the out-of-tree Reiser4 code that at this point still has no apparent trajectory towards mainline. The former Namesys developer previously indicated it's unlikely to see Reiser4 merged unless there is a company backing it to get it through the review process for merging into mainline. While Reiser4 was quite promising for its early time, it's only getting more difficult with Reiser4 effectively stagnating for years now while SUSE/openSUSE continues backing Btrfs, Ubuntu increasingly investing in ZFS support, Red Hat developing Stratis, XFS continuing to be advanced by Red Hat and others as well, Google continuing to invest in the likes of EXT4/F2FS, and there also being Bcachefs and other open-source storage solutions that are more promising than Reiser4 in 2019. Nevertheless, the out-of-tree kernel patches continue to be updated.

Read more

Reiser4 Brought To The Linux 5.0 Kernel

Filed under
Reiser

For those still using the out-of-tree Reiser4 file-system, it may be about time to consider alternatives like Btrfs, XFS, ZFS On Linux, F2FS, or even the likes of Stratis and Bcachefs. But should you still be using this once promising file-system, the out-of-tree patches have been revised to now work with the Linux 5.0 kernel.

There still is no trajectory for Reiser4 to the mainline Linux kernel with no major companies or other stakeholders backing Reiser4 but just a small group of developers and enthusiasts left working on this successor to ReiserFS. With the latest code posted on Friday by former Namesys developer Edward Shishkin, the Reiser4 kernel driver has been re-based to the Linux 5.0 kernel but with no other changes to the file-system noted.

Read more

Reiser4 File-System Benchmarks With Linux 4.17

Filed under
Graphics/Benchmarks
Linux
Reiser

It's been about three years since last carrying out any file-system performance benchmarks of Reiser4, but being curious how it stacks up against the current state of today's mainline Linux file-systems, here are some fresh performance tests of Reiser4 using the Linux 4.17 kernel. The Reiser4 performance was compared to Reiserfs, EXT4, Btrfs, XFS, and F2FS.

Read more

Reiser4 Updated For Linux 4.14 & Introduces Zstd Compression Support

Filed under
Reiser

The out-of-tree Reiser4 file-system driver has been updated with compatibility for the latest Linux 4.14 stable series. Besides reworking the code to run on Linux 4.14, this controversial file-system has also added support for Zstd file-system compression.

Linux 4.14 introduced Zstd support in the mainline kernel and wired it in for SquashFS and Btrfs. Our Btrfs Zstd benchmarks have been promising for transparent file-system compression compared to the other supported algorithms. Reiser4 has now picked up Zstd compression as an eventual replacement to their Gzip compression support.

Read more

Reiser4 Is Now Ready For Linux 4.13

Filed under
Reiser

For those wanting to use the Reiser4 file-system with the just-released Linux 4.13 kernel, patches are already available.

Less than one week after the release of the Linux 4.13 stable kernel, Edward Shishkin has already released an updated patch for the out-of-tree Reiser4 file-system for working with this new stable series.

Read more

Reiser4 Updated For Linux 4.12, Experimental Data Striping Support

Filed under
Reiser

Those using the Reiser4 file-system in some capacity can now safely upgrade to the Linux 4.12 kernel.

Edward Shishkin has updated this out-of-tree file-system for the Linux 4.12 kernel so it can be built with the latest mainline stable release.

Read more

Syndicate content

More in Tux Machines

Linux/DLSS Coverage Today

  • Nvidia's DLSS Has Come To Linux Gaming

    Years after its failed Steam Machines, Valve is slowly but surely improving the state of Linux gaming.

  • Nvidia’s DLSS has come to Linux gaming (but not the Steam Deck obviously)

    Years after its failed Steam Machines, Valve is slowly but surely improving the state of Linux gaming. The company’s upcoming Steam Deck handheld runs atop Linux, and its Proton compatibility layer lets it — and other computers — play Windows games as well. Now, Valve has officially added support for Nvidia’s DLSS machine learning temporal upscaling technique to Proton, potentially bringing big FPS boosts and less flicker in games that support the technology.

  • NVIDIA DLSS Landing On Proton Is A Win For Linux Gaming But There Are Caveats
  • Proton now officially supports Nvidia DLSS, but it won’t come to Valve’s Steam Deck | PCGamesN

    Valve is paving the way for us to ditch Windows and dive into Linux PC gaming, as the Steam Deck leads the charge with SteamOS and its Proton compatibility layer. Now, with the release of Proton 6.3-8 (via Videocardz), the company hopes to tempt even more players to jump ship with official support for Nvidia DLSS. The proprietary upscaling technology can help boost fps in games like Call of Duty: Vanguard or Back 4 Blood, without sacrificing much in the way of image quality. Unfortunately, team green’s upscaling technology won’t be supported on the Steam Deck as it uses an AMD Zen2-based SoC, and Nvidia DLSS requires an RTX chip.

  • Nvidia DLSS Upscaling Will Not Be Compatible With Steam Deck

    Upscaling is fast becoming the industry standard in modern AAA gaming, if it isn't already. Nvidia and AMD have their own versions, with Intel working on one for its upcoming range of GPUs, though "team green's" algorithm is probably the more popular one. The likes of Back 4 Blood use Nvidia's DLSS, or Deep Learning Super Sampling, with the purpose to improve visual fidelity using machine learning. However, not every system is going to be compatible with it, as it turns out that Valve's upcoming Steam Deck handheld PC won't have this specific upscaling technology. According to a recent report, it won't be possible for the Steam Deck to use DLSS, which may be a concern for some people. However, the reason why is quite simple. Nvidia's technology requires one of its own graphics cards, specifically one from the RTX range, such as the RTX 3070 Ti for example. Given that the Deck uses an AMD product under the hood, it won't be compatible with the rival upscaling algorithm. But that does mean it can run AMD's own FidelityFX Super Resolution, or FSR, instead so it will still have upscaling, just not Nvidia's. It's also possible that it could be compatible with Intel's upcoming Xe Super Sampling as well.

Today in Techrights

Devices: Raspberry Pi, Arduino, and ESP32

  • A masterclass in over-engineering

    Twitter went wild for the Robot Arm Clock featured in the new issue of The MagPi. At the last count our tweet had 1.8K retweets. We also showed you how to make Dune’s Gom Jabbar test, and we enjoyed a little Chopin as we watched a piano control LED lights.

  • Converting a Fat Cat cushion into a controller for Final Fantasy XIV | Arduino Blog

    Mounts in the video game Final Fantasy XIV act like how cars or horses do in our world since they allow players to travel around the map much faster than would otherwise be possible. But even better, mounts are ways to express personality and have some fun, which is especially evident with the infamous “Fatter Cat” mount, as it got so widely beloved that Square Enix, the game’s publisher, decided to start selling a plushie version of it in their store.

  • Unsurv offline open source, privacy friendly GNSS receiver with ESP32 & NFC

    “unsurv offline is a privacy friendly, small and lightweight PCB based on an ESP32 featuring a high quality GNSS receiver, accelerometer, and NFC capabilities. Using a combination of onboard features and OpenStreetMap (OSM) data, unsurv offline helps you collect and analyze location data in a privacy-friendly way. Originally conceived to better understand offline video surveillance, this fully open source project is here to help you find and develop a variety of custom use cases.”

today's leftovers

  • Is Linus Trolling The Linux Community? - Invidious

    Linus and Luke (from Linus Tech Tips) recently published video number two of their "Linux gaming challenge". In this video, both men had some complaints about their Linux experience so far. Linus, in particular, had a lot of negative things to say. Here are some of my thoughts on their video.

  • Bullseye

    I just upgraded my Debian GNU/Linux server to Bullseye, 11. Except for a shortage of disc space everything went smoothly. It was my fault. I created a bit too small a / partition when I moved to a newer computer… I looked around and found gigabytes of cruft I could clear out to make things fit: obsolete compilers, files I was never likely to use and I deleted a few packages I was never likely to use. Did that from my smartphone while watching old news on CNN. Went to the console for the real work which took about ten minutes.

  • OpenBSD on the VIA Eden X2 powered HP t510 Thin Client

    Back in 2017, I bought two used HP thin clients on a local auction site, the t5570e and the t510, both of them powered by VIA x86-64 CPUs. In this article, I will focus on the t510, which is the more powerful of the two.

  • Open-Source Virtual Assistant Almond Renamed Genie

    Genie (and Almond) were designed as an alternative to Alexa, Google Assistant, and other common voice assistants. Stanford computer systems designer Dr. Monica Lam set up OVAL to create a decentralized virtual assistant that stored and shared information based on user preferences, without mandates from a company. Almond’s success led to discussions of a rebrand to go with making a commercial product out of the academic experiment. The group wanted to come up with a word that would be useful regardless of the language spoken, thus accommodating international users. The researchers considered other names, like Coco, Mario, and Nico, before settling on Genie as the best option, one unrelated to the Genie virtual assistant developed by Disney for its theme parks and resorts or Alibaba’s Tmall Genie voice assistant.

  • The fish shell is amazing

    I’ve been lurking the fish shell for a couple of years now (and the nushell but it is another story for another time). Not so long ago, I decided to try it, and it’s simply… amazing. If I had to state one feature that makes me like to use it, it’ll be the autocompletion, hands down. It’s the first time I just take a shell and without customization it’s pleasing to use.