DonationCoder.com Forum

Main Area and Open Discussion => General Software Discussion => Topic started by: zridling on October 15, 2008, 03:26 PM

Title: Ten Tips for Windows users making the switch to Linux
Post by: zridling on October 15, 2008, 03:26 PM
Here are ten tips for Windows users (http://www.thegsblog.com/?p=98) who are considering making the switch to Linux. Details on each point and helpful links after the jump. If I can make the switch from Windows to GNU/Linux, anyone can. I’m not a programmer, not an expert, nor do I have time to endlessly futz with my system. Based on my experience over the past year, these tips will smooth your transition from Win to Lin.

[ You are not allowed to view attachments ] (http://www.thegsblog.com/?p=98)
01. KEEP YOUR OLD WINDOWS MACHINE/PARTITION INTACT
You may want some training wheels at first.

02. EXPECT A LEARNING CURVE AT FIRST
If I can make the switch, anyone can! Immersion is your best friend.

03. DON’T EXPECT LINUX TO BE JUST LIKE WINDOWS
It’s better, and you’ll soon see why.

04. WHETHER YOU USE UBUNTU OR NOT, PERUSE THEIR FORUMS TO GAIN KNOWLEDGE
Some Ubuntu forum members have written great tutorials on the intricacies of fstab, grub, virtualization, customization, etc.

05. DON’T BE AFRAID TO EXPERIMENT
It’s harder than you think to take down a Linux machine.

06. HELP IS AS NEAR AS YOUR KEYBOARD
There are forums. There are Usenet groups. There’s Google, of course. Better is Google/Linux (http://www.google.com/linux). In the end, it’s a community relationship, not a customer relationship. (A lot like DC!)

07. TAKE ADVANTAGE OF CROSS-PLATFORM SOFTWARE
You know more than you think you do, since you may already be using Firefox/Opera/Chrome or OpenOffice or 7-Zip/RAR or GIMP or MySQL or Beyond Compare or XnView/Picasa or Kompozer or FileZilla… I could do this all day.

08. TAKE ADVANTAGE OF THE CLOUD
Don’t laugh. Linux is built for cloud computing, mobile computing, thick computing, Hadron colliders, and even phones!

09. LET OTHERS KNOW YOU’VE SWITCHED TO LINUX, BUT DON’T BE A JERK ABOUT IT
Don’t be "that guy." Mac users have been this way and the whole routine gets old by the second sentence. Enjoy Linux for what it is — great code, stable OS, fast platform — not for what it’s not (Windows).

10. THE COMMAND LINE AND SHELL IS YOUR BEST FRIEND
A little command line knowledge goes a long way, but you will likely use it far less than you expect to. Its power is irresistible because it’s so efficient.

More... (http://www.thegsblog.com/?p=98)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: cranioscopical on October 15, 2008, 03:40 PM
Thanks, Zaine.  This will be an interesting one to follow...
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: fenixproductions on October 15, 2008, 06:12 PM
Wise thoughts but never worked for me. Everytime I've tried to switch there were more than 3 additional points against me which I couldn't pass right.

Why "additional"? Because 9th was always in the air :(

After few years of trying I don't see the point to change from XP.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 15, 2008, 07:04 PM
I wouldn't mind moving away from Windows, because I'm certainly not a fan of Microsoft at large, the DRM (even though that's not just Microsoft's fault), the proprietary file formats etc. But I don't want to move away when all the alternatives are inferior. Linux is not great code. Kernel and other parts might be OK, but when you start digging into the other components that make up a distribution, and start looking at some of the bitchfights... ugh. Microsoft certainly isn't perfect, but moving to that kind of infantility?

I had actually planned to dual-boot my new laptop with Xubuntu and give it a serious try, but of course the thing doesn't want to install - weird grub errors I've never seen before, and haven't been able to track down the source of. And can't give GRUB a try since, for some reason, it wants to grab that off the net. And while the pretty standard realtek gigabit NIC is detected by the kernel, there's no connectivity - some kernel IRQ routing fuckup is my guess, considering the insane number reported in /proc/interrupts .

And that's just the point where I give up. I don't want to go through a zillion hoops just to do simple things. I've used linux since RedHat 5.1, I've messed with debian, slackware, archlinux, gentoo, x/k/ubuntu and a couple of others. I've usually been able to make them do what I wanted (including DSL router/firewall, root-encrypted fileserver, various development support needs like apache/php/mysql/postgres/subversion/redmine etc.), but there's always been too much bloody work involved.

No filesystem hierarchy standard that everybody agrees on. And even when there's a somewhat similar layout, subtle (or not so subtle!) things are handled differently. A zillion different package managers, not to mention that Perl, Python and Ruby have their own systems. Makes me want to scream and knock my head against the wall.

But at least for server use, it makes sense. I can run the system headless and SSH to it, which is more efficient across the internet than remote desktop. And once you've spent all the frustrated time getting things working and firewalled the stuff, you can often let the systems sit by unattended for years (same with Windows, though. Both systems obviously need to be updated when there's vulnerable software).

But for desktops? Too much bloody work, I'd have to spend time hunting for replacement software (some of it beta and/or pretty inferior to what I have - show me a competitor to Visual Studio that isn't half-baked), and to what benefit? Sure, "freedom" - whatever that means.

Sorry for the rant, but I get frustrated when I see people claiming it's easy and full of joy to 'switch over'. Sure, it can work for some people - my mum could probably be happy with an Ubuntu, she'd still be able to play flash games, do her java-enabled web banking, surf the net, use OpenOffice and send/receive mails. And you don't need to "shop for compatible hardware" in the same sense as in the early years. But for me it's just too much frustration to be worth it :(

Oh, and that was just from the end-user's perspective. I won't go into the issues of GPL and program-for-a-living now, but that's another thing that I'm pretty skeptical about, to put it mildly.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: fenixproductions on October 15, 2008, 09:19 PM
2f0dder
100% agree.

In my case, many times the scheme was simple: Live CDs working flawless but when it goes to install... kernel panic.

He. Once I couldn't get my net working after HDD install and the only help I get was: "Google it, f*n n00b". OK, I did it. After dozen of hours in net cafeterias and many days of trying, the only thing I learnt was that "It is my fault for buying crappy wireless card". Well, it worked under Windows and any Live distro I've ever tried.

As I wrote in previous post: too many nines which drove me back to MS software. It is stupid but many times I felt too strange seeing looks full of disgust from "gurus", after they discovered that I own full-payed version of XP. It is not my pair of boots being somewhere unwelcome.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: zridling on October 16, 2008, 12:28 AM
[f0dder]:
Linux is not great code. Kernel and other parts might be OK, but when you start digging into the other components that make up a distribution....
Ah, but there's the rub. You're confusing Linux per se with any distribution. Two very different animals.

I don't want to go through a zillion hoops just to do simple things.... there's always been too much bloody work involved.
I don't doubt you had problems. I haven't had very many at all, and the ones I have had, I've been able to easily google my way out of in minutes.

No filesystem hierarchy standard that everybody agrees on. And even when there's a somewhat similar layout, subtle (or not so subtle!) things are handled differently. A zillion different package managers, not to mention that Perl, Python and Ruby have their own systems.
This confuses me. By "filesystem hierarchy standard" do you mean a particular one, such as Ext3, RFS, ZFS, Ext4? FAT, NTFS, or the traditional filesystem structure:

The mere choice of file system is great to me, and for my old data. Microsoft never got around to implementing a new FS for Vista, if you recall. Linux lets you spread the file system over as many different hard drives and partitions as you want but still appear like a seamless whole. The /home directory is always /home no matter if it is moved to a separate disk. I've only come across two package managers, rpm and deb, and LSB4 has conflated their SDKs as we speak. I don't know enough to ask about perl,python,ruby having their own.

But for desktops? Too much bloody work, I'd have to spend time hunting for replacement software (some of it beta and/or pretty inferior to what I have - show me a competitor to Visual Studio that isn't half-baked), and to what benefit? Sure, "freedom" - whatever that means.
Which software are you trying to replace? Isn't Visual Studio a Microsoft coding product for its OSes only? If it does C, then it should work, right? (I really don't know; I'm dropdead ignorant about programming.) For myself, freedom works in my favor:
- No DRM or interference with fair use content on your own system;
- no proprietary formats if I choose; open standards guarantee data portability;
- no licensing costs, i.e., no more paying for my OS. When you subsist in the lower middle class, this helps.
- freedom from Microsoft or Apple and its EULAs have been nice;
- free to read bug reports and their fixes;
- no data/email lock-in;
- freedom to choose which distro suits my needs (Windows/Mac give you one choice, theirs);
- freedom from blue screens, most all viruses, and best of all, from Microsoft's latest fiat;
- freedom from having to purchase new hardware to run every successive release;
- freedom from activation; product keys; validation; pay-per-incident support, and even a registry;
- freedom to install Linux on as many computers as I want, and have as many users on any one system, each with their own unique access, desktop setups, internet privileges (for the littlest ones) and software.

Sorry for the rant, but I get frustrated when I see people claiming it's easy and full of joy to 'switch over'. Sure, it can work for some people.... But for me it's just too much frustration to be worth it.
I can understand that. At least you're honest with yourself. As for me, it's not nearly as difficult as I was told and frankly, I haven't had this much fun on a computer since the early 90s. Use what you love; love what you use. Either way, as long as you're happy.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 16, 2008, 08:31 AM
[f0dder]:
Linux is not great code. Kernel and other parts might be OK, but when you start digging into the other components that make up a distribution....
Ah, but there's the rub. You're confusing Linux per se with any distribution. Two very different animals.
I know that "linux" is the kernel and that you should say GNU/Linux to refer to the system, and use a fully qualified distro name, and use SI-approved units like MiBiBytes etc... but I refuse to take part in that sillyness.

If you say "linux", any sane person will know you're talking about a distribution. If you say "the linux kernel", well duh. As for software and quality, there's a large subset of software used by all the distributions, so meh.

This confuses me. By "filesystem hierarchy standard" do you mean a particular one, such as Ext3, RFS, ZFS, Ext4? FAT, NTFS, or the traditional filesystem structure:
Since I say hierarchy, obviously it's the layout/structure. And no, this hasn't been properly standardized. Yeah yeah, there's the FHS (http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard), but that doesn't stop distros for doing things slightly differently. True, there's some differences between Windows versions, but at least you can look up paths in the registry. On linux, only the distribution's own tools knows where things go.

The mere choice of file system is great to me, and for my old data. Microsoft never got around to implementing a new FS for Vista, if you recall.
And I'm glad they didn't - all that SQL junk ontop of NTFS sounded like a trainwreck to me. NTFS by itself is a pretty decent and well tested FS. Sure, some of the newer filesystems like XFS or ZFS or BTRFS could be interesting - but it's not like anything stops you from porting those to Windows. People just don't seem to have much interest in doing so.

Linux lets you spread the file system over as many different hard drives and partitions as you want but still appear like a seamless whole.
NTFS junctions...

Which software are you trying to replace? Isn't Visual Studio a Microsoft coding product for its OSes only? If it does C, then it should work, right? (I really don't know; I'm dropdead ignorant about programming.)
It's a pretty well-polished programming IDE with features that aren't useful just for windows development. I've looked at code::blocks, anjuta, kdevelop and eclipse, but many are slightly buggy or outdated, and arent't really in the same league.

For myself, freedom works in my favor:
I snipped the list. But yes, some of those points are reasons why I wouldn't mind having a working alternative to Windows. I think the unconformity of distros is a problem, though, and I don't get viruses or BSODs on Windows (except for bad hardware or drivers, but that would cause kernel panics on linux anyway :)). The registry is a good thing, btw, and it's a shame linux is stuck with a cluttered mess of config files with different formats.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: ak_ on October 16, 2008, 10:42 AM
Don’t be "that guy." Mac users have been this way and the whole routine gets old by the second sentence. Enjoy Linux for what it is — great code, stable OS, fast platform — not for what it’s not (Windows).
-zriddling
Amen :)

That said, i recently installed Ubuntu on my laptop and i'm really glad i did it. It very fast (i could spend hours playing with those elastic windows) and less obscure than i expected. Wine really impressed me too. As i mainly use Photoshop and Flash for work, i never considered using Ubuntu as my main OS but now i've seen both programs running via Wine, i'm actually considering switching to Ubuntu. VirtualBox is pretty impressive too, i loved running XP through Ubuntu (yes, i have simple joys).
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 16, 2008, 11:43 AM
I don't know...

It's no harder for a person to become a "Linux  Guru" (whatever that is), than it is to become an expert in any other OS or application suite.

I wasn't a big fan  of Linux when it first came out. I had a ton of solid technical arguments as to why it wasn't really workable. But when I was being honest with myself, I realized that my real problem with Linux was that I felt threatened by it. I didn't want to have to learn a whole new OS. I was afraid my Windows credentials and work experience (both of which had cost me considerable time and capital to acquire) would suffer devaluation if Linux caught on. And even worse, to really learn Linux, I would have to become a novice again - a clueless newcomer. And that was a real problem because, quite frankly, I bathed in the glow of being The Guy people went to for answers instead of the other way around.

And then, there were all those horror stories from people that had "been there." Cautionary tales about ordinary people who innocently installed Linux only to discover that it set their computer on fire - or caused cancer in the family dog.

Scary stuff! Bad mojo, this penguin thing! :tellme:

But once I got past the angst (and my little ego trip), I discovered Linux was interesting, fun, and profitable to know. It was no harder to learn, or get good at, than anything else. And it was neither significantly better nor worse than any other family of software. It was just different.

And all the horror stories I was hearing turned out to be just that - stories. ;D

I personally find it rather interesting to hear how often Linux is criticized (usually by people that don't actually use it) for what can best be summarized as "Not Being Perfect." It's especially interesting when you consider most of the complaints are about problems with proprietary codecs and drivers (especially wifi), which are issues beyond any Linux developer's control. If Linux has compatibility issues with technology developed exclusively for Windows, it's because Linux is not Windows. (Ok Class, please repeat this three times: Linux is not Windows...) And to criticize it for that is no different than faulting a dog for not being a cat.

Well, the critics can rest easy. Linux isn't perfect. And nobody in the GNU/Linux camp that knows what they're talking about (including Richard Stallman, Linus Torvalds, et al) would claim otherwise. But that was part of the original plan anyway. GNU/Linux is easy to bash because its commitment to "openness" was designed to make GNU/Linux easy to bash. And to fix. And to improve.

Linux is a perpetual work-in-progress. So is almost everything else. The only difference is that the Linux world is completely up front about it. They embrace the unfinished. Some might even argue they revel in the fact it will never be "done." If you can live with that, then all's to the good.

But if you're the type that feels driven to hit your head against a wall when confronted by a vast selection of choices and options, then Linux is definitely not for you. And that's fine too. Just continue to use Windows or OSX or whatever works best for you. The Linux community wishes you well no matter what since personal choice is much what we're about.

[ You are not allowed to view attachments ]

And should you ever change your mind...well...you know where to find us. 8)
 :)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: zridling on October 16, 2008, 11:50 AM
