From: Alex deVries <adevries@thepuffingroup.com>
To: phi@tcleur.france.hp.com
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [Fwd: [parisc-linux] 715/80 problems]
Date: Wed, 22 Sep 1999 13:53:36 -0400 [thread overview]
Message-ID: <37E917A0.CEBD1D71@thepuffingroup.com> (raw)
In-Reply-To: 37E90B93.69DE1184@tcleur.france.hp.com
phi@tcleur.france.hp.com wrote:
>
> With the regression that occured after 14 september 1999, or so (20
> septembre is wrong, 14 setp is good), I can't use it anymore.
>
> I'm think about a newfs to regain the full HFS capacity unless one of
> you can tell me this will be put back as it was before. For now I assume
> the vmlinux is not supposed to boot from isl> hpux right?
It's *supposed to* work, but it doesn't.
Ah, okay. This means that we should just be able to see what changed on
Sept. 14 and figure out what to fix.
Is anyone interested in fixing this?
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-09-22 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 17:02 [Fwd: [parisc-linux] 715/80 problems] phi
1999-09-22 17:53 ` Alex deVries [this message]
1999-09-24 9:42 ` [parisc-linux] 715/80 problems Helge Deller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37E917A0.CEBD1D71@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=phi@tcleur.france.hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox