LibranetThis forum is for the discussion of Libranet Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
True you could update. But there are problems doing an update like that. I have killed my system more than once using apt-get. I am just waiting for Libranet 3.0 too. It is by far better. Ubutnuusnuu is good but one I can't pronounce the name or spell it and it really lacks in many areas. I went do install galeon (the best web browser ever) and NOPE, not there... the sources.list is near nothing. So, yep I am just waiting.
Originally posted by jaa1180 True you could update. But there are problems doing an update like that. I have killed my system more than once using apt-get. I am just waiting for Libranet 3.0 too. It is by far better. Ubutnuusnuu is good but one I can't pronounce the name or spell it and it really lacks in many areas. I went do install galeon (the best web browser ever) and NOPE, not there... the sources.list is near nothing. So, yep I am just waiting.
I see things differently. I had, until last summer, used Libranet 2.0 as my main desktop system, and I had no trouble with it at all. I purchased Libranet 2.7, but I had a lot of time and effort invested into installng just the right combination of stable, testing, unstable, and experimental packages that I had a great mix. But when Libranet 2.8 came out, they added an excellent safe upgrade feature, backed against their own set of changes, which in themselves were a blend of packages from testing and unstable. I ran 2.7 and 2.8 on their own partitions for a while, in addition to my well tuned 2.0 system, but one day, when the free 2.8.1 download became available, I decided to UPGRADE my 2.0 system to 2.8.1. That actually WORKED! I did it by adding the 2 Libranet 2.8.1 CDs to my apt list using the apt device tool. Libranet has their own tool, or you can use the manual apt tool. I used the manual tool. My upgrade to 2.8.1 worked fine.
One day, though, I just decided to see what would be different between my hybrid system and a pure 2.8.1 system, not because I had to do it, but just because I wanted to be able to write about it.
Replacing the system with my 2.8.1 new system was easy. I used another disk partition to copy any personal files, including configuration files that I wanted to change, and I used the tar command to copy them off to the other partition. Then I installed Libranet 2.8.1, then I tried out the plain system to make sure it worked, then I copied back in my files (untarring them from the other saved partition), then I checked out my system. It worked fine. Finally, I used the safe ugprade tool provided by Libranet to get the newest bits and apps available from their testing archive. That worked fine.
My final test was to add unstable packages into the mix and do a safe upgrade again and see if it still worked. The answer was yes, and to this day, I use Libranet's upgrade tool to update a blend of testing and unstable packages. I'm still based on 2.8.1, but I'm guessing that most of the applications in my existing system are as new or newer than what I'll see in the upcoming V3.0 release.
Nevertheless, I am excited about usability and packaging plans that are nearly complete for Libranet 3.0. I intend to test them and use them the next time I upgrade my system. Libranet is the best at this - they let you use either the plain Debian tools or their tools and both work. well.