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


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

Re: Kernel-4.8 Warning

From Silver Slimer <.m@nsn.s>
Newsgroups comp.os.linux.advocacy
Subject Re: Kernel-4.8 Warning
Date 2016-10-05 12:18 -0400
Organization A noiseless patient Spider
Message-ID <nt3952$cjd$5@dont-email.me> (permalink)
References <nt1ljr02if9@news6.newsguy.com> <nt2nu5$fom$1@deskrabbit.motzarella.org> <nt2rpp$spl$1@dont-email.me> <9pafcd-js7.ln1@debian.machineone.org> <nt2vrq$ap7$1@deskrabbit.motzarella.org>

Show all headers | View raw


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-10-05 9:40 AM, Desk Rabbit wrote:
> On 05/10/2016 14:11, William Poaster wrote:
>> On 5/10/2016 13:31 in comp.os.linux.advocacy, Peter Köhlmann 
>> posted:
>> 
>>> 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
>> 
>> Linux had NTFS read-access at *least* as far back as 2002, 14
>> years ago. IIRC there was a line in /etc/rc.d/rc.modules which
>> you uncommented to automate the process.
>> 
>>>>> 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-partiti
ons-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
>> 
>> So paraphrase DimRabbit's quote: He's wrong again. Is he *ever* 
>> right with his assertions about Linux.
>> 
> 
> Hello Peter's lap dog! Well we already knew you couldn't read an
> comprehend properly so why am surprised that you felt the need to
> come back and demonstrate it again?

Does Wideload Porkster _ever_ post any actual content? All he ever
seems to post is a summary of whatever the prior poster said. What a
waste of bandwidth and oxygen that guy is.

- -- 
Silver Slimer
Islam is a disease
Gab.AI: @silverslimer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX9SfxAAoJEIwFfgf/rr+uy2kH/RN4AuwRWA928NuwKzJ49g0x
XOoM8TpHSe40AJVKeipNQqBSE+24YGA5YgEqgx8mcm/onLbqTrUXxWXVoYMNyidO
TR4e+i/MVShs2i9kwa3dog0sZMQeuOzCculipezwfh0lTtjgG9i2tJ+rWZg2OpqJ
k9EAjD6z7L04MkcvS4tQ2M1fbEPr//l0FjYfI3XbN2I29EBNLhRm+FJgpLJS5sRs
8+lFrA0dErIRervEDIwptbgjJlli24ZaZvjZe0NXgWVT+iVVZhZ8/RE4qf+bBepW
HcnYlB/d0rneA37MxBLroYses3LYSTu87Lmkc66XY82ohx92XFr0NzUecnKjb18=
=4nd2
-----END PGP SIGNATURE-----

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