This may be a dumb question, but why can't Redhat distribute NVIDIA binary
In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it
"2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section
2.1.1, SOFTWARE designed exclusively for use on the Linux operating system
copied and redistributed, provided that the binary files thereof are not
modified in any
way (except for unzipping of compressed files)."
So, what's keeping RedHat from putting the drivers in the distribution? If
it's a GPL
thing, would it be easy to just download it during installation or at
least give the option to the user?
Ok, I have had Yarrow working well for a while now, but yesterday I
started experiencing some odd issues with my mouse. All of a sudden it
stops working correctly. The only thing that seems to fix is to kill X
and run mouse-test, then restart.
Also, I have FC 1 running on a desktop which is hooked up to a KVM
switch. Whenever I go to another PC, and return, the same thing
happens, the mouse goes crazy.
On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote:
> > Hi, folks! A while ago, Xen virtualization functionality was added to
> > the criteria and the validation test case set, on the understanding
> > that Oracle would provide testing for it (and help fix bugs as they
> > arose).
> > For the last couple of releases we really have not had any such testing
> We had been doing the testing, it just that we (or rather me and
> Dariof) seem to get a wind of this at the last minute. Not sure exactly
> how to fix that thought.
Well, I mean, every few *days* a compose gets nominated for validation
testing, and a mail is sent to test-announce. Just check your test-
announce archives for mails with "nominated for testing" in their
subject lines, and you'll see dozens. Is this not sufficient
> > from Oracle. On that basis, I'm proposing we remove this Final
> > criterion:
> s/Oracle/Xen Project/ I believe?
Perhaps, it's just that it always seemed to be you doing the testing,
so they got a bit conflated :)
> > "The release must boot successfully as Xen DomU with releases providing
> > a functional, supported Xen Dom0 and widely used cloud providers
> > utilizing Xen."
> > and change the 'milestone' for the test case -
> > https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt -
> > from Final to Optional.
> > Thoughts? Comments? Thanks!
> I would prefer for it to remain as it is.
This is only practical if it's going to be tested, and tested regularly
- not *only* on the final release candidate, right before we sign off
on the release. It needs to be tested regularly throughout the release
cycle, on the composes that are "nominated for testing".
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
my name is Julian Schlüntz, I have been using Fedora for a long time (I
think since Fedora Core 3) and it is time I started contributing. I like
testing stuff and figuring out problems, so I figured QA would be the
right place for me.
I am from Germany, 31 years old and have some development experience.
My IRC nickname is 'gapophustu'.
My name is Ryan Himmelwright and often go by himmAllRight on the
internet and IRC. Outside the web, I've spent the last few years in the
greater Boston area, but have recently moved to Durham NC (both USA).
I have been lurking around the various Fedora groups over the last few
years, but have never fully taken the plunge into a project. I am
interested in becoming more involved with the QA group, in particular to
help develop some of the testing tools (in addition to some package
I am a Linux and open source enthusiast and have been using Linux as my
main driver for over 8 years now. I work as a software developer that
unfortunately builds web applications to run on Windows (I don't get it
either). I primarily use Common Lisp at my day job to develop large,
automated, build systems, but am also familiar with Python, R, Go, and a
bit of C. While I spend my work day in Windows, I use my early mornings
and weekends learning everything I can about Linux. I am hoping to
finally put some of those skills to use with the Fedora community .
I'm a big fan of Fedora and want to contribute somehow to the Fedora QA.
I currently study electrical engineering at the Brno University of Technogy
in Brno, Czech republic and I'm also interested in computers generaly. I
mean just to imagine the "flying" electrons inside the silicon of the ICs
or just to bring my thoughts to the "other side" and think about anything
relating to UNIX-like operating systems and it's applications. I also enjoy
learning new things about how the things work on the Linux, and for this
reason I thought it would be interesting to see and be part of the team
which manages the testing in order to find out what is not working
Also currently I am an intern at the Red Hat's Brno office. I do have
experience with using and administrating Fedora and also RHEL, RHEV.... In
the field of programming I do have experience with C language, Python,
markup languages and not so markup language as YAML, also I do shell
scripting in BASH and sometimes I trying to be POSIX compliant with it. :-)
I am available also on:
e-mail: xtothp00(at)stud.feec.vutbr.cz -- alternative
I am looking forward to work with you!
My name is Diego Aaron, I'm 26 years old and live at Lima Perú. I have
started using Linux for a couple of months now, since I am preparing for
the LPIC I certification.
I am also learning about Java programming and application testing in a
personal way. I have more experience in configuring Cisco network equipment.
I'm very glad to join at Fedora QA Team. I have working with Red Hat Linux
in my work since six months ago. So, let's time to
contribute with the project.
So, thanks a lot for some people who accepted me at Fedora Project.
At my signature I'm sending my contacts fell free if anyone want to contact
irc nickname: diegoaaron909
Is there a specific download site for the fix for this problem? I wrote a bug report yesterday to the RedHat bugzilla "Bug 1596827 – dnf non-functional after upgrade".
Bug 1596827 – dnf non-functional after upgrade