Ask Your Question

lanmaster82's profile - activity

2014-09-29 00:18:54 -0600 received badge  Famous Question (source)
2014-09-29 00:18:54 -0600 received badge  Notable Question (source)
2014-08-21 02:04:25 -0600 received badge  Famous Question (source)
2014-05-10 05:41:42 -0600 received badge  Taxonomist
2013-09-16 11:16:25 -0600 received badge  Famous Question (source)
2013-09-16 11:16:25 -0600 received badge  Popular Question (source)
2013-09-16 11:16:25 -0600 received badge  Notable Question (source)
2012-09-24 18:51:51 -0600 received badge  Popular Question (source)
2012-07-15 06:05:33 -0600 received badge  Good Answer (source)
2012-06-13 07:56:05 -0600 received badge  Notable Question (source)
2012-04-30 11:56:16 -0600 received badge  Popular Question (source)
2012-04-19 14:26:54 -0600 received badge  Nice Answer (source)
2012-04-19 10:21:58 -0600 answered a question Sofia is not in the sudoers file

Open gnome-terminal and type the following:

$ su -
Password [type in the root password here]

Your bash line will change from $ to # indicating that you are now using the root account. At this point you’re going to use a text editor to modify the file /etc/sudoers. My preferred graphical editor is gedit.

# gedit /etc/sudoers

Once the document is open you will scroll down until you see:

## Allow root to run any commands anywhere
root            ALL=(ALL)     ALL

Simply append that section with your user account and save the file. You will need to log out so that the sudoers parameters propagates the system. Let’s pretend that your user account is testuser.

## Allow root to run any commands anywhere
root            ALL=(ALL)     ALL
testuser     ALL=(ALL)     NOPASSWD: ALL
2012-04-06 06:57:43 -0600 commented answer Get popup on boot, GNOME 3 unavailable

I agree, definitely a graphics driver issue. But to be honest, Gnome 3 is terrible, use KDE...LOL

2012-04-06 06:56:23 -0600 received badge  Supporter (source)
2012-04-04 09:04:17 -0600 answered a question Get system installation date

Here is another method, but this is assuming you formatted the disk when you installed:

dumpe2fs /dev/sda1 | grep 'Filesystem created:'

2012-04-04 08:18:35 -0600 commented answer Get system installation date

You want to look at the creation date, not the modified date.

2012-04-04 08:13:01 -0600 answered a question Get system installation date

Supposedly you can also get the installation date from the creation date of the install.log file in /root

I also just checked that on 2 other Fedora boxes I have and it is accurate.

2012-04-04 08:08:50 -0600 received badge  Commentator
2012-04-04 08:08:50 -0600 commented answer Get system installation date

Interesting, It has always worked for me. Not sure, let me do a little more digging.

2012-04-04 07:45:14 -0600 commented answer Get system installation date

ok, so it lost the formatting when I posted it, but the info is in there.

2012-04-04 07:44:21 -0600 answered a question Get system installation date

This will usually do the trick: rpm -qi basesystem

Here is what the results look like:

Name : basesystem Version : 10.0 Release : 5.fc16 Architecture: noarch Install Date: Wed 21 Mar 2012 01:21:36 PM EDT Group : System Environment/Base Size : 0 License : Public Domain Signature : RSA/SHA256, Wed 27 Jul 2011 07:20:14 PM EDT, Key ID 067f00b6a82ba4b7 Source RPM : basesystem-10.0-5.fc16.src.rpm Build Date : Thu 23 Jun 2011 04:31:58 PM EDT Build Host : x86-09.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project Summary : The skeleton package which defines a simple Fedora system Description : Basesystem defines the components of a basic Fedora system (for example, the package installation order to use during bootstrapping). Basesystem should be in every installation of a system, and it should never be removed.

2012-03-28 11:52:26 -0600 answered a question How to install XFCE on alongside Gnome Shell?

Just run the add/remove software application in Gnome, search for XFCE (Or KDE, LXDE, whatever you want.) Select it, let it install, then when you are at the login screen you have the option to select which environment you want to login to. The option should show right under the password box.

2012-03-26 06:44:27 -0600 commented question emachine fedora live cd won't load

Have you tried booting with basic video? I use linux live CDs quite often for general troubleshooting and data recovery, I boot many different machines off of them, and I'd say 35% to 45% of the time I have to boot using the basic video option.

2012-03-23 10:50:32 -0600 commented answer How to downgrade a package in Fedora 16?

Huh, I didn't know it had a downgrade function either....Thanks, this will be useful in the future I'm sure.

2012-03-23 08:34:27 -0600 commented question Nautilus ftp session delay

Are you sure it is not the server you are connecting to timing out your connection?

