steve_v

Muchus Agreeus, although it's not the NSA or Micro$haft data-mining that bothers me, more the pervasive "users are dumb, hide all the things" attitude. I'll use Windows if I have to, but it always feels like I'm renting time on someone else's machine... I like my systems to be under my control, and be free to make them do what I want them to. The whole "Computing as a service" thing, and the "Sit back and let MS take care of everything" marketing drive just don't sit right with me. I want to break it, I want to fix it. I want to learn how it actually works. To quote Eric S. Raymond: "Trying to learn to hack on a Microsoft Windows machine or under any other closed-source system is like trying to learn to dance while wearing a body cast." The excessive phoning-home in Win 10 is just the final straw. And yeah, on that "half broken game" bit... don't get me started. Just don't.

Agreed, I like mostly-SRB first stages, but it's pretty hard to find a reason to use them now as LF boosters are far more efficient and not too much more expensive. Eh, I guess bigger SRBs would be nice, but I'd prefer a simple toning down of the nerf-factor.

I've owned 3dfx, Intel, and Nvidia "accelerator" cards, besides many other 2d-only boards... I once owned an ATI card for all of 2 hours. I can't remember exactly what it was (supposedly equivalent to an 8800GT), but it was horrible. And the Linux driver was pure trash, in fact the worst driver I have ever been unfortunate enough to encounter. Returned immediately and never again. Personal bias accrued through small sample size experience and all. I'm sure they're much better now, but damage done. Current GPU: GTX680 (x2)

For the love of Dog, why? Whatever, so long as it doesn't compromise development on other platforms. But it feels a little like someone is setting things up for an epic fail, no? The game performs like unmentionable on high-end PCs as it is. And Flying Tiger, of all the outfits to pick, is going to make it work on that anaemic (~1.2Ghz PowerPC-ish) system? Really? Good luck and all that, FT. I suspect you're going to need it. I just hope your customers won't want more than ~100 parts in scene.

I've been "daily driving" GNU/Linux for ~15 years... So I recon it'll stay that way.

binfmt_misc / filetype magic should take care of the "open with mono" bit. As such, you should be able to simply execute the binary as if it was native. Any binary in your $PATH environment variable (e.g. stuff in /usr/bin/) can be invoked by name from anywhere, otherwise needs full path on the command line. Shorthand for the current working directory is './', so './ckan.exe' should work just like 'mono ckan.exe' or '/usr/bin/mono ./ckan.exe'. As far as "Program files", there is no equivalent. *nix locates files by function not by package, so all binaries go in e.g. /usr/bin/ and all libraries in /usr/lib/, regardless of what software package they belong to. See the Filesystem Hierarchy Standard for details. ---more "on topic"--- This "double clicking" thing everybody seems so enamoured with... It depends on your desktop environment. If you're using GNOME/MATE/Nautilus (I think that's what Mint ships by default nowadays), IIRC there's something like "Allow executing file as program" in the properties tab for the script in question, or "Run executable text files" somewhere in Edit -> Preferences menu. I run KDE mostly, but haven't actually bothered figuring this out myself, I just have "alias ksp='cd ~/Games/KSP_linux; ./KSP.x86_64'" in my ~/.bash_aliases, so I can enter "ksp" in a terminal to start the game. Likewise for ckan.

I assume you got '-bash: ./KSP.x86_64: Permission denied' Execute bit probably not set, though it is in all the KSP/Linux downloads I have seen... Try 'chmod +x ./KSP.x86_64' - - - Updated - - - More accurately, you must supply full path to execute files that are not in your $PATH, in this case './' simply denotes the current working directory.

Desktop/Games: 16GB Web/file server: 24GB Retro-gaming machine: 32MB Number of operational* Windows (10 or otherwise) installs: 0 *since I accidentally wiped out that silly "system reserved" partition while installing Solaris, and can't be arsed fixing it.

And the parts of course... all of which your local radio-shack equivalent (or rs online) should have, for far less total cost than a manufactured cable.

I barely played the last release at all, as I'm still waiting on reasonable performance and bugfixes. 1.0.x was slower and buggier than ever, here's hoping that 1.1 will see the game actually running at a reasonable framerate, without stuttering, OOM crashes (bug-free x64 please), or random overheating. As for new parts/features, they look cool but: meh. Mods are usually better anyway.

Cool.

As long as no pitchfork-wielding occurs if it goes horribly wrong, though this is pretty unlikely. Can't really help with finding correct firmware though, as I don't have that phone. I should also note that flashing a non-samsung ROM will break kies... which is one of the reasons I don't use it.

