Date: 27 Oct 1999 20:49:35 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: freebsd-questions@freebsd.org Subject: Re: Switching from Linux... What's the deal with Netscape Navigator? Message-ID: <86iu3sn174.fsf@localhost.hell.gr> In-Reply-To: "Ronald F. Guilmette"'s message of "Tue, 26 Oct 1999 16:00:21 -0700" References: <3743.940978821@segfault.monkeys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Ronald F. Guilmette" <rfg@monkeys.com> writes:
> What exactly is Xwrapper and where is its man page? (I'm using it in my
> new .xserverrc file, but I don't even know for sure what it does. I just
> know that it seems to work.)
The only difference that I see Xwrapper having from my XF86_SVGA server
executable is that the former is setuid-root. I'm sure this has something to
do with accessing hardware directly (which is required by most X servers), but
I wouldn't bet on my guessing all that much.
> What extra magic do I have to do in order to get the -C option for xterm
> to actually work? (I've already set /dev/console to mode 0622 and I've
> already made it be owned by me, so those things aren't the problem.)
>
> Is there a version of Adobe Acrobat that will work under FreeBSD 3.x?
Interesting question. I don't know if Adobe gives a FreeBSD-version on their
site. Have you tried searching over there? A friend of mine told me only
this morning that GV can read .pdf files too, so I am going to try that one
tonight and see if it works.
> Other changover related comments:
> ---------------------------------
>
> Whoever built the fvwm-1.24r package messed up and left out the XPM support.
> I hope that in future releases, this package will get properly built with
> the XPM support included. It makes a big difference.
Just by looking at my /usr/ports/ tree (updated on October 5, AFAIR) I noticed
that x11-wm/fvwm/Makefile includes:
LIB_DEPENDS= Xpm.4:${PORTSDIR}/graphics/xpm
It seems that the Xpm library is needed to build fvwm to my ports tree. Try
updating your ports and see if anything changes for the better.
> In my personal opinion, it would be Good if the default generic kernel had
> EXT2FS support built in.
Not really. Since installing FreeBSD on a "clean" machine would leave you
with EXT2FS support in a machine that knows nothing about Linux.
Since building a custom kernel is one of the first things that really ought to
be done on a newly installed machine, you can include EXT2FS support there,
and leave GENERIC without EXT2FS-support.
On the other hand, being able to mount Linux partitions where one has
downloaded the initial FreeBSD installation stuff seems cute. It would
probably have helped me in my transition from Linux to FreeBSD, about a couple
o' months ago.
--
Giorgos Keramidas, <keramida@ceid.upatras.gr>
"What we have to learn to do, we learn by doing." [Aristotle]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86iu3sn174.fsf>