The operating system wasn’t always known as Cub Linux. In actuality, when it first got announced back in 2014, Chromixium OS was what it was called. After a year of its announcement, its first stable version hit the open-source world as a 32-bit live ISO.

With that being said, this release didn’t go as smoothly as planned. There were several bugs reported by its users, which included slow menu generation and screen tearing. On the bright side, the developers soon got to solving these issues and released a service pack in addition to various updates. However, what really took Chromixium OS to the next level was the release of its 64-bit version in November 2015.

All of this development hit a roadblock when the owner of Chromium and Chrome OS, Google, sent a request to the operating system’s developers to give up the name ‘Chromixium’ and other related social media presences websites. However, that couldn’t stop the head of this project, RichJack, as they soon addressed this issue and renamed their OS as Cub Linux. These events took place in late 2015 and ended on a positive note, but the project didn’t know what was approaching its way in 2016.

When 2016 was nearing its end, Cub Linux users started noticing one big thing: the official website had been missing. This turned out to indicate the demise of a project that could have done wonders in the future. Even though their GitHub page is open to this very day, the development had stopped, and there was no point in keeping up with Cub Linux anymore. According to a developer, this project’s sudden end could be attributed to “private life restrictions,” which is as vague as a statement could get.

With that being said, as far as the future of Cub Linux is concerned, many other developers got interested in this project and wanted to pick it up. Accordingly, the Feren OS developer announced in 2017 that he would give Cub Linux a major overhaul and “bring back Cub” with the name of Phoenix Linux. This might seem like good news to some, but honestly, the future of Phoenix Linux doesn’t seem too bright since the project hasn’t received another update since March 2018. If we’re really hopeful, we’ll get something as soon as 2021, but waiting any longer wouldn’t make much sense.

            GDB 10.1 released!

Release 10.1 of GDB, the GNU Debugger, is now available.  GDB is
a source-level debugger for Ada, C, C++, Fortran, Go, Rust, and many
other languages.  GDB can target (i.e., debug programs running on)
more than a dozen different processor architectures, and GDB itself
can run on most popular GNU/Linux, Unix and Microsoft Windows variants.
GDB is free (libre) software.

You can download GDB from the GNU FTP server in the directory:

        ftp://ftp.gnu.org/gnu/gdb

The vital stats:

  Size   md5sum                            Name
  21MiB  1822a7dd45e7813f4408407eec1a6af1  gdb-10.1.tar.xz
  39MiB  67b01c95c88ab8e05a08680904bd6c92  gdb-10.1.tar.gz

There is a web page for GDB at:

        http://www.gnu.org/software/gdb/

That page includes information about GDB mailing lists (an announcement
mailing list, developers discussion lists, etc.), details on how to
access GDB's source repository, locations for development snapshots,
preformatted documentation, and links to related information around
the net.  We will put errata notes and host-specific tips for this release
on-line as any problems come up.  All mailing lists archives are also
browsable via the web.

GDB 10.1 includes the following changes and enhancements:

* Support for debugging new targets:

  - BPF  (bpf-unknown-none)

* GDBserver support for the following targets:

  - ARC GNU/Linux
  - RISC-V GNU/Linux

* Multi-target debugging support (experimental)

* Support for debuginfod, an HTTP server for distributing ELF/DWARF
  debugging information as well as source code.

* Support for debugging a 32-bit Windows program using a 64-bit Windows GDB.

* Support for building GDB with GNU Guile 3.0 and 2.2 (in addition to 2.0)

* Improved performance during startup through the use of threading
  during symbol table loading (an optional feature in GDB 9, now
  enabled by default in GDB 10).

* Various enhancements to the Python and Guile APIs

* Various TUI Mode fixes and enhancements.

* Other miscellaneous enhancements:

  - Detection when attaching to a process of a mismatch between
    this process and the executable previously loaded into GDB.

  - Support for default arguments for "alias" commands.

