-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The news about MS/Suse is all over the place: - - http://www.groklaw.net/article.php?story=20061102175508403 - - http://www.groklaw.net/article.php?story=20061103073628401 - - http://www.groklaw.net/article.php?story=20061103201234813 - - http://www.itbusiness.ca/it/client/en/home/News.asp?id=41048 - - http://www.eweek.com/article2/0,1759,2050848,00.asp?kc=EWRSS03129TX1K0000616 - - http://www.cio.com/blog_view.html?CID=26338 - - http://www.streetinsider.com/Downgrades/Robert+W+Baird+downgrades+Red+Hat+(RHAT)+to+Neutral/1314330.html - - http://linux.slashdot.org/linux/06/11/03/2024206.shtml - - http://linux.slashdot.org/article.pl?sid=06/11/02/1957252
Basically, follow any of the usual tech news sites, and it is there. That said, Suse has been one of the distros I would recommend for newer users. I think *ubuntu is a better option now (and for the time being), but Suse would still be a valid choice for new to intermediate users. Maybe even advanced. It has it's issues, but it's still simpler to understand than Gentoo/LFS/Slack/etc. With this news, I'm not so sure I'll be recommending Suse, at least not until we see what the fallout of the deal is. To get the popular distros up on the website, you would do the following. - - First, you'd need at least Tier 2 access to the site, or developer access. - - Create a page. (Login. Create Content -> Page). Make the body of the page the HTML for links to the distros in questions. Hit save. - - Copy the URL for the new page. - - At this point the page is done, you just have to link to it from in the site somewhere - Resources would be a reasonable place I think. - - So, edit the resources page, and add a link to the new page. - - Go have a drink, you're done. (ok, it's not quite THAT simple, but it's definitely not hard either) I still have admin access to the site (Dave? Should I?) So if you need help, let me know - Off list. Shawn Mitchell Brown wrote: > Good plan - How shall I go about setting up this webpage? > > And, I must have missed this story about MS and Suse... I was not aware > there was such a "deal" going on. > I have no argument to remove Suse; I've always found it intimidating, > and bloated - but still fairly functional - just not a good idea for > newbies IMHO. > > On 11/4/06, *Shawn* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Better option (I think), create a page on the web site for the "popular > distributions". Then in the brochure, point to that page. > > BTW, Suse might be considered as a removal... (it's a little early yet, > but the deal with MS looks real bad...) <flamebaite off /> > > Shawn > > Mitchell Brown wrote: >> Thanks Shawn... > >> I move that we add *buntu to the "popular distributions" list, since >> what appears to be the majority of us meeting-goers run that on our >> notebooks. > >> Opinions? > > _______________________________________________ clug-talk mailing list [email protected] <mailto:[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 > -- > pub 1024D/9091C422 02/05/2006 Mitchell Brown < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> Primary key fingerprint: 812B 94BC EA0D 345A CC1C 2ED9 F7F6 5CCF > 9091 C422 > ------------------------------------------------------------------------ > _______________________________________________ > 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFTE/R2B6Swl9qN24RAkIYAKDwUAyz/blxf954KshXuo/5L8oMYQCgkZYH GZa4eUsDU4bHzbKWIPUHC3A= =QOXC -----END PGP SIGNATURE----- _______________________________________________ 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