[tangent]: ak_, you'll be happy to know that Adobe Flash Player 10 for Linux was released yesterday and can be downloaded. Microsoft continues its own Silverlight development.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: wreckedcarzz on October 16, 2008, 02:51 PM
FYI:

All Ubuntu based distros (Ubuntu, Xubuntu, Kubuntu, EdUbuntu, etc) are going to have the 8.10 update on the 30th, followed by several last minute updates - it may be worth giving another shot.

My opinion on why Ubuntu is still not ready for "normal users":

I personally have a problem with Ubuntu's ability for "learning users" (wannabe power users, ex: me) being able to seriously fsck up the whole OS by one bad setting line; my laptop can no longer launch the X window system because of a "tweak" I found on Google (text based computing is a serious bummer). You [advanced linux users] can go on about how you have to use sudo and that you shouldn't mess with things you don't know about, but if you never mess with anything, you'll never learn anything. But the lack of an error recovery ability is simply appalling. I'm glad I have nothing life shattering on that ex3 partition, 'cause 8.10 is going on it as soon as ATI xorg drivers are out.

I love Ubuntu, but it still needs that little bit of extra "noob friendliness" IMO. Stuff should be wizard based, and less leaning on the terminal. And... *goes off to Ubuntu forums to complain* :P

Anyways, give it a go when it comes out. Might just work for you this time around ;) :Thmbsup:
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Dormouse on October 16, 2008, 04:19 PM
My kids love Linux. They use Windows at school. but mostly use Linux at home. Prefer the depositories to searching for Windows software. Have to use Windows for some progs. Certainly not Linux gurus - but not Windows gurus either and are equally competent (or incompetent) in both.

For many people, I think the biggest problem is Linux gurus. They want simple places to go for simple answers to simple questions. Not complex answers that make them feel they don't understand, when they don't really want to understand, just to know what to do.

I've never really had any problems with Linux. Mostly because, if I can't make it work fairly easily, I give up and use another distro or use Windows for that task; and now I find Linux deals with most hardware and has progs for most of the things I do. Had lots and lots of problems with Windows because there has never been much alternative except to find a solution. So I'm less inexpert in Windows and still use it more. Looking forward to 8.10 though.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: ak_ on October 19, 2008, 06:22 PM
I have a question : i'd like to install Ubuntu on my home computer, but i know 8.10 version is coming very soon. So, i need advice.

Should i :

- Install 8.04 and then upgrade to 8.10 when it's released (assuming that upgrading is safe and won't cause any weird problem).
- Wait for 8.10 and then install it.

Thank you :)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 19, 2008, 06:24 PM
Wait it out - upgrade might work just fine, but I generally stay away from updates on any OS. Heck, even service packs for windows warrant a clean reinstall from a slipstreamed CD, imho.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: VideoInPicture on October 19, 2008, 07:49 PM
I have used various versions of Linux in the past and I've been using Ubuntu for a couple of weeks since I wanted to do some Mono programming with it and port some of my software over to Linux. This means that I need to install Mono onto Ubuntu. From my impressions as a new user of Ubuntu and it's image as one of the friendlier Linux distros out there, I have to say that Windows still has Linux beat for user friendliness. I found out that there is no official user support for the installation of Mono onto Ubuntu so I'm now trying to download a torrent of a distro where somebody has done all the dirty work of figuring out how get the Mono framework running on it.

Another big problem is the requirement to use the terminal to do a lot of the program installations and any advanced settings that are required to get some programs up and running. It's not as simple as Windows where it is often a double-click on an icon that opens a wizard to guide you through installation in a graphical way. Also, I think that there are too many Linux distros out there and this harms it because now a user has to figure out if a Linux program will actually run on his system or if he has to compile it from the source code!

I think Linux could take a step forward by doing anyway with the terminal and simplifying the installation of some programs. I don't think any user short of a programmer should have to touch the terminal.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on October 19, 2008, 09:03 PM
I really can't agree with that advise. I think most of that have been solved by the most newbie friendly distros.

The thing that I think stops me from adapting to Linux aren't those but are:

1) Understanding the whole wine upgrade thing

You need the latest wine. You need to figure out if it's a wine bug, a font bug or a Microsoft program bug. That's three too many for most users. You even have to know that Cedega not wine is for games and you need to pay for it to see the difference and you're chained to most mainstream applications because if you have a niche group like any of the DC programs and am not a true power user, damn you better be sure that your forum has as much friendly community as DC that might care enough about Linux compatibility and that's still ignoring the problem of when it's not possible.

2) Lack of people porting programs requiring to gzip or to tar to a more friendly .deb or just a repository.

I fault myself for being too lazy to focus on this and am still looking for other things unrelated to Linux but I think this catches most casual users off. 1st, the distro makes it easy for you to install stuff with package managers than it quickly jumps to difficult forcing certain niche programs to be installed from source, there's just very little middle ground like in Windows where a program requires to download a new installer like those requiring .Net

3) Lack of understanding Virtualbox

I think for most people especially those who aren't into games, this is a more viable solution than dual booting but even when you get Windows to work, the whole sharing files between both OS's I think is still IT level. I know I really couldn't get whether a Virtualized OS can read flash sticks and external HDs or it's a whole nother beast altogether.

4) The minor bugs

Again, my fault for being too busy to follow up on my Linux problem where it failed to boot and lately even the bootloader GUI seems broken and I have to go to a terminal interface but it's minor things like these that make Linux more worrying because...

5) You really can't go wrong with having a real life Linux buddy to save your ass.

And unfortunately, they're not exactly as prominent as Windows buddy and then you have to be close enough friends to them that it doesn't come off as making friends with them for the sake of using Linux but Linux is so foreign that more times than not, you are actually asking them to help you with Linux than socializing with them and these are people who've battled through it alone so it's not always a sure thing that they can appreciate your hardships when they've been more tolerant.

Also with Windows, if it dies. It's either Windows update or the virus scanner stinks. With Linux, it can be anything about anything. 
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 19, 2008, 10:41 PM
Another big problem is the requirement to use the terminal to do a lot of the program installations and any advanced settings that are required to get some programs up and running. It's not as simple as Windows where it is often a double-click on an icon that opens a wizard to guide you through installation in a graphical way. Also, I think that there are too many Linux distros out there and this harms it because now a user has to figure out if a Linux program will actually run on his system or if he has to compile it from the source code!
-VideoInPicture (October 19, 2008, 07:49 PM)

(40hz sighs and hauls his butt up on his soapbox once again.... ;D)

There are a lot of people, Linux users among them, that would agree that there are too many separate distributions. But a lot of the confusion comes from people thinking that each distribution represents a radically different flavor of Linux.

In actuality, despite the number of distributions, there are really only four major distributions: Slackware; Debian; RedHat; and SUSE. Virtually all the other distros use one of the four 'majors' as the base and build from there. In most cases, the only real differences are: what non-free software gets included; what local languages are supported; and what the preferred desktop manager is.

So in a nutshell, there's significantly less there than meets the eye.

[ You are not allowed to view attachments ]

 8)

