On 26.06.2014 13:57, Luká? Czerner wrote:
> > So if the authors want to sell this new interface (in whatever form) to
> > the kernel community, they should start with providing a solid use-case,
> > with some more details, explore alternatives and show how the
> > alternatives do not work for
On 26.06.2014 13:57, Luká? Czerner wrote:
So if the authors want to sell this new interface (in whatever form) to
the kernel community, they should start with providing a solid use-case,
with some more details, explore alternatives and show how the
alternatives do not work for them.
On 11.11.2013 14:05, Shahbaz Youssefi wrote:
> On Sun, Nov 10, 2013 at 8:06 PM, Matthias Schniedermeyer wrote:
> > I don't see a way around "borders" (Papers please), otherwise you can't
> > reject things you don't want, you have to check if that something that
>
On 11.11.2013 14:05, Shahbaz Youssefi wrote:
On Sun, Nov 10, 2013 at 8:06 PM, Matthias Schniedermeyer m...@citd.de wrote:
I don't see a way around borders (Papers please), otherwise you can't
reject things you don't want, you have to check if that something that
is to be done is allowed
On 06.10.2013 23:55, Eric W. Biederman wrote:
> "Serge E. Hallyn" writes:
>
> So if we can feel safe just depending on the parent directory
> permissions (which are not hidden by a mount) protecting our mount
> points, I feel much better about this patchset.
As far as i can tell, the
On 06.10.2013 23:55, Eric W. Biederman wrote:
Serge E. Hallyn se...@hallyn.com writes:
So if we can feel safe just depending on the parent directory
permissions (which are not hidden by a mount) protecting our mount
points, I feel much better about this patchset.
As far as i can tell, the
On 28.04.2013 17:56, Linus Torvalds wrote:
I'm not sure if it is supported, but building with a O= -directory that
was previously used to build a 3.8.9-kernel that was "clean"ed (but not
"mrproper"ed) before building 3.9 results in a build-failure:
make[2]: *** No rule to make target
On 28.04.2013 17:56, Linus Torvalds wrote:
I'm not sure if it is supported, but building with a O= -directory that
was previously used to build a 3.8.9-kernel that was cleaned (but not
mrpropered) before building 3.9 results in a build-failure:
make[2]: *** No rule to make target
On 13.02.2013 11:33, Sarah Sharp wrote:
> On Wed, Feb 13, 2013 at 06:16:56PM +0100, Matthias Schniedermeyer wrote:
> > On 13.02.2013 09:28, Holger Hoffstätte wrote:
> > > On 12.02.2013 21:42, Sarah Sharp wrote:
> > > > [..]
> > > > There was a fur
On 13.02.2013 09:28, Holger Hoffstätte wrote:
> On 12.02.2013 21:42, Sarah Sharp wrote:
> > [..]
> > I think I see the issue. Your host controller reports the Inactive
> > state after a USB disconnect. My host controllers go to the RxDetect
> > state on a disconnect.
> >
> > The patches that
On 13.02.2013 09:28, Holger Hoffstätte wrote:
On 12.02.2013 21:42, Sarah Sharp wrote:
[..]
I think I see the issue. Your host controller reports the Inactive
state after a USB disconnect. My host controllers go to the RxDetect
state on a disconnect.
The patches that went into 3.8
On 13.02.2013 11:33, Sarah Sharp wrote:
On Wed, Feb 13, 2013 at 06:16:56PM +0100, Matthias Schniedermeyer wrote:
On 13.02.2013 09:28, Holger Hoffstätte wrote:
On 12.02.2013 21:42, Sarah Sharp wrote:
[..]
There was a further set of patches queued for 3.9 to deal with connected
On 03.10.2012 13:05, Kees Cook wrote:
> Hi Nick,
>
> 3.6 introduced link restrictions:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=800179c9b8a1e796e441674776d11cd4c05d61d7
>
> It sounds like you've got symlinks in a world-writable directory, and
> you're
On 03.10.2012 13:05, Kees Cook wrote:
Hi Nick,
3.6 introduced link restrictions:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=800179c9b8a1e796e441674776d11cd4c05d61d7
It sounds like you've got symlinks in a world-writable directory, and
you're following
On 12.01.2008 18:10, TimC wrote:
> Bodo Eggert <[EMAIL PROTECTED]> said on Sat, 12 Jan 2008 02:41:17 +0100 (CET):
> > On Fri, 11 Jan 2008, Lennart Sorensen wrote:
> > > On Fri, Jan 11, 2008 at 05:22:45PM +0100, Bodo Eggert wrote:
> >
> > > > What can happen if someone does tune2fs -Lroot
On 12.01.2008 18:10, TimC wrote:
Bodo Eggert [EMAIL PROTECTED] said on Sat, 12 Jan 2008 02:41:17 +0100 (CET):
On Fri, 11 Jan 2008, Lennart Sorensen wrote:
On Fri, Jan 11, 2008 at 05:22:45PM +0100, Bodo Eggert wrote:
What can happen if someone does tune2fs -Lroot /dev/usbstick
and
On 10.01.2008 12:30, Helge Hafting wrote:
> Matthias Schniedermeyer wrote:
>>>> Don't use udev then. Good old static dev works fine if you have a fixed
>>>> set of devices.
>>>>
>>> It doesn't, with the unpredictable SCSI mapping insanity.
On 10.01.2008 12:30, Helge Hafting wrote:
Matthias Schniedermeyer wrote:
Don't use udev then. Good old static dev works fine if you have a fixed
set of devices.
It doesn't, with the unpredictable SCSI mapping insanity.
That what LABEL und UUID-Support in mount is for.
You
On 09.01.2008 11:21, Matthias Schniedermeyer wrote:
> On 09.01.2008 09:56, Tuomo Valkonen wrote:
> > On 2008-01-09 00:06 +0100, Matthias Schniedermeyer wrote:
> > > That what LABEL und UUID-Support in mount is for.
> >
> > That's udev shit. I don't want it
On 09.01.2008 09:56, Tuomo Valkonen wrote:
> On 2008-01-09 00:06 +0100, Matthias Schniedermeyer wrote:
> > That what LABEL und UUID-Support in mount is for.
>
> That's udev shit. I don't want it.
No.
Bis denn
--
Real Programmers consider "what you see is what you get
On 09.01.2008 09:56, Tuomo Valkonen wrote:
On 2008-01-09 00:06 +0100, Matthias Schniedermeyer wrote:
That what LABEL und UUID-Support in mount is for.
That's udev shit. I don't want it.
No.
Bis denn
--
Real Programmers consider what you see is what you get to be just as
bad a concept
On 09.01.2008 11:21, Matthias Schniedermeyer wrote:
On 09.01.2008 09:56, Tuomo Valkonen wrote:
On 2008-01-09 00:06 +0100, Matthias Schniedermeyer wrote:
That what LABEL und UUID-Support in mount is for.
That's udev shit. I don't want it.
No.
To be more verbose.
The 'LABEL
> > Don't use udev then. Good old static dev works fine if you have a fixed
> > set of devices.
>
> It doesn't, with the unpredictable SCSI mapping insanity.
That what LABEL und UUID-Support in mount is for.
You label the filesystems (e2label for ext2 and ext3) and use that label to
mount them
Don't use udev then. Good old static dev works fine if you have a fixed
set of devices.
It doesn't, with the unpredictable SCSI mapping insanity.
That what LABEL und UUID-Support in mount is for.
You label the filesystems (e2label for ext2 and ext3) and use that label to
mount them
-
On 05.01.2008 01:31, Andrew Morton wrote:
> On Wed, 2 Jan 2008 20:35:03 +0100 Matthias Schniedermeyer <[EMAIL PROTECTED]>
> wrote:
>
> > Hi
> >
> >
> > Currently i'm deleting about 500.000 files on a XFS-filesystem which
> > takes a few minutes,
On 05.01.2008 01:31, Andrew Morton wrote:
On Wed, 2 Jan 2008 20:35:03 +0100 Matthias Schniedermeyer [EMAIL PROTECTED]
wrote:
Hi
Currently i'm deleting about 500.000 files on a XFS-filesystem which
takes a few minutes, as i had a top open i saw that 'wa' is shown as
0.0
On 03.01.2008 02:16, Maxim Levitsky wrote:
> On Wednesday, 2 January 2008 21:35:03 Matthias Schniedermeyer wrote:
> > Hi
> >
> >
> > Currently i'm deleting about 500.000 files on a XFS-filesystem which
> > takes a few minutes, as i had a top open i saw that 'w
On 03.01.2008 02:16, Maxim Levitsky wrote:
On Wednesday, 2 January 2008 21:35:03 Matthias Schniedermeyer wrote:
Hi
Currently i'm deleting about 500.000 files on a XFS-filesystem which
takes a few minutes, as i had a top open i saw that 'wa' is shown as
0.0% (Nothing else running
Hi
Currently i'm deleting about 500.000 files on a XFS-filesystem which
takes a few minutes, as i had a top open i saw that 'wa' is shown as
0.0% (Nothing else running currently) and everything except 'id' is near
the bottom too. Kernel is 2.6.23.11.
So, as 'rm -rf' is essentially a IO (or
Hi
Currently i'm deleting about 500.000 files on a XFS-filesystem which
takes a few minutes, as i had a top open i saw that 'wa' is shown as
0.0% (Nothing else running currently) and everything except 'id' is near
the bottom too. Kernel is 2.6.23.11.
So, as 'rm -rf' is essentially a IO (or
On 16.12.2007 02:39, Matthias Schniedermeyer wrote:
> Hi
It appears i found my culprit. :-)
I have a ISDN-controller which is driven by the HFC-PCI-driver and it
appears to not be 64bit-safe.
I will test more thorough after i have relocated the card to another
computer.
Bis d
On 16.12.2007 02:39, Matthias Schniedermeyer wrote:
Hi
It appears i found my culprit. Knocking on wood :-)
I have a ISDN-controller which is driven by the HFC-PCI-driver and it
appears to not be 64bit-safe.
I will test more thorough after i have relocated the card to another
computer
Hi
Yesterday i upgraded an 1 year old System from 4x1GB (32Bit, No
Memory-Remap) to 4x2GB (64Bit, Memory-Remap)
Today i due to a lucky coincidence i discovered that i have a memory
corruption problem.
This problem happens only with at least 4GB RAM and Memory-Remap. It
happens with any 2
Hi
Yesterday i upgraded an 1 year old System from 4x1GB (32Bit, No
Memory-Remap) to 4x2GB (64Bit, Memory-Remap)
Today i due to a lucky coincidence i discovered that i have a memory
corruption problem.
This problem happens only with at least 4GB RAM and Memory-Remap. It
happens with any 2
On 12.11.2007 17:18, Tuomo Valkonen wrote:
> On 2007-11-12, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > Geeks like you and me want the latest software
> > (I'm using Debian unstable/testing).
> >
> > But most users want a Linux installation that simply works - and this
> > includes all software on
On 12.11.2007 17:18, Tuomo Valkonen wrote:
On 2007-11-12, Adrian Bunk [EMAIL PROTECTED] wrote:
Geeks like you and me want the latest software
(I'm using Debian unstable/testing).
But most users want a Linux installation that simply works - and this
includes all software on the system
On 11.11.2007 15:05, Thorsten Leemhuis wrote:
> On 10.11.2007 00:32, Matthias Schniedermeyer wrote:
> > [...]
> > My computer/mainboard @work has such a "broken" BIOS. Of the 5
> > SATA-Ports this MB has only 1 (and 1 "missing" that is reporte
On 11.11.2007 15:05, Thorsten Leemhuis wrote:
On 10.11.2007 00:32, Matthias Schniedermeyer wrote:
[...]
My computer/mainboard @work has such a broken BIOS. Of the 5
SATA-Ports this MB has only 1 (and 1 missing that is reported by
linux but i can't find on the MB) is configured as AHCI
On 10.11.2007 13:01, Mark Lord wrote:
> Matthias Schniedermeyer wrote:
>> ..
>> My computer/mainboard @work has such a "broken" BIOS. Of the 5 SATA-Ports
>> this MB has only 1 (and 1 "missing" that is reported by linux but i can't
>> fi
On 09.11.2007 22:08, Jeff Garzik wrote:
> Matthias Schniedermeyer wrote:
>> And on the topic of "broken" BIOSes. I have a little empathy for the MB
>> manufactures as non-RAID AHCI royaly screws Windos, so not supporting it
>> reduces their support costs enou
On 09.11.2007 22:08, Jeff Garzik wrote:
> Matthias Schniedermeyer wrote:
>> And on the topic of "broken" BIOSes. I have a little empathy for the MB
>> manufactures as non-RAID AHCI royaly screws Windos, so not supporting it
>> reduces their support costs enou
On 09.11.2007 22:08, Jeff Garzik wrote:
Matthias Schniedermeyer wrote:
And on the topic of broken BIOSes. I have a little empathy for the MB
manufactures as non-RAID AHCI royaly screws Windos, so not supporting it
reduces their support costs enough to overlook screwing the non-windos
On 09.11.2007 22:08, Jeff Garzik wrote:
Matthias Schniedermeyer wrote:
And on the topic of broken BIOSes. I have a little empathy for the MB
manufactures as non-RAID AHCI royaly screws Windos, so not supporting it
reduces their support costs enough to overlook screwing the non-windos
On 10.11.2007 13:01, Mark Lord wrote:
Matthias Schniedermeyer wrote:
..
My computer/mainboard @work has such a broken BIOS. Of the 5 SATA-Ports
this MB has only 1 (and 1 missing that is reported by linux but i can't
find on the MB) is configured as AHCI which means that with
..
I have
On 09.11.2007 12:04, Alan Cox wrote:
> On Thu, 8 Nov 2007 22:46:22 -0500
> Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Nov 08, 2007 at 10:29:37PM -0500, Mark Lord wrote:
> > > And I might even privately patch my own kernels to map the ACHI BAR
> > > in the cases where the BIOS didn't...
On 09.11.2007 12:04, Alan Cox wrote:
On Thu, 8 Nov 2007 22:46:22 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
On Thu, Nov 08, 2007 at 10:29:37PM -0500, Mark Lord wrote:
And I might even privately patch my own kernels to map the ACHI BAR
in the cases where the BIOS didn't...
The
> > It's not very conservative to suddenly change default behavior and break
> > autofs mounts. There is not even one kernel message that "_tells_ user why
> > it thinks it's wrong". It just silently fails.
>
> No it doesn't. It reports an error code to the caller. If autofs is
> failing
It's not very conservative to suddenly change default behavior and break
autofs mounts. There is not even one kernel message that _tells_ user why
it thinks it's wrong. It just silently fails.
No it doesn't. It reports an error code to the caller. If autofs is
failing silently, then that
markus reichelt wrote:
PS: Just wondering: Who came up with this "on-demand" hype?
I don't remember the names, but i remember the root causes. Here we go:
The discussion started when someone with a CD-Server ran out of loops as 256 was the
"fixed" maximum.
The other "root"-cause was that
markus reichelt wrote:
PS: Just wondering: Who came up with this on-demand hype?
I don't remember the names, but i remember the root causes. Here we go:
The discussion started when someone with a CD-Server ran out of loops as 256 was the
fixed maximum.
The other root-cause was that the
Greg KH wrote:
> On Sun, Jun 10, 2007 at 07:56:52PM +0200, Matthias Schniedermeyer wrote:
>> Greg KH wrote:
>> I could see the point in ONE "HOWTO" file per language to get people
>> started, but everything else is a pointless exercise.
>> A developer/b
Greg KH wrote:
On Sun, Jun 10, 2007 at 07:56:52PM +0200, Matthias Schniedermeyer wrote:
Greg KH wrote:
I could see the point in ONE HOWTO file per language to get people
started, but everything else is a pointless exercise.
A developer/bug-reporter has to be able to express him-/herself
Greg KH wrote:
On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
Since the common language of most kernel contributors is english I
personally feel that we should stick to just that one language in the
tree and then perhaps keep translations on a website somewhere. So the
Greg KH wrote:
On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
Since the common language of most kernel contributors is english I
personally feel that we should stick to just that one language in the
tree and then perhaps keep translations on a website somewhere. So the
Yakov Lerner wrote:
> On 2/14/07, sfaibish <[EMAIL PROTECTED]> wrote:
>> On Sat, 10 Feb 2007 22:06:37 -0500, Sorin Faibish <[EMAIL PROTECTED]>
>> wrote:
>>
>> > Introducing DualFS
>> >
>> > File System developers played with the idea of separation of
>> > meta-data from data in file systems for a
Yakov Lerner wrote:
On 2/14/07, sfaibish [EMAIL PROTECTED] wrote:
On Sat, 10 Feb 2007 22:06:37 -0500, Sorin Faibish [EMAIL PROTECTED]
wrote:
Introducing DualFS
File System developers played with the idea of separation of
meta-data from data in file systems for a while. The idea was
Martin A. Fink wrote:
>> The needed total bandwidth may be to high and at least the incoming part via
> GigE may have serious overhead.
>> 150MB/s in via (at least 2) GigE, without Zero-Copy there is another 150MB/s
> memory to memory.
>> Then there is the next 150MB/s memory to the discs,
Martin A. Fink wrote:
>> Also you have skipped the information how the images "arrive" on the system
> (PCI(e) card?), that may be important for an "end to end" view of the
> problem.
>
> Images arrive via Gigabit Ethernet. GigE Vision standard. (PCIe x4)
The the next question is:
Martin A. Fink wrote:
> Am Dienstag, 13. Februar 2007 00:31 schrieben Sie:
>> Martin A. Fink wrote:
>>> I have to store big amounts of data coming from 2 digital cameras to disk.
>>> Thus I have to write blocks of around 1 MB at 30 to 50 frames per second
>>> for
>>> a long period of time. So
Martin A. Fink wrote:
Am Dienstag, 13. Februar 2007 00:31 schrieben Sie:
Martin A. Fink wrote:
I have to store big amounts of data coming from 2 digital cameras to disk.
Thus I have to write blocks of around 1 MB at 30 to 50 frames per second
for
a long period of time. So it is important
Martin A. Fink wrote:
Also you have skipped the information how the images arrive on the system
(PCI(e) card?), that may be important for an end to end view of the
problem.
Images arrive via Gigabit Ethernet. GigE Vision standard. (PCIe x4)
The the next question is: ChipSet/Used
Martin A. Fink wrote:
The needed total bandwidth may be to high and at least the incoming part via
GigE may have serious overhead.
150MB/s in via (at least 2) GigE, without Zero-Copy there is another 150MB/s
memory to memory.
Then there is the next 150MB/s memory to the discs, without
Martin A. Fink wrote:
> I have to store big amounts of data coming from 2 digital cameras to disk.
> Thus I have to write blocks of around 1 MB at 30 to 50 frames per second for
> a long period of time. So it is important for me that the harddisk drive is
> reliable in the sense of "if it is
Martin A. Fink wrote:
I have to store big amounts of data coming from 2 digital cameras to disk.
Thus I have to write blocks of around 1 MB at 30 to 50 frames per second for
a long period of time. So it is important for me that the harddisk drive is
reliable in the sense of if it is capable
Richard Knutsson wrote:
> Stefan Richter wrote:
>
>> On 15 Jan, Matthias Schniedermeyer wrote:
>>
>>
>>> Stefan Richter wrote:
>>>
>>>
>>>> On 14 Jan, Richard Knutsson wrote:
>>>>
>>>>
>
Richard Knutsson wrote:
Stefan Richter wrote:
On 15 Jan, Matthias Schniedermeyer wrote:
Stefan Richter wrote:
On 14 Jan, Richard Knutsson wrote:
(Really liked the idea to have a Maintainer-button next to Help
in *config)
Rhetorical question: What
Stefan Richter wrote:
> On 14 Jan, Richard Knutsson wrote:
>
>>(Really liked the idea to have a "Maintainer"-button
>>next to "Help" in *config)
>
>
> Rhetorical question: What will this button be used for?
Having "all(tm)" information of something in one place?
Help-Text and
Richard Knutsson wrote:
> Matthias Schniedermeyer wrote:
>
>> Richard Knutsson wrote:
>>
>>
>>> Matthias Schniedermeyer wrote:
>>>
>>>
>>>
>>>> Richard Knutsson wrote:
>>>>
>>>>
Richard Knutsson wrote:
Matthias Schniedermeyer wrote:
Richard Knutsson wrote:
Matthias Schniedermeyer wrote:
Richard Knutsson wrote:
Any thoughts on this is very much appreciated (is there any flaws with
this?).
The thought that crossed my mind
Stefan Richter wrote:
On 14 Jan, Richard Knutsson wrote:
(Really liked the idea to have a Maintainer-button
next to Help in *config)
Rhetorical question: What will this button be used for?
Having all(tm) information of something in one place?
Help-Text and Dependencies/Selects are
Richard Knutsson wrote:
> Matthias Schniedermeyer wrote:
>
>> Richard Knutsson wrote:
>>
>>
>>
>>> Any thoughts on this is very much appreciated (is there any flaws with
>>> this?).
>>>
>>
>>
>> The thou
Richard Knutsson wrote:
> Any thoughts on this is very much appreciated (is there any flaws with
> this?).
The thought that crossed my mind was:
Why not do the same thing that was done to the "Help"-file. (Before it
was superseded by Kconfig).
Originaly there was a central Help-file, with all
Richard Knutsson wrote:
Any thoughts on this is very much appreciated (is there any flaws with
this?).
The thought that crossed my mind was:
Why not do the same thing that was done to the Help-file. (Before it
was superseded by Kconfig).
Originaly there was a central Help-file, with all the
Richard Knutsson wrote:
Matthias Schniedermeyer wrote:
Richard Knutsson wrote:
Any thoughts on this is very much appreciated (is there any flaws with
this?).
The thought that crossed my mind was:
Why not do the same thing that was done to the Help-file. (Before
Loye Young wrote:
>>Take for example the AT keyboard which is
>>one of the most common keyboards in the world. I have seen and
>>used it attached to a PC via parport, serial port and the standard
>>PS/2 port. So to handle cases like this the input layer created a
>>serio interface.
>
>
> If
Loye Young wrote:
Take for example the AT keyboard which is
one of the most common keyboards in the world. I have seen and
used it attached to a PC via parport, serial port and the standard
PS/2 port. So to handle cases like this the input layer created a
serio interface.
If plain ASCII text
Jaswinder Singh wrote:
> Hello,
>
> I want to support old 2.4 modules features in 2.6 kernel modules:-
> 1. no kernel source tree is required to build modules.
I don't think that is possible.
There are a few "questions" that are quite fundamental when you want to
build a module that can be
Jaswinder Singh wrote:
Hello,
I want to support old 2.4 modules features in 2.6 kernel modules:-
1. no kernel source tree is required to build modules.
I don't think that is possible.
There are a few questions that are quite fundamental when you want to
build a module that can be loaded by
Stefan Richter wrote:
> Matthias Schniedermeyer wrote:
>
>>Robert Hancock wrote:
>>
>>>Matthias Schniedermeyer wrote:
>>>
>>>>I have a 1,5 Meter and a 4,5 Meter cable connected to the USB-Controller
>>>>and i only use of them depend
Pete Zaitcev wrote:
> On Thu, 07 Dec 2006 20:41:12 +0100, Matthias Schniedermeyer <[EMAIL
> PROTECTED]> wrote:
>
>
>>>>I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
>>>>(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 T
Robert Hancock wrote:
> Matthias Schniedermeyer wrote:
>
>> Hmmm. That's the only thing that i currently may be doing wrong.
>> I have a 1,5 Meter and a 4,5 Meter cable connected to the USB-Controller
>> and i only use of them depending on where the HDD is placed in m
Robert Hancock wrote:
Matthias Schniedermeyer wrote:
Hmmm. That's the only thing that i currently may be doing wrong.
I have a 1,5 Meter and a 4,5 Meter cable connected to the USB-Controller
and i only use of them depending on where the HDD is placed in my room,
the other one is dangling
Pete Zaitcev wrote:
On Thu, 07 Dec 2006 20:41:12 +0100, Matthias Schniedermeyer [EMAIL
PROTECTED] wrote:
I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is used)
[]
This time i kept the defective files
Stefan Richter wrote:
Matthias Schniedermeyer wrote:
Robert Hancock wrote:
Matthias Schniedermeyer wrote:
I have a 1,5 Meter and a 4,5 Meter cable connected to the USB-Controller
and i only use of them depending on where the HDD is placed in my room,
the other one is dangling unconnected
DervishD wrote:
> Hi Matthias :)
>
> * Matthias Schniedermeyer <[EMAIL PROTECTED]> dixit:
>
>>My averate file size is about 1GB with files from about 400MB to
>>5000MB I estimate the average error-rate at about one damaged file in
>>about 10GB of data.
&
Alan Stern wrote:
> On Wed, 6 Dec 2006, Matthias Schniedermeyer wrote:
>
>
>>Hi
>>
>>
>>I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
>>(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is used)
>>
>>After i
Robert Hancock wrote:
> Matthias Schniedermeyer wrote:
>> Hi
>>
>>
>> I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
>> (currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is
>> used)
>
> All the same enclosu
Robert Hancock wrote:
Matthias Schniedermeyer wrote:
Hi
I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is
used)
All the same enclosure type?
36xFantec (was MaPower) DB-335U2-1 with Genesys-Logic-Chipset
DervishD wrote:
Hi Matthias :)
* Matthias Schniedermeyer [EMAIL PROTECTED] dixit:
My averate file size is about 1GB with files from about 400MB to
5000MB I estimate the average error-rate at about one damaged file in
about 10GB of data.
I'm not sure and haven't checked if the files
Hi
I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is used)
After i realised about a year(!) ago that the files copied to the HDDs
sometimes aren't identical to the "original"-files i changed my
procedured so
Hi
I'm using a Bunch auf HDDs in USB-Enclosures for storing files.
(currently 38 HDD, with a total capacity of 9,5 TB of which 8,5 TB is used)
After i realised about a year(!) ago that the files copied to the HDDs
sometimes aren't identical to the original-files i changed my
procedured so that
Martin Wilck wrote:
Jens Axboe wrote:
If I am reading the specs correctly, that'd mean the ahci driver is
wrong in setting the SActive bit.
I completely agree, that was my reading of the spec as well and hence my
original posts about this in the NCQ thread.
Have you (or has anybody else)
Martin Wilck wrote:
Jens Axboe wrote:
If I am reading the specs correctly, that'd mean the ahci driver is
wrong in setting the SActive bit.
I completely agree, that was my reading of the spec as well and hence my
original posts about this in the NCQ thread.
Have you (or has anybody else)
On Sun, Jun 03, 2001 at 06:38:27PM +0200, Gérard Roudier wrote:
>
> On Sat, 2 Jun 2001, Matthias Schniedermeyer wrote:
>
> > I have 3 SCSI-CD-Writers. "Strange" is that the boot-process only finds
> > the first one (1 0 5 0), the other two i have to add with
> &
On Sun, Jun 03, 2001 at 06:38:27PM +0200, Gérard Roudier wrote:
On Sat, 2 Jun 2001, Matthias Schniedermeyer wrote:
I have 3 SCSI-CD-Writers. Strange is that the boot-process only finds
the first one (1 0 5 0), the other two i have to add with
echo scsi add-single-device 2 0 4 0
#Include
I have 3 SCSI-CD-Writers. "Strange" is that the boot-process only finds
the first one (1 0 5 0), the other two i have to add with
echo "scsi add-single-device 2 0 4 0" > /proc/scsi/scsi
echo "scsi add-single-device 2 0 6 0" > /proc/scsi/scsi
to make them useable.
Here is the
#Include hallo.h
I have 3 SCSI-CD-Writers. Strange is that the boot-process only finds
the first one (1 0 5 0), the other two i have to add with
echo scsi add-single-device 2 0 4 0 /proc/scsi/scsi
echo scsi add-single-device 2 0 6 0 /proc/scsi/scsi
to make them useable.
Here is the
> I just bought one of $subject (PDC 20268)
>
> Removed a Ultra 66 from my system and plugged the new one into the 66Mhz
> PCI-Bus (Intependent from the 33Mhz PCI-Bus (Tyan Thunder HE-SL Mainboard
> with Serverworks HE-SL-Chipset))
>
> Kernel is 2.4.4 with Promise support compiled in. (The
#Include
I just bought one of $subject (PDC 20268)
Removed a Ultra 66 from my system and plugged the new one into the 66Mhz
PCI-Bus (Intependent from the 33Mhz PCI-Bus (Tyan Thunder HE-SL Mainboard
with Serverworks HE-SL-Chipset))
Kernel is 2.4.4 with Promise support compiled in. (The Ultra
#Include hallo.h
I just bought one of $subject (PDC 20268)
Removed a Ultra 66 from my system and plugged the new one into the 66Mhz
PCI-Bus (Intependent from the 33Mhz PCI-Bus (Tyan Thunder HE-SL Mainboard
with Serverworks HE-SL-Chipset))
Kernel is 2.4.4 with Promise support compiled in.
1 - 100 of 116 matches
Mail list logo
