Groups > comp.os.linux.advocacy > #374914

Kernel-4.8 Warning

From	Adlbifhr Mjduhgfks <am@random.us>
Newsgroups	comp.os.linux.advocacy
Subject	Kernel-4.8 Warning
Date	2016-10-05 01:39 +0000
Organization	NewsGuy - Unlimited Usenet $23.95
Message-ID	<nt1ljr02if9@news6.newsguy.com> (permalink)

Show all headers | View raw

Kernel-4.8 runs well, as fully expected, on my system.
Never have I experienced a problem with a new kernel.
NEVER.  That's how fantastic the Linux kernel is.

However, after booting with the new kernel I need to do
two things.

1) Compile new nvidia drivers.  I need this to run X.

With Gentoo this is NO problem.  I just execute:

emerge nvidia-drivers

2) Compile exfat kernel module.  I need this to read/write
that stupid Microshit file format, mainly for USB thumb drives.

This is also simple.  Just cd to the exfat-nofuse source tree
and execute:

make && make install && depmod -a

But this time there is an "issue" with the exfat source:

https://github.com/dorimanx/exfat-nofuse/issues/89

It seems that the exfat module folks are not keeping up with
the latest kernel changes.

Oh well.  A patch will likely be available shortly.

GNU/Linux can read/write ALL Microshit disk formats, even
though Microshit has never publicly released the specs.

How many GNU/Linux disk formats can Microshit, using the
fully open specs, read?

The answer is NONE.  That's NONE.  ZIP.  NADA.

In fact, Microshit can't read ANY disk formats other than
its own.

Can there be a better indicator of a junk OS?

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

Back to comp.os.linux.advocacy | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Kernel-4.8 Warning Adlbifhr Mjduhgfks <am@random.us> - 2016-10-05 01:39 +0000
  Re: Kernel-4.8 Warning DFS <nospam@dfs.com> - 2016-10-04 23:10 -0400
    Re: Kernel-4.8 Warning GreyCloud <Cumulus@mist.com> - 2016-10-05 00:07 -0600
    Re: Kernel-4.8 Warning Adlbifhr Mjduhgfks <am@random.us> - 2016-10-05 09:45 +0000
      Re: Kernel-4.8 Warning DFS <nospam@dfs.com> - 2016-10-05 08:54 -0400
    Re: Kernel-4.8 Warning Adlbifhr Mjduhgfks <am@random.us> - 2016-10-05 10:25 +0000
    Re: Kernel-4.8 Warning Silver Slimer <.m@nsn.s> - 2016-10-05 07:59 -0400
  Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 12:25 +0100
    Re: Kernel-4.8 Warning Melzzzzz <mel@zzzzz.com> - 2016-10-05 13:31 +0200
      Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 13:04 +0100
    Re: Kernel-4.8 Warning Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-05 14:31 +0200
      Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 14:10 +0100
        Re: Kernel-4.8 Warning Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-05 15:23 +0200
          Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 14:42 +0100
        Re: Kernel-4.8 Warning Silver Slimer <.m@nsn.s> - 2016-10-05 12:12 -0400
          Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 17:21 +0100
            Re: Kernel-4.8 Warning Silver Slimer <.m@nsn.s> - 2016-10-05 12:33 -0400
      Re: Kernel-4.8 Warning William Poaster <wp@dev.null> - 2016-10-05 14:11 +0100
        Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 14:40 +0100
          Re: Kernel-4.8 Warning Silver Slimer <.m@nsn.s> - 2016-10-05 12:18 -0400
    Re: Kernel-4.8 Warning fr314159@gmail.com - 2016-10-05 09:03 -0700
      Re: Kernel-4.8 Warning Desk Rabbit <me@example.com> - 2016-10-05 17:20 +0100

csiph-web