As far as compiling packages goes, most Linux users will never need to do that unless they are installing something so arcane or bleeding edge that distro-specific precompiled packages haven't yet been made. But with approximately 18-20,000 (and still growing!) packages available in each of the major distro repositories, it's getting a little difficult to find something the average (or even not so average) user would want that isn't already precompiled.

Furthermore, there are working conversion utilities that allow you to use the packages from one distro's repositories with a completely different distro (i.e. RPM to DEB, etc.). I've used such converted packages several times when I couldn't be bothered to wait for something to be included in my preferred distro's repository and I didn't feel like compiling it on my own. And to date, I never experienced a problem with doing so.

And compiling isn't really such a big deal. Compiling a Linux app is almost always done in four simple steps:

Step-1:Unpacking
Most packages come compressed when you download them. Unpacking a package in Linux is not very different from unzipping a file in Windows: you copy the file to a directory and unpack it. The ususal command to do that is called tar (from the archaic 'tape archive') and usually looks like this:

tar -xvzf package.tar.gz (sometimes the file extension is bz2 which is just a variant of .gz)

Step-2: Configure
Configuration is actually a bit of a misnomer. You aren't configuring something so much as you're checking your system to make sure all the system dependencies are in place before you start compiling. This is an important step because this process generates values for system dependent variables that are needed for something called a makefile. You don't need to know what that is just so long as you know that the configuration step has to be completed successfully before you actually compile you application.

All you need to do to make all this happen is change to the directory that you unpacked your package in:

cd/package

and run the supplied configuration script which is included as part of your package:

./configure

Usually it will execute without a problem. The only time you will normally get an error will be if the package is damaged (in which case you need to download it again) or you're missing a dependency which you can almost always install through your distro's normal package manager (i.e. APT, YUM, Synaptic, etc.). This is no different than what you run into in Windows when an application informs you that you need to install .NET Framework, a VisualBasic runtime, a Java runtime, or update a Windows component before it can be installed.

Step-3:Build the binary
Once ./configure exits without errors you actually compile your binary package. This is done with the make command:

make

Step-4: Install the app
Once make completes all that's left to do is install the binary t you just created. That's done with the make-install command:

make install

And that's it. You've just compiled your very own Linux package from source!

Here's a quick review. We'll use a fictional Linux application named w00t that ships as a tar.gz archive for this example:

# tar -xvzf w00t.tar.gz
# cd w00t
# ./configure
# make
# make install

That's it. Not so hard, right? Especially when you consider that you don't really need to know what any of that actually means so long as you follow the steps. And these four steps are the same for about 99.9% of what's out there. Do it once and you know how to do it for almost everything.

I think Linux could take a step forward by doing anyway with the terminal and simplifying the installation of some programs. I don't think any user short of a programmer should have to touch the terminal.

The Terminal (brass fanfare as the incense rises...) goes right to the heart of what Linux is all about. It's a philosophical as well as a technical issue for many people. Especially once they get some experience and discover just how powerful and useful a tool the command line is.

Much like touch-typing, the command line is a skill set that takes some effort to learn. But once you make that effort, there's just no going back.

I can't say much in response to your suggestion to do away with the command line other than to say not to hold your breath. You can take the command prompt away from many Linux users "when you can pry it from their cold dead fingers" to borrow from an old bumper sticker.

So spend a little time getting acquainted with the bash shell and your terminal app. And make a modest effort to learn how to use Vim, or some other basic editor. You'll be amazed how much power you've gained with nothing more invested than your time.

 8)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 19, 2008, 10:59 PM
Only four major distros? Which one of those would you say gentoo derives from, then? ;)

As for building from source, yeah those are the basic steps. But you forgot the whole hunting-down-dependency-hell and uninstall/upgrade bother.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on October 19, 2008, 11:39 PM
Only four major distros? Which one of those would you say gentoo derives from, then?  ;)

Zing!  :P

I think that puts it to 6. Puppy, Slackware, Debian, Suse, Gentoo and...I'm not really sure Redhat counts. Technically it is but I think just based on user needs Ubuntu even though it's based on Debian is more of a major distro nowadays.

Terminal

I think this is just a misunderstanding between two parties. Usually when I hear people say "no to terminal", I think what they mean is for it to function more like a Mac than for the terminal to be get rid of all together.


Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: wreckedcarzz on October 19, 2008, 11:52 PM
I'm downloading the 8.10 Ubuntu beta right now (Intrepid Ibex) and I plan to install it as a Windows application and run it from within Windows (never done it before, but I want to be able to use my X-Fi while running Ubuntu, along with some other things that Ubuntu still has iffy support for (*cough* 3D GAMES *cough*). I've heard this is the best way for Windows -> Ubuntu users to give it a shot, but I am not sure if it needs to have a separate partition or not. Even if it does, the "real" install does too, so its not any more work.

I can have my Ubuntu and eat it too! Er.. how does that go again? :P
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on October 20, 2008, 12:11 AM
Thanks. Keep us updated. Would be nice to see how different it is from Wubi.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 12:20 AM
Only four major distros? Which one of those would you say gentoo derives from, then? ;)

As for building from source, yeah those are the basic steps. But you forgot the whole hunting-down-dependency-hell and uninstall/upgrade bother.

Gentoo is what's called a "sourced-based" distro, and isn't derived from any of the four majors I cited (as if you didn't know ;)). On their website, Gentoo claims to be "based on either Linux or BSD", so go figure. I guess you can say it's based on everything.

I didn't forget the dependency issue. From my experience, the whole "hunting-down-the-dependency-hell" thing is vastly exaggerated and somewhat outdated. You can always find exceptions, but if you install the build-essential (or equivalent) package in most distros you will seldom encounter any problems. Build-essentials are usually included, or flagged as 'recommended', in most default installations.

If ./configure reports any other missing dependencies (i.e. missing package-name) a simple invocation of the distros package manager (ex: apt-get install package-name) will fix it.

Pretty much the only time you'll encounter the missing dependency issue is if you did a custom (or minimal) install of your distro. Either that, or you're trying out some fairly esoteric piece of software. I don't think either situation would apply to the average Linux novice.

If you know enough to do a custom distro install, or you're experimenting with some really weird or bleeding-edge app, then hunting down a dependency shouldn't present much of a challenge. 8)

Zing!  :P

I think that puts it to 6. Puppy, Slackware, Debian, Suse, Gentoo and...I'm not really sure Redhat counts. Technically it is but I think just based on user needs Ubuntu even though it's based on Debian is more of a major distro nowadays.

Nyet. ;)

I said major distros.

Gentoo is a classic example of a VCIW - another great idea rendered moot by advances in hardware. Puppy is a specialist minimalist distro with an emphasis on frugal system resource requirements.

Redhat counts because of RPM and the RedHat repositories. Repositories are the keys to the kingdom. Few care about the distro they're using. What they do care about is how much 'vetted' software is available that can be installed with the minimum fuss and bother. And if you'll notice, the distros with the biggest and most complete repositories also tend to be among the most popular.

To a certain extent, f0dder is absolutely right about the dependency-hell issue. People don't need the hassles. And all they have to do is pick a distribution that has the most available via its package manager to avoid them. :Thmbsup:


Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 12:25 AM
I'm downloading the 8.10 Ubuntu beta right now (Intrepid Ibex) and I plan to install it as a Windows application and run it from within Windows (never done it before, but I want to be able to use my X-Fi while running Ubuntu, along with some other things that Ubuntu still has iffy support for (*cough* 3D GAMES *cough*). I've heard this is the best way for Windows -> Ubuntu users to give it a shot, but I am not sure if it needs to have a separate partition or not. Even if it does, the "real" install does too, so its not any more work.