* GDBserver support for the following host triplets has been removed:

    i[34567]86-*-lynxos*
    powerpc-*-lynxos*
    i[34567]86-*-nto*
    bfin-*-*linux*
    crisv32-*-linux*
    cris-*-linux*
    m32r*-*-linux*
    tilegx-*-linux*
    arm*-*-mingw32ce*
    i[34567]86-*-mingw32ce*

For a complete list and more details on each item, please see the gdb/NEWS
file, available at:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;...

-- 
Joel Brobecker

• Ncmpcpp: The Best MPD Client With The Worst Name - YouTube

  I picked a good place to start with MPD client, I think it's fair to say that ncmpcpp might be one of the best mpd clients that exist, I'll be trying out other but I don't know how anything will top this one.

• Things I do: Proposal to add build graph output to GNU Make

  In 2015 I worked as a consultant at a large company in Lund. My position was with the build team and one of our responsibilities was managing and maintaining the build system for their Android based phones.

  The problem I was tasked with solving was the fact that running 'make' for a product after a successful build resulted in a lot of stuff being rebuilt unnecessarily.

  A stock Android build tree behaved nicely: a second run of 'make' only produced a line about everything being up-to-date. But the company products were taking a good 15 minutes for a rebuild even if nothing had been changed.

  The Android build system works by including all recipes to be built (programs / libraries / etc) using the GNU Make include directive, so that you end up with one giant Makefile that holds all rules for building the platform. Possibly to avoid the problems laid out in the paper Recursive make considered harmful.

• Sébastien Wilmet: gedit crowdfunding

  The gedit text editor has a long history of development, it has been created in 1998 at the beginnings of GNOME. So it is one of the oldest GNOME application still alive and usually installed by default with Linux distributions that provide GNOME as their desktop environment.

  It is this – the fact that many Linux users know and have gedit installed – that motivates me to improve it, to make it a top notch core application. It is not an easy undertaking though, the codebase is old and large, and there are several underlying software components (libraries) that are critical for the main functioning of gedit.

release notes:

  A spate of bugfixes, new support for nanosecond mtime, etc.

README excerpt:

  GNU RCS (Revision Control System) manages multiple revisions of files.
  RCS can store, retrieve, log, identify, and merge revisions.
  It is useful for files that are revised frequently, e.g.,
  programs, documentation, graphics, and papers.

