On 07/13/15 21:54, jd1008 wrote:
> On 07/13/2015 08:43 PM, g wrote:
<<<>>>
>> ok. you have now thrown in *pipe* and process *un-tar*.
>>
>> are you using tar to pass files to target and have them end up as separate
>> files, or as a single archive file?
>>
>> ria, all i see in your original post
On 07/13/2015 08:43 PM, g wrote:
On 07/13/15 21:17, jd1008 wrote:
On 07/13/2015 06:52 PM, g wrote:
more for thought, is tar building finale file in memory, /tmp, or on
the usb3 drive?
:)
Well, since I was using a pipe, I assume swap backed memory is used.
However, the un-tar process is runn
On 07/13/15 21:17, jd1008 wrote:
> On 07/13/2015 06:52 PM, g wrote:
>> more for thought, is tar building finale file in memory, /tmp, or on
>> the usb3 drive?
> :)
> Well, since I was using a pipe, I assume swap backed memory is used.
> However, the un-tar process is running in parallel, so the
On 07/13/2015 06:52 PM, g wrote:
more for thought, is tar building finale file in memory, /tmp, or on
the usb3 drive?
:)
Well, since I was using a pipe, I assume swap backed memory is used.
However, the un-tar process is running in parallel, so the RAM
pipe is shared between the producer "tar
On 07/13/15 19:38, jd1008 wrote:
> On 07/13/2015 05:15 PM, Patrick O'Callaghan wrote:
<<>>
>> IIRC USB drives are not DMA driven, i.e. each filesystem block written
>> to the drive has to be pushed over the serial bus and handled by the
>> CPU. Also, check if the drive is mounted with the 'flush
On 07/13/2015 05:15 PM, Patrick O'Callaghan wrote:
On Mon, 2015-07-13 at 15:42 -0600, jd1008 wrote:
On 07/13/2015 03:13 PM, Patrick O'Callaghan wrote:
On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
I started a tar command from
one external eSATA drive (ext4), connected to eSATA port,
out t
On Mon, Jul 13, 2015 at 3:24 PM, John Wright wrote:
> The precise appearance of the error message is as follows:
>
> A small dark rectangular box appears at the top center of the blue
> wallpaper page. The box contains a large frowny-face and the words:
That's an abrt message coming through the
On Mon, 2015-07-13 at 15:42 -0600, jd1008 wrote:
>
> On 07/13/2015 03:13 PM, Patrick O'Callaghan wrote:
> > On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
> > > I started a tar command from
> > > one external eSATA drive (ext4), connected to eSATA port,
> > > out to a USB flash drive (with vfat)
On Mon, 2015-07-13 at 15:37 -0600, jd1008 wrote:
>
> On 07/13/2015 03:13 PM, Patrick O'Callaghan wrote:
> > On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
> > > I started a tar command from
> > > one external eSATA drive (ext4), connected to eSATA port,
> > > out to a USB flash drive (with vfat)
Hi All;
I've installed Fedora 21 KDE spin on a 2015 Macbook air. I installed
the rpmfusion repos and enabled kmod-wl and kernel-devel packages to
enable wireless support. At this point most everything works, the
screen brightness keys, keyboard backlight keys, keyboard volume keys,
etc all work.
On 07/13/2015 03:13 PM, Patrick O'Callaghan wrote:
On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
I started a tar command from
one external eSATA drive (ext4), connected to eSATA port,
out to a USB flash drive (with vfat). The USB stick is touted
to support 50MB/s write, 160MB/s read.
Have
On 07/13/2015 03:13 PM, Patrick O'Callaghan wrote:
On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
I started a tar command from
one external eSATA drive (ext4), connected to eSATA port,
out to a USB flash drive (with vfat). The USB stick is touted
to support 50MB/s write, 160MB/s read.
Have
On Mon Jul 13 18:52:16 UTC 2015 Chris Murphy typed:
So there's the kernel bug, 1225671, that ends up stopping the arrays,
but then there's a misleading message saying there's a problem that's
been corrected, yet clearly not corrected.
The exact wording of the message is:
'Unexpected system
On Mon, 2015-07-13 at 13:50 -0600, jd1008 wrote:
> I started a tar command from
> one external eSATA drive (ext4), connected to eSATA port,
> out to a USB flash drive (with vfat). The USB stick is touted
> to support 50MB/s write, 160MB/s read.
Have you actually measured its real write speed for l
I started a tar command from
one external eSATA drive (ext4), connected to eSATA port,
out to a USB flash drive (with vfat). The USB stick is touted
to support 50MB/s write, 160MB/s read.
The USB port itself is USB 2.0 (480MBits/s).
The desktop (Mate) response goes down the tubes.
I ran top and f
Date: Sun, 12 Jul 2015 06:43:50 -0500
On Sun, 2015-07-12 at 19:35 +0800, Ed Greshko wrote:
> On 07/12/15 19:23, Gregory P. Ennis wrote:
> > Thank you for your reply. I had to remove f22 dcmtk before this
> > would
> > work, but at least I have my DICOM viewer back. Thanks again!
>
> You're
You are not running Enterprise Linux 7. This repo is not for Fedora.
Using it will cause conflicts and unpredictable problems.
--Pete
Thanks Pete finally figured that out too.
Greg
--
users mailing list
users@lists.fedoraproject.or
On Mon, Jul 13, 2015 at 11:33 AM, John Wright wrote:
>
> On Mon Jul 13 02:19:31 UTC 2015 Chris Murphy typed:
>
>> So there's the kernel bug, 1225671, that ends up stopping the arrays,
>> but then there's a misleading message saying there's a problem that's
>> been corrected, yet clearly not correc
On 2015-07-10 12:42, Joe Zeff wrote:
> On 07/10/2015 07:33 AM, Matthew Woehlke wrote:
>> probably have a more benign reason (maybe to stop people that don't know
>> what they're doing from accidentally bricking their machines).
>
> That's no excuse. Once you've paid for the machine and received i
On 13.07.2015, Aaron Gray wrote:
> Cheers Mike. I did try mounting previously but did not work will try
> again tomorrow.
If you want proper help, please post the output of your mount attempt, e.g.
mkdir /test
mount /dev/sdX /test
Where "X" is the proper partition/device number.
--
users mai
On Mon Jul 13 02:19:31 UTC 2015 Chris Murphy typed:
So there's the kernel bug, 1225671, that ends up stopping the arrays,
but then there's a misleading message saying there's a problem that's
been corrected, yet clearly not corrected.
The exact wording of the message is:
'Unexpected system e
On 12.07.2015, tangen...@hushmail.com wrote:
> You can take the src rpm from Fedora 21 and use the command:
> rpmbuild --rebuild src rpm. This generates a version of aeskulap to
> Fedora 22. It works in several times.
It doesn't.
Aeskulap may compile, but won't work because the Dicom Toolki
On Jul 11, 2015 12:38 PM, "Gregory P. Ennis" wrote:
>
> > > [root@HmGe f21]# rpm -Uhvf aeskulap-0.2.2-0.19beta1.fc21.x86_64.rpm
> > > error: Failed dependencies:
`rpm` knows about dependencies but does not pull other packages to resolve
them. That's dnf's job. Use dnf, do not use rpm directly.
On Mon, 2015-07-13 at 18:38 +0800, Ed Greshko wrote:
> On 07/13/15 17:27, Jean Jacques wrote:
> > will not generated an module for kernel but works well under 4.0.6
> >
> I see you got your answer on the rpmfusion list.
>
> When you have a problem with akmods you can check
> /var/cache/akmods/ak
On 07/13/15 17:27, Jean Jacques wrote:
> will not generated an module for kernel but works well under 4.0.6
>
I see you got your answer on the rpmfusion list.
When you have a problem with akmods you can check /var/cache/akmods/akmods.log
for information about what when wrong.
--
Sorta what I w
Hi Chris,
Thanks for this. Just had a fantastic honeymoon, but now back in the real
world and onwards with trying to fix this.
On Friday 03 July 2015 18:35:47 Chris Murphy wrote:
> There's an awful lot going on here. And to vent, I'm going to start
> out by saying dual boot sucks. It's not you,
On 07/12/2015 11:31 PM, Chris Murphy wrote:
> On Sun, Jul 12, 2015 at 8:43 AM, Paul Cartwright
> wrote:
>
>> problem is, only a blinking cursor, no grub menu.. that's my problem.
>> I know how to edit grub menus using e.. since I have multiple ( mostly
>> linux) OSes, grub gets updated every now
On 07/12/2015 10:47 PM, Gordon Messmer wrote:
> On 07/12/2015 03:43 AM, Paul Cartwright wrote:
>> rebooted and... a blinking cursor on a black background..
>> this seems to happen everytime now when I get a new kernel in F22
>
> Next time you update, save a copy of /boot/efi/EFI/fedora/grub.cfg,
>
not yet.
2015-07-13 18:01 GMT+08:00 Frank Murphy :
> On Mon, 13 Jul 2015 17:27:46 +0800
> Jean Jacques wrote:
>
> > will not generated an module for kernel but works well under 4.0.6
>
> Have you check the rpmfusion mailing listslist for any other users
> reporting problems\solutions.
>
>
> ___
On Mon, 13 Jul 2015 17:27:46 +0800
Jean Jacques wrote:
> will not generated an module for kernel but works well under 4.0.6
Have you check the rpmfusion mailing listslist for any other users
reporting problems\solutions.
___
Regards
Frank Murphy
--
users mailing list
users@lists.fedoraproject
will not generated an module for kernel but works well under 4.0.6
--
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.org/code-of-conduct
Guidelines:
31 matches
Mail list logo
