On Thursday 30 November 2006 23:40, Gustin Johnson wrote:
> Shawn wrote:
> > This split is overdue.  Though it's been discussed and rejected a few
> > times in the past 3 or 4 years.  I personally think the tech issues are
> > lost in the non-tech chatter that has become clug-talk (through no fault
> > of anyone though).
>
> Clug-tech is a good idea.
>
> > As for interoperability.  I'm having problems seeing the distinction.
> > Am I hearing that anything to do with Windows should not be on this
> > list?  If so what about asking for help with my samba config because a
> > windows box can't connect to it (and presumably other Linux boxes).  The
> > samba configs are rather technical, and FOSS specific.  Granted,
> > configuring Windows is definitely off topic, but the samba based problem
> > introduces a grey area.
>
> I do not happen to agree with this distinction, but then networking and
> therefore interoperability between many different OSs (I interact with
> at least 4 OSs on a near daily basis) is central to my computing
> paradigm.  I will comply with this distinction as best I can, though for
> the record I think it is a bad idea.
>

I agree. There are times when interoperability is not optional. My network at 
home is exclusively Linux, with my laptop dual-booting for games and testing 
that other browser (though Shawn finding ies4linux was very useful!). However 
I work with people that use Windows every day and if they can't get on one of 
my Linux-driven services does that make it a non-Linux issue? I don't think 
so....perhaps it becomes a Windows issue if the problem is on their end, but 
it can be hard to tell even that sometimes. On the other side of the coin if 
someone on a Windows-centric group told me to solve my Samba issue by 
switching to Windows they would get an unfavorable response.

What if it's a client on Windows unsuccessfully connecting to my Linux box 
because his Linux-based router is somehow screwed up? :P food for thought - 
OSS is about choice, and for Linux to be my choice I need to be able to work 
with those that haven't seen the light.

> > Just trying to make sure I'm understanding the distinction.
>
> This is good time to have this discussion, before a precedent has a
> chance to be set.
>
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to