On Fri, 2016-01-15 at 08:08 -0800, Doug H. wrote:
> After about a day of not having crontabs running I realized that
> SELinux was stopping both user and root crontab jobs. I messed with
> it
> and then discovered:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1298192
> (Recent dnf updates caus
So on a different system upgraded from f22 and not f21 the directions work so
there must be some cruft hiding on the one upgraded from f21. I'll have to dig
into the differences.
Nate Pearlstein - npe...@sgi.com - Product Support Engineer
-Original Message-
From: Nate Pearlstein [npe.
The message that I sent to this list, a few minutes ago (with subject
line "WARNING you cannot build info or html versions of the R manuals")
was sent here by mistake. I *intended* it to go to r-sig-fedora, and
messed up.
I have re-sent this message to the address that I originally intended.
On 01/16/2016 01:07 PM, Andrew R Paterson wrote:
How about when the root filesystem was created?
This works fine if and only if you haven't upgraded from a previous version.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapr
It's no big deal, but when I build R from source (as I must) I always
get the warning given in the subject line of this post.
I have searched the web a bit and have found a number of references to
this warning. Universally the proffered solution is "install texinfo".
So I did (just now)
On Sat, Jan 16, 2016 at 09:07:52PM +, Andrew R Paterson wrote:
> On Saturday 16 Jan 2016 02:19:59 Tim wrote:
> > --- snip ---
> >
> > Obviously most of that is pre-release, but some of it is post.
> How about when the root filesystem was created?
> ls -alct /|tail -1|awk '{print $6, $7, $8}'
Hi Cole,
Thanks for the response. I’m still seeing problems.
I start virt-manager and it prompts me for the root password.
My user is now a member of the libvirt group
[npearl@caprica ~]$ id
uid=1(npearl) gid=1000(npearl) groups=1000(npearl),10(wheel),982(libvirt)
context=unconfined_u:unco
On Saturday 16 Jan 2016 02:19:59 Tim wrote:
> On Fri, 2016-01-15 at 10:34 +, Christopher Ross wrote:
> > # rpm -qi fedora-release
>
> Occasionally, even *that* package gets updated, so it's not an indicator
> of install time. Unless someone else knows of something intended to show
> you the i
On 01/16/2016 12:09 PM, Temlakos wrote:
As I said before: when I boot into what I call the "last known good
kernel," meaning the kernel one version earlier than the current one, I
don't have this problem. As I specifically say in my comments to this bug.
Great! I don't keep posts like this aft
On 01/16/2016 03:00 PM, Joe Zeff wrote:
On 01/16/2016 11:46 AM, Temlakos wrote:
Added as a comment after I filed the report. You can see it there.
Good! I don't have any x64 systems (Although, if I ever need to do a
clean install on this box, I'll migrate from PAE to x64.) so it
doesn't co
On 01/16/2016 11:46 AM, Temlakos wrote:
Added as a comment after I filed the report. You can see it there.
Good! I don't have any x64 systems (Although, if I ever need to do a
clean install on this box, I'll migrate from PAE to x64.) so it doesn't
concern me directly. Also, what happens if
On 01/16/2016 02:33 PM, Joe Zeff wrote:
On 01/16/2016 11:16 AM, Temlakos wrote:
Filed with Bugzilla as Bug No. 1299130. Assigned to the Kernel
Maintainers' Group. Add this to it: I fell back on the next earlier
version of the kernel. And the problem vanished. So let no one say I'm
just typing on
On 01/16/2016 11:16 AM, Temlakos wrote:
Filed with Bugzilla as Bug No. 1299130. Assigned to the Kernel
Maintainers' Group. Add this to it: I fell back on the next earlier
version of the kernel. And the problem vanished. So let no one say I'm
just typing on a keyboard with sticky keys. Temlakos
Did you look at docker for your project?
Day after day it's becoming more and more in use, it allow simpler (in my
opinion) managing if you have multiples instances, even if they're not in
the same server
On Sat, 16 Jan 2016 at 19:36, Tim wrote:
> Allegedly, on or about 16 January 2016, bruce sen
With the latest Fedora kernel build (4.2.8-200.fc22.x86_64), I see this
behavior:
A string of spurious characters, beginning with a digit 6 and continuing with
an unending stream of digit-8 characters, suddenly appears and fills whatever
text workspace, dialog box, etc. currently has the focus
Allegedly, on or about 16 January 2016, Bob Marcan sent:
> What about /root/initial-setup-ks.cfg or /root/anaconda-ks.cfg ?
> I belive it is created at the installation time.
I've already suggest them, and others have suggested at least one of
them, too. However, there is one potential problem
Allegedly, on or about 16 January 2016, bruce sent:
> The goal is to get a basic sys admin understanding of DNS, and how to
> apply it to a few instances/VMs.. Over time, the number of machines
> will increase. Simply doing the etc/host isn't reasonable.
I that case, I'd say look into learning BI
Hi,
I just purchased a Lexar Jumpdrive S25 2x32GB USB sticks and just
noticed it has some kind of built-in encryption. Any chance it's
supported with Linux? What is it exactly?
Before I open the package, I thought I'd post a message to see what
people's experience has been with them?
I didn't no
On 01/15/2016 07:44 PM, Nate Pearlstein wrote:
> I’ve been trying to get policykit to automatically authorize virt-manager.
>
> This was working fine with fedora 21, but with fedora 23 it doesn’t seem to
> work. For both I’ve been using the mate desktop.
>
> With f21 I had the following in
> /
Hi Tim. Thanks for the reply.
The goal is to get a basic sys admin understanding of DNS, and how to
apply it to a few instances/VMs.. Over time, the number of machines
will increase. Simply doing the etc/host isn't reasonable.
On Sat, Jan 16, 2016 at 5:51 AM, Tim wrote:
> Allegedly, on or abou
I have an old laptop that I use as a home server, so it sits in the
corner closed most of the time. Something changed with the last set of
updates I applied so now if I reboot, it suspends in the middle of the
boot process, and will not continue until I open the laptop, at which
point it will cont
On Sat, 16 Jan 2016 21:32:28 +1030
Tim wrote:
> Allegedly, on or about 15 January 2016, Andrew R Paterson sent:
> > How about the creation date of /etc/redhat-release
> > Works for me!
>
> Doesn't work for me, so you can't guarantee it'll work for others,
> either.
>
> That file comes from t
Tim:
>> This shows just one advantage of doing fresh installs, instead of
>> updates. Those of use who do fresh installs, won't have old keys from
>> prior releases still on our systems.
Gordon Messmer:
> "Your keys" means your private authentication keys. The ones in
> ~/.ssh. If you keep or
Allegedly, on or about 15 January 2016, Andrew R Paterson sent:
> How about the creation date of /etc/redhat-release
> Works for me!
Doesn't work for me, so you can't guarantee it'll work for others,
either.
That file comes from the fedora-release RPM package, which has already
been shown to get
Allegedly, on or about 15 January 2016, bruce sent:
> I want to setup a few (4-5) different test servers. I want the servers
> to be able to communicate with each other via name. I'd also like to
> be able to access one of the servers by name, to allow me to ssh into
> the box via name, as opposed
25 matches
Mail list logo