The answer to both questions depends on whether it's just a cosmetic / stock app loadout 'branding' or a full sim-lock. As you stated you aren't locked to '3' sim, you should be good to flash any compatible rom you please. This also opens possibilities well beyond the stock firmwares... Again, search xda for your model. I personally like an AOSP or CyanogenMod based rom with minimal bloatware. There probably is a way to do it with kies, but I've no experience with (or use for) that particular application.

Short version of "flash firmware from a non-rooted ROM/stock recovery": Get firmware files and Odin (not my upload, YMMV). Reboot into 'download mode' by, IIRC, holding 'volume down', 'home' and 'power' buttons from a cold (battery out) shutdown. Kill any open kies and ensure appropriate USB drivers are loaded on PC. Then Open Odin, connect phone and wait for detection. Select appropriate firmware files and proceed with flash. When complete, reboot phone into new OS. More to be found by searching xda. Spot on Nibb31, but you did miss that all-important 'a' Also, you should be able to do this even with a 'branded' phone, but you will want to ensure you have a backup of the stock ROM, and trawl xda for any special software you may need for your carrier.

My approach would be: Flash ClockworkMod recovery -> download appropriate ROM image -> flash ROM from recovery, but I ditched kies about 5 minutes after getting the device. You could try grabbing the official image for your model / country and flashing it manually with kies or from (stock?) recovery though, looks like 5.0.1 is available for most models now.

AFAICT, the only thing the non-GPL (PUEL) licensed version brings is USB2 support. Though it may still be worth looking at if it's a few versions ahead of the packages in the repos. Yeah, it's going to work better with a real GPU.

@ebigunso: y u still no post dmesg output? Want help or not?

FWIW, Linux doesn't need to get the device details from the bios nowadays, unless you need to actually boot from it. Unless the BIOS intentionally lies about it, the driver will pick it up after the kernel boots anyway. If "Buffalo 0001" is indeed the USB disk, setting it to HDD emulation probably caused the BIOS to try booting from it. This would explain needing to disconnect it to boot, and also indicates that the BIOS sees it just fine. - - - Updated - - - If it were me, I'd crack open the USB case at this point and plug the disk inside into an internal SATA port to make sure it's OK. But that's just me, and I dislike/distrust external spinning disks generally. Also, USB disks are often cheaper here than the identical model without the case..? Not sure how that works, but I now have a bunch of "free" USB-SATA adaptors.

Post the last 20 lines or so of output from the 'dmesg' command (or that which looks relevant, see my post above), executed a few seconds after un-plugging/plugging the drive. The fact that your "cdrom" device, has a Windows 'Autorun.inf' on it suggests that it's some kind of fake drive, possibly created by some 'enhanced feature' software shenanigans on the USB device - see above post re. garbage-ware.

But, AFAIK, the joystick support issue that started all this falls into the former category.

I know most of us here have become accustomed to the bugs and endless crashing, we've all had the "it's Unitys fault" excuse drummed into us over and over again. But if you take a step back for a moment, from the point of view of someone who hasn't followed the development (or lack thereof) so closely, it's a pretty dismal effort. The game is slower and buggier than ever before, the only things that have changed are the label and the price. If you put a big "now released" sign up, and you want to charge release grade prices, people are going to expect a product that actually works properly. Enough with the excuses already. Fix It. Unity 5 is not a magic fix for all the problems, and anyone who thinks it will be is going to be disappointed. Again. "Open a support request" is pretty pointless, the only support you'll get is "It's Unitys fault, can't fix" or "here's a partial (non-squad) workaround". As usual.

Yeah, this^. How many complaints about the comprehensive brokenness of this "release" does it take for Squad to take bugfixing seriously? 1.x is the worst release yet. A large number of well known bugs from "alpha" are still not fixed, new bugs have been introduced, old players are left swinging waiting for a playable release (since the last that could be called that is no longer on the store) and new players are expected to pay ~2x the price of the early access for a game that is even more broken. The OP may be overreacting, but joystick support isn't exactly a new and experimental feature - It's completely reasonable to expect that simple functions like this work out of the box. Of course, the joystick issues are only the tip of the iceberg.

Sad but true. KSP is not release quality, not even close. It's an alpha quality game, with a big "1.x" hastily slapped on the side and a price tag to match. Here is a) an overreaction, and a perfect example of why all the major bugs need to be sorted ASAP. It turns people away from the game real quick.

Nvidia cards are certainly better supported under GNU/Linux, and IME tend to be slightly faster (and slightly more expensive) than the comparable AMD offering. But in reality it's neck-and-neck, and which is better value depends on the month you ask.

I am, if you discount cross-platform stock bugs. The only issue I had is that in-game AA/PPFX is broken... but forcing AA with the Nvidia drivers works fine. 40+mods, ~7GB memory usage. Watch out for mod-induced lag/garbage churn though.