Subj : Win4lin To : Time Warrior From : Sam Alexander Date : Tue Sep 27 2005 11:55 am Re: Win4lin By: Time Warrior to Sam Alexander on Tue Sep 27 2005 03:38 am > > > Question for anyone who has the answer... > > > > I've wondered if Synchronet/Win32 will work on Linux via Win4lin. As f > > > anyone who has gotten it to work, I haven't heard anything. As for it > > > working, i've heard one person say it breaks. > > > > So, has anyone gotten it to work with Win4lin? Has anyone broke it? If > > > why did it break (if you know) and how might the error be fixed to mak > > > Synchronet not get mad at it? (if its possible) > > > Just a question -- why use Win4Lin when you can use the native Linux inst > > of Synchronet on Linux? Just curious... the Linux version is rock solid! > > #1 - My unfamiliarity with Linux. Would you give a toddler a motor cycle or > a big wheel? :-) If you've got a BBS up and going and have more then a total novice's knowledge of computers, your analogy isn't all that accurate. Anyone who's worked with BBSes for years and knows Windows, plus had a computer pre-M$ can grasp Linux without any problem. It's like going from HTML to PHP. Linux totally lets you take control of your computer, and granted it takes alittle extra effort to learn the system, but once learned you'll wonder why you ever gave Bill any money :) > #2 - I've heard the Linux version lacks a few things that Win32 Sysops are > accustom to. Like what? Sync has a fancy GUI interface, but you have all the same tools through Linux, just not as pretty'ed up. I for one run my BBS on a headless computer, so this type of interface is useless to me. My BBS literally sits in my living room under an end table. With Linux no worries about needing a reboot or needing any interaction other then via Telnet/SSH. > #3 - You need to learn to walk before you can run :-) If you know enough about computers to build a BBS then you're already jogging. You don't need to be a programmer or UNIX guru to work with Linux, but you do need to be happy using command line. With Linux (and OSX for the most part too) every GUI action generally has a command line command behind it, which means anything GUI you can do in commandline. Windows isn't like this,w hich is one of the MANY reasons I don't care for it and why I didn't like Mac's until OSX. Any strong OS needs to have a strong Command Line IMO. > In the same way we don't send a kindergartener to attend high school, people > need to start slow and simple and work their way up with any learning > proccess. > > I can't just be hurled into the complex linux world from the mundaine Window > World. I need the training wheels on first :-) Download Knoppix and go from there. Somethign else to throw out there... here's my uptimes on two Linux servers I run at work: 10:05:25 up 325 days, 17:14, 1 user, load average: 250.99, 250.97, 250.91 9:58am up 536 days, 20:23, 1 user, load average: 0.20, 0.32, 0.33 The first is a file and print server running Slackware 10.1 on a Dell Optiplex GX1 (almost identical box to what my BBS runs on). The second is our FTP and Proxy server running Red Hat 7.2 on a Dec Alpha. When a Windows box can have 100% uptime for an entire year I'll trust it. Oh, and the 536 day uptime box would be almost doubled but we upgraded our UPS in the datacenter 536 days ago and everything got rebooted. FWIW... Sam --- "Data is not information, Information is not knowledge, Knowledge is not understanding, Understanding is not wisdom." -- Cliff Stoll --- þ Synchronet þ Life is Bunk BBS (Linux) in Waco, Tx -- lifeisbunk.homelinux.com .