On Sun, 2016-10-02 at 10:23 -0700, stan wrote:
> On Sun, 02 Oct 2016 09:34:52 -0700
> Howard Howell wrote:
>
> >
> > Hi, everyone,
> > I use Pycam with my milling machine. The process I follow is:
> > design with OpenSCAD, export as DXF or STL format.
> >
On Sun, 2016-10-02 at 10:23 -0700, stan wrote:
> On Sun, 02 Oct 2016 09:34:52 -0700
> Howard Howell wrote:
>
> >
> > Hi, everyone,
> > I use Pycam with my milling machine. The process I follow is:
> > design with OpenSCAD, export as DXF or STL format.
> >
On 11/10/16 22:23, Ahmad Samir wrote:
On 10 October 2016 at 22:47, Stephen Morris wrote:
On 11/10/16 03:37, Ahmad Samir wrote:
On 9 October 2016 at 23:03, Stephen Morris
wrote:
Hi,
I'm using Thunderbird 52.0a1 and I have an issue
On 10/12/2016 03:57 PM, c...@zip.com.au wrote:
Except it the wildest scenarios, XFS fsks at mount, almost immediately.
Is that different from fsck.ext4 replaying the journal?
Go and cat (yes, cat) the fsck.xfs command.
OK. I'm not sure what you think I'll learn by doing so. fsck.xfs
On Thu, 13 Oct 2016 12:08:06 -0700
Howard Howell wrote:
> > > radeon: Failed to deallocate virtual address for buffer:
> > > radeon:size : 4096 bytes
> > > radeon:va: 0x884000
> > > Segmentation fault (core dumped)
> Ok, I tried the previous kernel,
On Thu, Oct 13, 2016 at 10:08 PM, Michael B Allen wrote:
> I'm trying to boot the latest Fedora Live iso on a brand new Dell and
> I'm getting:
>
> Selected boot device failed
>
> What is the trick to getting this to boot?
>
> I just dd'd the iso on the USB drive.
Nevermind.
I'm trying to boot the latest Fedora Live iso on a brand new Dell and
I'm getting:
Selected boot device failed
What is the trick to getting this to boot?
I just dd'd the iso on the USB drive. Do I need to make it bootable or
some such?
I updated the BIOS to the latest. I verfied everything
-Original Message-
From: c...@zip.com.au [mailto:c...@zip.com.au]
Sent: donderdag 13 oktober 2016 0:58
To: Community support for Fedora users
Subject: Re: Filesystem for backup system
On 12Oct2016 09:40, Mike Wright wrote:
>On 10/12/2016 08:53 AM, Heinz Diehl
On Thursday 13 October 2016 09:48:31 Gary Stainburn wrote:
> On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> > That looks similar to this upstream bug:
> > https://bugs.kde.org/show_bug.cgi?id=366793
>
> Interestingly, I now have two problems.
>
> This is indeed the problem on the PC I
On Saturday 08 October 2016 11:02:48 Ahmad Samir wrote:
> That looks similar to this upstream bug:
> https://bugs.kde.org/show_bug.cgi?id=366793
Interestingly, I now have two problems.
This is indeed the problem on the PC I initially experienced the problem on.
As suggested in the bug report,
On Thu, 2016-10-13 at 10:36 +0100, Gary Stainburn wrote:
> On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> > Unfortunately, I cannot convert this into a usable solution in the KDE menu
> > Editor
>
> I've been totally unable to get this working properly within KDE Menu Editor.
This
On Thursday 13 October 2016 10:05:56 Gary Stainburn wrote:
> Unfortunately, I cannot convert this into a usable solution in the KDE menu
> Editor
I've been totally unable to get this working properly within KDE Menu Editor.
Instead I've had to modify my root BASH script to cope. Not pretty, but
user authentication errors are usually recorded on the client end.
On Thu, Oct 13, 2016 at 4:47 PM, Jason Nielsen wrote:
> Im looking for ways to pull a number of audit events from 389. Such as:
>
> -User authentication success and failures.
> -Group additions, removals and
Im looking for ways to pull a number of audit events from 389. Such as:
-User authentication success and failures.
-Group additions, removals and changes.
-User additions, removals and possibly changes.
Details in each of these would include items such as:
username
groupname
attribute changed
14 matches
Mail list logo