NEWS for 5.10.0 (2020-10-20):

  - bug fixes

    - RCS file search skipped RCS/FILENAME by default

      The default set of candidate filenames for the RCS file is:

       RCS/FILENAME,v
       RCS/FILENAME
       FILENAME,v

      RCS 5.8 (released 2011-08-30) introduced a bug which caused the
      default RCS file search to skip RCS/FILENAME.  Regression fixed.

    - ‘rlog -w’ behaved like ‘rlog’ (sans ‘-w’)

      RCS 5.8 (released 2011-08-30) introduced a bug which caused
      ‘rlog -w’ (without any logins specified) to fail to default to
      the user login.  Instead it behaved as if option ‘-w’ were
      omitted entirely.

      The cases where logins are specified (e.g., ‘rlog -wjrhacker’)
      were not affected.

    - missing string in comma-v detected, diagnosed

      Previously, if foo,v contained fragment:

       1.1
       log
       text
       @@

      i.e., there was no string value following the ‘log’ keyword,
      then rlog (et al) would interpret that as an "empty log message"
      instead of as a violation of the RCS file format grammar, which
      stipulates that a string value must follow the keywords ‘desc’,
      ‘log’ and ‘text’ -- (info "(rcs) comma-v grammar").

      Now, such a situation causes rlog (et al) to abort w/ message
      "missing string after KEYWORD" (KEYWORD ∈ {desc, log, text}).

    - subsecond resolution maintained for ‘-d’, ‘-T’

      An RCS ‘delta’ includes a ‘date’ component w/ second (whole
      number) resolution.  Previously, on filesystems that support
      subsecond (fractional) resolution for the file modification time
      (aka "mtime"), RCS commands given the ‘-d’ and/or ‘-T’ options
      would disregard, on read, and specify 0 (zero), on write, the
      fractional mtime.

      Now, RCS preserves subsecond mtime in those cases.  More details
      in new manual section -- (info "(rcs) Stamp resolution").

  - portability fixes

    - now buildable under ‘gcc -std=c11’ (default for GCC 5)

      RCS previously failed to build under ‘-std=c11’, which happens
      to be the default mode of GCC 5.  In particular, ‘-std=c11’ is
      more strict about function attributes syntax than ‘-std=c99’.

      Now, the offending code has been rectified.  (Specifically,
      attribute ‘_Noreturn’ now is at the start of a func decl.)

    - threads support

      RCS itself is clueless about threads, but it uses gnulib, which
      may or may not require threads support.  This manifests as the
      configure script options ‘--enable-threads=MODEL’ as well as
      ‘--disable-threads’.

      Previously, "make" would ignore MODEL (even implicitly), acting
      as if ‘--disable-threads’ were specified.  Now, it takes into
      account MODEL by propagating makefile var ‘LIBTHREAD’.

    - consult ‘USER’ first if ‘LOGNAME’ read-only

      To determine the user (login) name in the absence of a specific
      command-line option, RCS normally checks first the env var
      ‘LOGNAME’ and second, ‘USER’.  Alas, this is unworkable under
      AIX, where ‘LOGNAME’ is read-only.  So now, if the configure
      script finds ‘LOGNAME’ to be read-only, it arranges to build RCS
      to check ‘USER’ first and then ‘LOGNAME’.  See README.

    - configure script avoids ‘date -r’

      Unfortunately ‘date -r’ is not POSIX.  This made AIX unhappy.

    - other AIX accomodation

      The AIX compiler complains about the implicit casting that
      occurs when returning a pointer from a function whose return
      type is ‘bool’.  So, we are now explicit.

  - documentation improvements

    - docfix: add "Log message option" to Detailed Node Listing

      Probably Emacs by now has some automagic way to sync the
      ‘@detailmenu’ section w/ the text body... hmmm.

    - style change due to ‘-zZONE’ option

      Specifying option ‘-zZONE’ to ‘rcs log’ changes the date output
      style to use hyphens (ISO) instead of slashes (YYYY/MM/DD).

    - rlog, use with CVS

      Since RCS 5.8 (released 2011-08-30), there have been sporadic
      reports of rlog (aka "rcs log") failing with CVS files.  The
      manual now addresses this -- (info "(rcs) comma-v particulars").

    - delim-separated list

      GNU RCS has always supported comma to separate items in a list
      (e.g., ‘rcs frob -o1.1,2.2’ to remove (or "outdate") revisions
      1.1 and 2.2).  But did you know that most places a comma is
      welcome and you can use other delimiter characters as well?
      Read all about it -- (info "(rcs) Delim-separated list").

    - (style) pargraphs no longer indented

      This looks nicer (IMHO) for Info and Text output formats.

  - testing improvements

    Many new tests and test cases for existing tests were added, to
    catch regressions and exercise infrequent code paths.  For "make
    check" (locally), function coverage is 97.3% (considered "high")
    and line coverage is 84.9% (considered "medium"), per lcov.

  - bootstrap/maintenance tools

    upgraded:

     GNU gnulib 2020-10-19 23:37:09
     GNU texinfo 6.7
     GNU Automake 1.16.2
     GNU Autoconf 2.69c

    as before:

     (none)

tarballs and detached signatures:

  http://ftpmirror.gnu.org/rcs/rcs-5.10.0.tar.lz
  http://ftpmirror.gnu.org/rcs/rcs-5.10.0.tar.lz.sig
  http://ftpmirror.gnu.org/rcs/rcs-5.10.0.tar.xz
  http://ftpmirror.gnu.org/rcs/rcs-5.10.0.tar.xz.sig

source code:

  https://git.savannah.gnu.org/cgit/rcs.git/?h=p

homepage:

  https://www.gnu.org/software/rcs/