Re: Installing net-BSD hpcmips on compaq 2010C

Hello!

Finally I got the netBSD hpcmips working on compaq 2010C.
Thanks for the 
help and advices!

I got a CF reader and a net-BSD live CD in order to copy the
sets to the 
UFS partition. That worked! X windows running too.
Now It's time for me to know how to "customize"
twm cos' I had never 
used before.
Does anybody tried installing another light-weight window
manager on 
this old handhelds?
I like to do some wordprocessing with it. Which application
would you 
suggest?

Regards,
Matías

On 4/3/07, Matias Gut <matiasartournet.com.ar> wrote:
> Hello!
>
> Finally I got the netBSD hpcmips working on compaq
2010C. Thanks for the
> help and advices!
>
> I got a CF reader and a net-BSD live CD in order to
copy the sets to the
> UFS partition. That worked! X windows running too.
> Now It's time for me to know how to
"customize" twm cos' I had never
> used before.
> Does anybody tried installing another light-weight
window manager on
> this old handhelds?
> I like to do some wordprocessing with it. Which
application would you
> suggest?

I've used blackbox with success. I know fluxbox works too. I
think I
am currently using fluxbox.

Word processing might be difficult. I believe gtk1 apps will
build,
but not gtk2. I might have some packages you can download
depending on
what level of NetBSD you are on.

I just use pico if I want something that resembles a
"real" word
processor. But that's rare, normally I just use vi.

Andy

On 04/03 09:01 , Andy Ruhl wrote:
> I just use pico if I want something that resembles a
"real" word
> processor. But that's rare, normally I just use vi.

at the risk of being off-topic...

I've written a couple of books using vim and LinuxDoc SGML
(tho I need to
find a better markup language). word processors mostly just
get in the way
of content, making you focus on formatting. the power,
speed, and
reliability of vim makes editing text (the real content)
much easier.

If necessary, the plain text can be imported into a word
processor after
it's written. You'd be surprised how long you spend futzing
with fonts and
column widths and paragraph placements... and it's better to
do that all
afterward; so you're not fighting the word processor every
step of the way
toward getting your content out.

-- 
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com