Re: F21 Interface renaming

On Mon, 2016-04-11 at 12:41 +, Weiner, Michael wrote: > 1) append "net.ifnames=0 biosdevname=0" to /etc/default/grub > GRUB_COMMAND_LINUX (doesn’t seem to have any affect) After modifying the default grub config, did you run: `grub2-mkconfig -o /boot/grub2/grub.cfg` or

Re: Fedora-like Linux for 1.99GB RAM?

On Sat, 2014-05-31 at 16:36 -0400, Oliver Ruebenacker wrote: > I would have installed Fedora, but they say the requirements are at > least 4GB RAM. 2GB should be possible... From the official Fedora 20 release notes

RE: Fedora Present and Future: a Fedora.next 2014 Update (Part I,?“Why?”)

> I`m not an expert with Fedoras installers in any way. This is simply my "user > experience". Maybe the "user experience" the installer provides should be > different. Your user experience is important, but just because you think it should be one way doesn't mean the community or developers ec

RE: Fedora Present and Future: a Fedora.next 2014 Update (Part I,?“Why?”)

> It doesn`t give you choices. It leaves you in the dark about that it is > somehow > possible to use an non-gui installer and to do a minimal install. It leaves > you > in the dark about what exactly happens when you do the partitioning and > with trying to figure out how get the partitioning

RE: Fedora Present and Future: a Fedora.next 2014 Update (Part I,?“Why?”)