I can have my Ubuntu and eat it too! Er.. how does that go again? :P

Yep. Do a WUBI install. It does not require a separate partition when you do it that way. Ubu gets installed into an ordinary file on your Windows NTFS partition that behaves like a regular Linux partition when you boot into it.

Be forewarned, Ibex is a beta. Hardy Heron would probably be a safer bet if you're new to Ubuntu. :tellme:

Have fun! :Thmbsup:
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 12:50 AM
I found out that there is no official user support for the installation of Mono onto Ubuntu
-VideoInPicture (October 19, 2008, 07:49 PM)

That may be because of the whole issue of Mono being a .NET 'clone' rather than for any technical reason.

There are some serious legal questions regarding whether or not Microsoft will assert patent violations against the Mono platform. Microsoft has stated publicly on more than one occasion that they believe Mono to be infringing on Microsoft intellectual properties. And although Microsoft has recently signed agreements with Novell not to pursue legal action against Novell's customers for patent violations (which includes the use of Mono), this only applies to the use of Mono on Novell platforms.

There is also a feeling in many parts of the general Linux community that Mono is a 'big mistake' that does nothing for Linux and only serves to further entrench Microsoft's .NET platform as the development framework of choice. There is also some concern that Mono could function as a "Trojan horse" in that Microsoft may decide wait until Mono has made itself essential to Linux software development before they take legal action against it.

I don't think you can blame Canonical for being leery of granting 'officially supported' status to Mono. Especially when you consider what a thorn in the side Ubuntu has been to Microsoft.

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 01:09 AM
Terminal

I think this is just a misunderstanding between two parties. Usually when I hear people say "no to terminal", I think what they mean is for it to function more like a Mac than for the terminal to be get rid of all together.

I understand that VideoInPicture is not saying to get rid of the terminal altogether...

I don't think any user short of a programmer should have to touch the terminal.
-VideoInPicture (October 19, 2008, 07:49 PM)

... what I'm disagreeing with is the notion that only programmers should ever have to touch the terminal.

Some tools are just too useful to leave on the shelf - even if they can be dangerous in the wrong hands. ;D


Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 20, 2008, 01:56 AM
I wouldn't say that gentoo is based on BSD, since it's a linux distro - but it's pretty evident where it got the "portage" idea from, though. Btw, gentoo isn't made superfluous by advances in hardware, it's just as much about having configurability options. With other distros, I've found that oftentimes I get a lot of features I don't need from standard packages (including dragging in a crapload of dependencies), but a feature I need isn't enabled - and I end up having to do those messy from-source installs after all. That's the cool thing about gentoo and it's use-masks, I don't run into the situation.

Dependency-hunting isn't hard, it's just a waste of time. And for some software, you get into the iffy situation where very specific versions are needed. Installing redmine (http://www.redmine.org/), for instance, was pretty fun :)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: urlwolf on October 20, 2008, 10:44 AM
My main 3 problems with linux:
1 - you better invest some of your time learning sysadmin stuff. With values of 'some' that may range out of reach for most people, if you have a real job :)

2 - Quite a lot of software, for any category, is worse on linux. Music player? check. Amarok is not really up to pair, and it's a hell of a wonder compared to other linux software. Office suite? Check. Many little tools that make your life easier (ahk, etc)? check

3 - Buying hardware is a real adventure. You better scourge the web before paying for something that linux will not even see.

Even in the unlikely case that an up-to-pair software exists that repleaces your favorite windows one, you'll need to find it and play with it till you get it to suit your needs. And development may stop at any time, as soon as the main dev. gets bored.

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 12:05 PM
I wouldn't say that gentoo is based on BSD, since it's a linux distro - but it's pretty evident where it got the "portage" idea from...

You don't need to say it. Gentoo did: ;D

What is Gentoo?

Gentoo is a free operating system based on either Linux or FreeBSD that can be automatically optimized and customized for just about any application or need. Extreme configurability, performance and a top-notch user and developer community are all hallmarks of the Gentoo experience.

http://www.gentoo.org/main/en/about.xml

Btw, gentoo isn't made superfluous by advances in hardware, it's just as much about having configurability options.

Agree. But to what point? If you're looking to improve performance, it becomes somewhat pointless to spend dozens of hours researching what compilation flags to set in order to squeeze a 5% improvement in efficiency on a specific platform. You could just invest in more RAM or a faster processor.

Now I agree that it might be worth it if you were doing a Gentoo Stage-3 install as a learning experience Or if you wanted to do it for pure technical aesthetics. That's one advantage of being a student, a hobbyist, or a tech person. You get to do things like that.

I fit into the third group, so I made it a point to do a few "Stage-3's" just to find out what Gentoo was all about. And when I was finished, I considered it a good investment of my time. But that's because I'm a "computer guy" in the tech business. I can easily justify wallowing in levels of detail the average person would consider silly because it's my job to do that.

But if you're only looking for performance (and you value your time at more than $6/hour  :mrgreen: ) it doesn't make economic sense to do a Stage-3 installation. Especially when you realize could get a part-time job that pays better than that, and then use the money you earn to buy a more capable computer.

Where Gentoo really would (and does) shine is when you use it as the basis for an application appliance. But again, that is a specialized situation where there are pragmatic reasons for wringing every last ounce of performance out of your product - because if you don't, the competition in the marketplace will kill you. And there are two other good reasons. First, once you create a fully optimized Gentoo "gold master" you can just keep cloning it until you change your hardware configuration. And second, because you're going to be responsible for support, it also makes sense to get everything "just right" before you ship out 5000 boxed products.

Gentoo is an amazing version of Linux. But it is a niche product. And I still maintain that most of its benefits apply, in practice (as opposed to in theory) to only a very small subset of the Linux community. From the level of knowledge you've displayed in many of your forum posts, I suspect you (i.e f0dder) are part of that small cadre of people that has specific goals combined with the necessary technical background to pull them off. For folks like you, Gentoo makes sense.

"There's some Linux experiences money can't buy. For everything else there's Ubuntu." 8)

With other distros, I've found that oftentimes I get a lot of features I don't need from standard packages (including dragging in a crapload of dependencies),

True. But to go back to an earlier observation I made about custom and minimalist installations, those very same dependencies you don't want installed by default may later be needed for when you want to do a source install of something else. You can't have it both ways. If you want lean - you get lean.

but a feature I need isn't enabled - and I end up having to do those messy from-source installs after all.

I don't know of any supported 'feature' for a distro that isn't found in its repositories and installable via the preferred package manager. If you're doing source compiles for a core function, I suspect you're either hacking the kernal, or getting into something that hasn't been fully tested and approved for distribution. Nothing wrong with doing that (I'm guilty of it myself) but once again you can't have it both ways. If you want beta - you get beta.

Dependency-hunting isn't hard, it's just a waste of time. And for some software, you get into the iffy situation where very specific versions are needed. Installing redmine, for instance, was pretty fun smiley

It is a waste of time. No argument there.

But redmine isn't a good argument for that point. Let's get some background on that story:

Redmine's hassles were the result of a change to the SQlite-3 database table_info pragma that was made by the SQLite development team. The change was made  in response to what they thought was a request from the RubyCore team. Such was not the case, and the change that got made broke all Ruby on Rails apps that were using SQLite-3. What makes this story really tragic is the fact that the problem didn't come about through an arbitrary program change, but rather by SQLite's genuine effort to be accommodating and responsive to a request it thought was from the Ruby community.

