On Mon, 2013-06-24 at 13:45 +0100, Ben Hutchings wrote:
> On Mon, 2013-06-24 at 15:44 +0700, Yura Pakhuchiy wrote:
> > Hello Ben,
> >
> > Looks like setting per route MTU (as described in [1]) is broken in
> > Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 an
Hello Ben,
Looks like setting per route MTU (as described in [1]) is broken in
Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
looks like problem is fixed there. I filled Ubuntu bug report [2] with
more details and sample script which illustrates problem. But since this
Hello Ben,
Looks like setting per route MTU (as described in [1]) is broken in
Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
looks like problem is fixed there. I filled Ubuntu bug report [2] with
more details and sample script which illustrates problem. But since this
On Mon, 2013-06-24 at 13:45 +0100, Ben Hutchings wrote:
On Mon, 2013-06-24 at 15:44 +0700, Yura Pakhuchiy wrote:
Hello Ben,
Looks like setting per route MTU (as described in [1]) is broken in
Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
looks like problem
2005/7/14, Christoph Hellwig <[EMAIL PROTECTED]>:
> On Thu, Jul 14, 2005 at 04:50:01PM +0300, Yura Pakhuchiy wrote:
> > 2005/7/14, Nathan Scott <[EMAIL PROTECTED]>:
> > > On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
> > > > I found
2005/7/14, Nathan Scott <[EMAIL PROTECTED]>:
> On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
> > I found patch by Greg Ungreger to fix this problem, but why it's still
> > not in mainline? Or it's a gcc problem and should be fixed by gcc folks?
>
2005/7/14, Nathan Scott [EMAIL PROTECTED]:
On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
I found patch by Greg Ungreger to fix this problem, but why it's still
not in mainline? Or it's a gcc problem and should be fixed by gcc folks?
Yes, IIRC the patch was incorrect
2005/7/14, Christoph Hellwig [EMAIL PROTECTED]:
On Thu, Jul 14, 2005 at 04:50:01PM +0300, Yura Pakhuchiy wrote:
2005/7/14, Nathan Scott [EMAIL PROTECTED]:
On Wed, Jul 13, 2005 at 06:22:28PM +0300, Yura Pakhuchiy wrote:
I found patch by Greg Ungreger to fix this problem, but why it's
2005/7/8, Nathan Scott <[EMAIL PROTECTED]>:
> On Thu, Jul 07, 2005 at 08:15:52PM +0300, Yura Pakhuchiy wrote:
> > Hi,
> >
> > I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
> > copyied files on it and moved this hard drive to i686 machine. When
2005/7/8, Nathan Scott [EMAIL PROTECTED]:
On Thu, Jul 07, 2005 at 08:15:52PM +0300, Yura Pakhuchiy wrote:
Hi,
I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
copyied files on it and moved this hard drive to i686 machine. When I
mounted it on i686, I found no files
Hi,
I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
copyied files on it and moved this hard drive to i686 machine. When I
mounted it on i686, I found no files on it. I runned xfs_check, here is
output:
pc299:/home/yura# xfs_check /dev/sda5
dir 128 size is 31, should be 13
dir
Hi,
I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
copyied files on it and moved this hard drive to i686 machine. When I
mounted it on i686, I found no files on it. I runned xfs_check, here is
output:
pc299:/home/yura# xfs_check /dev/sda5
dir 128 size is 31, should be 13
dir
On Thu, 2005-04-07 at 14:40 +0200, Patrice Martinez wrote:
> When using a machine with a 2612-rc 1kernel, I encounter problems
> reading /dev/random:
> it simply nevers returns anything, and the process is blocked in the
> read...
> The easiest way to see it is to type:
> od < /dev/random
>
On Thu, 2005-04-07 at 14:40 +0200, Patrice Martinez wrote:
> When using a machine with a 2612-rc 1kernel, I encounter problems
> reading /dev/random:
> it simply nevers returns anything, and the process is blocked in the
> read...
> The easiest way to see it is to type:
> od < /dev/random
>
On Thu, 2005-04-07 at 14:40 +0200, Patrice Martinez wrote:
When using a machine with a 2612-rc 1kernel, I encounter problems
reading /dev/random:
it simply nevers returns anything, and the process is blocked in the
read...
The easiest way to see it is to type:
od /dev/random
Any
On Thu, 2005-04-07 at 14:40 +0200, Patrice Martinez wrote:
When using a machine with a 2612-rc 1kernel, I encounter problems
reading /dev/random:
it simply nevers returns anything, and the process is blocked in the
read...
The easiest way to see it is to type:
od /dev/random
Any
16 matches
Mail list logo
