[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: silug: IP address?



On Mon, 2004-12-27 at 14:39, bentley_rhodes wrote:
> Why? Mozilla doesn't have ActiveX support, and damned if
> i (The Ignorant Little Linux User) know how to make it.

The problem is that non-Win32 platforms do not have ActiveX support.
You can pull up MS IE on MacOS X or Solaris and it will not work either.

And that's the "litmus test."  Take the Microsoft program for another
platform and ask if it works there.  99.99% of the time it is a Win32
only application.

It's the main reason why Microsoft Office for Linux document
compatibility with Windows would _suck_ as bad as it does for Windows. 
You're better off sending a document from Microsoft Office for MacOS X
back to a Open/StarOffice for Windows user because of how byte
alignment/order-ignorant Microsoft Office for Windows is.

And that's not me talking, but people I knew on the MS Office for MacOS
X team.

> Basically Linux works, i have learned how to do some things with
> or as ROOT,

As running as a non-privileged user by default is a major security
bonus.  This is unlike Windows where about 50% of Microsoft written
libraries (not even looking at 3rd party/ISV libraries) break if you
don't run privileged.

You can game under Linux as a non-privileged user.  Distros setup the
limited access to the necessary devices and it just works.

Not under Windows.  Because of how DirectX works -- heck, how "Direct
DOS Memory Map" which became DirectX was designed (because OpenGL
performance _tanked_ under "Chicago") this will _never_ be.  It goes
back to Microsoft "Chicago" v. "Cairo" -- which is a long story.

And "Longhorn" is a repeat of "Cairo" (i.e., neither will ever be).

> how to tar stuff, reassign ownership for files from a command prompt/
> terminal, and make a shell script to tar and then reassign the files
> to a user.

All details that you must learn to be an effect Windows administrator
too.  Running Linux is not like running Windows 95/98/ME, but
NT/2000/2003.

> * get networking to work with Linux to Linux, and or Linux to
>   Windows, and by networking i mean:
>     o filesharing

The complexity of the CIFS/SMB protocols are entirely Microsoft's fault.
In fact, because of issues, Microsoft just flat out dropped complete
pre-XP SMB protocol support in Windows Server 2003.  I.e., if your
organization uses Windows Server 2003, you need to be _all_ XP clients
or you will have varying issues.

Samba allows you to tweak the server for endless Windows client support.

If you are doing UNIX-to-UNIX, NFS is very, very easy.

>    o sharing the IP or ISP (routing)
>    * making a Linux Router box / NATter thing. 

That's what distributions like this are for:  
  http://www.ipcop.org  

BTW, "NAT" is not "Routing."  They like to marketing as such, but it's
not.

> i might even want to try messing with GNU's Zebra (http://www.zebra.org).

Now Zebra _is_ routing.  ;->

> * taking a Linux User's course or some type of computer programming
>   course or something that would help me learn the system.

Any UNIX fundamentals course would be outstanding.  UNIX is a major
shift from Windows.

As I've always argued, it's better to have _no_ concept of how Windows
works and learn Linux than to come to Linux from Windows and assume
UNIX/Linux has a Windows approach.

> Steven or Bryan gave me some pointers on NAT configuration, but after i 
> typed it all in i'm not sure if it works or not. or if i typed it in 
> right, or if i had a cable crossed.

We try.  In a nutshell, you're not even really looking at
"Linux-specific" issues, but issues you'd have with Windows too if you
tried to do the same things.  These are IP networking fundamentals.

> i bought some cards (six of them) from a person on ebay, they are
> 3com's 3c905's and i /think/ they work. i've plugged my card in
> (linksys or nVidia's nforce ethernet card) and the lights come on.

> But those are plugged into the aDSL modem. The 3com one is plugged
> (through a long cable) into the windows computer. but i 
> do not see those lights come on when everything is plugged in. even when 
> i activate the card under the 'network' thing with root, or root 
> privileges. i'm thinking i might have to come up to some of the meetings 
> and figure what the heck is going on with the thing by watching 
> experienced people do stuff.

Again, some of the networking details that we've tried to help you with
are not even "Linux-specific" issues, but general issues that you'd have
with Windows too.

In fact NT5.x (2000/XP/2003) has severe limitations compared to what
even old Linux 2.2 (let alone newer Linux 2.4/2.6) can do.  That's how
I.D.E.A.L. Technology here in Orlando swindled a major contract with the
IEEE for network streaming away from a Microsoft Solution Provider and
then even Microsoft directly itself (after it reached the visibility of
executives).

Long story short (this was a few years ago), my old time friend Tony
Aawtrey's little Pentium 2 notebook running Linux could do more than a
4-way Xeon server running a beta of Windows Server 2003 at the time. 
After Tony got the IEEE working in real-time at an in-progress
conference in about 10 minutes, the MSP was in disbelief.  Then
Microsoft fought IDEAL tooth'n nail for months until they had to admit
Windows Server 2003 would not have the capability to do what a measly,
cheap Linux box could do.


-- 
Bryan J. Smith                                    b.j.smith@ieee.org 
-------------------------------------------------------------------- 
Subtotal Cost of Ownership (SCO) for Windows being less than Linux
Total Cost of Ownership (TCO) assumes experts for the former, costly
retraining for the latter, omitted "software assurance" costs in 
compatible desktop OS/apps for the former, no free/legacy reuse for
latter, and no basic security, patch or downtime comparison at all.




-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.