<br><br><div class="gmail_quote">On Mon, Apr 26, 2010 at 11:32 AM, Ramnarayan.K <span dir="ltr"><<a href="mailto:ramnarayan.k@gmail.com">ramnarayan.k@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 4/26/10, Ritesh Sinha <<a href="mailto:sinha.k.ritesh@gmail.com">sinha.k.ritesh@gmail.com</a>> wrote:<br>
>><br>
> Arch is the best (well documented) rolling release. No other beginner<br>
> friendly ones that I am aware of. But you can look at it this way,<br>
> once you've spent the effort in setting it up the first time you don't<br>
> really have to do much to keep it running. You should also be aware<br>
> that you will usually have bleeding edge software and compatibility<br>
> might break from time to time (this is anecdotal of course, YMMV).<br>
<br>
</div>So what kind of net connection is required for Arch -<br>
<br>
from what i can gather a pretty reliable and fat pipe seems to be the<br>
order of the day.<br>
<br>
was realy curious what rolling release meant - so checked the wiki<br>
<a href="http://en.wikipedia.org/wiki/Rolling_release" target="_blank">http://en.wikipedia.org/wiki/Rolling_release</a><br>
<br>
"A rolling release is typically implemented using small and frequent<br>
updates. However, simply having updates does not automatically mean<br>
that a piece of software is using a rolling release cycle; to qualify<br>
as a rolling release, the philosophy of developers must be to work<br>
with one code branch, as opposed to discrete versions. Updates are<br>
typically delivered to users using a package manager and a software<br>
repository accessed through the internet."<br>
<br>
seems to me that this is something that requires constant access to<br>
the net and also not really meant for systems that require stability.<br>
The latter because there is no way such solling release can account<br>
for individual systems setup and cutomized (or can it)<br>
<br>
The advantage i see is that instead of lump sum one gets small updates<br>
(maybe) and it means that after the initial install , maybe, one can<br>
survive on a small bandwidth.<br>
<br>
There won't be patches, anything recitified will automatically appear<br>
in the main rolling release<br>
<br>
Also it probably means there is never going to be any excitement /<br>
hype about the latest release. Once you install a rolling release all<br>
one can say is "aha my system is the same as it was 10 years ago" -<br>
thats something actually.<br></blockquote><div><br>on the bright side, no need to reinstall with every release(Of course Upgrade option is there, but I say "Upgrade is fairly usless to 60% of the users", reinstallation will give a different feel than Upgrade")<br>
<br>Now I feel should give a try to Arch and Gentoo.<br><br>Ubuntu is becoming more of Suse I think, more commercialization than Democracy...<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
<br>
regards<br>
ram<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">ubuntu-in mailing list<br>
<a href="mailto:ubuntu-in@lists.ubuntu.com">ubuntu-in@lists.ubuntu.com</a><br>
<a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-in" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-in</a><br>
</div></div></blockquote></div><br>