Unfortunately, both versions of SQLite's binaries are now found in many repositories, and most Linux package managers will default to the most current version of a binary for installation purposes. This can be overridden on a package by package basis by the person doing the install as long as they know about the problem. In the case of Redmine, an older version of the binary is needed. Unfortunately, most of the people involved with Redmine didn't know about the problem until after they broke their installation.

Now from my perspective, this problem has nothing to do with any Linux distro, it's repositories, or the system of package management. It has everything to do with communications issues between the developers of Ruby and SQLite.

On a side note, I would also like to point out that Redmine is not found in most Linux repositories. Furthermore, if you go over to the Redmine website and read the installation instructions, you will see that the developers have left their userbase a lot of manual setup actions that should have been scripted instead. This is probably because Redmine is still under heavy development and not quite out (ver. 0.7.3) of beta. If the installation routine had been scripted, it would have been a simple matter to check for the correct version of SQLite prior to installation. And that would have avoided the whole problem in the first place.

On a related note, Redmine is a web-based project management application. If you go over to SourceForge you will find there are something like 1700 packages that are tagged  "project management." A cursory look at a few dozen will show several that duplicate, and in some cases exceed, the functionality of Redmine. Many are also out of beta.

From what I can see, there doesn't appear to much that is unique about Redmine, other than the fact that it is being implemented in Ruby on Rails. Now while I have the greatest respect for the Ruby community, and I admire the work of the folks that came up with Ruby on Rails, I can't help thinking "so what?" when I look at Redmine. Especially when there are equivalent applications I can install directly from my distro's repositories that will give me the same functionality without the hassles of doing a source compilation or a pile of manual configurations.

It's nice that Linux has made provisions for you to compile an application from source. But unless you have a very specific reason for doing so (or you just plain want-to-do-it*), why bother?

* That wouldn't normally be considered a reason - but this is Linux we're talking about, right?

 8)

P.S. - Sorry for writing a freekin' book. Somebody else talk, please?
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Edvard on October 20, 2008, 01:09 PM
I've already said more than once that I'm http://taking my GNU and going home.

I love Linux and I don't have half the problems anybody else has, but I've suffered through my fair share in the beginning.
(Slackware 8 and Mandrake 9, blaargh!!)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 20, 2008, 02:44 PM
Btw, gentoo isn't made superfluous by advances in hardware, it's just as much about having configurability options.
-f0dder

Agree. But to what point? If you're looking to improve performance, it becomes somewhat pointless to spend dozens of hours researching what compilation flags to set in order to squeeze a 5% improvement in efficiency on a specific platform. You could just invest in more RAM or a faster processor.
I said configurability (as in --without-package or --with-feature), I didn't mean tweaking the compiler flags. For most applications, you don't really get any kind of performance increase from doing that. Heck, you could end up with slightly slower performance in some cases.

Where Gentoo really would (and does) shine is when you use it as the basis for an application appliance. But again, that is a specialized situation where there are pragmatic reasons for wringing every last ounce of performance out of your product - because if you don't, the competition in the marketplace will kill you. And there are two other good reasons. First, once you create a fully optimized Gentoo "gold master" you can just keep cloning it until you change your hardware configuration. And second, because you're going to be responsible for support, it also makes sense to get everything "just right" before you ship out 5000 boxed products.
If I was to do an appliance, and especially something that'd run on a system with limited performance and storage, I'd probably go linux-from-scratch instead of using a distro - even something that can be as minimal as gentoo.

but a feature I need isn't enabled - and I end up having to do those messy from-source installs after all.
-f0dder
I don't know of any supported 'feature' for a distro that isn't found in its repositories and installable via the preferred package manager. If you're doing source compiles for a core function, I suspect you're either hacking the kernal, or getting into something that hasn't been fully tested and approved for distribution.
I'm thinking enabling/disabling individual features from individual programs. But sure, I do tend to do custom kernel builds as well.

Redmine's hassles were the result of a change to the SQlite-3 database table_info pragma that was made by the SQLite development team. The change was made  in response to what they thought was a request from the RubyCore team. Such was not the case, and the change that got made broke all Ruby on Rails apps that were using SQLite-3. What makes this story really tragic is the fact that the problem didn't come about through an arbitrary program change, but rather by SQLite's genuine effort to be accommodating and responsive to a request it thought was from the Ruby community.
I opted for MySQL instead of SQLite for exactly that reason. But that was only part of it - you also had to make sure you got the right ruby verson, the right rails version, et cetera. Lots of manual configuration. Pretty sucky and not up-to-date documentation, etc.

OK, fair enough, redmine is relatively bleeding-edge, and it's certainly more fun focusing on core development rather than documentation and proper setups. I just tend to bump into that kind of mentality too often with linux.

On a related note, Redmine is a web-based project management application. If you go over to SourceForge you will find there are something like 1700 packages that are tagged  "project management." A cursory look at a few dozen will show several that duplicate, and in some cases exceed, the functionality of Redmine. Many are also out of beta.
Haven't found any other that I like, though. Looks, usability, etc.

It's nice that Linux has made provisions for you to compile an application from source. But unless you have a very specific reason for doing so (or you just plain want-to-do-it*), why bother?
For me, it's about getting the features I want, but also not getting the features I don't want. For instance, my server doesn't run X11 and I don't print from it. I want to have as few services running as possible, since there's then less things to worry about wrt. updates, following security issues, et cetera. There's also less dependencies that can break when a stoned developer checks in a patch that messes up other things.

And the nice thing about gentoo is that you get most of the benefits from source installs, but still with the benefits of package management (uninstalls, dependency resolution, etc).
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 20, 2008, 03:57 PM
If I was to do an appliance, and especially something that'd run on a system with limited performance and storage, I'd probably go linux-from-scratch instead of using a distro - even something that can be as minimal as gentoo.

You could. But there are plenty of micro-distros that would serve equally well.  Still, I wouldn't automatically limit my definition of an appliance to some minimal hardware configuration. I think of appliances as any purpose-built system that basically runs right out of the box and gets administrated via a web-type interface. I'd lump full bore security gateways, mail servers, CMS servers, etc. into the 'appliance' designation. At least those are the 'appliances' I've built.


It's nice that Linux has made provisions for you to compile an application from source. But unless you have a very specific reason for doing so (or you just plain want-to-do-it*), why bother?

For me, it's about getting the features I want, but also not getting the features I don't want. For instance, my server doesn't run X11 and I don't print from it. I want to have as few services running as possible, since there's then less things to worry about wrt. updates, following security issues, et cetera. There's also less dependencies that can break when a stoned developer checks in a patch that messes up other things.

And the nice thing about gentoo is that you get most of the benefits from source installs, but still with the benefits of package management (uninstalls, dependency resolution, etc).

To which I'd have to repeat an earlier statement I made:
From the level of knowledge you've displayed in many of your forum posts, I suspect you (i.e f0dder) are part of that small cadre of people that has specific goals combined with the necessary technical background to pull them off. For folks like you, Gentoo makes sense.

And it's good that there are people like you around to knowledgeably challenge the occasional fits of groupthink and rampant boosterism that sometimes gets the Linux community into so much trouble. :Thmbsup:


Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on October 21, 2008, 07:24 AM
Keep educating us idiots, f0dder and 40hz.  :up:

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 21, 2008, 11:25 AM
Keep educating us idiots, f0dder and 40hz.  :up:



