How do I rebuild the builtin openssl with debugging symbols? I thought I could
simply edit /usr/src/crypto/openssl/Makefile and then run make from the same
directory, but that doesn't seem to work. Is there some way to do this w/o
rebuilding world?
Using the port isn't an option since I need
Mikhail Teterin wrote:
Hi!
I updated world to today's 6.1 and my syslog is filling up with:
Mar 24 15:08:29 aldan sshd[2163]: login_getclass: unknown class 'root'
The /etc/login.conf did not change since November. I never had login.conf.db
-- it was always optional. Did that just change, or
Ceri Davies wrote:
What does your nsswitch.conf look like, and does removing the NIS
entries fix it?
Somebody else pointed out that changing compat to files for the group and
passwd lines silences the error. It appears to be working.
Thanks.
___
I have several machines running 6-STABLE that are showing the error listed below in /var/log/cron every few minutes. Google didn't turn up much of relevance, other than the fact that this might be related to disabling NIS. And, in fast, I have NO_NIS=true in /etc/make.conf on every single box.
Eirik Øverby wrote:
I've spent about a week trying to accomplish a rather simple task: To
build kernel and world once for each architecture we have, and
distribute this precompiled src and obj tree via NFS to all the systems
that need updating. I have combined this with a locally
Scot Hetzel wrote:
You just need to define the _MAKE_CONF variable for the appropriate OS
that you are building:
make _MAKE_CONF=/etc/make.conf.6x [build|install]world
make _MAKE_CONF=/etc/make.conf.6x [build|install]kernel
I spent a bit of time today trying to figure out why the above
Dick Hoogendijk wrote:
Oops, it seems this feature is in 7-CURRENT only. If the appropiate
person is reading this, why isnt something like that available in 6? I
think it would be a very useful feature.
What a shame. You made me glad for a very short time. This seemed to be
the option I was
Vinod Kashyap wrote:
Going by the dmesg, you have a 9.1.5.2 driver and 9.2 firmware. The
driver in 5 -STABLE is from the 9.2 release. So, you might not have
the driver upgrade done properly. Try using the driver and firmware
from the same release. If you still see problems, please contact
Vinod Kashyap wrote:
How did you figure out the versions? I'm looking at his
dmesg, and my own, and I'm not seeing the version info in a
recognizable form. I must admit that I haven't been able to
grok the 3ware version numbers at all, so maybe I'm dense.
What am I missing?
9.1.5.2 and
I have a Soekris crypto card (hifn driver) in a box that I don't have immediate
access to. Is there some way to disable the card w/o rebooting the machine? I
know I could take the driver out of the kernel or force it not to load, but
that requires a reboot that I'd like to avoid if possible.
Vinod Kashyap wrote:
Under 'Release Notes to View', select 'release_Release_Notes_Web',
and you will get to a page which lists the version of each individual
component that's part of the release, among other things.
:) I would have known that if Firefox wasn't barfing on PDF's right now, or if
Robert Watson wrote:
Last I checked, MySQL used solely TCP and UNIX domain sockets for
communication, and not System V IPC. I believe PostgreSQL, however,
used System V IPC.
For some reason I was thinking that domain sockets and System V IPC were the
same thing. Now I know better. Thanks.
Ok, here's what I've decided. But first, thanks for all of the help.
Currently the MySQL databases are on a seperate RAID volume, and I'd like to
keep it that way for performance purposes. In general I want to avoid putting
anything on the raid that isn't a database. I don't want the raid volme
Robert Watson wrote:
There are several ways you can do it, but they generally fall into two
classes of activies:
(1) Modifying the name space exclusion assumption for jails, so that the
file system name spaces overlap. One way to do this is with nullfs.
(2) Having a daemon or tool
Robert Watson wrote:
(1) Modifying the name space exclusion assumption for jails, so that the
file system name spaces overlap. One way to do this is with nullfs.
nullfs looks interesting. I was thinking about sharing files between jails
using NFS, but it looks like nullfs would do the
I have a 5.4-S box running apache2 that's serving data from mysql running on
the same box. I'm thinking about putting both in seperate jails, partly for
security and partly for practice. Would this impact network performance between
the two? Currently the mysql connection is using localhost
The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card.
I wrote a test script to fill up the raid array with lots of files, and it did
just that. Afterwards I did a 'rm *' to clean out the test files and naturally
checked the results with ls. All the files were gone. For some reason,
for the trouble. Nothing to see here...move along. :)
Brandon Fosdick wrote:
The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card.
I wrote a test script to fill up the raid array with lots of files, and
it did just that. Afterwards I did a 'rm *' to clean out the test files
and naturally
Oliver Fromme wrote:
Brandon Fosdick [EMAIL PROTECTED] wrote:
[...]
Determined to press on I tried the install from existing file
system option, w hich I had never noticed before. That didn't work
since I had no idea what path to give it, or even if the flash drive
had been mounted
Oliver Fromme wrote:
It depends on the FreeBSD version. Older versions mounted
it on /dist, if I remember correctly, but newer ones mount
it directly on /.
I just tried booting to the flash with a cdrom installed so I could run the fixit shell. Apparently the cdrom is mounted on /dist and the
So I had this brilliant idea that I was going to install FreeBSD on my new
amd64 system using a 512MB flash drive since I didn't feel like digging out a CD-ROM. I
ended up installing from CD anyway, but I thought I'd share my experience in case anyone
else knows how to do this.
My first
David Magda wrote:
There's the Bonnie and Bonnie++ file system testing programs. I believe
one or both are in the Ports.
Thanks. I'll take a look.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
I recently dealt with the same controller, with a 3TB array. My
solution is tons easier than dealing with gpt or breaking it up. So
long as you don't need to boot from the raid, and you just want it as
one big disk, forget partitioning it. newfs the device directly, and
mount it directly.
Mikael Krantz wrote:
I had the same problem with 8x400 disk on a areca hardware sata card in
fbsd 5.4-stable. Soo I just did newfs -m 2 -U -O 2 -i 262144 /dev/da0
with those options as I needed as much space as possible.
Ok, so that appears to have worked. Is there any benefit to doing this?
dpk wrote:
Whatever you end up doing (we used auto-carving here, had to
unfortunately) be sure to test the partitions fully before proceeding.
Any suggestions? Are there specialized raid test suites or should I just write
a script that writes/deletes a lot of files?
Firefox keeps taking X11 and then the whole machine with it. It
requires a hard reset as even pinging the machine does not work. Only
Firefox seems to be doing this.
Does anyone else have the same problem?
Anyone knows how to solve/debug this?
I've been having this problem for about a month
Chuck Swiger wrote:
If it's going to be a big database server, why aren't you using all of
those drive spindles to help break up the I/O load? :-)
I have other drives for other things, but I still end up with a single large
volume. Thanks for the suggestion.
Now that my shiny new 9500S is installed and not fighting for IRQs, I've created and initialized a ~2.5TB array using the bios utility. So the next step is mounting the new array.
I naively tried following the regular handbook instructions for adding a new drive and failed miserably. And after
Jon Dama wrote:
Where exactly did you run into trouble?
I'm guessing you made the array, you have a device for it in /dev but
ran into problems (expected) using fdisk or bsdlabel.
Yup, that's exactly what happened. I ended up with a 0.5TB partition. At least,
thats what df said.
A few
Erik Stian Tefre wrote:
You can avoid the problem by splitting the array up in partitions
smaller than
2TB each. (I know this does not answer your question, but it simplifies
things,
and it works for me(TM)... :-)
:) Thanks, but I thought of that already. This is going to be a big database
Darren Pilgrim wrote:
I believe the IEEE was involved. :)
That explains a lot :)
IRQ sharing is a known issue with many RAID cards and even some gigabit
ethernet cards. It seems to correlate to cards that push the
performance limit of the bus.
And here I am with both a RAID card and a
So I'm having yet another problem with my AMD64x2/nforce4 system. Of the two
builtin NICs 5.4-S is only recognizing the marvell gigabit chip, which wasn't a
problem until I added a 3ware 9500S-12. With the 3ware card in the network
doesn't work, take it out and it works. From the dmesg bits
Mike Jakubik wrote:
The easiest thing would probably be to disable the onboard sk card, and
put in an em (intel gigabit card). The marvell chipset and driver is known
to be problematic.
I had thought of that, but the motherboard only has 2 non-express PCI slots and
they're both currently
Mike Jakubik wrote:
Forgot to mention. You can always buy a cheap pciE video card :)
You're a big help :)
I was fiddling and I noticed something odd. Previously, the ESCD screen at boot
showed the raid controller and network controller both at IRQ 5. The dmesg I
sent before showed both at
Darren Pilgrim wrote:
Try switching slots with the RAID and video cards. It's silly, but then
so is PCI interrupt routing.
Unbelievable. Who ever wrote the PCI spec should have been shot.
I switched the cards and now the network card is sharing an interrupt with the
video card, but neither
Christian Brueffer wrote:
It doesn't work because the ataraid code in 5.4 doesn't understand
the NVIDIA MediaShield metadata format. It is supported on HEAD
and the RELENG_6 branch that will result in FreeBSD 6.0-RELEASE.
Take a look at the ataraid(4) manpage in HEAD and RELENG_6 for more
I have a DFI Lanparty nf4 Ultra-D with two 80GB drives configured as a raid1
array. The bios lists the array as scsi-0 and claims that its healthy. When I
boot from the disc1 cd and try to do the usual install the only device options
I'm given for fdisk are ad4 and ad6, which obviously aren't
Thanks for all of the replies. It sounds like SMP is doing better than I thought so I've decided to go with the dual core option.
Thanks for the help
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so
Björn König wrote:
Hello Brandon,
I get the same error messages if ACL are not enabled. I just want to
make sure that you didn't overlook the part of the handbook where it
says that you have to enable it.
It seems that's exactly what happened. Thanks for pointing it out.
By the way, the
I have a 5.4 install that I'm trying to use to experiment with ACL (and
extended attributes). Handbook section 14.12.1
(http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/fs-acl.html) has a
few sample commands that I tried running. But I get operation not supported,
like so:
17:02
Jeff Seeman wrote:
I have a client who has 3 restaurants and wants to provide wifi access
to the customers. He wants to be able to control who and when it can be
accessed. He is not planning on charging for the access at the moment
but certainly would like that ability. I want to use freebsd,
I'm working on a small app that talks to a device with a FTDI USB to 232 chip in it. ucom
and uftdi seem to detect it just fine. But calls to read() hang and I'm getting messages
like putc to a clist with no reserved cblocks in my kernel logs. Any idea
what this is?
In a previous post (subject:
Daniel O'Connor wrote:
On Mon, 28 Feb 2005 11:14, Brandon Fosdick wrote:
I'm working on a small app that talks to a device with a FTDI USB to 232
chip in it. ucom and uftdi seem to detect it just fine. But calls to read()
hang and I'm getting messages like putc to a clist with no reserved
cblocks
I'm getting this message when starting X with the nvidia driver...
NVRM: AGP cannot be enabled on this combination of the AMD CPU and OS kernel
NVRM: kernel upgrade recommended.
NVRM: AGP cannot be enabled on this combination of the AMD CPU and OS kernel
NVRM: kernel upgrade recommended.
It always
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Brandon Fosdick [EMAIL PROTECTED] writes:
: Judging from the man page, ucom is limited to acting like a tty with no
: support for sio. Is this true? Is there some magic config bit somewhere
: that will enable hidden sio support?
Ummm
Daniel O'Connor wrote:
Is it blocking waiting for carrier detect to come up?
Try using the cuaNN device instead.
The software in question worked fine using a cuaNN device until said
device died.
Somebody else mentioned that I could set the device to ignore the
carrier detect signal. How do I do
Daniel O'Connor wrote:
ie setting CLOCAL.
That fixed it, thanks.
Is it worthwhile to change the ucom man page to not imply that it only
works for tty? That led me astray. I think I would have eventually found
CLOCAL if I hadn't stopped looking. Or am I the only one that finds it
misleading?
Judging from the man page, ucom is limited to acting like a tty with no
support for sio. Is this true? Is there some magic config bit somewhere
that will enable hidden sio support?
I have some old software that talks to some old hardware over rs232 (using
cuaa) and the builtin 232 port just died.
.
--
Brandon Fosdick
http://www.terranspace.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Jack Raats wrote:
At this moment I cann't connect with ftp.freebsd.org.
I've had the same problem all day.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
I've filed PR i386/69218 for this problem.
Lee Harr wrote:
Wanting to test the -RC, I ran through the updating procedure this
evening,
but I am unable to boot the resulting kernel. The system hangs trying to
detect something with the disks...
This is one of those troublesome nvidia chipset A7N8X
Doug White wrote:
Also, Lite-on drives are known to have buggy firmware. Does removing the
CDROM drive make it boot?
No. It hangs on whatever the last drive is. For example, if I have a
hard drive and a cd-rom it displays ad0... for the hard drive and then
will hang on the cdrom (after
Lee Harr wrote:
So, now... what could be the difference that allows the cd to boot, but
not the same kernel booting from the hard drive?
Do we know that the cd has the same kernel? Could it be possible that
the install cd's kernel isn't GENERIC?
___
On both stable and current I'm having problems getting ftp or fetch to
connect to ftp servers (fetch can't connect to anything). I'm behind a
firewall but the ftp ports are open and I'm sitting next to an HPUX box
that doesn't have the same problem.
All of the output below came from a 5.1-R
Joe Kelsey wrote:
I have a system running
FreeBSD zircon.zircon.seattle.wa.us 4.9-PRERELEASE FreeBSD
4.9-PRERELEASE #20: Fri Sep 19 12:55:28 PDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZIRCON i386
When I upgraded to fix the OpenSSH problems, the system started hanging
at boot time right
M. Warner Losh wrote:
Where 0x12345678 is obtained from pciconf -l and 0x10 is the BAR. If
you don't know the BAR, try 0x10, 0x14 and 0x18.
None of the BAR values worked. In case anyone cares the type value returned by
pciconf -l was 0x1507148d.
However, I'd bet a good dinner that your
Cy Schubert - ITSD Open Systems Group wrote:
In message [EMAIL PROTECTED], "David O'Brien"
writes:
On Sun, Nov 19, 2000 at 01:55:29PM +0100, Roelof Osinga wrote:
Yesterday I installed the 4.2 RC1 in dangerously dedicated
mode on a SCSI disk I had lying around.
Why did you choose a
I cvsup'd on friday (8 Sept), did the whole make world/kernel routine thats in
UPDATING, rebooted and the kernel panics with "kmem_malloc(very large negative
number):kmem_map too small: 3592192 total allocated". I tried booting off the
generic and .old kernels but that doesn't work either (same
Brandon Fosdick wrote:
I cvsup'd on friday (8 Sept), did the whole make world/kernel routine thats in
UPDATING, rebooted and the kernel panics with "kmem_malloc(very large negative
number):kmem_map too small: 3592192 total allocated". I tried booting off the
generic and .o
Thomas Köllmann wrote:
Grigoriy Strokin wrote/schrieb (Friday, March 31, 2000):
| While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
| driver is in UDMA mode is being fixed, I suppose there at least should be some
| note added to /usr/src/UPDATING, so that another
David O'Brien wrote:
On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote:
I asked the same question abot a month ago and didn't get an answer. A
quick search of the archives will find some others with the same
problem. It seems to
I got the report, but got busy
62 matches
Mail list logo