> Then they need to turn around at once! Leaving users in the dark about > what`s going on makes things more difficult for them. Taking away choices > limits the use of the software to the point where it eventually becomes > unusable. > > Good design, clarity, good documentation and letting the

RE: Fedora Present and Future: a Fedora.next 2014 Update (Part I,?“Why?”)

> I don't get it, how is "bouncing around" faster? I bounced around for an > eternity when I installed F20 on my new laptop. Earlier it used to take me > something of the order of an hour to get everything done, this time around it > was so frustrating I gave up after a couple of hours more than o

RE: Fedora Present and Future: a Fedora.next 2014 Update (Part I, “Why?”)

> Every single aspect of it is a real problem. In the dictionary they have a > picture of it next to the word "disaster". The whole random wheel/spoke > thing is an invitation to forget to do something important. And who the hell > would think that "network" would be the spoke where you set the sys

RE: Help needed with xhost

> > It beats me why one would go through all the effort of extraordinary > > measures so they can run as root, rather than just run as a user, and > > use the system in a straight-forward manner. > > > > Because I don't like to spend time to issue sudo or su - command everytime I > need it. > It

RE: Installing Linux on a windows hd

> A friend who is not computer literate at all has a Dell 1520 laptop which when > new, Dell required it have xp installed. I insisted at the time that the hd > have > 2 partitions as I intended to install either Fedora or Ubuntu but that was > years ago and I had forgotten all about it till today

RE: f20 - difference between i386 and x86_64 distros

> -Original Message- > As I have mentioned, my x86_64 install on my Lenovo is a bit of a hack. > Hopefully things will be better for f21, but meanwhile... > > I am continuing to have problems. Most recently, Gnome keeps crashing > even without suspend attempts. > > S, I DO have a dri

RE: "liveusb-creator" versus "livecd-iso-to-disk"?

> -Original Message- > background: i'm teaching a linux admin class next week and i will be > supplied with laptops for the students that i've been asked *not* to > overwrite, so my plan is to create bootable *and writable* USB drives > for everyone. (the course will actually run on RHEL/

RE: akmod isn't reliable

> I think it is reliable, you just need to wait it out. The rebuilding of > akmod is being done for a given kernel while that kernel is running, so > when you update the kernel, the akmod doesn't get built until you boot > into it. And when you boot into it, systemd will at some point try to > acti

RE: akmod isn't reliable

>At this risk of sounding a bit harsh... If you don't know where your software >is coming from, don't use it. If >you don't understand that you had to install >the RPM Fusion repositories to get akmods, you probably shouldn't >be using >it. It's really designed for people who are running modifie

RE: akmod isn't reliable

>Wrong list, this should be discussed on the RPM Fusion mailing list. > >Richard Hmm... how so? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.or

akmod isn't reliable

I guess this is more of a general question, but sometimes after updating the kernel or nvidia drivers an akmod isn't regenerated and my system will begin to boot, fedora logo will show, but eventually it will dump to the systemd log of services being started and just sit there. I have all the re

RE: permissions -

> I spent the last half hour googling with no success. What does the "b" > mean and how is it controlled? > > [root@box10 bobg]# ll /dev/sdb* > brw-rw. 1 root disk 8, 16 Sep 23 14:36 /dev/sdb brw-rw. 1 root > disk 8, 17 Sep 23 14:36 /dev/sdb1 > > Bob The first character is the file type.

RE: configure yum to ignore kernel updates?

> in using the cli just yum update exclude=kernel* or stuck > exclude=kernel* in /etc/yum.conf and use "--disablexcludes" when > required to update kernel This sounds like what I need :) thanks -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: http

configure yum to ignore kernel updates?

Is there a way to configure yum to ignore kernel updates besides manually removing an update before the update? The problem is that there's a very strong chance a kernel update will break drivers (read: nvidia), and I don't want to have to swing to extremes, like not updating at all... I update

RE: fedora 17 yum update

> -Original Message- > From: users-boun...@lists.fedoraproject.org [mailto:users- > boun...@lists.fedoraproject.org] On Behalf Of Jim Duda > Sent: Thursday, September 12, 2013 10:39 AM > To: users@lists.fedoraproject.org > Subject: fedora 17 yum update > > I did a fresh install of fedora 1

RE: Native Nvidia Optimus and Fedora 19

> I have been using an optimus laptop quite some time (Asus U45JC), with > a BIOS which doesn't have any switch related to optimus or the nvidia > graphics. I recompiled my kernel without nouveau and run the integrated > Intel graphics. After heavy trouble with gpu hangs, ILK seems to be > fixed in

RE: Native Nvidia Optimus and Fedora 19

>I'm considering buying a laptop with Nvidia Optimus, and this looks really >bad! Have you managed to fix this issue? Did you get Fedora 19 to install? Do >Ubuntu and Linux Mint work better with Nvidia Optimus graphics? I gave up; I resigned myself to use bumblebee which works moderately well fo

Yum tries to update to three nvidia drivers all at once

I attempted to perform a `sudo yum update`, but yum produced an error and exited because it was trying to update to nvidia drivers 319.32, 304xx, and 173 all at the same time. I excluded the older drivers (304xx and 173) and proceeded with the update, and Nvidia-settings shows that the version ru

RE: Native Nvidia Optimus and Fedora 19

A re-post since I forgot HTML was on. Has anyone tried to get native Optimus running on a Fedora 19 box? When I attempt it, I get a blank black screen. I posted on the Nvidia forums, but no one has replied yet and I'm getting anxious ;-) The general consensus is that the kernel must be 3.9 or h

Native Nvidia Optimus and Fedora 19

Has anyone tried to get native Optimus running on a Fedora 19 box? When I attempt it, I get a blank black screen. I posted on the Nvidia forums, but no one has replied yet and I'm getting anxious ;-) The general consensus is that the kernel must be 3.9 or higher, and I am running 3.9.9-302. The

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

> On 07/14/13 09:39, Powell, Michael wrote: > >> On 07/14/13 07:30, Powell, Michael wrote: > >>> Greshko, Ed wrote:> > >>>> /var/log/yum.log has date/time updates were applied > >>> Thanks, Ed. Unfortunately I don't need a timestamp of whe

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

> On 07/14/13 07:30, Powell, Michael wrote: > > Greshko, Ed wrote:> > >> /var/log/yum.log has date/time updates were applied > > Thanks, Ed. Unfortunately I don't need a timestamp of when the > updates were applied to the machine, but instead, I need a timestamp

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

Greshko, Ed wrote:> > /var/log/yum.log has date/time updates were applied Thanks, Ed. Unfortunately I don't need a timestamp of when the updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191

Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

The machine details: - Dell XPS 17 (L702X) BIOS A19 - Intel Core i7-2720QM (2.2GHZ) - Intel Sandybridge - Nvidia GeForce GT 555M >From a complete fresh install of F19, I’m seeing 214 updates. The updates >break down into 8 security, 80 bugfix, 22 enhanceme