CrunchBang Linux

Best way would be to boot a live system built with Gnome 3.  Try it out, and see if you like it before you install anything.

If you are still interested in this particular ThinkPad, I would contact the seller asking for the seven character type number.  Then look that number up on the Lenovo Support website using "Quick Path".  If it has the Intel graphics, you should get a cool running and reliable machine.  If you find it does indeed have the NVS 140 chip, I would pass on it.  BTW, I own two T61 ThinkPadss, both of which have the Intel graphics, and they are fine machines.

http://www.debian.org/Bugs/Reporting

nore posted a link just a couple of posts above that should help you get Firefox on #!.  Still, I hope someone can tell us why Firefox would be able to do anything that Iceweasel can't....I mean Iceweasel is just a rebranded Firefox, isn't it?

Just dropped in to ask...why?  Iceweasel is the default browser in Waldorf, and it's the same thing as Firefox.

I agree with you, ew.  Probably should have said that by plenty I meant 1.5GB.  Plenty most of the time, but that's why I said just in case.  So far I haven't needed swap, but if I get careless and open 50 browser tabs, who knows?

I've occationally noticed similar behavior too, but don't know what the cause is.  I'll join you in awaiting someone to come along who knows what's going on here.

Haven't had time to try it yet, but Ted looks interesting.

Nice find!  Somehow, in my searching around, I had missed that one.  So, I too installed "system-config-samba" on my Xubuntu laptop, and in seconds had the chosen directories available on the network, accessible to other Linux and Windows machines alike.  No more difficult than doing the same in Windows.  I'm thinking this is one of the reasons Ubuntu, and it's derivatives, are so popular with those of us who are simply "users", and not system admins.  Sadly, the package doesn't seem to be in the Debian repos, but I suppose one could install it from source.  When I get some time, I'm going to look through the Xubuntu smb.conf file to see what changes have been made there, and then apply those to my #! box to see if I can make it's files available to the network.

Thanks for all the suggestions.  Feels like we are making some progress!

I'm kind of a MATE fan also, but am trying to learn to manage this #! install with OB only.  Would love to see some screenshots!

I appreciate the help guys.  I'm sure my problems are not because the system doesn't work, it's my lack of knowledge about setting things up, and the way folks who are trying to be helpful always forget to include a few details about how they got it working.  For example:

I suspect you're right, and ssh should work, but with only the instructions lilince wrote, it doesn't for me.  If I enter "sudo service ssh start" in terminal, I get the error "ssh: unrecognized service".  So I tried openssh, and get "openssh: unrecognized service".  So, I'm still lost as to why it doesn't work for me, since I know openssh is installed.  If I run apt-get install openssh-server again, apt shows it as already installed.

Phillipel's guide didn't add any functionallity that I don't already have, and he didn't include the one most important edit needed to browse Windows shares in Thunar,  i.e. add "name resolve order = bcast host" right under the WORKGROUP entry.  But, even with Phillipel's edits, I can't browse #! from Windows.

Yes, for the most part, but even as delivered with Waldorf it doesn't just work OTB, smb.conf still needs at least the one edit above to make it work.

This is not of great importantence to me, as it's just a hobby and something I'm trying to learn.  So, I will keep reading, and trying things until I stumble onto something, amid all the incomplete suggestions, that makes it work for me.  At this point, I'm thinking that setting Samba up as a server is what we are trying to do, but as of yet, I have only seen it work with a Puppy Linux distro that was pre-configured as a server (PupServer).  Since Linux is so often used as a server OS, one would think this would not be so hard, but so far, it has been for me, and apparently so for matroska, and many others a well.

Sound simple and easy.  OK, installed as directed on both machines.

Nope...doesn't work.  WinSCP replies, "host does not exist".

Now this works splendidly!  I have no trouble setting up Samba to access Windows files from #!, but have yet to get it working the other way around.  Just tried Philippe1's suggestions, but that didn't seem to help the situation any.  Still can't browse #! from the Windows box.