Re: Using regex(3)

2005-06-22 Thread Titus von Boxberg

Olivier Nicole schrieb:

Hi,

I must missunderstand how to use regex(3).

no, you're misunderstanding regoff_t or printf.
it's a 64 bit type. thus your printf should read:

ret=regexec(preg, string, nmatch, pmatch, 0);
printf(return from regexec=%d\nnmatch=%d\np0.so=%lld p0.eo=%lld\np1.so=%lld
p1.eo=%lld\np2.so=%lld p2.eo=%lld\np3.so=%lld p3.eo=%lld\n,
ret, nmatch,
pmatch[0].rm_so, pmatch[0].rm_eo,
pmatch[1].rm_so, pmatch[1].rm_eo,
pmatch[2].rm_so, pmatch[2].rm_eo,
pmatch[3].rm_so, pmatch[3].rm_eo );

regards
titus
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Booting with multiple RAID1 configs

2005-06-17 Thread Titus von Boxberg

Here is what I did, and the subsequent effect:

(Remember, ad4 and ad6 (promise drives) make up the bootable ar0):

# after 2 brand new drives installed:

- atacontrol create RAID1 ad0 ad2
...at which point it said it was successful, and designated the new RAID
config as ad1.

After reboot, the server comes up, identifies ad0, ad2, ad4 and ad6 as
expected. Then it tries to load up the ar driver. It clearly says ar0
has 2 disks, ad0 and ad2, and ad1 now has ad4 and ad6, which is
backwards from how it should be.

Then it baffs with a mountroot error, and no manner of trying to point
to any disk or array is successful. Mountroot errors 16 and 22 come up.

I pull the new drives back off the motherboard IDE connections, box goes
back to exactly how it was before this mess started.


You might use loader(8) to set the root device (rootdev variable) 
explicitly to ar1s1a. Then you should also update fstab to reflect the 
numbering change.

I don't know of any way to change the ata numbering scheme.
Mainboard controllers always seem to be probed (and numbered)
first. I think there is no way to get your original raid
back to ar0 if you also use your mainboard controllers.

Cheers
Titus
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


AW: Logging via Serial Port

2005-06-16 Thread Titus von Boxberg
 I have a phone system that I need to log information from to a FreeBSD
 box via a serial cable. What would be the best way to listen to the
 serial port and write those messages to a log file?
Why not simply use 
cat /dev/cuaax  logfile

You might use stty to set communication parameters after issueing 
the cat command.

regards
titus

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


inconstistent snapshot contents

2005-06-16 Thread Titus von Boxberg
Hi,

during regularly backups with tar from a filesystem snapshot 
I noticed that the contents of the snapshot changed during the
backup.

Is there any bug known with the snapshot code?

Can someone point me to the appropriate code in the 
kernel where to check for inconsistent snapshot contents?

Thanks in advance

Titus von Boxberg

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: disabling ata devices

2005-06-15 Thread Titus von Boxberg

JM schrieb:
i'm not exactly sure how to accomplish this... i'm having problems with 
my cd-rom, which isn't surprising since it's a slim-line without UDMA 
and probably isn't supported... but... it's eating up time when i'm 
just remove the device node altogether.  every time i remove /dev/acd0 
it's just recreated each time i restart.  not sure how to permanently 
remove it without physically removing it from the system.  is there 
anyway to remove the node without removing the iso9660 entry from the 
kernel?

Neither iso9660 nor the device entry have to do with the probing of
your CD drive.
Either you make a custom kernel and comment out the appropriate
line for the driver or you can configure the kernel at boot
time via UserConfig not to probe for the device.
The first way is straightforward and documented in the handbook.
The second way is documented in the loader(8) manpage
and e.g. here:
http://www.treefort.org/~rpratt/freebsd/31/userconfig.html
or for different CD-ROM drives mentioned here:
http://www.freebsd.org/relnotes/5-STABLE/installation/i386/trouble.html

regards
Titus
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]