If I ever get the time to set up that bloody Linux info website I've been plotting and designing for the last two years, I'm going to sure to invite f0dder to be it's Official Contra-Pundit. ;D

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: zridling on October 21, 2008, 01:57 PM
Once again, thanks 40hz for the feedback, which is far more than I know. However, for those with the patience, here's a longer, very simplistic explanation of dependency management

[40hz]: I didn't forget the dependency issue. From my experience, the whole "hunting-down-the-dependency-hell" thing is vastly exaggerated and somewhat outdated.

Dependency management can get fiendishly complicated at times. But no worries. Like a good butler, the Linux software subsystem hides all that from you. This is one argument people use if they object to package management systems, such as that used by Ubuntu (or any other Distro). However, the counterargument is a good one: it never breaks -- unless the user does something stupid, that is.

[ You are not allowed to view attachments ] (http://www.anova.org/target/dcc/synaptic01.png)

How software installation and removal is handled under Linux is radically different compared to Windows or OS X, but it isn’t hard to understand. As we all know, to install a program, a Windows user will double-click an installation .exe. Linux is different because software installation is automated -- even including the download. You literally just choose what you want to install and sit back while Linux (actually, your distro) takes care of it.

Virtually all Linux software is open source and therefore available for anybody to create their own versions of. So, the Linux developers take the source code for thousands of software projects and compile it themselves, tweaking it to ensure it works correctly on Fedora (or Ubuntu or Gentoo or Mandriva, etc.), and put it into large publicly accessible repositories (known as repos for short). In nearly all cases when you install software, it’ll come from these repositories. Manually downloading and installing software is rare, although not unheard of -- I do it to test software and when I'm at the dev's website.

The second key difference between Linux and other operating systems like Windows and Mac OS X is that Linux lets you install and remove just about everything, including system components that are otherwise invisible but make everything work. The bits of software that are installed and removed are referred to as packages. Packages are nothing more than program and/or system files bundled together in one file, complete with scripts (chains of commands) that configure things so that the software works with everything else on the system.

Typically, to install a particular piece of software, it’s necessary to install not only the program itself, which is usually provided as a single package, but several other packages containing the background system software it needs to work. You might say that such software installation is modular. The software you want to install is said to depend on these other packages that provide the system files. As you might be coming to expect, your distro's software install/removal tools automatically take care of installing these dependencies, and because of this, you will often hear people talk of dependency management when discussing Linux’s software management system as if it's a scary thing.

[ You are not allowed to view attachments ]

It isn’t just about managing dependencies when software is installed, of course. If you remove some software, you’ll be told whether that software is depended upon by any other software. If it is, you might see a suggestion that you remove the other software too. The other software might have its own set of dependencies. But again, the counterargument is a good one: it never breaks -- unless the user does something stupid.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 21, 2008, 03:41 PM
[/b] for the feedback, which is far more than I know. However, for those with the patience, here's a longer, very simplistic explanation of dependency management

Go zridling! :Thmbsup:
Very nice summation.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 21, 2008, 04:17 PM
Dependency management can get fiendishly complicated at times. But no worries. Like a good butler, the Linux software subsystem hides all that from you. This is one argument people use if they object to package management systems, such as that used by Ubuntu (or any other Distro). However, the counterargument is a good one: it never breaks -- unless the user does something stupid, that is.
Except when bad stuff happens. Like an install that updates a dependency that somehow for unexplainable reasons break another piece of software. Or when two pieces of software are incompatible because of library conflicts. Or when package maintainers forget some dependencies.

Funny enough I've never seen the "DLL hell" some people talk about on Windows... but I've had my fair share of library conflicts on linux :)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Edvard on October 21, 2008, 06:03 PM
That is the one thing that still bugs me about Linux. I've never been burned by library conflicts but I always wondered why I had to download ONE... MORE... LIB... UNTIL... IT... RAN... :wallbash:

This has been mostly alleviated by Ubuntu's (actually Debian's...) magical apt-get dependency resolution, but I hit that wall every damn time on Slackware.

Actually it still happens if I install something from source or off-repository, but at least with apt I don't have to go Googling for onemorefreekinglib_i386_1.2.6.so.tar.gz and manually linking every stinking time...  :'(
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: f0dder on October 21, 2008, 06:05 PM
Oh yeah, I had plenty of fun with that kind of thing when I used slackware. And then you forget to use --prefix when doing ./configure , and you end up with software scattered all over. Yum yum.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on October 21, 2008, 06:47 PM
Oh yeah, I had plenty of fun with that kind of thing when I used slackware. And then you forget to use --prefix when doing ./configure , and you end up with software scattered all over. Yum yum.

Got that right.

Then there's also the fun you sometimes have trying to figure out in which directory the executable (or script) actually got installed in...

Since I'm always one of the people praising Linux, I'll now level it a criticism:

That &$#! file structure has got to be simplified and rationalized.

It looks like somebody came up with in an outliner app after dropping six tabs of LSD. What in the name of all that is holy were they thinking of?
 >:(
There is one distribution that is trying to address this problem: GoboLinux ( www.gobolinux.org )  :-*

GoboLinux at a glance
What is GoboLinux?


GoboLinux is a modular Linux distribution: it organizes the programs in your system in a new, logical way. Instead of having parts of a program thrown at /usr/bin, other parts at /etc and yet more parts thrown at /usr/share/something/or/another, each program gets its own directory tree, keeping them all neatly separated and allowing you to see everything that's installed in the system and which files belong to which programs in a simple and obvious way.

This is what you see in the root of a GoboLinux system:

~] cd /
/] ls
Programs
Users
System
Files
Mount
Depot

/Programs is where all programs reside. No exceptions. You can explore what is installed in the system by looking inside it:

There is a great page up on the website that has several interesting essays about the design and implementation of the Gobo file system. Well worth reading if you're interested in how an OS could be better designed.

Link: http://www.gobolinux.org/index.php?page=documentation

From the paper: I am not clueless-or-Myths and misconceptions about the design of GoboLinux

"There is a reason why things are the way they are''

This is something I hear constantly, often followed by an explanation about the difference between /, /usr and /usr/local, and/or /bin and /sbin. I do understand the difference1. If I did away with this three-level distinction, is because I believe there are other ways to approach the problems this distinction tries to solve. In a GoboLinux system, the argument for having separate /usr and /usr/local trees in order to separate programs shipped by the distribution and compiled by the user clearly does not hold. Each program is naturally separated, and this was the prime intention of creating GoboLinux in the first place.

The historical reason why Unix systems have some of its tree directly at the root partition (/bin, /lib, /sbin) as opposed to having it under /usr, is because this way you can boot in a bare-bones single-user rescue mode using those files only, in order to fix problems in the /usr tree. This is arcane. When I need to rescue my system, I can use a fully-featured live CD that runs a complete Linux distribution with a graphical desktop, that allows me to browse the web and search for the solution to my problem, and use all of the features of a regular system to fix it. I understand the rationale for having a bare-bones rescue mode decades ago, but we have a better solution in our hands now.

The distinction between bin and sbin makes no sense, in the present context. Historical evolution led to crazy arbitrary distinctions, like ping and traceroute lying in different directories (I fail to see how can they be of distinct ``program classes'', by any measure). Unix systems have a permissions system. If one wants only the superuser to be able to run a command, then chmod 700 it. I suspect the separation could have been conceived to reduce the number of programs in the $PATH of regular users. In today's Linux systems, having 400 or 500 programs in your $PATH, does not make any difference.

