• General Linux Chat and Small Questions
    3,153 replies, posted
[QUOTE=pebkac;23339413]I suppose i put those commands into terminal? Also why can't i just access the file through the file browser?[/QUOTE] Yep, those commands are for the terminal. With the file browser, you can't open the files as the root user, therefore you can't save your changes. Thats what sudo does in the above commands. There is a plugin for nautilus that lets you open files as root, but I don't know if it's installed by default.
:wtc:, i can't type anything into terminal when it asks me for password. What's up with that?
[QUOTE=pebkac;23339619]:wtc:, i can't type anything into terminal when it asks me for password.[/QUOTE] Don't worry, it is typing; it's just like that so people around you don't get your password.
[QUOTE=MasterF3n;23339732]Don't worry, it is typing; it's just like that so people around you don't get your password.[/QUOTE] Oh ok thanks. It's just that usually when a program censors what you type it puts the dots or stars instead of the text, but here i really thought that something didn't work properly.
Glad to help! Speaking of which can anyone help me with my problem? I posted it back on page 2.
[img]http://www.shrani.si/f/1w/WQ/2oJzzilR/screenshot.png[/img] Here comes another problem. The folder is definitely there, not sure about the file though. Also why can't i copy to clipboard after i press printscreen? I press the button and it does nothing. Edit: wait nevermind, now the clipboard works.
[QUOTE=MasterF3n;23229398]I'm trying to get my internal wireless card in my laptop working in Mint 9 using Ndiswrapper. It says it needs both a .inf and a .sys file to work, but I only have a .sys file. Will it work without the .inf?[/QUOTE] I would assume you need both because the .sys file is the driver itself and the .ini file is the instructions for windows (or ndiswrapper in that case) to install the driver. [editline]07:04PM[/editline] [QUOTE=pebkac;23340209][img]http://www.shrani.si/f/1w/WQ/2oJzzilR/screenshot.png[/img] Here comes another problem. The folder is definitely there, not sure about the file though. Also why can't i copy to clipboard after i press printscreen? I press the button and it does nothing. Edit: wait nevermind, now the clipboard works.[/QUOTE] Well I just did some reading and just remembered that ubuntu uses GRUB2 which has a fancy auto-detection of everything (even the linux kernels.) It looks like the easiest way of removing the entries is by uninstalling the old kernel images. [url]http://ubuntuforums.org/showthread.php?t=1195275[/url] This is a post on the ubuntu forums describing the situation. In section 7 it shows you how to remove the old images. It seems like there's no fully automatic way of doing this. Here's a set of instructions I found: (they are simpler) [url]http://tombuntu.com/index.php/2007/10/17/remove-ubuntu-kernels-you-dont-need/[/url] When removing the old images, their entry from the menu should be removed. Be [b]VERY[/b] careful while removing kernel images. You don't want to remove the current Image. You also mentioned that you wanted to change the name of your Windows entry. That will be a little more complicated. What you have to do then is to disable automatic OS detection and then create your own list of menu entries. I can't really help you with that I'm not very familiar with GRUB2.
Thanks for the help Boris-B, will try doing that. Renaming the entry isn't really necessary, what i really want to do is change the order so it defaults to Windows.
Alright here's what you have to do. [b](Do this after you're done removing the old kernel images)[/b] First we need to find what's the position of the entry for the windows partition. To check this, simply go and execute the following line in a terminal: [code]less /boot/grub.cfg[/code] Now count the entries. Each menu entry should start with the following text: menuentry Press q to exit out of there when you're done. Here's something important. I would assume that you count starting from 1. GRUB doesn't. So if you started from 1 and counted up to 5 the number of the entry is actually 4. That's because GRUB starts counting at 0. So 0, 1, 2, 3, 4... and not 1, 2, 3, 4, 5... Make sure you have the right number. (4 actually means it's the 5th) Once you have that number you need to edit a config file: [code] sudo nano /etc/default/grub [/code] In there there will be a line that should look like this: GRUB_DEFAULT=0 Go ahead and change the number from 0 to the number of the entry. (Make sure you have the right number, remember that GRUB starts counting at 0 not 1. One that's changed hit Ctrl+O to save and then Ctrl+X to exit. Once you have changed that config file run the following command: [code] sudo update-grub [/code] This will generate a brand new grub.cfg file with all the changes you made. Once you're done with all give it a reboot and check if it works.
I'm trying to install Maya (Which is supported locally n'stuff) and the first line is: "Open a shell as a super user and type./setup." I can't seem to figure out how to open a shell as a super user, I'm not getting good results from my searches aside that I need to use the terminal. Any help would be awesome.
sudo ./setup Or, su root. If there are many commands to be run as root use the second one.
[QUOTE=redonkulous;23343317]sudo ./setup Or, su root. If there are many commands to be run as root use the second one.[/QUOTE] I get a "command not found" with sudo. The second one from what I read isn't something to be used if there's a better way, which sudo seems to be. Odd that it isn't quite working.
does it say that sudo doesn't exist or that ./setup doesn't exist?
[QUOTE=Boris-B;23344358]does it say that sudo doesn't exist or that ./setup doesn't exist?[/QUOTE] I get: "sudo: ./setup: command not found"
you need to cd into the directory where the setup file is located [code] cd /where/that/file/may/ever/be [/code]
[QUOTE=Boris-B;23344505]you need to cd into the directory where the setup file is located[/QUOTE] That worked perfect, thanks! Thought it appears I only have a install for 64 bit linux and no 32 bit. Can I just switch over to 64 bit with no problems or does my hardware need to support it? I'm sorta in the dark with this stuff.
Wait, how in hell does Maya only support 64bit?
[QUOTE=Boris-B;23345564]Wait, how in hell does Maya only support 64bit?[/QUOTE] There is only a 64 bit for Linux for maya 2010, everything else has 32 and 64, why this is I don't know.
Well, if you want to switch to 64 bit you need a 64 bit capable CPU and you'll need to reinstall. A 64 bit capable CPU is any multicore CPU (Dual Core and up). Make sure you didn't get the 64bit version and not the 32bit version.
[QUOTE=Boris-B;23345953]Well, if you want to switch to 64 bit you need a 64 bit capable CPU and you'll need to reinstall. A 64 bit capable CPU is any multicore CPU (Dual Core and up). Make sure you didn't get the 64bit version and not the 32bit version.[/QUOTE] IT seems I blankquoted, what I meant to say: I have a quad core so I SHOULD be good right? Anyway now to fiddle with wine and get touhou running at a decent fps.
Thanks again Boris, it all worked great.
[QUOTE=Boris-B;23340217]I would assume you need both because the .sys file is the driver itself and the .ini file is the instructions for windows (or ndiswrapper in that case) to install the driver.[/QUOTE] [img]http://anyhub.net/file/4untitled.bmp[/img] Problem is, I don't have a .inf file with it.
Some horrible fuck up just happened to me. I didn't like the panel at the top in Ubuntu, so i decided to have two panels at the bottom of the screen. I proceeded to add and remove some items from the panels and turned on autohide, then everything just froze up. I could move the mouse but nothing would respond to clicks. I rebooted the computer and when i logged in to my account, the desktop was completely empty, there was only the background image and rightclick refused to work. I then rebooted into recovery mode and chose the fix packages option, it downloaded a few packages and installed them. I rebooted again but it seems to have fixed nothing. What should i do now?
[QUOTE=pebkac;23352191]Some horrible fuck up just happened to me. I didn't like the panel at the top in Ubuntu, so i decided to have two panels at the bottom of the screen. I proceeded to add and remove some items from the panels and turned on autohide, then everything just froze up. I could move the mouse but nothing would respond to clicks. I rebooted the computer and when i logged in to my account, the desktop was completely empty, there was only the background image and rightclick refused to work. I then rebooted into recovery mode and chose the fix packages option, it downloaded a few packages and installed them. I rebooted again but it seems to have fixed nothing. What should i do now?[/QUOTE] Boot into Ubuntu live environment, delete Ubuntu partitions (right click on the swap partition and choose swapoff before you delete it (doesn't let you if you don't)) and reinstall on the empty space. By the way, keep it as unallocated space; NOT an empty partition, it'll make one for you.
Is there no way to fix it without reformatting?
Not one I can think of, stick around for a while, maybe someone else can help you out without reformatting.
Okay i tried to login using failsafe gnome and it actually displayed the panel but it was flashing weirdly and when i opened the system monitor from the panel i found out that the gnome-panel process was maxing the CPU. I tried to end or kill the process, but it just says "uninterruptible".
If you can get into terminal kill `ps ax | grep gnome-panel | grep -v grep | awk '{print $1}'` should kill it (I think)
I can run the xterm session and run nautilus from there and also access firefox if i need to. Now i just want to know where the gnome configuration settings are and how do i delete them? [editline]02:53PM[/editline] Nevermind i managed to reset it with the help of uncle Google. [editline]02:54PM[/editline] Note to self: Never, ever put two panels at the same place. Ughh.
with gcon-editor you should be able to remove the panels next time :P
Sorry, you need to Log In to post a reply to this thread.