SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 Introductions » First time linux user. » 2013-02-04 14:14:24

rhizo
Replies: 6

Hi guys, first time linux user here! I have installed and tried:
ubuntu
mint
fedora
crunchbang
debian
and lubuntu.

And I prefer crunchbang by far smile Can't wait to get used to the interface and customise it to my liking, it seems to be a very steep learning curve coming from windows though smile

#2 Re: CrunchBang Talk » [SOLVED] Is there a general rice guide? » 2013-02-04 13:02:27

SabreWolfy wrote:

^ Dude, search is your friend here. These forums are full of what you are looking for. Use the search at the top, or go here:

http://crunchbang.org/forums/index.php

and look at the various sub-forums, particularly this one:

http://crunchbang.org/forums/viewforum.php?id=8

So wait, let me get this straight, what exactly changes the interface? tint2? When I searched earlier it came up with tint, but I wasn't sure exactly what it was. hmm

edit: Sabre, I searched for how to customize crunchbang.

edit2: Searched a few more times, sorry for the useless post guys!

conky
gtkrc (gtk theming)
themerc (openbox theming)
terminator preferences
tint2 (panel)
thunar
window decorations (on/off/theming)
compton (window opacity, shadows, titlebar opacity, etc.)
iceweasel userstyles
iceweasel startpage
Infinity, and beyond

thanks,

#3 CrunchBang Talk » [SOLVED] Is there a general rice guide? » 2013-02-04 12:55:48

rhizo
Replies: 5

Just wondering if there is a guide on how to customize crunchbang fully, such as title bar colours, menu colours, top bar configuring and colouring, etc. I'm sure there must be one but I can't seem to find it?

Thanks, sorry for the noob question.

#4 Re: Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-04 01:16:24

dura wrote:

How has this been 'solved' since your last post?

sudo update-grub

perhaps? Or you installed grub correctly to sda or something? Just curious because I haven't got my head around chroot completely either; some of the steps are confusing...

I found some bootloaderfix .iso from googleing, put it onto live usb, it loaded up a lightweight distro with xfde interface and automatically fixed grub. No idea how, but I will be sure to keep it handy smile

#5 Re: Help & Support (Testing/Unstable) » [SOLVED] Debian menu help » 2013-02-04 01:11:27

dura wrote:

How did you solve this? Curious... I have not had to add in anything to menu.xml when I've installed openbox on a base debian. It's just shown itself up in menu automagically, I think...

instead of adding

<menu id="Debian" />

to menu.xml I added

<menu id="/Debian" />

. For some reason it's not called /debian instead of just debian.

#7 Re: Help & Support (Testing/Unstable) » [SOLVED] Debian menu help » 2013-02-03 14:03:37

fatmac wrote:

Did you run menu > settings > openbox > restart.

yes, tried several times to no avail sad

#8 Help & Support (Testing/Unstable) » [SOLVED] Debian menu help » 2013-02-03 13:01:31

rhizo
Replies: 5

So I did the following, but when i add

<menu id="Debian" />

to the menu.xml, it doesn't show the menu, any ideas?

FIXED: instead of

<menu id="Debian" />

you use

<menu id="/Debian" />

due to updated code.

What I did:

1) Open the file ~/.config/openbox/rc.xml and find the following section near the bottom:

    <!-- system menu files on Debian systems 
    <file>/var/lib/openbox/debian-menu.xml</file>
    <file>debian-menu.xml</file> -->

Changed it to look like this:

   <!-- system menu files on Debian systems  -->
    <file>/var/lib/openbox/debian-menu.xml</file>
    <file>debian-menu.xml</file>

Saved the file and exit.

2) Install the menu package with the following terminal command.

sudo apt-get install menu

3) Add the following line to ~/.config/openbox/menu.xml where you would like the menu to appear:

<menu id="Debian" />

#9 Re: Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-02 20:52:47

dura wrote:

You might find this chroot method a little less confusing. It's the same, but you can see which bits to change according to your set up a bit more clearly:

sudo su
mount /dev/sda1 /mnt
mount --bind /dev  /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc  /mnt/proc
mount --bind /sys  /mnt/sys
chroot /mnt /bin/bash

Don't worry about fiddling with it. Chroot is very useful knowledge to have.

Did it all, said install successful, reboot, boots straight into windows. sad

#10 Re: Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-02 20:09:52

dura wrote:

If you installed it on a second hard drive, or your hard drive is for some recognised as sdb and you have #! installed to the third partition then yeah. You can easily examine partitions in a human readable way using 'sudo gparted'.

It's installed on a partition next to windows, so?

Thanks,

#11 Re: Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-02 20:04:00

dura wrote:

No, use it as is. Presuming you have #! installed on sda1.

I will replate sda1 with sdb3 because that is where it is installed on my hdd, does that sound right?

#12 Re: Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-02 19:58:47

[spoiler]

dura wrote:

Use Chroot:

Assumption 1: Linux is installed on /dev/sda1 but is not accessible via grub
Assumption 2: /dev/sda1 is the root partition, and you do not have a separate boot partition
Goal: reinstall GRUB in mbr of /dev/sda:

Boot from LiveCD or USB, then in the terminal window enter:

TARGET=/media/sda1
sudo mkdir -p $TARGET
sudo mount /dev/sda1 $TARGET
sudo mount --bind /dev     $TARGET/dev
sudo mount --bind /dev/pts $TARGET/dev/pts
sudo mount --bind /proc    $TARGET/proc
sudo mount --bind /sys     $TARGET/sys
sudo chroot $TARGET /bin/bash

This places you in a root terminal on the system. Do whatever you want to do there, e.g. re-install GRUB

sudo grub-install /dev/sda
sudo update-grub

To exit from chroot: press control-D or enter exit

This brings you back to where you were in the live session and you can unmount

sudo umount -l $TARGET/dev/pts
sudo umount -l $TARGET/dev
sudo umount -l $TARGET/proc
sudo umount -l $TARGET/sys

Thats it.

[/spoiler]
Thanks! so where it says $TARGET i should type /media/sda1?

#13 Help & Support (Testing/Unstable) » [SOLVED] Waldorf 64-bit fails to install grub loader » 2013-02-02 18:06:56

rhizo
Replies: 11

Installed waldorf 64-bit, worked perfectly, said grub was installed, all that good stuff, and turn pc back on and it boots straight into windows. Reinstalled 2 times with the same result, any ideas on how to fix this?

thanks,

EDIT: Just used a bootloaderfix .iso, and it fixed it for me, will link if I find where I got it from.

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo