[ Closed ] CrunchBang 10 "Statler" Alpha 2 Released (Page 5 of 5)

FWIW, I did a Live USB install using the method in post #79 on this thread and my account was added to /etc/sudoers and sudo works fine.  (The Live USB was created with the #! wiki instructions, but I believe the method would work the same with a Unetbootin stick.)

My /etc/apt/sources.list includes the crunchbanglinux.org repos, official debian squeeze repos and official debian security repos.  My /dev/sdb (substituted for /dev/cdrom in the install process) is not in my /etc/apt/sources.list.  It was only used during initial install, in lieu of a CD-ROM.

Edit: copy of sources.list

## CrunchBang Linux 10.xx aka Statler
## Compatible with Debian Squeeze, but use at your own risk.
deb http://packages.crunchbanglinux.org/statler statler main
## Official Debian Repositories:
deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free
# deb-src http://ftp.de.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main
# deb-src http://security.debian.org/ squeeze/updates main

Last edited by secdroid (2010-06-28 14:33:32)

Oh I didn't know about that method! It would have saved me from reinstalling in the first place... anyway it's working now Thanks for the tip secdroid!

Glad to see I am not the only one with UNetbootin problems.  It tells me, it is not me.  When I looked at the card all the files were there, it just did not boot, and I have my BIOS set to boot from:
1. CD
2. USB
3. HD
4. Floppy (yes, I still one, no idea why - have not uses it in YEARS!)

FWIW, I've had problems with Unetbootin in the past.  That's why I used the #! wiki USB creation method instead --
http://crunchbanglinux.org/wiki/statler … stallation

Note: Gparted and other disk tools show the USB stick as invalid, but it boots fine.  Ran Live USB on desktop and netbook.

Note: If you are going to install  from the boot menu --
Due to an apparent hardcoded installer assumption that Debian distro files come from CD-ROM, check out my post #79 in this thread for a workaround.

Same here. Must be related to the unetbootin install method.

Oh, OK,  thanks for the tip.

I would have though  UNetbootin would have set it up that way. 

GREAT link, bookmarked (post 79 as well) ... since this was my first attempt I didn't see that I read a bit at the UNetbootin site, should have been more. 

I want to thank everybody who has responded with their alpha 2 feedback. I am sorry that I have not been able to reply to each individual post, but rest assured I have been reading all the posts carefully and making notes -- my TODO list is growing by the day.

From what I have been able to gather, it seems as if the keyboard language/layout problem is currently the issue which is affecting the most users. It also looks as if the UNetbootin issues are only partially resolved with some people reporting successful installs, while others have experienced failures.

With regards to the keyboard problem, it looks as if the language selection which is chosen during the installation is not being carried through to the installed system. I am not too sure why this is happening, but I will look into it and try to get it fixed before the next build. Meanwhile, I will create a "known issues" topic with details about how to change the default system keyboard layout.

With regards to the UNetbootin issues, this could be more difficult to pin down as there are so many different variables involved. Maybe a good place to start would be to try and figure out which versions of UNetbootin are working? I will start a new topic for this too.

I will now close this thread, so as to encourage people to start new topics for individual problems. Thank you again to everybody who has provided feedback.