Tell the kind of your machine and the content of your make.conf, i.e.
CFLAGS if there are any and so on.
Regards Björn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
Jan Sebosik wrote:
I`ve klkload-ed msdosfs module, tried disklabel on
/dev/ad0s2
(which damaged my partition table), but it still something
about that it cannot mount partition (yeh, mount point
e.g.
/mnt/c exists :-\ ). Is freebsd so different against
Linux, or NetBSD?
What is the error
I am a bit confused. Neither de_DE.ISO-8859-1 nor
de_DE.ISO8859-1 work properly in all cases.
setenv LANG de_DE.ISO8859-1
echo abcdef uvwxyz | tr '[a-z]' '[A-Z]'
ABCDEF ÚWXYÝ]
setenv LANG de_DE.ISO-8859-1
echo abcdef uvwxyz | tr '[a-z]' '[A-Z]'
ABCDEF UVWXYZ
perl
perl: warning: Setting locale
Michael Nottebrock schrieb:
Use tr [:lower:] [:upper:] instead.
I was wondering about a third-party script which always
worked for years with Solaris. I just didn't realized that
this issue concerns a difference between SysV and BSD.
I tried to set another LANG string and it worked, but now
I see
It has been decided to provide two disc1 ISO
images, one with the KDE windowing system
packages on it and the other with the GNOME
windowing system packages. They are named
disc1-kde and disc1-gnome respectively. Other
than which major windowing system is on them
they are identical.
It
Darryl Okahata wrote:
find . -type f -print0 | xargs -0 rm -f
Slightly more typing, but more robust.
The find utility of FreeBSD knows a -delete option, e.g.:
find /path/to/your/directory -type f -delete
Regards Bjrn
___
Godwin Stewart wrote:
Is there any particular reason why ports are sticking with
this version when 1.875 was released 2 years ago almost to
the day?
From the first commit comment of devel/bison1875:
Some grammars require the new version of Bison (such as
PostgreSQL), however the new
Hello,
thanks a lot for your hints. The null-modem cable connection is working now.
Anyway, it was surprisingly easy, but I'm totally inexperienced and the
neglected manpages and handbook discouraged me, because I didn't touch serial
ports since a decade ;-) Finally someone points me at [1].
Hello,
I wanted to use SLIP to connect two machines with a null-modem cable, but I
realize that all information concerning this topic seems to be out of date.
First of all the device sl0 doesn't exist in 5.3 although there is a device
sl in sys/i386/conf/GENERIC for Kernel SLIP. The manpage of
Either you set the release name in Options menu to 5.3-RELEASE before going
to Packages menu or start sysinstall with
sysinstall releaseName=5.3-RELEASE configPackages
Regards
Bjrn
___
[EMAIL PROTECTED] mailing list
Hello,
Your problem occures with bash-3.0.16, but it works fine for me. I have
bash-3.0.16_1. That's the reason why the maintainer told you that you have to
update your ports. Maybe your used CVSup server is out of date; try another
one, e.g. cvsup2.freebsd.org.
Bjrn
use -E
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Rob wrote:
[...]
both have
*default release=cvs tag=RELENG_5
although the first one claims to download CURRENT.
And, eh, why is the filename standard-supfile and
why not the more obvious current-supfile ?
It only claims, but it doesn't bring you -CURRENT. That's the reason why it
Rob wrote:
If so, then why do we have a standard-supfile and a stable-supfile
doing the same thing? If both bring you -STABLE, one of the two seems
to be redundant to me and having two sup files doing the same only
causes confusion.
Maybe you're right. There is a kind of redundancy now, but
14 matches
Mail list logo
