On Fri, Jul 21, 2023 at 11:03:28AM +1000, Finn Thain wrote:
> On Fri, 21 Jul 2023, Dave Chinner wrote:
>
> > > I suspect that this is one of those catch-22 situations: distros are
> > > going to enable every feature under the sun. That doesn't mean that
> > > anyone is actually _using_ them
On Thu, Jul 20, 2023 at 05:38:52PM -0400, Jeffrey Walton wrote:
> On Thu, Jul 20, 2023 at 2:39 PM Matthew Wilcox wrote:
> >
> > On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > > > Then we should delete the HFS/HFS+ fil
On Thu, Jul 20, 2023 at 07:50:47PM +0200, John Paul Adrian Glaubitz wrote:
> > Then we should delete the HFS/HFS+ filesystems. They're orphaned in
> > MAINTAINERS and if distros are going to do such a damnfool thing,
> > then we must stop them.
>
> Both HFS and HFS+ work perfectly fine. And if
it. Resurrecting it will be quite a task. Best of luck.
I'm willing to answer questions (please cc linux-scsi), but not do
the work.
--
Matthew Wilcox Intel Open Source Technology Centre
Bill, look, we understand that you're interested in selling us this
operating system
On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote:
As many of you may know on some machines users will need to install
a current kernel before they will be able to upgrade woody to sarge
(or better: glibc of woody to glibc of sarge). I've tried to use the
available information
You probably just want to give this package back to the buildd:
devel/ocamldsort_0.14.1-1: Uploaded by buildd-vore [optional:out-of-date]
Previous state was Building until 2003 Aug 31 19:33:27
--
It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about
On Mon, Aug 26, 2002 at 09:06:00AM -0400, Carlos O'Donell wrote:
Done. I've submitted the output for HPPA boxes running 32 and 64-bit
kernels. Looks like they pass without any problem. I'll pass on the
yes, but it may well crash them. some parts of /dev/mem map random IO
addresses which may
On Mon, Aug 26, 2002 at 09:10:54PM +0200, Marcus Brinkmann wrote:
Also, reading /dev/mem doesn't sound very secure at all (even if it works)
because the patterns in the memory of a computer are probably predictable
and a lot of information can be observed from the outside (which processes
are
On Wed, Dec 12, 2001 at 02:34:22PM -0500, John R. Daily wrote:
I'm cc'ing the ports in question in hopes that some of these
problems can be solved by developers more familiar with those
platforms. I haven't included s390, because the failure to build
there seems to involve several missing
On Wed, Dec 12, 2001 at 12:56:53PM -0700, Tom Tromey wrote:
I'm unaware of a libffi port to HPPA. If there is one, it hasn't been
integrated into the main libffi sources :-(
Nobody's made libffi compile on debian/hppa yet:
$ madison libffi2
libffi2 | 1:3.0.2-4 | testing | alpha,
10 matches
Mail list logo
