Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: Kernel-4.8 Warning

From Peter Köhlmann <peter-koehlmann@t-online.de>
Newsgroups comp.os.linux.advocacy
Subject Re: Kernel-4.8 Warning
Date 2016-10-05 15:23 +0200
Organization DNLA GmbH
Message-ID <nt2urt$7l6$1@dont-email.me> (permalink)
References <nt1ljr02if9@news6.newsguy.com> <nt2nu5$fom$1@deskrabbit.motzarella.org> <nt2rpp$spl$1@dont-email.me> <nt2u4k$4de$1@deskrabbit.motzarella.org>

Show all headers | View raw


Desk Rabbit wrote:

> On 05/10/2016 13:31, Peter Köhlmann wrote:
>> Dimbulb Rabbit wrote:
>> 
>>> On 05/10/2016 02:39, Adlbifhr Mjduhgfks wrote:
>>>> 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.
>>> 
>>> Wrong again. Are you *ever* right with your assertions about
>>> Microsoft?
>>> 
>>> https://technet.microsoft.com/en-us/library/cc781134(v=ws.10).aspx
>>>
>>
>>> 
> Well, he *is* right.
>> NTFS can be both read and written by linux since nearly 10 years.
>> Read-access works even longer
> 
> WOW! That's world class Klowning Peter. You really need to read more
> carefully.

No need. You provide a link to NTFS as "support" which MS data can't be 
accessed by linux

And don't know that the very same NTFS is both read- and writeable siknce a 
very long time

The much newer ExFAT from MS is also both read- and writeable by linux

>> 
>>>> 
>>>> How many GNU/Linux disk formats can Microshit, using the fully
>>>> open specs, read?
>>>> 
>>>> The answer is NONE.  That's NONE.  ZIP.  NADA.
>>> 
>>> Wrong again
>>> http://www.howtogeek.com/112888/3-ways-to-access-your-linux-partitions-from-windows/
>>>
>>
>>> 
>> Basically he is correct. Ext2Fsd can read EXT2, EXT3 and EXT4 Write
>> access is *dangerous* and symlinks-support is dubious
>> 
>> Other linux filesystems are unreadable by windows, such as Btrfs,
>> Xfs and Zfs
>> 
>> 
> 
> Jeez, your comprehension is well and truly broken today. Don't go
> writing any code.

Pray tell, what part of that was incorrect? 
Please show us the windows fs driver which can *safely* write to EXT2/3/4 
(naturally journaled) and provides correct symlink support
While you are at it, please show us the windows drivers which can read/write 
Btrfs, Xfs or Zfs

You are really the dumbest brick in cola, Dimbulb Rabbit

Back to comp.os.linux.advocacy | Previous | NextPrevious in thread | 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