All Things Microsoft > Microsoft as a Company

Windows not ready for the desktop YET

<< < (5/5)

Aloone_Jonez:

--- Quote from: piratePenguin ---It's slightly faster to have the drivers in the kernel. But only the ones you use alot, the ones you only use now and again are better off as modules, although they'd usually be faster if they were in the kernel (but they'd always be in ram too).
--- End quote ---

I can see that advantage.



--- Quote from: piratePenguin ---Bad drivers don't get into the kernel source. Usually you compile a third party driver as a module, not into the kernel. Only compile the stuff that comes in the kernel source code into the kernel.
Yes, and it works.
--- End quote ---

Sorry I didn't mean bad as in shit, I meant wrong, as in what would happen if I added the wrong driver so the system wouldn't boot.


--- Quote from: piratePenguin ---I really don't see the point in the kernel programmers in spending much more time trying to get NTFS write into the kernel. Even if they get it working now, it won't work for future versions of Windows. And if it works for Windows XP, it might'nt work for Windows 2000 (I heard they're different versions of NTFS).
--- End quote ---

Sorry I was never trying to argue that read/write NTFS support is realy important. My point was that when you require it needs to be added to the kernel - you can't just add a device driver, and also there's no write access because the driver is hacked together like many Linux drivers.


--- Quote from: piratePenguin ---It's only the Windows + GNU/Linuc dualbooters that have any use for Captive NTFS, usually, and they already have the Windows NTFS driver so... It makes sense,
--- End quote ---

I agree, I bet most Linux users don't need NTFS at all.


--- Quote from: piratePenguin ---NTFS is *far* better off as a module IMO. I don't see much point in compiling NTFS *into* the kernel.
--- End quote ---

No but you do need to compile it into the kernel to use it for some Linux distros, how ever many nowadays already come with it.


--- Quote from: piratePenguin --- It could make it less stable. It *will* make it bigger (and the kernel is always in ram, of course).
--- End quote ---

Exactly.


--- Quote from: piratePenguin ---Whenever I install any GNU/Linux distro, I *never* worry about drivers. I don't even think about them. The essential stuff (for almost all setups) is in the kernel, and the other drivers are compiled as modules. No non-free drivers either (usually), because it's just the stuff from the kernel source.
I love it!
--- End quote ---

Well good for you, but spare a thought for people who aren't as lucky. :(

solemnwarning:
Windows aint ready for anything

i plugged in a freshly instaled windows laptop i was reinstalling for my mum and it thought, hmmmm 2 network adaptors?

LETS START DNS GATEWAY AND DHCP!!!!

So i spent 2 hours searching all the hubs and routers for connections that wernt supposed to be there since the winshit laptop had taken over dhcp and got all boxes on wrong ip info while setting domain to mshome.net

piratePenguin:

--- Quote from: Aloone_Jonez ---Sorry I didn't mean bad as in shit, I meant wrong, as in what would happen if I added the wrong driver so the system wouldn't boot.
--- End quote ---
As long as the right drivers *required to boot* are *in* the kernel, then it will boot. If one, say, the ext3 driver is missing, you get a kernel panic, so it's back to menuconfig.

--- Quote from: Aloone_Jonez ---My point was that when you require it needs to be added to the kernel - you can't just add a device driver
--- End quote ---
You can compile the module and load it with modprobe/insmod. Same thing.

--- Quote from: Aloone_Jonez ---and also there's no write access because the driver is hacked together like many Linux drivers.
--- End quote ---
It's the best that can be done, and it's done well. I'm happy with all the drivers that I'm using anyhow. The ISDN drivers were "hacked together" in the same way, and there is no question, the Linux (hisax) driver beats the living daylights out of MS's one (which doesn't exist) and the manufacturers ones. I couldn't get my ISDN card to work in Windows XP, even using the manufacturers drivers for Windows XP. Sometimes it would work but after a reboot I'd need to reinstall them. The Linux (hisax) driver is ****better****.

--- Quote from: Aloone_Jonez ---No but you do need to compile it into the kernel to use it for some Linux distros, how ever many nowadays already come with it.
--- End quote ---
You *never* need to compile the NTFS driver *into* the kernel. Compile it as a module, and load it with insmod/modprobe.

--- Quote from: Aloone_Jonez ---Well good for you, but spare a thought for people who aren't as lucky. :(
--- End quote ---
Heh. If their system works, they'll be fine. Printers, scanners, etc., they're a different story, and can only be blamed on the manufacturers.

Navigation

[0] Message Index

[*] Previous page