Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft's Linux Kernel

github.com

Post reply on HN
Print view View original

421–430 of 532 posts

Re: Microsoft's Linux Kernel

#421

Post by [deleted] »

ex3xu wrote: post #403
rbanffy wrote: post #347

Earlier quoted context omitted.

> I find it fairly easy to work on both Mac OS X, Linux and WSL2 -- but not pre-WSL Windows The thing that annoys me most on Windows is Windows itself. After using Linuxes for almost two decades now, the notion of the OS taking tens of minutes to self update when all I wanted was to quickly reboot it is unbearable. > I don't know how/if they're going to handle freeing memory again -- here the NT kernel really needs t…

> The thing that annoys me most on Windows is Windows itself. After using Linuxes for almost two decades now, the notion of the OS taking tens of minutes to self update when all I wanted was to quickly reboot it is unbearable. This is definitely a problem especially considering that the shotgun approach to some Windows updates actually hurt the performance of some machines, even breaking Windows on occasion [0]. Howe…

[deleted]

Re: Microsoft's Linux Kernel

#422

Post by robrtsql »

ndarwincorn wrote: post #385
dingu wrote: post #250

Earlier quoted context omitted.

> YMMV, but as far as I know that's more or less a solved problem by default (for X anyway) with DRI3. https://wiki.archlinux.org/index.php/NVIDIA_Optimus LOL. What a bunch of crap.

If you're gonna reference the wiki, cite the right article[1]. Under the 'GPU Offloading' heading (the feature most folks want in dual discrete/integrated laptops): > Note: This setting is no longer necessary when using the default intel/modesetting driver from the official repos, as they have DRI3 enabled by default and will therefore automatically make these assignments. Explicitly setting them again does no harm,…

Most people want to use the proprietary drivers, because nouveau's performance is prohibitively low for gaming. And that only supports switching GPUs with a reboot.

It does work, but it's not very nice, which is what we are upset about.

Re: Microsoft's Linux Kernel

#423

Post by slantyyz »

bnt wrote: post #414
slantyyz wrote: post #409

Earlier quoted context omitted.

FWIW, when I switched from Mac to Windows, I was able to still do Rails development in Windows itself (I guess it ultimately depends on your Rails app complexity and the gems you rely on) and deploy my solutions to Linux servers. This was before WSL came out.

For sure, but it was pretty slow (every page reload took ages) and with WSL it is much faster.

Really? That's interesting.

I don't have that experience running Rails on Windows. Having said that, I do use thin for my development instance, so maybe that's why.

Re: Microsoft's Linux Kernel

#424

Post by nolok »

dehrmann wrote: post #413
nolok wrote: post #323

Earlier quoted context omitted.

Ahhh, the eternel dilemna they face. Either recreate the wheel and get complaints about that, or re-use the wheel and have people "crack up" about you doing that.

What cracks me up is the irony of seeing ...\etc\hosts on Windows, not the entire decision.

Then I don't understand your comment. What's the irony in there ? Or do you mean humor instead of irony / is it not irony at all ?

Re: Microsoft's Linux Kernel

#425

Post by dang »

Keyframe wrote: post #303
monkeydust wrote: post #297

Earlier quoted context omitted.

I still spend 80% of my workday on a PC running windows. So not sure I agree.

Oh well, if YOU spend 80% of your workday on a PC then it must be true for everyone.

Please don't be snarky here.

https://news.ycombinator.com/newsguidelines.html

Re: Microsoft's Linux Kernel

#426

Post by Sangeppato »

cmiles74 wrote: post #393
fortran77 wrote: post #392

Earlier quoted context omitted.

From the very start, the NT micro kernel was designed with multiple OS APIs in mind. They implemented a Posix subsystem decades ago.

I think it's a little sad that they are going this route (wrapping a running Linux kernel) rather than working to improve Windows disk performance and continuing to improve their WSL 1.x product. It looks like they are missing out on an opportunity to improve the NT kernel for what looks like short-term gain.

I don't think they could improve I/O speed without modifying NTFS itself (unlikely). This new approach is certainly easier to maintain and develop

Re: Microsoft's Linux Kernel

#427

Post by posix_me_less »

tjoff wrote: post #288
posix_me_less wrote: post #285

Earlier quoted context omitted.

It is not false. Complaining about obscure gpu driver feature not working in Linux kind of proves the parent's point. Most usual hardware works out of the box on Linux now, except for the nvidia cards, but even that can be made to work with their binary driver. If the AMD driver does not support some obscure feature, that is on AMD. They work on it, complain there, but naturally some things have higher priority than…

I'm not blaming linux for manufacturer not supporting linux well enough. But I'm stating drivers are an immense issue for linux - regardless of who is to blame. Maybe I shouldn't have started with an "obscure" example. Maybe that the driver crashes if displays are awakened from sleep? Mind you - only waking the screens from sleep, not the entire system (that doesn't work either, but I don't know which driver that is…

Yeah, those other issues are real and they suck, especially when one uses the most up-to-date software and they still happen. Point taken.

Re: Microsoft's Linux Kernel

#428

Post by mamcx »

AnIdiotOnTheNet wrote: post #154
mamcx wrote: post #143

Earlier quoted context omitted.

No, but I suspect the array of devices is more narrow than suspected? I think that nail the software (app + dev experience) is a bigger challenge and priority than worry about the (external) hardware. P.D: One thin I forget to articulate is the possibility to leverage linux as a bridge for drivers (possible)? so the new OS ship a smallish linux just for get compatibility.

Then you're just making a Linux distribution, or something like Android I suppose. You may as well say extending Chromium would solve the web monoculture issue. That isn't how it works. > I think that nail the software (app + dev experience) is a bigger challenge and priority than worry about the (external) hardware. You are ludicrously wrong. Using the Linux kernel as an example, because drivers are in-tree, as of 4…

I stand corrected :)

Re: Microsoft's Linux Kernel

#429

Post by h1d »

ChuckMcM wrote: post #51

Well that is pretty nice. WSL gets that much more exactly like Linux. What I really appreciate about WSL is that you get the accessibility of a bunch of OSS projects and a machine which has legit drivers for all of its component bits. What this means to me is that searching for a "linux laptop" won't be a chore, if it runs the latest Windows it will run Linux. And I can do development on the Linux side while communic…

That was possible for quite some years if you'd just used any VM solution locally and just SSH into it. At least VMware has decent file system performance when VirtualBox doesn't.

Re: Microsoft's Linux Kernel

#430

Post by ex3xu »

gambiting wrote: post #417
ex3xu wrote: post #403

Earlier quoted context omitted.

> The thing that annoys me most on Windows is Windows itself. After using Linuxes for almost two decades now, the notion of the OS taking tens of minutes to self update when all I wanted was to quickly reboot it is unbearable. This is definitely a problem especially considering that the shotgun approach to some Windows updates actually hurt the performance of some machines, even breaking Windows on occasion [0]. Howe…

So after a very long hiatus I have decided to try installing linux on a raspberry pi - and wow, the results were amazing. Using my decade-old knowledge of using fstab I added some drives to /etc/fstab and rebooted. Oooops. Raspbian would fail boot with a message "root account locked, couldn't open console". Fantastic - so if any of the fstab entries are missing, the entire system effectively bricks itself. The only w…

With great power comes great responsibility, I guess. I agree it would have been nice for Linux to come with a few more sanity checks by default, like maybe a warning flag for rm -rf /* and dd commands...
Post reply on HN