2012-03-23 07:30:00 -0600 received badge  Organizer (source)
2012-03-23 07:06:33 -0600 answered a question Fresh install no bootable drive

I'm thinking you may be seeing the same issue I just had recently. It was caused by Fedora 16 using GPT labeling for the hard drive be default. Your BIOS may just be handling it a little differently than mine. I just got a blinking cursor. Here is the link to my post with the issue:

http://ask.fedoraproject.org/question/1346/flashing-cursor-on-fresh-install-of-fedora-16

You can read through it, but basically you would need to boot from the live usb, when you get to the grub screen hit "Tab" and append "nogpt" (without the quotes) to the end of the line.

Hope this helps.

2012-03-23 06:55:13 -0600 answered a question Is there a way to install Fedora16 from a LiveCD with GPT disabled?

Wow, I guess I just wasn't thinking. You can boot the LiveCD with the "nogpt" option just the same.

2012-03-23 06:49:11 -0600 received badge  Editor (source)
2012-03-23 06:47:09 -0600 received badge  Autobiographer
2012-03-23 06:41:24 -0600 commented answer Sound working in Gnome but not KDE

Yeah no luck there. Its got to be something in the settings, if I boot from the Fedora Live KDE spin it works fine, I've got to be missing something stupid...LOL

2012-03-22 16:43:26 -0600 received badge  Teacher (source)
2012-03-22 12:47:41 -0600 commented question Blank screen after installing F16 (upon reboot)...Please let me know if there are any answers?

Hmmm... I just had a similar issue, but I had a blinking cursor. Come to think of it, because of the odd resolution as the BIOS level, I could not see the blinking cursor at first until I played with the V-Position on my monitor. The odd resolution had the image going off of the screen.

2012-03-22 12:44:58 -0600 commented answer Sound working in Gnome but not KDE

Already installed.

2012-03-22 11:35:51 -0600 commented question Blank screen after installing F16 (upon reboot)...Please let me know if there are any answers?

Was it a completely blank screen, or did you have a flashing cursor in the top left corner?

2012-03-22 07:42:19 -0600 asked a question Sound working in Gnome but not KDE

So I have always been a Gnome user, but now with Gnome 3.... Well... You know.

So I'm using KDE, but my sound isn't working. Seems to be a fairly common thing judging by my Google searches, but I have yet to find a fix for it. Anyone have any suggestions?

[EDIT]

I should mention that the sound works fine if I boot from the Fedora Live KDE spin CD.

2012-03-21 15:00:07 -0600 answered a question terminal fedora 16

sudo only works if your user is in the sudoers file.

you may have to try typing "su" in the terminal and entering the root password when it prompts for it. Then running yum.

But I agree, don't play with root access until you understand how much you can screw up.

2012-03-21 14:23:30 -0600 asked a question Is there a way to install Fedora16 from a LiveCD with GPT disabled?

I had to install from the full DVD and add the nogpt option at boot. Is there a way to install from a LiveCD and have GPT disabled or tell it not to use it somehow?

2012-03-21 12:51:49 -0600 answered a question Flashing cursor on fresh install of Fedora 16

Ok, it was the new GPT labeling for the disk that Fedora 16 uses by default. Here is the info to work around it:

"If you are affected by this problem, you can work around it by passing the parameter nogpt to the Fedora installer. To do this, at the initial bootloader menu for the Fedora installation, where you can select to install, install in basic graphics mode, boot to the rescue mode and so on, hit the Tab key, then edit the command line for the Fedora installer and add the word nogpt. "

And the url of the page I found the info:

https://fedoraproject.org/wiki/CommonF16bugs#Somesystems.2CparticularlyAppleMacs.2CcannotbootGPT-labelleddisks

Look about 1/3 of the way down for the heading "Some systems, particularly Apple Macs, cannot boot GPT-labelled disks ".

2012-03-21 12:15:04 -0600 commented question Flashing cursor on fresh install of Fedora 16

I may have just found the issue. My BIOS may not support booting from a GPT disk. Am re-installing now with nogpt added to the installer boot line from the dvd. If it works I will post results and more specific instructions.

2012-03-21 11:48:39 -0600 asked a question Flashing cursor on fresh install of Fedora 16

I just did a clean install of Fedora 16 on my system. All I get after the BIOS screen is a flashing cursor. I have found and red numerous posts all over the internet for similar issues, but have yet to find anything that fixes my problem. Obviously it has something to do with the MBR and Grub, but just can't seem it resolve it.

The disk did have Windows installed on it previously, some people have mentioned that this makes a difference. Also, if I install Fedora 15 it boots fine, re-install 16 and I get the same blinking cursor.