All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Taggart <taggart@carmen.fc.hp.com>
To: Charlie Navarro <charlie_navarro@yahoo.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Problems with debian instalation
Date: Thu, 10 May 2001 11:36:58 -0600	[thread overview]
Message-ID: <20010510173658.12FB237CFD@carmen.fc.hp.com> (raw)
In-Reply-To: Message from Charlie Navarro <charlie_navarro@yahoo.com> of "Thu, 10 May 2001 09:53:02 -0300." <01051009530200.01761@diana>

Charlie Navarro writes...

> I installed my 712/60 from palinux-0.6-32STI.iso and all OK. I had some 
> poblems with the keyboard (some sequence of key in vi, in some case fell down
> the system)

This is a known problem with STI console, but no bug was filed in the BTS. So 
I just filed one. IIRC, setting TERM to vt100 helps.

> I made a "apt-get dselect-upgrade" with out problems, with the original 
> sources.list that it came in the iso.
> Now I have the dependences problems to install gcc. cpp depends of cpp-3.0 
> but it is not installable. xbase-clients depends of cpp.

The gcc package is just a pseudopackage that depends on the right version gcc 
for the architecture, in this case gcc-3.0. Since gcc-3.0 is not yet in the 
archive it can't find the dependency. As Richard pointed out, use the debs on 
puffin.external.hp.com for now. I am working on getting those integrated and 
in the Debian archive.

> Ok, I want to run X, but I can not. I want to compile X but I don't have the 
> gcc.

XFree86 is in the Debian archive but you can't run a local Xserver yet. You 
can run apps remotely and even use Xnest. Does this answer your question?

-- 
Matt Taggart        Linux Development Lab
taggart@fc.hp.com   HP Linux Systems Operation

      parent reply	other threads:[~2001-05-10 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 12:53 [parisc-linux] Problems with debian instalation Charlie Navarro
2001-05-10 13:59 ` Richard Hirst
2001-05-10 17:36 ` Matt Taggart [this message]

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=20010510173658.12FB237CFD@carmen.fc.hp.com \
    --to=taggart@carmen.fc.hp.com \
    --cc=charlie_navarro@yahoo.com \
    --cc=parisc-linux@parisc-linux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.