General Linux Chat and Small Questions - Hardware & Software

Couple of awesome questions: How do you change the number of desktops? 9 is way more than I'll ever need and I'd like to change it to three or four. How do you reposition floating windows with the mouse? The windows don't have title bars or borders so there doesn't seem to be a way to grab them. [b]Edit:[/b] Figured out the floating windows. Still trying to get to the bottom of the number of desktops...

[QUOTE=Larikang;29325527]Couple of awesome questions: How do you change the number of desktops? 9 is way more than I'll ever need and I'd like to change it to three or four. How do you reposition floating windows with the mouse? The windows don't have title bars or borders so there doesn't seem to be a way to grab them. [b]Edit:[/b] Figured out the floating windows. Still trying to get to the bottom of the number of desktops...[/QUOTE] In this part of the config just remove the numbers you don't want: [code]tags = {} for s = 1, screen.count() do -- Each screen has its own tag table. tags[s] = awful.tag({ 1, 2, 3, 4, 5, 6, 7, 8, 9 }, s, layouts[1]) end[/code] EDIT: I haven't tested, but I think it should work.

Ah thanks. That worked.

Hey guys. Quick question: I'm trying to install Arch Linux on my computer, first time. I have partitioned the drive like this: 100 mb : Windows 7's boot thinge ~200 gb : C: drive ~200 gb : D: drive (Both of these came by default) /dev/sda4 : Extended ---/dev/sda5 : ext4 ---/dev/sda6 : linux-swap First of all: Is it okay if I install the whole of it to a single ext4 partition? Even if it's logical and not primary? Second: The Wiki says [QUOTE]Note: It is also possible to install GRUB to MBR (dev/sda). This works fine with Windows 7. [/QUOTE] But I'm skeptical: Would /dev/sda be the "whole" drive, or the 100mb partition Win7 uses as a boot? (Though I think that's /dev/sda1). Can I just install GRUB in the /dev/sda5, that is, the logical ext4 partition? Or would that fuck shit up due to being, well, logical?

[QUOTE=Eudoxia;29369181] First of all: Is it okay if I install the whole of it to a single ext4 partition? Even if it's logical and not primary?[/quote] Yeah, that will work. [QUOTE=Eudoxia;29369181] But I'm skeptical: Would /dev/sda be the "whole" drive, or the 100mb partition Win7 uses as a boot? (Though I think that's /dev/sda1). Can I just install GRUB in the /dev/sda5, that is, the logical ext4 partition? Or would that fuck shit up due to being, well, logical?[/QUOTE] /dev/sda does refer to the whole drive, and this is where you should install grub. Whatever is in the MBR at /dev/sda is loaded at boot which is the windows boot loader right now. In order to use grub you have to replace this.

I've [b]FULLY[/b] updated my Gentoo installation. 39 configuration files need to be modified. It doesn't want to boot right now. :saddowns:

Such is life with Gentoo. (I'm sorry, I had to!)

There we go, it booted up, now I'm off to update 39 configuration files :v:

Just have it replace them all and see what happens =P

Done, everything works now (hopefully) ! :keke:

What should I use? Nginx or Apache2?

Thumbs up for nginx.

Apache2 if you're a pussy who just wants stuff to work, nginx if you have balls and want to punch babies with laser beams.

Why is pacman -Syu taking so long on my Arch machine. :colbert:

After forgetting to check Facepunch for the answers last page and finally getting access to an wired connection, I managed to update my Arch install and then get wireless working (though it was a bit difficult). But, I'd like to try getting it to connect automatically. I have to enter a few commands (ifconfig wlan0 up, then ifconfig wlan0 essid "access point name", then in some cases dhcpcd wlan0) to get on the internet though, and it's sometimes a pain in the ass because I'm used to having wireless working instantly. They all have to be run as root, so I can't add them as a gnome startup application or anything. I've read the Wireless Setup article on the arch wiki and I've tried netcfg and something else (forgot what it was) but it wasn't doing anything.

Get Wicd.

[QUOTE=Ca5bah;29392674]Get Wicd.[/QUOTE] Funny, I could never get either Wicd or Networkmanager or Connman to work for me, I had to use netcfg if I wanted it to work reliably.

[QUOTE=Lyoko774;29392690]Funny, I could never get either Wicd or Networkmanager or Connman to work for me, I had to use netcfg if I wanted it to work reliably.[/QUOTE] I've never had a single problem with Wicd at all.

[QUOTE=Ca5bah;29392778]I've never had a single problem with Wicd at all.[/QUOTE] Except for me - the interface confuses me terribly.

[QUOTE=Sonicfan574;29392459]After forgetting to check Facepunch for the answers last page and finally getting access to an wired connection, I managed to update my Arch install and then get wireless working (though it was a bit difficult). But, I'd like to try getting it to connect automatically. I have to enter a few commands (ifconfig wlan0 up, then ifconfig wlan0 essid "access point name", then in some cases dhcpcd wlan0) to get on the internet though, and it's sometimes a pain in the ass because I'm used to having wireless working instantly. They all have to be run as root, so I can't add them as a gnome startup application or anything. I've read the Wireless Setup article on the arch wiki and I've tried netcfg and something else (forgot what it was) but it wasn't doing anything.[/QUOTE] netcfg works well for me on my laptop.

[QUOTE=Ca5bah;29392778]I've never had a single problem with Wicd at all.[/QUOTE] While for me, Wicd keeps disconnecting from my wireless network, so I just use networkmanager.

[QUOTE=IpHa;29369412]/dev/sda does refer to the whole drive, and this is where you should install grub. Whatever is in the MBR at /dev/sda is loaded at boot which is the windows boot loader right now. In order to use grub you have to replace this.[/QUOTE] Excellent. So I just install GRUB on /dev/sda. However, the Wiki... [QUOTE]When installing grub, you must configure /boot/grub/menu.lst), and make sure to install grub to /boot (or root (/) if you did not create a separate partition for /boot). Installing grub onto your Windows partition may cause Windows not to boot. Note: The above instruction is conflict with the GRUB installation position documented in GRUB#General notes about bootloader installation which says GRUB should be installed to MBR or the first partition to be recognized by most BIOS. [/QUOTE] But then: [QUOTE]Note: It is also possible to install GRUB to MBR (dev/sda). This works fine with Windows 7. [/QUOTE] So I will just install over the MBR. Now, on the Wiki it also says I have to make sure to uncomment a few lines in the .conf file if I'm dual-booting with Windows so it looks like this: [QUOTE]# Windows XP title Windows XP rootnoverify (hd0,0) chainloader +1 [/QUOTE] But on sample GRUB.conf files there's always some "makeactive" line. Does this mean I should just leave it commented out? In any case I can always reboot and try again, to an extent. Moreover: If I fuck shit up (Without deleting any partitions, just a sibbly-wibbly GRUB placement/conf error) is there a way (Without the disk, which I don't have) to recover access to Windows 7? Maybe with one of those "Super GRUB" disks?

I think you've been over-complicating this. Here's how it goes. First you install grub to /dev/sda (the MBR) this is the first 512 bytes of the drive IIRC. The MBR is the code segment used to boot the OS from the drive. When you install GRUB there it will overwrite what was there. This is what you want. You'll still be able to boot windows through chainloading. The entry in the config should look like this [code] # (2) Windows 7 title Windows 7 rootnoverify (hd0,0) # Should point to the windows partition #makeactive # Uncomment this if you're not using windows 7 chainloader +1 [/code] If by some odd reason the thing doesn't want to boot. You can always try to either boot Windows or your Linux install. Any live CD that comes with GRUB should allow you to enter the GRUB console and boot an OS manually. IIRC c will bring you to the console. It should tell you what key to press. To boot windows you should type the following in the console [code] rootnoverify (hdX,Y) # make sure it's your windows partition makeactive # Only if not windows 7 chainloader +1 boot [/code] Once you're in windows you can reinstall the windows bootloader using [code] fdisk /fixmbr fdisk /fixboot [/code] If you're unsure you can always post your config and let us make sure it's all right. As a side note here's a correction to the confusion on the wiki. If you want to install alongside windows and you have no other Linux distro installed. Install grub to the MBR (/dev/sda) if you have another Linux Installation that provides GRUB already. Install grub to your /boot partition (if you didn't make one install to your /) partition. I'm assuming you only have windows installed. It would be best to install to the MBR then.

So, the built-in weather argument for conky isn't working. Is it just me or everyone?

I tried installing Arch Linux yesterday, and I managed to do so. Great! Now, I installed xorg, my nVidia driver, etc., and I should be ready to go with my gui. Unfortunately, whenever I start my computer and boot into Arch, I am unable to type or go to different screens (via ctrl + alt + Fn), and I get a bunch of the same error ("gdm-binary[1014] warning: GdmDisplay: display lasted 0.9xxxx... sec") and then a final error ("GdmLocalDisplayFactory: Maximum number of X display failures reached: check X server log for errors."). I tried changing my rc.conf and inittab files back to what they originally were, and that gets rid of the errors, but I still can't type into the terminal. As far as I remember, I've only edited rc.conf, inittab, and .xinitrc. Any advice will be greatly appreciated.

[QUOTE=Boris-B;29406440]I think you've been over-complicating this. Here's how it goes. First you install grub to /dev/sda (the MBR) this is the first 512 bytes of the drive IIRC. The MBR is the code segment used to boot the OS from the drive. When you install GRUB there it will overwrite what was there. This is what you want. You'll still be able to boot windows through chainloading. The entry in the config should look like this [code] # (2) Windows 7 title Windows 7 rootnoverify (hd0,0) # Should point to the windows partition #makeactive # Uncomment this if you're not using windows 7 chainloader +1 [/code] If by some odd reason the thing doesn't want to boot. You can always try to either boot Windows or your Linux install. Any live CD that comes with GRUB should allow you to enter the GRUB console and boot an OS manually. IIRC c will bring you to the console. It should tell you what key to press. To boot windows you should type the following in the console [code] rootnoverify (hdX,Y) # make sure it's your windows partition makeactive # Only if not windows 7 chainloader +1 boot [/code] Once you're in windows you can reinstall the windows bootloader using [code] fdisk /fixmbr fdisk /fixboot [/code] If you're unsure you can always post your config and let us make sure it's all right. As a side note here's a correction to the confusion on the wiki. If you want to install alongside windows and you have no other Linux distro installed. Install grub to the MBR (/dev/sda) if you have another Linux Installation that provides GRUB already. Install grub to your /boot partition (if you didn't make one install to your /) partition. I'm assuming you only have windows installed. It would be best to install to the MBR then.[/QUOTE] Everything's answered. Thank you! Now... One more thing: I have a 64-bit processor, running 32-bit Windows 7 (Long story) and I'm going to install 64-bit Arch. I'm assuming there won't be any complications.

No complications at all

Was installing Blackbuntu 0.2. Installer crashed. I guess that's why it's 0.2.

Anyone happen to know what mono addon rpm pdb2mdb is in? I can't find it :( [url]http://ftp.novell.com/pub/mono/download-stable/RHEL_5/x86_64/[/url]

Where can I get the source code of Cedega?