pw_user.c change for samba
I know we're in a code freeze right now, but would anyone have a
problem with this patch once the freeze is up? This brings us closer
to allowing samba to automatically joining machines to the domain.
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org
Index: pw_user.c
===
RCS file: /home/ncvs/src/usr.sbin/pw/pw_user.c,v
retrieving revision 1.51
diff -u -r1.51 pw_user.c
--- pw_user.c 24 Jun 2002 11:33:17 - 1.51
+++ pw_user.c 27 Nov 2002 19:07:02 -
@@ -1195,7 +1195,7 @@
pw_checkname(u_char *name, int gecos)
{
int l = 0;
- char const *notch = gecos ? :!@ : ,\t:+#%$^()!@~*?=|\\/\;
+ char const *notch = gecos ? :!@ : ,\t:+#%^()!@~*?=|\\/\;
while (name[l]) {
if (strchr(notch, name[l]) != NULL || name[l] ' ' || name[l] == 127
||
Re: pw_user.c change for samba
On Wed, Nov 27, 2002 at 02:32:22PM -0500, David Rhodus wrote: Can you provide more meaning as to what the patch does? It allows usage of $ signs for adding users like pw add user asdf$ which for samba asdf$ would be a computer name -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
Why is this actually necessary for SAMBA? Is it necessary for all three of these to permit this, or is it sufficient to (for example) allow it in the group name? Samba needs a user account for the domain machine account the machine account always ends with a $ So it would only have to be for the account name -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
Go read the SAMBA website, there's a good deal about how us lucky FreeBSD + SAMBA users get to vipw+vi /etc/group by hand, since pw(8) doesn't let one do what [adduser] does. Last I checked adduser doesn't even let you use $ It claims to support it with the RE it shows you, but then when you try to add a user with a $ in it, it says you've entered an invalid user name. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
I gathered that from the SAMBA site, too. The '$' is a pain. None of the examples in the original post would have worked, because the '$' was not '\$', and the shell would have blown chunks over the variable expansion. The patch I sent in works with pw add user asdf$, but you may be right about scripts if the $ is at the beginning. It seems to me that this could cause a great deal of problems for scripts that process the password files, as they currently exist, if they use constructs like eval, or back-ticks, etc.. The problems are already being caused though. If one wants samba to work on NT/2K/XP they have to manually add these entries in now anyway. If it's allowed, it whould probably only be allowed in the user name (i.e. the patch is wrong; it should probably add another parameter to the allowable values of 'int gecos', and change it to 'int checktype' or similar). I don't have a problem with this, but the patch I sent in is the extent of my abilities to give me desired results(making pw like samba) It seems to me that another alternative is that all these names end in '$'; therefore, when you are expecting one of these names, you could imply a '$', without needing to actually have it in the password file -- in other words, it's an attribute, not really part of the account name. Will this open up a security hole for a nomal user account being used to compromise the domain system security? Is it absolutely necessary to use an in-band method to distinguish these records from ordinary user accounts? I don't think the samba people would be willing to make this type of change just for FreeBSD since it works for most everyone else. I also don't think there is currently a way to store attributes about machines/users permanently in samba. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
On Wed, Nov 27, 2002 at 01:37:05PM -0800, Terry Lambert wrote: David W. Chapman Jr. wrote: If it's allowed, it whould probably only be allowed in the user name (i.e. the patch is wrong; it should probably add another parameter to the allowable values of 'int gecos', and change it to 'int checktype' or similar). I don't have a problem with this, but the patch I sent in is the extent of my abilities to give me desired results(making pw like samba) See attached patch. It could still screw scripts (e.g. the perl script version of adduser) by allowing the $ in the login field, but at least it keeps it out of the login class and group fields. That sounds great! I think you misunderstand. The intent is to allow accounts without $ appended to be used as machine logins. Samba would see the '$', remove it, and check normally. The proper BSD way to avoid this hack would be to add a login class samba_server (or whatever), and make Samba permit this type of check only if the user was in the correct login class. Unfortunately they have to support more than just BSD, but I do agree with you that there is probably a better way of doing things. I am just not technically inclined enough to bring this to the attention of the samba team properly. I do have some contacts I could forward to anyone that is interested in trying to persuade them though. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
David Last I checked adduser doesn't even let you use $ How about to set usernameregexp = '^[a-z0-9_][a-z0-9_-]*[a-z0-9_$-]$' in /etc/adduser.conf? It allows to make a 'machine account' ending with '$'. I checked this about two months ago. Wouldn't pw still have to be updated. I haven't looked at adduser but I thought it was a wrapper for pw? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pw_user.c change for samba
The '$' is a pain. None of the examples in the original post would have worked, because the '$' was not '\$', and the shell would have blown chunks over the variable expansion. Your foundation is flawed, we allow $ in passwd just fine, and the only problem here is whether a pw should let someone do something we support which they might need to do. Apply the patch. Then try to add a user with a trailing $ via adduser(1); Note the failure. I think NAKAJI Hiroyuki pointed out that adduser has nothing to do with pw_user and if you add usernameregexp = '^[a-z0-9_][a-z0-9_-]*[a-z0-9_$-]$' to /etc/adduser.conf adduser will then allow $'s To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Lots of swapping from 'kldload acpi'
On Fri, Nov 22, 2002 at 11:56:29AM -0800, Kris Kennaway wrote: I tried to kldload acpi on a system that has been running for about 3 days, and the kldload process has been sitting there swapping for about an hour now. Breaking into DDB shows that acpi_alloc_wakeup_handler() is trying to contigmalloc(), and this is swapping around presumably trying to find enough space. The kldload process is unkillable from userland because it's working in the kernel. Can something be done to guard against this? From what I was told you can't kldload acpi after boot or that you shouldn't. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildkernel failure
I have been trying to cvsup since yesterday to get this fixed, so it appears to still be broken, anyone else seeing this? anding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-p rototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /us r/src/sys/dev/pcic/i82365.c /usr/src/sys/dev/pcic/i82365.c: In function `pcic_event_thread': /usr/src/sys/dev/pcic/i82365.c:566: `DETACH_FORCE' undeclared (first use in this function) /usr/src/sys/dev/pcic/i82365.c:566: (Each undeclared identifier is reported only once /usr/src/sys/dev/pcic/i82365.c:566: for each function it appears in.) /usr/src/sys/dev/pcic/i82365.c: In function `pcic_intr_socket': /usr/src/sys/dev/pcic/i82365.c:673: `DETACH_FORCE' undeclared (first use in this function) /usr/src/sys/dev/pcic/i82365.c: In function `pcic_detach_card': /usr/src/sys/dev/pcic/i82365.c:728: too many arguments to function `CARD_DETACH_ CARD' *** Error code 1 Stop in /usr/src/sys/modules/pcic. *** Error code 1 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate lock
searching archive yields this thread. 'Subject: /usr/src/sys/netinet/udp_usrreq.c:290' looks like I'm not the only one seeing this. This happens on my test machine directly after samba starts ... Can you disable samba from starting just to make sure it isn't the cause? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why is my -current system Hard Locking?
... don't think this is related to the X FP problem ( although I am running X11 ). There have been many times when I'd walk in the ... options DDB #Enable the kernel debugger ... Its likley you are panic'ing in X, and the system is waiting at the ddb prompt. But you can't see it or do anything, since X has control of the graphics and kbd, so it looks like the machine is frozen. Try adding options DDB_UNATTENDED to your config. Or just do sysctl debug.debugger_on_panic=0 I can't seem to find the beginning of this thread, but I think I may be seeing the same problem. Whenever I try to close X I get a blank screen, but I can ssh in from another machine. I can even run startx from ssh and it brings up X on the console again. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Recent panics in -current
On Fri, Nov 01, 2002 at 08:40:00PM -0600, David W. Chapman Jr. wrote: getting this. Does anyone have any clues. It usually happens during periods of high cpu and disk activity, like make -j25 buildworld. and how many gigs of ram do you have? 1 gig of registered ECC And since memory has something to do with it, let me add that this is a tyan K7 and I have ECC Scrub turned on in the bios. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Recent panics in -current
And since memory has something to do with it, let me add that this is a tyan K7 and I have ECC Scrub turned on in the bios. odds are your running out of memory, i also have a tyan thunder k7 w/ dual 1.2ghz procs with 1 gig of registered ecc, but ive never pushed more than a -j8 I don't believe I am, after building for a while I was able to use 99% of the 1gig, but around 450MB was inactive. This doesn't just occur during make buildworld, sometimes it is just compiling regular programs like kde3. What is your ECC setting in the bios or do you have it turned on? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Recent panics in -current
I recently came across a dual MP 2000 and installed a snapshot of 10/29, then did a few buildworlds to check out the speed. I then upgraded to -current as of day and various times of today and started getting this. Does anyone have any clues. It usually happens during periods of high cpu and disk activity, like make -j25 buildworld. Does anyone have any clue what is going on here? Let me know if I need to provide any more details(which I am sure I do). panic: vrele:negative ref cnt cpuid=0;lapic.id=0100 Debugger(panic) stopped at Debugger+0x4e: xchgl %ebx,in_debugger.0 Timecounter i8254 frequency 1193182 Hz CPU: AMD Athlon(tm) MP 2000+ (1659.27-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM OV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1073676288 (1048512K bytes) avail memory = 1036312576 (1012024K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040010, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic from dd to ATA disk
2050949120 bytes transferred in 198.151980 secs (10350384 bytes/sec) ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. ad0: removed from configuration While I don't remember if my panic was the same, the above message is what I have been seeing recently as well in times of high disk activity. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Request: remove ssh1 fallback
Check the mailing list archives around 4.3-RELEASE, when it was discovered that /etc/pam.conf didn't get ssh lines added to it on upgrades, and people were getting locked out of boxes left and right (predates other entries). Changing behaviour on an upgrade, without the user's consent, is a bad thing (note: *consent*, not *knowledge*: it's not up to the user to know about everything some programmer has diddled into non-operability in the two years since FreeBSD 5.x was branched). Isn't that what UPDATING is for and wouldn't between 4.x and 5.x be better than 5.x and 5.x+n? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New 5.0 ports uploaded
Hmm, I've more broken ports on my system.. Like a trouble with net/samba-devel (because of PAM headers) and I can't compile lang/librep since KSE III. Are you still having problems with this. If you could show me some errors I may be able to relay them to the samba developers for you unless this is something wrong with freebsd. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where to get -current pkgs?
bento should have them but I dont' know how up to date it is. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Old port recompiles needed (Re: Unknown symbol __sF)
On Sun, Oct 13, 2002 at 11:29:32PM -0400, Carl Schmidt wrote: On Mon, Oct 14, 2002 at 11:43:20AM +0900, Makoto Matsushita wrote: tlambert2 That's 3.4 hours saved on a 28.8K modem download time, tlambert2 overall... a 14% reduction in size. The percentage doesn't matter. If ISO image is compressed, user who downloads the image may de-compress that image to burn (I don't know any about the burner softwares which support compressed ISO image). What's happen if there is no space to make de-compressed image on a HDD? I do not follow this. If the user can not fit a non-compressed image on their drive then they certainly will not be downloading a non- compressed image nor a compressed image hence rendering this whole discussion moot for that user...it seems so to me at least. Maybe I am not seeing something? The temporary space required to do the decompression is what I am assuming is being reference, although I'm not sure how accurate that argument is. Whether we think the size is too large for dial-up or not people will still download it. And 200MB is absolutely nothing compared to what people put up with for full-size distribution ISOs. You could argue that not everyone has gzip (I would assume primarily a Windows user). As far as I know there is a DOS version of gzip. This would be where you might need both types of images (compressed and not compressed), and that is something up to the snapshots people. Winzip supports tar and gz, winrar supports bzip2 One might argue that Mr. Lambert is simply speculating that anyone has a 28.8k connection anymore. What are the odds that everyone fits this: a: they live close enough to a provider to get broadband (see 'b'), I did not think distance was a requirement for cable modem, but I do agree with your logic that not everyone has broadband. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 10:11:56PM -0400, Carl Schmidt wrote: cheerleading There seems to be many complaints of things being broken. Maybe I'm just lucky and never cvsup when things are broken. I have encountered -no- errors over the past month when building world and kernel. So anyway to add to that I'd just like to report on today's build so as to balance things out. After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine. No war stories to speak of. I've not had any problems either and I usually build once or twice a week. Now if only my laptop would stop overheating whenever I run FreeBSD on it. Does the fan not turn on? Are you using acpi? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: installworld broken
Strange, I just did a make buildworld ... mergermaster sequence and I did not need the three utilities you mention. Why is that strange? You're talking about everything up to but not including installworld. Warner's talking about installworld. :-) Sigh. I said 'make buildworld ... mergemaster sequence'. I assume people running -current would understand the use of ... and the word sequence to mean Some build just do buildworld to make sure it compiles not needing to install it. Just for clarification in the future, saying make world sequence will get your exact point across as well as saying make kernel instead of make buildkernel -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: internal compiler error with gcc 3.2
On Mon, Sep 02, 2002 at 09:01:31AM -0700, Steve Kargl wrote: On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote: To test gcc 3.2, I've been updating all of my installed ports. It appears gcc 3.2 is having problems with libiconv-1.8_1. cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\ -march=athlon -c ./iconv.c -fPIC -DPIC -o .libs/iconv.lo ^ This appears to be the cause of the problem. If I comment out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles without a problem. Yes, seems to be any CPUTYPE as far as I can tell -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2.1-pre imported
On Sun, Sep 01, 2002 at 05:58:46PM -0400, Alexander Kabaev wrote: GCC 3.2.1-pre is now in the tree. Please let me know if you see any problems recompiling your world/kernel. I have completed a world and kernel, just upgrading all my ports with portupgrade -a -f now, we'll see how that goes. Remember to recompile your C++ ports. GCC 3.2 is not binary compatible with 3.1. If this works out would it be a good idea to get this new gcc version on the port build clusters for -current so we can get to work on making sure all the ports work with the new compiler? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2.1-pre imported
On Sun, Sep 01, 2002 at 04:46:18PM -0700, Kris Kennaway wrote: On Sun, Sep 01, 2002 at 06:33:05PM -0500, David W. Chapman Jr. wrote: Remember to recompile your C++ ports. GCC 3.2 is not binary compatible with 3.1. If this works out would it be a good idea to get this new gcc version on the port build clusters for -current so we can get to work on making sure all the ports work with the new compiler? I'll be doing a new bento run ASAP. I will look at the logs when its done and see where I can help out. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Of course. And being accused of 'trolling' is also a learning experience. I would have to agree with your sarcasm, seems like there is a big troll hunt and everyone is being accused. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BTX Loader issue with today current
GTX Loader 1.0 BTX Version 0.00 Error: Client format not supported Anyone have any ideas to be able to boot. I'm seeing this as well. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /boot/loader problem
On Fri, Aug 30, 2002 at 11:48:52AM -0700, walt wrote: After make world/kernel yesterday I get this error from the bootloader: BTX version =0.00 (instead of 1.01) Client format not supported. and then it hangs. I have to do a hard reset to reboot at that point. I can still boot with /boot/loader.old which works fine. I see that today's /boot/loader is 10kb smaller(166960) than loader.old(176128). I can't seem to get far enough to pick my /boot/loader -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cbb module build failure
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I@/. ./include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/pccard/../.. /dev/pccard/pccard.c /usr/src/sys/modules/pccard/../../dev/pccard/pccard_cis.c / usr/src/sys/modules/pccard/../../dev/pccard/pccard_cis_quirks.c === cbb @ - /usr/src/sys machine - /usr/src/sys/i386/include make: don't know how to make pccbb.c. Stop *** Error code 2 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pkg_version and no origin found == SEGFAULT
Can someone with a src commit bit please do the honours... Cool, thanks for the quick fix! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pkg_version and no origin found == SEGFAULT
It seems when pkg_version hits an installed port that has no origin found it segfaults. I have found other people to verify that it segfaults for them too. DWhite seems to think that it may be pointer corruption in libc, specifically snprintf, fopen, strlcpy or strncpy Here is the backtrace Program received signal SIGSEGV, Segmentation fault. 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 (gdb) bt #0 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 #1 0x0804a003 in pkg_do (pkg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:169 #2 0x08049bfc in pkg_perform (indexarg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:71 #3 0x08049a45 in main (argc=1, argv=0xbfbffc0c) at /usr/src/usr.sbin/pkg_install/version/main.c:79 #4 0x08049879 in _start () Any help or guidance would be appreciated. It does seem that portupgrade -f the ports that cause this problem fixes it because the origin is created. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pkg_version and no origin found == SEGFAULT
Have you checked your /var/db/pkg/port_name/+CONTENTS files? For some reason some ports on my relatively stale -CURRENT box had these files truncated to zero length, and this caused some package tools (namely pkg_version) to crash. The procedure to read plist simply returns with all plist struct members set to zero without indicating any errors when CONTENTS file is empty, and the pkg_version crashes trying to defererence null 'origin' pointer. This is exactly the problem I'm seeing and would explain why portupgrade -f fixes the problem for the port that causes the segfault. Shouldn't pkg_version handle this a little more gracefully? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: DIskcheckd Problems
I did not create diskcheckd, I just ported it from src/ let me cc some people that may know something more about it. Since then it was running fine for a few months. Then I did an Upgrade of Diskcheckd and FreeBSD on one of the machines. After that, Diskcheckd refused to check one of the 8 disks in the system. Aug 22 10:13:20 diskcheckd[128]: seek failure on /dev/da1: Bad file descriptor I tried a lot to get it up and running again: - remade all devices in /dev - undo the diskcheckd upgrade (diskcheckd-20010823_3 - diskcheckd-20010823) - checked the disk several times for errors - Google didn't help also The disk is fine. I gave up and forgot about it, until it happened to another machine. We got 2 more machines with exactly the same hardware and software setup. On one of the machines diskcheckd is working fine, on the other one it stopped checking the disk-array. Same Message: Aug 22 10:12:45 diskcheckd[130]: seek failure on /dev/twed0: Bad file descriptor This time i even synced /dev and the binarys of both systems, it didn't help either. Is this a known problem? What can i do about it? Both Systems are running on FreeBSD 4.5-RELEASE. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much functionality to the kernel and I always turn this on on every box. I think you are missing his point though. Some people kldload ipl.ko because they don't want to recompile their kernel. IF they recompile it with PFIL_HOOKS might as well do ipfilter at the same time. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
No, ipl.ko is not broken. It depends on pfil(9). Shouldn't we try to make a pfil.ko that ipl.ko depends on then? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: question about ipl.ko
There are a few files with PFIL_HOOKS-dependant #ifdefs, but it is strongly tied with the code. /sys/net/bridge.c /sys/netinet/ip_input.c /sys/netinet/ip_output.c /sys/netinet6/ip6_forward.c /sys/netinet6/ip6_input.c /sys/netinet6/ip6_output.c Darren Reed has some pieces of code on his site, but I did not read it. ftp://coombs.anu.edu.au/pub/net/ip-filter/pfil-1.26.tar.gz According to pfil(9) manual --- BUGS The current pfil implementation will need changes to suit a threaded ker- nel model. --- May be this is the reason not to make it default. I'm sure there is probably some reason, but if we can make it a kld, there shouldn't be a reason we can't make ipl.ko depend on it. I do not do much coding so I don't know if its even possible to do it as a kld -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: lockmgr: draining against myself
On Thu, Apr 18, 2002 at 11:25:10AM +0900, Jun Kuriyama wrote: This is today's kernel. Should I test with -DDEBUG_LOCKS? I'm seeing this again panic: lockmgr: draining against myself syncing disks... panic: bwrite: buffer is not busy??? Uptime: 22m5s I was doing a buildworld to produce this. David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NEWCARD support for Linksys Ethernet broken?
On Thu, Jul 18, 2002 at 08:52:43AM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Ian Dowse [EMAIL PROTECTED] writes: : I think the ed problem is that without pccardd, the 0x8 flag : is no longer being passed to the driver, so it doesn't try probing : it as a Linksys card (I haven't checked for sure, but that would : be consistent with it being detected as an NE2000). That may be true. I thought I had flags in the table of ne2000 pcmcia cards... Hey, this sounds like it could be my problem as well. If anyone has any patches, I would gladly test them. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mozilla port?
On Thu, Jul 11, 2002 at 08:35:27PM +0200, Martin Faxer wrote: On Thu, Jul 11, 2002 at 10:58:01AM -0700, Seth Hettich wrote: Is this building for anyone? I always get: gmake[1]: Leaving directory `/u1/src/ports/www/mozilla/work/mozilla' /usr/bin/sed -e s;@PREFIX@;/usr/X11R6;g /u1/src/ports/www/mozilla/files/mozilla.sh /u1/src/ports/www/mozilla/work/mozilla/mozilla (cd /u1/src/ports/www/mozilla/work/mozilla/dist/bin; /usr/bin/env LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regxpcom; echo skin,install,select,classic/1.0 chrome/installed-chrome.txt; echo locale,install,select,en-US chrome/installed-chrome.txt; /usr/bin/env LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regchrome) [1] 32857 Segmentation fault (core dumped) *** Error code 139 Joe Marcus Clarke ([EMAIL PROTECTED]) posted a message earlier today containing a patch that fixes this. Perhaps you should read the list a little bit more closely. :) You also could install compat4x and install the mozilla package compiled for 4.6-STABLE until the patch is committed. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org
On Sun, Jul 07, 2002 at 11:28:30PM -0400, Chuck Robey wrote: is that machine dead? Is it still the source of current snaps? I need to re-install (having booting problems between old version of FreeBSD and new one, easiest fix is just to re-install) and I want to know where to go for a snap of current. Anyone got one? Have you tried the jp site? It should be on the list of the ftp sites from sysinstall. Last I checked you could ftp install via ftp from the jp site that hosted the latest snaps. Nope. I checked ftp,ftp2, and ftp3.jp.freebsd.org, and the best they had was a copy of the old 5.0DP1 release. That's months old now, I don't want to install that unless I must. try snapshots.jp.freebsd.org That's the site I meant! :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: current.freebsd.org
On Sun, Jul 07, 2002 at 11:28:30PM -0400, Chuck Robey wrote: is that machine dead? Is it still the source of current snaps? I need to re-install (having booting problems between old version of FreeBSD and new one, easiest fix is just to re-install) and I want to know where to go for a snap of current. Anyone got one? Have you tried the jp site? It should be on the list of the ftp sites from sysinstall. Last I checked you could ftp install via ftp from the jp site that hosted the latest snaps. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl in make world
On Fri, Jul 05, 2002 at 11:29:30AM +0100, Mark Murray wrote: I think we should add a target to make world that checks for the existence of an old base install of Perl and removes it if it exists. I agree that we may need a tool to do this, but I don't agree that it gets done automatically by make world. Could we also make this tool mv /usr/include /usr/include.old so that it could be run before an installworld? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [OT] ACPI based support for suspend to disk?
On Thu, Jun 20, 2002 at 08:37:35PM +0200, Fischer, Oliver wrote: Hello, is there a upcomming feature similar to W2K's ability to suspend the current state of the machine to a disk and to restore it from there? I believe it already exists, it just depends on your bios as to whether you need a fat partition or if you can use UFS. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More X breakage in XFree86-4-Servers ...
Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src. *** Error code 1 I'm getting this as well. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ESS sound card support on laptop
I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) Wel I look forward to this if it fixes my sound and linksys card :) -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
We write it. It isn't in the BIOS anymore. Usually with ACPI. Now that msmith left, do we have any acpi gurus? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. I'm not sure I understand if you're referring to me. I haven't blamed MS or even mentioned MS. If I understand warner correctly, it can be solved by working on ACPI. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 05:07:53PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : We write it. It isn't in the BIOS anymore. Usually with ACPI. : Now that msmith left, do we have any acpi gurus? There are many japanese that are expert at this. I had plans on taking up at least some familiarity with the ACPI code because it directly impacts a usable cardbus subsystem. The rumor I heard is that their english isn't that good so that I might not be able to communicate with them, english being the only language I know. I would be glad to contact them if this isn't the case, but Im not sure exactly who they are. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More X breakage in XFree86-4-Servers ...
Has anyone actually submitted a bug report to GCC yet? I don't believe so. I'm not sure exactly what is broken or the circumstances that cause the problem. My lack of c knowledge is preventing me from saying much more than X-Servers won't build. Would you be willing to help me figure out what is going on so I can file a proper report or were you offering to file it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI errors on laptop running latest -current
When I boot up my gateway solo 2550, I get the following errors ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR I've attached my dmesg. I also think there is a problem with acpi detecting the battery properly. IF anyone has any ideas I'd appreciate it. hw.acpi.acline: 0 hw.acpi.battery.life: 0 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Wed Jun 12 22:44:45 CDT 2002 root@:/usr/obj/usr/src/sys/DWCJR Preloaded elf kernel /boot/kernel/kernel at 0xc03e9000. Preloaded elf module /boot/kernel/usb.ko at 0xc03e90a8. Preloaded elf module /boot/kernel/random.ko at 0xc03e9150. Preloaded elf module /boot/kernel/sysvmsg.ko at 0xc03e91fc. Preloaded elf module /boot/kernel/sysvsem.ko at 0xc03e92a8. Preloaded elf module /boot/kernel/snp.ko at 0xc03e9354. Preloaded elf module /boot/kernel/acpi.ko at 0xc03e93fc. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 647189041 Hz CPU: Pentium III/Pentium III Xeon/Celeron (647.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 167706624 (163776K bytes) avail memory = 158613504 (154896K bytes) Pentium Pro MTRR support enabled Using $PIR table, 15 entries at 0xc00fded0 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0x1000-0x100f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller irq 5 at device 7.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 pci0: bridge, PCI-unknown at device 7.3 (no driver attached) pccbb0: TI1225 PCI-CardBus Bridge irq 10 at device 10.0 on pci0 cardbus0: CardBus bus on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1225 PCI-CardBus Bridge irq 10 at device 10.1 on pci0 cardbus1: CardBus bus on pccbb1 pccard1: 16-bit PCCard bus on pccbb1 pci0: multimedia, audio at device 14.0 (no driver attached) pci0: simple comms at device 16.0 (no driver attached) acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_button0: Sleep Button on acpi0 acpi_ec0: embedded controller port 0x66,0x62 on acpi0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 pmtimer0 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled
PCMCIA 32-bit Cardbus Network Card
I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to work on -stable or 5.0DP1 The error I get is kernel: pcic1: Card type 32-bit cardbus is unsupported. Luckily I have a linksys laying around somewhere, but has anyone tried to get this card to work under FreeBSD? --- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCMCIA 32-bit Cardbus Network Card
On Wed, Jun 12, 2002 at 07:24:49PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to : work on -stable or 5.0DP1 : : The error I get is kernel: pcic1: Card type 32-bit cardbus is : unsupported. Luckily I have a linksys laying around somewhere, but : has anyone tried to get this card to work under FreeBSD? You need to run a NEWCARD kernel. I got it working pretty good with NEWCARD. The network card seems to hang sometimes and I lose connection. What's the best way to debug this when it happens, I think it may be a conflict with acpi, so I currently have it disabled. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current as guest of VMWare2
I'm running windows XP and vmware 3.1.1 with a guest os of FreeBSD 4.5 which I'm going to upgrade to -current. I couldn't find too much info on this thread. Does anyone know if vmware3 is affected by this problem when using a windows host os? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FW: Re: Error with post 1.1 release Postfix and Cyrus -Possible Bug in VM system
Do we have anyone working on the VM system that could look at this? - Forwarded message from Wietse Venema [EMAIL PROTECTED] - Date: Thu, 30 May 2002 12:49:10 -0400 (EDT) Reply-To: Postfix users [EMAIL PROTECTED] From: [EMAIL PROTECTED] (Wietse Venema) To: Postfix users [EMAIL PROTECTED] Subject: Re: Error with post 1.1 release Postfix and Cyrus X-Mailer: ELM [version 2.4ME+ PL82 (25)] Sender: [EMAIL PROTECTED] You're somehow still running qmgr code that speaks the protocol from before 20020514. To find the file, # find / \( -name qmgr -o -name nqmgr \) -ls But you may not find this file. After upgrading Postfix I very, very, occasionally find that FreeBSD will execute a new process from an old file that was just replaced. Postfix always installs executables by using mv newfile oldfile. At this time, the old file may still be executing, and the parent process is always executing (the Postfix master daemon). I suspect an obscure VM system bug. postfix reload does not seem to cure this condition. The problem goes away after postfix stop then postfix start, which terminates the parent process. This has happened to me only twice over the past year. My server and workstations run FreeBSD versions 4.1 - 4.4. I haven't found the time and energy to debug this. Wietse - To unsubscribe, send mail to [EMAIL PROTECTED] with content (not subject): unsubscribe postfix-users - End forwarded message - -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gdb breaks world
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote: At Wed, 22 May 2002 18:54:02 + (UTC), David O'Brien wrote: -ggdb means to use the most expressive debugging format the compiler knows about. You want -gstabs+ or -gstabs I cannot debug a kernel with -gstabs+ option. Any hints about this? % cd sys/i386/compile/WATERBLUE % grep gdb ../../conf/WATERBLUE makeoptions DEBUG=-gstabs+ #Build kernel with gdb(1) debug symbols % sudo gdb52 (gdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (gdb) exec-file kernel (gdb) core-file /var/crash/vmcore.4 /var/crash/vmcore.4 is not a core dump: File format not recognized Last time I checked, gdb was broken in -current and people were encouraged to use gdb in the ports system, but this may be oudated. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld broken
On Wed, May 22, 2002 at 05:21:59PM +0200, Martin Kacerovsky wrote: Hi, I've got this error during buildworld: Have you read UPDATING and put what it told you to in make.conf? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
On Tue, May 21, 2002 at 10:41:05AM -0700, Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. You are if you run mount it will tell you /dev is devfs you don't need to run MAKEDEV on -currrent as devices are created as you need them. If you're having a problem with a certain device not existing, then you should post that with all details. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /usr/ports/emulators/bochs on -CURRENT
On Thu, May 16, 2002 at 01:14:01PM -0400, Mike Barcroft wrote: Riccardo Torrini [EMAIL PROTECTED] writes: # cd /usr/ports/emulators/bochs make [...] gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include -I.. -I./.. -I../instrument/stubs -I./../instrument/stubs cdrom.cc -o cdrom.o In file included from cdrom.cc:40: /usr/include/arpa/inet.h:102: conflicting types for `typedef __uint32_t socklen_t' ../osdep.h:105: previous declaration as `typedef int socklen_t' gmake[1]: *** [cdrom.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' gmake: *** [iodev/libiodev.a] Error 2 *** Error code 2 The problem appears to be that osdep.h is defining types it should not be defining. Software should include system headers to get new types, not try and out-smart the OS by defining its own (possibly incorrect) types. There is a patch in gnats to fix this error, but it still has errors, pat@ is currently looking at this and I'm building patches for him since I have a -current machine Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
installworld problem with /usr/src/usr.bin/tip/tip
I get the following everytime I make installworld on -current ln: /usr/bin/cu: Operation not permitted *** Error code 1 To fix it I have to modify /usr/src/usr.bin/tip/tip/Makefile and remove the LINKS to cu and then all works well. Is anyone else having this problem? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
On Mon, May 13, 2002 at 02:45:09PM -0600, Lyndon Nerenberg wrote: Jonathan == Jonathan Perkin [EMAIL PROTECTED] writes: Jonathan An auto-configuration script which merely checks for the Jonathan existance of a file rather than actually testing it's the Jonathan file it needs is a bit silly and probably deserves the Jonathan breakage. And just what else besides Perl would you expect to find in /usr/bin/perl you silly pedant?!? ;-) A perl wrapper? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch to add athlon to bsd.cpu.mk
On Sat, May 11, 2002 at 01:35:05PM -0700, David O'Brien wrote:
On Sat, May 11, 2002 at 01:08:35PM -0700, Kris Kennaway wrote:
On Sat, May 11, 2002 at 12:12:16PM -0700, Steven G. Kargl wrote:
-. if ${CPUTYPE} == k7
-_CPUCFLAGS = -march=k6 # gcc doesn't support athlon yet, but it will
+. if ${CPUTYPE} == athlon
+_CPUCFLAGS = -march=athlon
AFAIK the k7 is a valid name for the athlon (marchitecture name).
Don't break backwards compatibility here.
Nope. Athlon(tm) is the correct name, just like there really isn't a
i586. I just posted a patch for review. Being the originator of
bsd.cpu.mk, I hope you review it.
So if I have an athlon-xp do I set CPUTYPE to athlon and it handles
everything for me and selects the correct one or athlon-xp?
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: make.conf and -CURRENT
On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: Hello, Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps something that I have messed up on my end? I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that changes nothing. /usr/src/etc/*/* does not contain said file, the only place it does exist is in /usr/share/examples/etc. sysctl.conf is also missing. If its not there, it doesn't get parsed. You only need make.conf if you wish to put stuff in there. same with rc.conf, except everyone puts something in rc.conf -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make.conf and -CURRENT
On Fri, May 10, 2002 at 05:40:11PM -0500, David W. Chapman Jr. wrote: On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: Hello, Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps something that I have messed up on my end? I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that changes nothing. /usr/src/etc/*/* does not contain said file, the only place it does exist is in /usr/share/examples/etc. sysctl.conf is also missing. If its not there, it doesn't get parsed. You only need make.conf if you wish to put stuff in there. same with rc.conf, except everyone puts something in rc.conf N/m on the sysctl.conf I think that one exists now. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD security hole?
On Thu, Apr 25, 2002 at 02:56:26PM +0600, Vladimir G. Drobyshevsky wrote: Hello all! stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE decided to make a trivial exploit to easily get root :) CW Indeed, see security advisory FreeBSD-SA-02:23.stdio at: CW ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:23.stdio.asc CW Please upgrade to 4.5-p4 or 4-STABLE (April 21 or after). That's really strange - I subscribed to freebsd-security-notifications, but didn't receved that message. Or just readed it by Delete key. ;-) Anyway, thank you for your help. It was on anounce as well for future reference. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
I have cvsuped my source and already made buildworld and buildkernel. But installworld failed with Signal 12 while installing chpass. You're attempting to upgrade incorrectly. Follow the directions _precisely_ and this won't happen. I just got bit by this one myself from not following instructions, for the past 2 weeks you didn't have to, you could just upgrade to 5.0 like tracking -stable. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
No, for the past several months you haven't been able to installworld a -current system under a -stable kernel. That you were ever able to do that before that time is pure chance. Very strange that I did it last week then, possibly a fluke? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-current buildworld breakage?
On Thu, Apr 18, 2002 at 10:29:23AM +0900, Makoto Matsushita wrote: Using 5-current code as of Apr/17/2002 15:00:00 GMT: # pwd /usr/src/gnu/usr.bin/groff/src/preproc/eqn # ident Makefile Makefile: $FreeBSD: src/gnu/usr.bin/groff/src/preproc/eqn/Makefile,v 1.3 2002/04/11 11:06:03 ru Exp $ # make -n neqn make: don't know how to make neqn. Stop # Anybody have seen this? or it's my local problem? Yeah, your make is broken, try rebuilding make by itself and install it then try the buildworld again -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make world stops...
On Sun, Apr 14, 2002 at 07:22:33PM +0200, Jeroen Ruigrok/asmodai wrote: -On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote: make: don't know how to make neqn. Stop *** Error code 2 I think David O`Brien fixed this by backing out a commit to make. In general, wait a couple of hours or a day before reporting a failure, since chances are good it has already been fixed. I got hit by this on a machine that had just been updated from 4.5 to -current and then I went to buildworld again and got the above. At the same time a machine that had been -current for a while didn't get this. I'm going to try to remake make as suggested. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PAM error messages
I'm seeing this a lot on a recent 4.5-STABLE to -current upgrade, is this a problem or something I did wrong? dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current breakage
I'm getting this on a recent machine that has been upgraded from 4.5 to a -current today o over.o text.o script.o mark.o other.o delim.o sqrt.o pile.o special.o /usr/obj /usr/src/i386/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/libs/libgro ff/libgroff.a make: don't know how to make neqn. Stop *** Error code 2 I'm not getting this on a machine that's been running -current for a while. I was able to do one buildworld from 4.5-STABLE to -current, but after that I keep getting this? Let me know if anyone else has seen this. About 2 hours after I started seeing this, I removed /usr/src and cvsup'd and I still get it. Any ideas? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA errors on recent -current
I updated to -current today and am now getting these errors ad0: READ command timeout tag=1 serv=1 - resetting ata0: resetting devices .. ad0: invalidating queued requests done -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ntfs causing kernel panic
Has anyone seen mounting an NTFS drive casing a kernel panic? I'd love to give the output, but I'm not sure how to redirect the output into a file so I can post it here. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntfs causing kernel panic
On Tue, Mar 26, 2002 at 10:08:20AM +1030, Greg 'groggy' Lehey wrote: On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote: Has anyone seen mounting an NTFS drive casing a kernel panic? I'd love to give the output, but I'm not sure how to redirect the output into a file so I can post it here. You need to take a dump and analyse it. There's some stuff in the handbook about how to do it. Unfortunately it has been fixed, but I am still planning on looking at the handbook, thanks! -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntfs causing kernel panic
It could be this problem is a result of the loadable VFS module bug hacked/fixed in the tree this morning. Was the NTFS driver being loaded as a module, or compiled into the kernel? If a loadable module, could you try compiling it into the kernel, or updating past the fix? If already compiled in, follow the directions grog pointed at to generate useful debugging output. Ideally, a copy of the full panic message, stack trace, and information on what kernel options you linked with so that the symbol offsets are useful. The recent vfs fix has fixed it, but thanks for the tips on what information to provide. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I'm able to compile kdelibs now, no problem as well as QT, but when I run configure on kdebase it locks my system up. I can switch terminals but that's it. It locks up on configure when detecting QT(I believe line 5612). The first time it did this I decided that was because I need to rebuild QT, so I did that, but it still locks up. Is anyone else seeing this with a very recent -current? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: I've uploaded a new set of packages to ftp-master for -current on i386; they should be picked up by the mirrors shortly. As I mentioned in a previous mail, there were compilation problems which caused a number of ports to fail, including qt2 and gnomelibs, meaning there were no KDE or GNOME packages built (hey, at least it's a symmetric failure!). QT built fine for me with a -current as of yesterday night, and so does kdelibs, but as I posted earlier kdebase locks up the system on configure, but I believe this is known as the (Subject: Keyboard (quasi-)lockup running script) or sounds similar. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
As discussed at BSDCon, the release engineers are committed to releasing a relatively stable snapshot of FreeBSD -CURRENT on or around April 1, 2002. Obviously, a lot of major components are still in progress, but a great deal of work has already been accomplished, and could benefit from the additional exposure that a polished snapshot with full package set and documentation will provide. I don't know if this is something worth making it the snapshot, but currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. Hmm. My impression was that the libpng stuff had been fixed, could you confirm that KDE still doesn't build on 5.0-CURRENT? Its not related to libpng, I believe that has been fixed, but I cannot tell for sure because kde cannot be compiled under -current. I'm not the only one that is experiencing it either, here is what I was told by Alan Eldridge [EMAIL PROTECTED] On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote: When I try to build kdelibs2 I get the following under recent -current builds ,.deps/kextsock.pp -c kextsock.cpp -fPIC -DPIC -o .libs/kextsock.o kextsock.cpp: In method `struct kde_addrinfo * KExtendedSocketLookup::results()' : kextsock.cpp:294: implicit declaration of function `int __htons(...)' kextsock.cpp:353: implicit declaration of function `int __htonl(...)' Yes. Recent changes to netinet/in.h have made it require the inclusion of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, each of these files must #include the other in order to work correctly. As you might guess, this is a less than desirable situation. A #includes B and B #includes A is a very bad arrangement. However, unless both files are overhauled, that is what will have to happen. To say that this sucks is an understatement. I already have an open PR on the arpa/inet.h problem. Now that the reverse dependency has been made to occur, I have written portmgr@ requesting a referral to a mainline developer who can handle this mess in an expedient manner. In the meantime, you need to find every occurence of either of those files being included, and make sure the other is included as well. netinet/in.h needs to come first. Since the problem is a large one, and any change will not happen without a reasonable amount of deliberation, I suggest you submit a PR with a patch for kdelibs source tree. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. If you're referring to the problems loading libpng.so (and probably other shared libraries), I can confirm that it's been fixed now. I was curious about that, but it wasn't my main concern. Have you been able to run anything that uses OBJPRELINK? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, Mar 08, 2002 at 11:20:35AM -0500, Will Andrews wrote: On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote: currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. Hmm. My impression was that the libpng stuff had been fixed, could you confirm that KDE still doesn't build on 5.0-CURRENT? Its not related to libpng, I believe that has been fixed, but I cannot tell for sure because kde cannot be compiled under -current. I'm not the only one that is experiencing it either, here is what I was told by Alan Eldridge [EMAIL PROTECTED] You said binutils upgrade broke KDE -- the quoted mail has nothing to do with binutils. I'm sorry for the lack of clarity in my email, if I didn't explain it the way I wanted to here is a better attempt. I cannot recompile kde due to the reasons stated in the quoted email so I'm not sure if the binutils problem has been fixed, but apparently a few people can vouch that it has. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I'm surprised that everyone hasn't complained about world breakage from this. It has been broken for almost 2 weeks now. Everything that goes near ntohl and has WARNS = 2 fails to compile. Without WARNS, the bug is reported as above, but a bogus version of __hton* is found in the library and only optimization of hton* is broken. Very strange, I have been making world over the past few weeks (just did one yesterday) with no problems, maybe I have some stuff that it stale? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
Hmm. This should be non-fatal in any event, but which header does it include to get it's htons() and htonl() prototypes? netinet/in.h, arpa/inet.h, or sys/param.h? Yes. Recent changes to netinet/in.h have made it require the inclusion of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, each of these files must #include the other in order to work correctly. From reading all the posts, I believe the solution has been to manually modify the kde port to do this. This is almost completely bogus. I recently saw a PR of similar bogusness. This was most likely quoted from the same person who submitted the pr you read. I'm not sure how I can help you because I'm not a programmer, but I'd be happy to boot into -current and give you any information you need if there is actually a problem(I don't totally understand what it is at the moment). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
Maybe not. I think missing prototypes might be fatal in C++. If this is the case, my new endian patch will fix this. Try compiling KDE after installing a world with the following patch applied: http://people.FreeBSD.org/~mike/patches/endian-ng3.diff I plan on committing this on Sunday. I don't know if its related to this patch, but I get this when I buildworld now cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -c /usr/src/bin/ed/sub.c cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -c /usr/src/bin/ed/undo.c gzip -cn /usr/src/bin/ed/ed.1 ed.1.gz cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -static -o ed buf.o cbc.o glbl .o io.o main.o re.o sub.o undo.o -lcipher cbc.o: In function `get_keyword': cbc.o(.text+0x17d): undefined reference to `getpass' *** Error code 1 1 error *** Error code 2 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I don't know if its related to this patch, but I get this when I buildworld now I just did a complete buildworld + installworld with no trouble, and I then added the above patch and did another complete buildworld + installworld. I had no problems with either build. Applying the above patch got rid of about 81 warning messages in the buildworld process, and another 9 from buildkernel. Applying the patch causes no new warning messages (for me, with my kernel options, make options, on i386, etc etc). I wonder what's broken, I did a buildworld twice with the same result, I'll try to cvsup tomorrow and see if its fixed, maybe I caught it between commits. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: DHCP 3.0.1RC6 imported
On Tue, Feb 19, 2002 at 07:07:24AM -0800, Murray Stokely wrote: DHCP 3.0.1 RC6 has been imported into -CURRENT. DHCP 3.x provides DHCP failover support, dynamic DNS updates, and much more. http://www.isc.org/products/DHCP/dhcp-prerelease.html I've been pushing for this for a while on irc, I'm glad its getting imported. Thanks -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FW: Re: windbindd
It's actually not that hard to write a libdlopen that mmap's exectuable the ld.so itself, and then does manual lookup of the dl entry points, providing symbols for them which are actually externed functions wrapping dereferenced function pointers. It's just that no one has bothered to do the work, yet, for FreeBSD (other OSs have it). That sounds great, maybe I can trick someone into doing it so that we can have winbindd support for samba. I don't know if this is the only obsticle, but I belive its the biggest one that's being faced. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FW: Re: windbindd
Is there any way to impliment dl_open in our nsswitch for -current so that samba's winbindd can work on FreeBSD? - Forwarded message from Richard Sharpe [EMAIL PROTECTED] - Date: Wed, 13 Feb 2002 11:29:24 +1030 Reply-To: [EMAIL PROTECTED] From: Richard Sharpe [EMAIL PROTECTED] To: David W. Chapman Jr. [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], SAMBA TECH List [EMAIL PROTECTED] Subject: Re: windbindd User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205 David W. Chapman Jr. wrote: On Wed, Feb 13, 2002 at 10:48:09AM +1030, Richard Sharpe wrote: David W. Chapman Jr. wrote: Is there any reason winbindd is not supported on FreeBSD? I'm just curious of the hold ups, maybe I can get things rolling from the FreeBSD team if there is anything we need to do? This is an interesting question. Here at Panasas we have rolled our own support by communicating directly using TCP. The issue, when I last looked at it, was a good nsswitch implementation. I would be interested in keeping across this issue. Well FreeBSD-STABLE (4.x) doesn't have nsswitch, but FreeBSD-current (5.x) does. That may be part of the problem. That was the first problem I encountered ... I suspect that, barring some screwed up tests in configure, it will work. I guess I should update my repository and check out FreeBSD-current and see. I would appreciate it if you could let me know what you find. As the maintainer of the FreeBSD samba port I have received a few requests about this. Hmmm, having had a brief look at what I think is FreeBSD-current, it seems that the nsswitch implementation does not use dl_open to pick up shared libs so that it can be extended ... :-( This is a crucial piece of functionality for winbindd, it seems. -- Richard Sharpe, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba - End forwarded message - -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Binutils fixed in -current?
Does anyone know if the problem with kde and other programs not working with the new binutils not working have been fixed yet? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mergemaster niggle
The real question here is: why is the RCSid changing when the file isn't? Sometimes things get changed and then backed out to their original state, but you cannot keep the original RCSID To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mergemaster niggle
Diffs like there show up for COUNTLESS times in mergemaster. In fact, nothing changed except the cvs id. Why am I asked about these in mergemaster? Is there a way to ignore files that only have the cvsid changed? This would speed up the mergemaster run considerably... mergemaster only checks to see if RCSID's are different by default, I forget which option, but there is one to actually diff the two files when doing its inital compare, but the RCSID's would be different so I'm not sure it would help you. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mergemaster niggle
The real question here is: why is the RCSid changing when the file isn't? Sometimes things get changed and then backed out to their original state, but you cannot keep the original RCSID To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mergemaster niggle
I can see that happening on the head, but this also happens on stable ... One example of it happening to -stable was the addittion of www to master.passwd, www has been added and removed a few times from -stable. I'm not trying to say that this explains all the times that it happens, just that it happens more than you might think. I think we need to keep track of the RCSID's of the new and old files that exhibit this problem to better be able to keep track of it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mergemaster niggle
What I think mergemaster should do is compere the file with the original checked out one it claims to be and if it's the same, it should just update silently.. i.e. if the user didn't change anything in th old one he's unlikely to want to change anything in the new one (maybe a datafile that contains cksum outputs for each version of each file) I think part of the problem(from what I'm hearing on irc), someone made a lot of commits to etc which weren't supposed to happen, but I cannot confirm all the facts at the moment. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Binutils fixed in -current?
Does anyone know if the problem with kde and other programs not working with the new binutils not working have been fixed yet? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Pam problems today
On Fri, Feb 01, 2002 at 06:25:21AM -0800, Edwin Culp wrote: David, Thanks for posting this. I have built a new world and kernel but haven't run mergemaster, yet. I did see the problem just waiting in /usr/src/etc/rc.d so I think I'll just leave it there for the time being. Thanks again for the advance notice. If you cvsup now, it should be fixed, it was a missing Makefile. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Recent -Current KDE problems
I'm seeing this on a -current as of yesterday and as of today. I just finished a make world and kernel a few mins ago as well as rebuilding all my ports, but kde still dies when I try to load it, last night before I tried to rebuild all the ports I was getting signal 11's. Any ideas anyone? list! Bus error - core dumped Feb 1 09:03:19 dwcjr kernel: pid 88809 (ksplash), uid 1000: exited on signal 10 (core dumped) Bus error - core dumped Bus error - core dumped Feb 1 09:03:20 dwcjr kernel: pid 88810 (kdeinit), uid 1000: exited on signal 10 (core dumped) Feb 1 09:03:20 dwcjr kernel: pid 88811 (ksmserver), uid 1000: exited on signal 10 (core dumped) connect() failed: : No such file or directory -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Login failures ...
On Fri, Feb 01, 2002 at 03:06:17PM -0800, Bokyung Wang wrote: Hello, I faced Login Fail problem when I upgrade to FreeBSD 5.0 Current. Error messages are login: PAM unable to dlopen(/usr/lib/pam_login_access.so) login: PAM[dlerror: Cannot open /usr/lib/pam_login+access.so] login: PAM adding faulty moule: /usr/log/pam_login_access.so Does anybody know how to solve it? I posted a quick solution earlier today/last night on -current, should be easy to find since there hasn't been much traffic since I posted it. if you cvsup and make world it should fix it now. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Pam problems today
I cvsuped a few hours ago, did the normal buildworld and installworld, new kernel and mergemaster, but when I rebooted I could not login, I had to comment a few lines in /etc/pam.d/login #accountrequiredpam_login_access.so #accountrequiredpam_securetty.so #sessionrequiredpam_lastlog.so are the lines I had to comment out. I checked and I don't have pam_login_access.so. I know that there have been a bunch of changes recently, so if this is a known problem I apologize. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Pam problems today
Same thing happened to me yesterday after a make install world and mergemaster. Took awhile to figure out. Building and installing libpam does not install pam_login_access.so Manfred I'm glad I'm not alone. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
