<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://ideas.4brad.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Brad Ideas - whofig - Comments</title>
 <link>http://ideas.4brad.com/tags/whofig</link>
 <description>Comments for &quot;whofig&quot;</description>
 <language>en</language>
<item>
 <title>Alias?</title>
 <link>http://ideas.4brad.com/posix-universal-api-package-management#comment-3956</link>
 <description>&lt;p&gt;Surely rather than rename (or as well as) you&#039;d just want an &quot;alias&quot; command of some sort. Being able to say BlogFartz 4.9.2 is also SpellCheckMyBlog 2.4.0.27365 is probably only going to happen a few million times, so it is probably worth including.&lt;/p&gt;
&lt;p&gt;But I admit that I&#039;m a complete knucklehead on this stuff, I invariable spend much time cursing when I have to upgrade anything significant.&lt;/p&gt;
</description>
 <pubDate>Fri, 27 Apr 2007 22:04:41 -0700</pubDate>
 <dc:creator>Moz</dc:creator>
 <guid isPermaLink="false">comment 3956 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>Kernel drivers</title>
 <link>http://ideas.4brad.com/linux-package-upgrade-nightmare-part-1#comment-2551</link>
 <description>&lt;p&gt;I think making custom kernels is still considered a wizard thing in Linux.  There are some automatic tools for certain drivers that will do all the work for you.  &lt;/p&gt;
&lt;p&gt;But even if the package is smart enough to compile with the headers of your current kernel, you need it against all kernels you run, and you need it to know that if I upgrade my kernel, I need to recompile all the special drivers for the new kernel -- which is a risky step because they probably have not been tested against that kernel, and the whole idea of a binary package is you&#039;re getting something that&#039;s been built and tested at least minimally against what it depends on.&lt;/p&gt;
&lt;p&gt;I don&#039;t know what the plans are for the 2.8 linux kernel but a more modular driver architecture would be nice.&lt;/p&gt;
</description>
 <pubDate>Wed, 06 Dec 2006 12:36:54 -0800</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">comment 2551 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>One aspect that I appreciate</title>
 <link>http://ideas.4brad.com/linux-package-upgrade-nightmare-part-1#comment-2547</link>
 <description>&lt;p&gt;One aspect that I appreciate (at least theoretically; I run Debian Sid) about Ubuntu (and its K- and Edu- sisters) is the completeness of the system install:  most users don&#039;t want to choose between the XFree86 and X.Org, for example.  Let the advanced users worry about specialized configurations, rather than leaving it up to everyone to make each choice.  And newer machines have enough disk space that installing a &quot;complete&quot; set of libraries and system tools isn&#039;t an issue.&lt;/p&gt;
&lt;p&gt;If we were further willing to &quot;version&quot; those libraries (i.e. in the file tree, not just within the libraries), we might be able to let applications compile against newer libraries without affecting which version of each particular library other applications used.  (And tracking the reverse links could allow an eventual trimming of the library versions.  I&#039;d like to see improved support for such capabilities in the file system, but that might cause additional problems, especially in the near term.)&lt;/p&gt;
&lt;p&gt;As for kernel upgrades, I have never understood why the &quot;default&quot; binary driver packages didn&#039;t simply do the compile and install within the installation script, rather than making me execute such a script manually, line by line - often needing to consult pieces of multiple diverse sources where a script could determine the environment automatically.&lt;/p&gt;
</description>
 <pubDate>Wed, 06 Dec 2006 03:56:10 -0800</pubDate>
 <dc:creator>Paul O</dc:creator>
 <guid isPermaLink="false">comment 2547 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>Not an OS War issue</title>
 <link>http://ideas.4brad.com/linux-package-upgrade-nightmare-part-1#comment-2545</link>
 <description>&lt;p&gt;I am not sure people would switch to VMS to fix this, unless it did what they need to do.  Or Windows for that matter.&lt;/p&gt;
&lt;p&gt;This is something that Linux and most other systems have to improve.  Sysadmin cost is the highest cost of any OS, and the fact that linux is free-as-in-beer is really a pretty minor part of the cost equation right now.&lt;/p&gt;
&lt;p&gt;To my mind, unless you do want to do a lot of things yourself, you need to pick a popular distribution.  There is strength in numbers in any OS.  With a popular distro (Ubuntu/debian, Fedora, SuSE) what you&#039;re going to get is a large body of people who have been through your problems, and already solved it.   That&#039;s in part of what people like about the package systems -- on a big, popular distro, if there is some software you want, it is more likely to be in the package system so somebody has done the work of configuring and testing it on your system.  &lt;/p&gt;
&lt;p&gt;But we can do better.&lt;/p&gt;
</description>
 <pubDate>Mon, 04 Dec 2006 15:57:54 -0800</pubDate>
 <dc:creator>brad</dc:creator>
 <guid isPermaLink="false">comment 2545 at http://ideas.4brad.com</guid>
</item>
<item>
 <title>One reason why I don&#039;t use Linux</title>
 <link>http://ideas.4brad.com/linux-package-upgrade-nightmare-part-1#comment-2544</link>
 <description>&lt;p&gt;This is one of the SEVERAL reasons I would never use&lt;br /&gt;
Linux, but prefer VMS.  (VMS is free for non-commercial use;&lt;br /&gt;
for commercial use, it does cost money, but a) you get what&lt;br /&gt;
you pay for and b) it more than pays for itself since one needs&lt;br /&gt;
far fewer people to keep it running.)  I have NEVER had to do&lt;br /&gt;
a fresh install.  OS upgrades or patches are out-of-the-box.&lt;br /&gt;
It just works.  I&#039;m even running the latest version of VMS on&lt;br /&gt;
hardware which is 15 years old, and of course an executable&lt;br /&gt;
produced 15 or 20 years ago will still run on the most modern&lt;br /&gt;
hardware, with any version of the OS.&lt;/p&gt;
&lt;p&gt;I&#039;m fortunate to have a VMS day job, but I also have VMS at home.&lt;br /&gt;
No need to worry about viruses!  True, it&#039;s not a popular virus&lt;br /&gt;
target, but even if targeted it is difficult or impossible to&lt;br /&gt;
write a virus.&lt;/p&gt;
&lt;p&gt;Some folks might have used VMS several years ago and think it&lt;br /&gt;
is somewhat old-fashioned.  Actually, it is still being developed&lt;br /&gt;
and was recently ported to Itanium hardware.&lt;/p&gt;
</description>
 <pubDate>Mon, 04 Dec 2006 06:02:08 -0800</pubDate>
 <dc:creator>Anonymous</dc:creator>
 <guid isPermaLink="false">comment 2544 at http://ideas.4brad.com</guid>
</item>
</channel>
</rss>
