Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Back for a limited time - Get 15% off sitewide on Slashdot Deals with coupon code "BLACKFRIDAY" (some exclusions apply)". ×

Comment Re:LILO? (Score 1) 135

GRUB doesn't do stages anymore. That would be a "rescue>" prompt. It's a little better, and can usually help to save from minor configuration mishaps, though not useful for more major oopses (maybe you changed file systems and forgot to update GRUB, now the boot.img doesn't understand how to read the file system...). It also gives a lot of pause to the thought of "Oh crap, what are GRUB's commands?"

Comment Re:What's it good for? (Score 1) 135

Entirely this. In my opinion grub 2 is where they really went off the rails. When you have a set of configuration files that configure the set of scripts that generate the _actual_ configuration, something has gone horribly, horribly wrong.

Those scripts and configuration files sprang into existence well before GRUB 0.97 even. In GRUB 2, they're still not required and the configuration file is not hard to hand-write if you don't want the auto-OS detection and config generation said scripts provide :P

Comment Re:Try and make an OS that viruses couldn't target (Score 2) 484

I'd add the ability to run Windows binaries in emulators, but they can't access other programs than themselves. If that was a problem, add a phantom disk image so it could see other files that you place in the phantom disk image. Imagine each Windows emulated program saw their own personal c:/ , and it and you can populate it with files.

So... Wine with a new WINEPREFIX for each program?

I figure if the software you download can't get out of the Windows emulator or its own personal filesystem, it can't mess with your OS or the rest of your filesystem. If it can't record your keystrokes unless you have the window actively open, a keylogger can't get you either. The problem is that we probably don't have perfect Windows emulation. Another problem is you have to be able to trust your drivers or that is a possible vector to an attack.

Run Wine in a Docker image? That's pretty well-sandboxed. and easy to set up.

Comment Re:Unspecified or undefined behaviors (Score 1) 172

Wine is a compatibility layer for Windows applications. It must emulate all of Windows' bugs and undefined behavior to the best possible extent, even containing a whole bunch of case statements to change its behavior when different versions of Windows are set via winecfg (not unlike Windows' own compatibility mode, which tends to just have every version of every DLL ever in WinSxS to solve the problem...).

To Wine, Windows bugs are features, and applications depend on them. Maybe it will never be perfect, but Wine's philosophy is basically "If it works in Windows, it should work in Wine" -- even if that comes down to an application running in Windows 95 but not later versions, Wine will try its best to keep that Windows 95 app running, even if you have to set the Windows version to 95 via winecfg. If the app doesn't run, it is a Wine bug.

Comment Re:Sounds like someone is getting old... (Score 1) 716

It still does, so long as you're selective of the software you run on it. You could run a totally modern kernel and (or Wayland) on an original Pentium with 32MB of RAM, but in no way should you expect to run GNOME or LibreOffice or Chrome or Firefox on it, at least not without glacial loading times.

But more frequently, PCs from 10-15 years ago still in service just aren't that starved on resources anymore. They'll chug along slowly, but they can still get the job done, and nobody is really surprised when they're capable of it. Hell, if you have half a gig of RAM, you can probably still run full GNOME and LibreOffice and all without major issues.

Never say you know a man until you have divided an inheritance with him.