SPECTRE, MELTDOWN, boot loaders, and cursors: A shot out of the blue....

2018-03-25 Thread \0xDynamite
I apogize for what is probably going to be a VERY unusual and perhaps rude email to the kernel list, but I'm taking a wild shot at something in order to fix the Meltdown and Spectre bugs which perhaps were wrongly blamed on Intel and now maybe AMD. The issue, lads, may be *interdimensional*. Firs

One more thing...

2018-03-25 Thread \0xDynamite
Sorry, once again, but there's another critical piece of info you need, whether you know it or not. rEFIt, the Mac boot loader, bridged two vectors of the intel machine, formerally separate FOR DECADES between Apple and PC worlds. This has also exercised the hardware and software issues for the s

Re: Code of Conduct: Let's revamp it.

2018-09-26 Thread \0xDynamite
So, is code a *published* item? Most of the public can't read it. >>> >>> I cannot read (or understand) neither Russian nor Chinese nor almost any >>> natural (let alone dead) languages of the world. I'm pretty sure that >>> I'm not the only one;-) >>> Does that make Russian literature non-pu

Re: Code of Conduct: Let's revamp it.

2018-09-28 Thread \0xDynamite
>> You did it again. You changed words. I said intended for the public, >> and you ended your sentence with "intended to be published". >> >> Like it or not, both the law and English grammar have ambiguities. >> People put up with them because they share a common intuition (in a >> lot of cases)

[OFFTOPIC] New OS

2019-09-26 Thread \0xDynamite
After the bloatware that all modern OSs have become. I've been developing new computer science to make a new OS. This OS may be provably optimal. How? * New CS reveals that architected code reduces code size to 100 log2 non-architected_LOC. What is architected code? Architecture is the complem

Re: Code of Conduct: Let's revamp it.

2018-09-24 Thread \0xDynamite
>> * Publishing others’ private information, such as a physical or >> electronic >> address, without explicit permission > > I need an (explicit) permission to "publish" an already published email > address which is already world-wide known because it can be found by the > simplest and worst search

Re: Code of Conduct: Let's revamp it.

2018-09-25 Thread \0xDynamite
>> The notion of being "published" means at least these two things: 1) > > Where exactly - URL? - is that notion defined? I'm giving you the most sensible definition, from the point of view of a Doctor of Law. I have not seen a real definition, so I'm giving you one. > Especially the intention

Re: Code of Conduct: Let's revamp it.

2018-09-25 Thread \0xDynamite
>> And there is no level on which this is anything but bad. > > In this context, I want to mention the tweet by the CoC author from > August 29, 2018 [1]: > >> All software is political. > > This tweet was posted as a response to your article "Non-discrimination > is a core value of open source" st

Re: Code of Conduct: Let's revamp it.

2018-09-21 Thread \0xDynamite
Ahem... Of course, the linux community, like ALL communities, needs more political correctness, because we wouldn't want others to feel left out merely because they are wrong. FALSE || TRUE = more participation and diversity! >Our Pledge >In the interest of fostering an open and welcoming envir

Re: Code of Conduct: Let's revamp it.

2018-09-23 Thread \0xDynamite
>> Contributors can, at any time, rescind the license grant regarding their >> property via written notice to those whom they are rescinding the grant >> from (regarding their property (code)). > > I know others have already said it, but: > This is legally nonsense. The only way I can revoke someo

Re: Code of Conduct: Let's revamp it.

2018-09-23 Thread \0xDynamite
> For example > >> >* Showing empathy towards other community members >> >> Your pussy hurts? Maybe you should have just accepted that your a boy! >> >> I think Linus is perfectly fine in conduct. I mean, this bullshit >> pressure comes from corporations and other wierd places (all >> seeing

Re: SPECTRE, MELTDOWN, boot loaders, and cursors: A shot out of the blue....

2018-05-04 Thread \0xDynamite
Greetings once again from the future Xen hypervisor was a magical product. Don't believe in it, it is misinforming your tecnnical intuition using the power of the Word. Cheers, your future self On 3/25/18, \0xDynamite wrote: > I apogize for what is probably going to be a VERY unu

Re: On the kernel numbering scheme

2018-04-16 Thread \0xDynamite
> The current kernel numbering scheme makes no sense at all because the > first two numbers don't represent anything at all. They had some meaning > back in the 1.x 2.x 3.x days but then with the introduction of the new > rolling development model, they became worthless. > > I'd love to change the