Joshua Isom wrote:
> But google and other search engines treats words([A-Za-z0-9])
> starting with - as meaning exclude results with this, even when
> obvious it's about unix commands. It can be rather annoying
> when searching for help.
This comment suggests a new translation of GNU: Google's
Is there a limit on line length in FreeBSD's /etc/hosts?
I'm not finding any mention of such a limit in hosts(5), but
characters beyond the first 660 or so seem to be ignored.
To answer the inevitable followup "why would anyone need such
a long line in /etc/hosts":
With this line in /etc/nsswitc
"Steve O'Hara-Smith" wrote:
> It's a pity there are now only two manufacturers of spinning rust.
I didn't think there were _any_! Haven't oxide-coated platters gone
the way of the dodo bird?
___
freebsd-questions@freebsd.org mailing list
http://lists.
Gary Aitken wrote:
> Air ducting shouldn't be a problem; I've got the side of the case off...
This just might be part of the problem. Air plumbing
is not as forgiving as it was in the old days.
___
freebsd-questions@freebsd.org mailing list
http://lis
Robert Bonomi wrote:
> > Date: Wed, 14 Nov 2012 05:48:48 +0100
> > From: Polytropon
> > Subject: Re: well, try here first...
> >
> > On Tue, 13 Nov 2012 20:20:51 -0700, Chad Leigh Shire.Net LLC wrote:
> > >
> > > To be fair, a lot of the same rules exist for English. The
> > > comma is not opti
Bernt Hansson wrote:
> On 2012-11-17 21:36, Gary Aitken wrote:
> > # portmaster -n emulators/wine-fbsd64
> > ===>>> No /usr/ports/emulators/wine-fbsd64 exists, and no information
> > ===>>> about emulators/wine-fbsd64 can be found in /usr/ports/MOVED
> > hints?
> There has never been such a po
When trying to open an X application on a remote display,
I am getting
No protocol specified
Error: cannot open display: 192.168.200.61:0
The "No protocol specified" message is bogus: the display is
specified correctly*, and the same operation -- with exactly
the same setting of DISPLAY
> I am interested in downloadind the 2 disks for linux, and trying
> to install them on my computer, but I am not sure what i have to
> download, could comeone please help me
You may be asking the wrong list. FreeBSD is not Linux, although it
can run many Linux binaries if configured appropriatel
Anyone know where I can find a working word processor for 6.1?
AbiWord and OpenOffice both require Gnome, which won't build.
richtext builds OK, but as soon as I try to select "bold" it
writes 4 lines to stderr and drops core:
Message backtrace:
bold
bold
OutOfBounds: offset 0, size 0
__
> > Anyone know where I can find a working word processor for 6.1?
> > AbiWord and OpenOffice both require Gnome, which won't build.
>
> What do you mean: which won't build? No problems here - I recently
> compiled both. They don't require the full gnome package.
Both of them (and also Dia) requ
> > Anyone know where I can find a working word processor for 6.1?
...
> You can go to http://porting.openoffice.org/freebsd/ and download
> openoffice2.0.3 pre-built binaries from there. I would suggest
> that, rather than trying to build it.
Thanks for the pointer. That is the sort of thing I
> > Anyone know where I can find a working word processor for 6.1?
> > AbiWord and OpenOffice both require Gnome, which won't build.
...
> KOffice 1.5 has OpenDocument support.
Not that I'm any more eager to get into
a KDE mess than a Gnome mess :)
File format support is not important.
I just nee
> >>> Anyone know where I can find a working word processor for 6.1?
> >>> AbiWord and OpenOffice both require Gnome, which won't build.
> >> What do you mean: which won't build? No problems here - I recently
> >> compiled both. They don't require the full gnome package.
> >
> > Both of them (and
> > > If you installed programs from packages when you installed the
> > > system, you may get problems with version conflicts installing
> > > from an updated ports collection - this happens usually when the
> > > last release is getting old. In that case, maybe you should clean
> > > out the syst
> > FreeBSD and Linux will not meet your teenagers needs, If you really
> > want to introduce your kid to UNIX then buy a Mac... trust me on
> > this... I interact with many high school and college kids on a daily
> > basis. Any used Mac capable of running Mac OS X 10.4 Tiger and
> > NeoOffice2 wil
> By the way, Openoffice does work nicely on FreeBSD 6.1 and Gnome
> is not needed for it at all. Gnome is irrelevant to Openoccife.
The Ports build of OpenOffice seems to require glib, which seems
to be maintained by the gnome folks even if it is not, strictly
speaking, part of gnome. If there
> I think FreeBSD supports ext2 better than Linux supports UFS.
This is a ways down my priority list, but since the subject has
come up :)
It is not working for me at all (in 6.1):
# ll /dev/ad0s7
crw-r- 1 root operator0, 93 Sep 4 02:30 /dev/ad0s7
# file -s /dev/ad0s7
/dev/ad
Having gotten a sufficiently-recent version of glib, I am now
several hours into the build of OpenOffice, and I've discovered
that Firefox has quit working. When I try to start it:
GThread-ERROR **: file gthread-posix.c: line 187 (): error 'Invalid argument'
during 'pthread_mutex_trylock'
aborti
> > Having gotten a sufficiently-recent version of glib, I am now
> > several hours into the build of OpenOffice, and I've discovered
> > that Firefox has quit working. When I try to start it:
> >
> > GThread-ERROR **: file gthread-posix.c: line 187 (): error 'Invalid
> > argument' during 'pthre
Anyone seen this and know how to get past it?
Configuring out the failing component would be fine,
if possible, since I really only need the word processor.
Making: ../../../../unxfbsdi.pro/slo/SlideSorterView.obj
g++-ooo -fmessage-length=0 -c -Os -fno-strict-aliasing -fvisibility=hidden
-I. -
> > Making: ../../../../unxfbsdi.pro/slo/SlideSorterView.obj
...
> > g++-ooo: Internal error: Killed: 9 (program cc1plus)
...
> > dmake: Error code 1, while making
> > '../../../../unxfbsdi.pro/slo/SlideSorterView.obj'
> > '---* tg_merge.mk *---'
> >
> > ERROR: Error 65280 occurred while making
>
Has anyone gotten OpenOffice to use a Postscript printer's built-in
fonts? If so, how did you do it? I haven't found the answer in the
docs or FAQs, and got no response on the OpenOffice list.
___
freebsd-questions@freebsd.org mailing list
http://lists.
This hack presumably results in a broken slidesorter, but at least
Writer seems to work (after a fashion), and that's all I really need.
Since the *.obj are just empty sentinel files indicating that the
corresponding *.o have been built, this
# cd /usr/ports/editors/openoffice.org-2.0
# touch
> Before you can build from ports, you need to have ports tree
> in place, the standard way to do this is by running portsnap.
with the caveat that, at least in my recent experience, an
up-to-date ports tree does not always play nicely with a
not-updated base install from CD. OP might be bet
> > ... at least in my recent experience, an up-to-date ports tree
> > does not always play nicely with a not-updated base install from
> > CD.
>
> That's very interesting. However, the ports tree on the CD isn't
> complete, as in: not all the ports are there.
Any idea why? (I am referring t
What am I doing wrong?
# ll /dev/ad0s7
crw-r- 1 root operator0, 93 Sep 4 02:30 /dev/ad0s7
# file -s /dev/ad0s7
/dev/ad0s7: Linux rev 1.0 ext2 filesystem data
# grep -w ad0s7 /etc/fstab
/dev/ad0s7 /linux ext2fs ro 0 0
# ll -d /linux
drwxr-xr-x 2 root
> > # ll /dev/ad0s7
> > crw-r- 1 root operator0, 93 Sep 4 02:30 /dev/ad0s7
> > # file -s /dev/ad0s7
> > /dev/ad0s7: Linux rev 1.0 ext2 filesystem data
> > # grep -w ad0s7 /etc/fstab
> > /dev/ad0s7 /linux ext2fs ro 0 0
> > # ll -d /linux
> > drwxr-xr-x
> >> > # ll /dev/ad0s7
> >> > crw-r- 1 root operator0, 93 Sep 4 02:30 /dev/ad0s7
> >> > # file -s /dev/ad0s7
> >> > /dev/ad0s7: Linux rev 1.0 ext2 filesystem data
> >> > # grep -w ad0s7 /etc/fstab
> >> > /dev/ad0s7 /linux ext2fs ro 0 0
> >> > # ll -d /l
> I'm beginning the install of 6.1 RELEASE on a Dell 1950. It uses
> Dual Embedded Broadcom NetXtreme II 5708 Gigabit Ethernet NICs,
> and they are not correctly recognized during the install. The
> system identifies them as bce0 and bce1, but apparently the driver
> isn't working right.
>
> Does
> >> The standard kernel doesn't have ext2fs support now; I doubt the 6.1
> >> release was different. Try loading it as a module; "kldload ext2fs".
> >
> > It seems not to be that easy :(
> >
> > # kldload ext2fs
> > kldload: can't load ext2fs: No such file or directory
> >
> > Where is ext2fs
> In order to follow the upgrade instructions in the Handbook or
> /usr/src/UPDATING to the letter, you need console access to the
> machine being updated. That is [a] problem ... when it's in a
> hosting centre umpty dozen miles away ...
>
> There are essentially three possibilities.
>
> i) get s
> - login as user 'kiosk' into FreeBSD and getting a desktop in (for
> example KDE);
> - launch a graphical MUA (for example Kmail, or a browser) which
> supports more than one identity, let's say <[EMAIL PROTECTED]>,
> <[EMAIL PROTECTED]> and so on, and each user must somehow
> authenticat
> > I was just looking over the release schedule for the 6.2
> > release, a few weeks ago, there was no detailed plan, now
> > it's there including the todo-list,
> >
> > http://www.freebsd.org/releases/6.2R/todo.html
> >
> > No critical pending issues, no show stoppers left, no required
> > or d
> > Where would one find the list of problems already fixed -- hence
> > not being tracked -- so as to know whether a given 6.1 problem
> > needs to be pointed out?
>
> http://www.freebsd.org/cgi/query-pr-summary.cgi?query
It looks as if the closest that comes is to produce a list of
everything fi
> So I got up and walked away from my computer this afternoon, and
> came back to find it in the middle of shutting down. No good
> reason, no crash dump (yes, they're configured) no nothing, just
> this:
>
> Sep 19 18:14:53 colossus syslogd: exiting on signal 15
>
> At this point, everything sync
>> rpc.lockd remains unreliable; avoid using it if practical.
statd and lockd have been problematic ever since Sun invented them
a couple of decades ago, at least partly because what they are
trying to do is fundamentally not computable. (There is no way to
distinguish between the other side havi
Do I need to do anything about these lines near the end
of the dmesg?
unknown: can't assign resources (memory)
unknown: can't assign resources (port)
unknown: can't assign resources (port)
unknown: can't assign resources (port)
unknown: can't assign resources (port)
unknown: can'
Where would I find functionality similar to regcomp(3) and friends,
without the complexities of supporting multiple locales? I only
need the C locale, and would much prefer to avoid the performance
and code size costs associated with handling multi-byte characters.
I've just installed FreeBSD 6.1 on a Dell Pentium III, and I must have
done something wrong -- or missed a step -- somewhere along the way.
When trying to boot, I do not get even as far as the situation
described in sec. 4.2.5 of the installation instructions. The system
hangs, with a completely
> Do you get the FreeBSD boot menu ?
>
> Pramod Venugopal
> [EMAIL PROTECTED]
No. The BIOS clears the screen and loads the boot sector, then nothing.
> On Aug 14, 2006, at 7:24 PM, Perry Hutchison wrote:
>
> > I've just installed FreeBSD 6.1 on a Dell Pentium
> > The BIOS clears the screen and loads the boot sector, then nothing.
>
> I'm not sure exactly what the problem is, but I can say I've
> installed FreeBSD x.y on just about every flavor of Dell hardware
> without much trouble, so it should work for you. Disclaimer: the
> Dimension line is hig
> Recommend you get a [bigger|second] disk if you can though,
> or housecleaning will be a constant chore.
I got it more or less working, although not completely set up, and
then that 10GB disk died: click -- kerthunk -- click -- kerthunk
continuously, even after cycling power, even with only the
> Well, you're at least as far as having the disk sliced up in a
> workable way, or the bootstrap wouldn't start at all. This jumps
> out as not only being bad, but happening right before meltdown.
>
> > acpi: bad RSDP checksum (210)
I suspect it's a red herring, since I was getting that message
> > After a CD boot, is there a reasonably simple way to have
> > sysinstall reinstall just the kernel -- or the package
> > containing it -- without starting completely over?
>
> Yeah, see what Derek wrote. Never done that, myself, or even
> heard of the kernel not getting installed.
What Derek
In 6.1, how would I set up xorg.conf to restrict Xorg to a few
specific modes? The Xorg.8.log created during xorgcfg shows 24
modelines, but when I cycle through the modes using CtrlAltPlus
there are two which don't work at all and the remaining 22 cover
only 8 resolutions (of which only about 3 s
> > In 6.1, how would I set up xorg.conf to restrict Xorg to a few
> > specific modes? The Xorg.8.log created during xorgcfg shows 24
> > modelines, but when I cycle through the modes using CtrlAltPlus
> > there are two which don't work at all and the remaining 22 cover
> > only 8 resolutions (of
What I have done:
* Installed 6.1, including the Ports Collection, from CD.
* Ran portsnap fetch.
* Attempted portsnap update.
? It sez this only works after an extract. What is the point of
installing the collection from CD if it has to be completely
reinstalled from a download anyway?
> > * Reran 'portupgrade -a' ... This time it complains about the
> > pkgdb.
> > ? Now what? Is it time to "rm -rf /usr/ports /var/db/pkg"
> > and start completely over (and if so, what should I do
> > differently this time)?
>
> Try this. Run everything as root.
>
> pkgdb
> > # pkgdb -F
> > ---> Checking the package registry database
> >
> > [Updating the pkgdb in /var/db/pkg ...
> > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid
> > argument; rebuild needed] [Rebuilding the pkgdb in
> > /var/db/pkg ... /var/db/pkg/pkgdb.db: unexpected file type
49 matches
Mail list logo