Not only did GoboLinux create a workable alternate file system, but it was made compatible with the rest of the Linux world:

GoboHide: surviving aside the legacy tree
As you might have already seen, GoboLinux adopts an alternative directory tree. As you might also be wondering, without the legacy tree a lot of common applications wouldn't work in GoboLinux. This document explains how this problem is solved by the distribution and how it's solved by other operating systems which must address the same problem. If you simply don't want to read the entire story,  click here  to get directly into the download section.

A long time ago, in a mailing list far, far away.... There was a discussion about how we could get rid of the legacy tree, without actually removing it. We needed to keep it, but we just didn't want to know it existed.

At last - some sanity. Let's hope this concept gets eventually wider adoption in the Linux community. :Thmbsup: :Thmbsup:

Mr. Shuttleworth? You fancy yourself a maverick.  Are you listening?



Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: wreckedcarzz on October 21, 2008, 08:27 PM
The Wubi install was a bust - not only did I misunderstand that you have to boot it separately from Windows, but when i figured that out, GRUB nor the Windows Boot Manager appeared on boot. Uninstalled.

Ubuntu 8.10 is on my new (old) IDE drive (I'm running it now) - it took a truckload of updates and an insane amount of bandwith, but I am running on all the latest versions of everything.

Changes that I've noticed (negative items):

OK, on to the positives! (Yes, there are good things about 8.10!!! ... sort of...)

Seriously, it is nice, but... freaking annoying as can be to get past the bugs. Wait till November 10th-ish (right after my birthday!) to update or give it a shot. If you try it now... well... see the above. I'm not leaving it, but I spent time on it and I can mind the bugs ... for now.

-Brandon
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on February 05, 2009, 02:04 PM
Unfortunately GoboMint...not so easy or popular.  :(

http://linuxmint.com/forum/viewtopic.php?f=29&t=11836&p=72869&hilit=gobolinux#p72869

http://linuxmint.com/forum/viewtopic.php?f=6&t=1200&p=7707&hilit=gobolinux#p7707

Suddenly the niche for another distro just got a wider. I wonderf if there would be a subsection of bored ReactOS reverse-engineers considering taking a gander at Windows Linux. (Now with new and improved file system!)

P.S. Sorry for resurrecting a thread. I just recently read the latest post here and I got excited about Gobo despite not having any technical know how and Mint often seems to be the trailblazer in Linux Distro features so I was too disappointed to not not post a reply here.
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on February 05, 2009, 03:16 PM
P.S. Sorry for resurrecting a thread.

I'm not complaining. Some of my best postings can be found here... ;D
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Josh on February 05, 2009, 03:18 PM
P.S. Sorry for resurrecting a thread.

I'm not complaining. Some of my best postings can be found here... ;D
You have good postings? ;-)
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: iphigenie on February 05, 2009, 03:39 PM
You could also switch away from windows without going to Linux, for example OpenSolaris or PC-BSD are nice packages. PC-BSD is an amazing install (It's the first OS I install on that machine that puts all other OSes into its boot menu automatically, how refreshing!)

As for Linux, the distributions I tend to use - and have for years - are Slackware (or the "vector" variant when i want a slackware desktop easily), SUSE (I used to use a distro called DLD which was bought by suse in 96 or so), Debian, or Arch (hard core, compile from source). All old distributions that aren't "sexy" but neither have the mess that comes with being popular.

I have a new subnotebook running Suse, but I also have a machine running non linux open source OSes - both openSolaris and PC-BSD

PS I just bought an HP mininote 2133 cheap, with SUSE, so am catching up on linux games and gnome apps :D
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: Paul Keith on February 05, 2009, 05:26 PM
Lol 40hz.

I've been meaning to switch to PC-BSD (although not Solaris, using this PC purely for desktop) but nothing I've read makes me think it's much more ready for the desktop than Linux is and unless I'm mistaken, it still has the same filesystem hierarchy as most Linux distros doesn't it?

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on February 05, 2009, 06:01 PM
Lol 40hz.

I've been meaning to switch to PC-BSD (although not Solaris, using this PC purely for desktop) but nothing I've read makes me think it's much more ready for the desktop than Linux is and unless I'm mistaken, it still has the same filesystem hierarchy as most Linux distros doesn't it?

Very similar hierarchy, and much more consistently utilized by installed applications.

I think you're really going to like using PC-BSD. Out of all the Unix-like variants, BSD is still my favorite. PC-BSD takes a good thing and makes it even better for desktop deployment. Enjoy!

-----------

P.S. Sorry for resurrecting a thread.

I'm not complaining. Some of my best postings can be found here... ;D
You have good postings? ;-)

Yup.

And my Mom thinks I'm pretty too! :P


Title: Re: Ten Tips for Windows users making the switch to Linux - Tip 11
Post by: Lutz_ on February 06, 2009, 08:14 PM

Tip 11:

- Do not expect most things to work by drag-and-drop. They won't.

Linux is still far away from the UI consistency of the commercial OS'ses.  But you have the choice among twenty different "variations on a theme".
Title: One reason for Windows users to use Linux
Post by: e712 on February 18, 2009, 03:54 PM
You need an app that doesn't run well under cygwin or virtual box. 
Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: 40hz on February 18, 2009, 08:25 PM
You need an app that doesn't run well under cygwin or virtual box. 

That is an excellent reason - it was precisely this that got me into using Linux in the first place. :Thmbsup:

(In my case it was a project management app.)

Title: Re: Ten Tips for Windows users making the switch to Linux
Post by: PC Gamer on May 29, 2009, 06:01 AM
I found a useful (summary) information about Linux and Windows:

Both Windows and Linux come in many flavors. All the flavors of Windows come from Microsoft, the various distributions of Linux come from different companies (i.e. Linspire, Red Hat, SuSE, Ubuntu, Xandros, Knoppix, Slackware, Lycoris, etc. ).

Windows has two main lines. The older flavors are referred to as "Win9x" and consist of Windows 95, 98, 98SE and Me. The newer flavors are referred to as "NT class" and consist of Windows NT3, NT4, 2000, XP and Vista. Going back in time, Windows 3.x preceded Windows 95 by a few years. And before that, there were earlier versons of Windows, but they were not popular. Microsoft no longer supports Windows NT3, NT4, all the 9x versions and of course anything older. Support for Windows 2000 is partial (as of April 2007).

The flavors of Linux are referred to as distributions (often shortened to "distros"). All the Linux distributions released around the same time frame will use the same kernel (the guts of the Operating System). They differ in the add-on software provided, GUI, install process, price, documentation and technical support. Both Linux and Windows come in desktop and server editions.

There may be too many distributions of Linux, it's possible that this is hurting Linux in the marketplace. It could be that the lack of a Linux distro from a major computer company is also hurting it in the marketplace. IBM is a big Linux backer but does not have their own branded distribution. Currently there seem to be many nice things said about the Ubuntu distribution.

Linux is customizable in a way that Windows is not. For one, the user interface, while similar in concept, varies in detail from distribution to distribution. For example, the task bar may default to being on the top or the bottom. Also, there are many special purpose versions of Linux above and beyond the full blown distributions described above. For example, NASLite is a version of Linux that runs off a single floppy disk (since revised to also boot from a CD) and converts an old computer into a file server. This ultra small edition of Linux is capable of networking, file sharing and being a web server.