gunnervi wrote:ew wrote:Ok, open a terminal window and enter the commands below,I did this, and nothing changed. I rebooted, and still nothing. Should I resort to re-installing #! now, or are there other things I can do to try and fix this?Is it Waldorf or Statler you use? If it`s Statler you probably would want to upgrade to Waldorf anyway, now that Waldorf is the new stable release.
I currently run Statler on my laptop, but now I'm looking to install Crunchbang on my desktop. I was wondering whether I should install Statler or the latest beta on my desktop. If I install Statler, how easy will updating to Waldorf be in the future? I've never done an upgrade beyond just updating packages before. Will the move to Waldorf be simple as that?
hi,I am afraid I cannot help very much as for your first request, but maybe this page will... If you decide to reinstall Waldorf, as long as you do not touch the /home partition, everything should be fine...I won't go for Statler now that it is about to become old-Stable..it is just, well, old and Waldorf is already extremely reliable...
@Blackout: Is this after a migration from Statler to Wheezy/Waldorf or Sid, or is this on a clean Waldorf install? If the latter, I can fork this to the Development area.
As I'm sure many here will remember, whenever a new "point release" of Statler came out, the most reliable upgrade path was, unfortunately, a clean install. Has anyone heard anything about Corenominal developing a more painless upgrade path for getting from Statler to Waldorf? (Perhaps a script?)Looks like someone's recently tried such an upgrade through editing sou
Hey all, I'm new to #!, and I currently have Statler on my laptop. I enjoy it, and everything is working as it should. I've noticed that Waldorf is being tested currently.
What records should I include in sources.list to properly and without complications update CrunchBang Statler to Waldorf ? Please inclusion of the relevant entries.
a weird one here, I have been running statler for a while, numerous installs, everything fine. But Waldorf wont let me connect wirelessly. Here is the deal, I have an acer aspire one netbook. #! statler works out the box, but waldorf, no network. I have hooked up wired and installed every wireless package that I have in statler and no go.
Hello everyone. I am Eduardo, a new Ubuntu refugee that's happily turning to Crunchbang. :)While not any admin by far, I have some Debian experience from long years ago using testing, and no trouble making some tweaks here and there.
Email this page
