Reports at BP over years find history of problems By Abrahm Lustgarten and Ryan Knutson Washington Post Tuesday, June 8, 2010; A01 ProPublica A series of internal investigations over the past decade warned senior BP managers that the oil company repeatedly disregarded safety and environmental rules and risked a serious accident if it did not change its ways. The confidential inquiries
David Malone wrote: MZ <mark@nospam.void> writes: Also, I don't believe I can fsck the device, because it's a zfs raidz array. But I'll research this some more. Ah - now we're talking! It seems that zfs can be told to consider filenames to be in utf8, rather than just be sequences of bytes. I don't know a lot about this, but turning on/off the "utf8only" properity on
On 6/7/2010 11:57 AM, David Malone wrote: MZ <mark@nospam.void> writes: Still returns illegal byte sequence. Hmmm - odd - "Illegal byte sequence" is definitely a locale related error, it's listed as EILSEQ in errno(2) and should usually only happen if you're using multibyte or wide characters. The multibyte stuff changes the behaviour of quite a number of library functions
Tim Daneliuk wrote: On 6/7/2010 1:42 PM, MZ wrote: Tim Daneliuk wrote: On 6/7/2010 12:27 PM, MZ wrote: David Malone wrote: MZ <mark@nospam.void> writes: Still returns illegal byte sequence. Hmmm - odd - "Illegal byte sequence" is definitely a locale related error, it's listed as EILSEQ in errno(2) and should usually only happen if you're
On 6/7/2010 1:42 PM, MZ wrote: Tim Daneliuk wrote: On 6/7/2010 12:27 PM, MZ wrote: David Malone wrote: MZ <mark@nospam.void> writes: Still returns illegal byte sequence. Hmmm - odd - "Illegal byte sequence" is definitely a locale related error, it's listed as EILSEQ in errno(2) and should usually only happen if you're using multibyte or wide characters
