Version Number Only Changes
I am sure there is a reason for it. Upon running mergemaster this time through it seemed like there were _a lot_ of files where the only change was the version number. I have run to mergemaster on four more hosts. Ugh! mergemaster -aiU still seems to require a ton of interaction. Is there a better way? Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Heimdal Breakage
After installing 6.4-RELEASE on my secondary KDC I decided to test the secondary KDC. When trying kinit I get this error: j...@w17 ~ $ kinit j...@stradamotorsports.com's Password: kinit: krb5_get_init_creds: Key size is incompatible with encryption type One post on the net says that Heimdal changed the key format to add some padding or somesuch. I haven't gone about fixing the problem yet so maybe that post is not applicable to FreeBSD. Just the same I thought I would let folks know that their key databases are probably not forward compatible with 6.4-RELEASE. This would be a pretty big deal for some users. It would be nice to see this in UPDATING. Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Blacklisted ACPI Prevents Boot
I just installed a 6.4-PRERELEASE kernel and tried to boot. The boot failed with a message that my ACPI was blacklisted. I have had 'device acpi' in my kernel for some time now. The boot interruption is new behavior. Is this sort of change a good thing to put in UPDATING? Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Old Libraries After 6.4 Upgrade
I noticed that a bunch of libraries lib*_p.a and lib*.a were not updated with my latest installworld. I do not disabled compilation of profiled libaries. Can these be safely deleted? Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld fails immediately
Ruslan Ermilov wrote: Make sure /dev/null inside a jail is a device and not a plain file. If the latter, you probably forgot to mount devfs onto a jail's /dev. Groovy! Thanks. Later, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
CPUTYPE Now Required?
While trying to build RELENG_6 I receive this error: make: fatal errors encountered -- cannot continue /usr/src/Makefile.inc1, line 142: warning: MAKEFLAGS= CPUTYPE=pentium /usr/obj/usr/src/make.i386/make -f /dev/null -m /usr/src/share/mk -V CPUTYPE returned non-zero status /usr/src/Makefile.inc1, line 144: CPUTYPE global should be set with ?=. I've never set CPUTYPE in the past. I don't want specific CPU optimizations as I am building for multiple generations of processor. What is a person to do? Later, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld fails immediately
I am trying to build RELENG_6. I receive the following errors. [EMAIL PROTECTED] /usr/src]# make buildworld /dev/null, line 4: Need an operator /dev/null, line 6: Need an operator /dev/null, line 8: Need an operator /dev/null, line 9: Need an operator /dev/null, line 11: Need an operator /dev/null, line 12: Need an operator /dev/null, line 13: Need an operator /dev/null, line 15: Need an operator /dev/null, line 16: Need an operator /dev/null, line 18: Need an operator I figured I got a partial update or something. Re-supping didn't help. I am building on 6.2-RELEASE inside a jail. Jails are new for me so maybe I missed something there. Any ideas? Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Installworld deletes libc
I have the problem similar to one described in 20071024 UPDATING. The build is running inside a jail. The system is 6.2-RELEASE. I supped this moring. I have the correct lib/Makefile. During installworld I receive an error: install: /lib/libc.so.6: chflags: Operation not permitted *** Error code 71 Stop in /usr/src/lib/libc. My situation is different in the libc is erased in the process. Copying the new libc.so.6 from /usr/obj does not fix the problem. Any ideas? Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installworld deletes libc
Jeremy Chadwick wrote: On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote: I have the problem similar to one described in 20071024 UPDATING. The build is running inside a jail. The system is 6.2-RELEASE. I supped this moring. I have the correct lib/Makefile. During installworld I receive an error: install: /lib/libc.so.6: chflags: Operation not permitted *** Error code 71 Stop in /usr/src/lib/libc. My situation is different in the libc is erased in the process. Copying the new libc.so.6 from /usr/obj does not fix the problem. Any ideas? Sounds like kern.securelevel is in the way. See security(7). The securelevel would normally prevent the deletion of a file. The secure level of this jail is -1 in any case so the schg flag should be ignored. security.jail.chflags_allowed=0 seems to supersede the securelevel according to sysctl(8). Some part of installworld is misbehaving in the jail. The security mechanisms in securelevel and security.jail.chflags_allowed are not working. Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installworld deletes libc
Jason C. Wells wrote: Jeremy Chadwick wrote: On Sun, Sep 21, 2008 at 11:17:58AM -0700, Jason C. Wells wrote: I have the problem similar to one described in 20071024 UPDATING. The build is running inside a jail. The system is 6.2-RELEASE. I supped this moring. I have the correct lib/Makefile. During installworld I receive an error: install: /lib/libc.so.6: chflags: Operation not permitted *** Error code 71 Stop in /usr/src/lib/libc. My situation is different in the libc is erased in the process. Copying the new libc.so.6 from /usr/obj does not fix the problem. Any ideas? Sounds like kern.securelevel is in the way. See security(7). The securelevel would normally prevent the deletion of a file. The secure level of this jail is -1 in any case so the schg flag should be ignored. security.jail.chflags_allowed=0 seems to supersede the securelevel according to sysctl(8). Some part of installworld is misbehaving in the jail. The security mechanisms in securelevel and security.jail.chflags_allowed are not working. I should add that 'systcl security.jail.chflags_allowed=1' allowed installworld to proceed without error. That solves my immediate problem. There appears to be a bug in the security mechanism. Later, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Install -S Not Safe was: Re: Installworld deletes libc
Jason C. Wells wrote: Jason C. Wells wrote: I should add that 'systcl security.jail.chflags_allowed=1' allowed installworld to proceed without error. That solves my immediate problem. There appears to be a bug in the security mechanism. The reason there appeared to be a bug in the security mechanism is that I performed (IIRC) chflags -noschg on libc as root on the host system outside the jail. But for some reason 'install -S' was not safe. (outside the jail) ~$ chflags noschg /usr/jails/cr/lib/libc.so.6 (inside the jail) [EMAIL PROTECTED] /usr/src/lib/libc]# ls -lao /lib/libc.so.6 -rwxr-xr-x 1 root wheel - 981331 Sep 21 15:57 /lib/libc.so.6 [EMAIL PROTECTED] /usr/src/lib/libc]# sysctl -a | grep secur kern.securelevel: -1 security.jail.chflags_allowed: 0 [EMAIL PROTECTED] /usr/src/lib/libc]# make install install -C -o root -g wheel -m 444 libc.a /usr/lib install -C -o root -g wheel -m 444 libc_p.a /usr/lib install -s -o root -g wheel -m 444 -fschg -S libc.so.6 /lib install: /lib/libc.so.6: chflags: Operation not permitted *** Error code 71 Stop in /usr/src/lib/libc. [EMAIL PROTECTED] /usr/src/lib/libc]# ls -lao /lib/libc.so.6 /libexec/ld-elf.so.1: Shared object libc.so.6 not found, required by ls [EMAIL PROTECTED] /usr/src/lib/libc]# Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 Stable and the CP2101 driver
Dennis Flynn wrote: That doesn't seem right to me. Shouldn't I see something like 7.0-RELEASE-p1 or 7.0-STABLE? Did I do something wrong in my update to RELEASE? How do I know if I'm running the STABLE kernel with the driver I want? How can I tell if the driver (uslcom) is there and/or loaded? To tell if a driver is loaded: dmesg | grep uslcom You'll also want to know about kldstat(1). I've never used freebsd-update. I do suspect that the standard MO in FreeBSD land is to _not_ update the kernel unless explicitly requested. You might want to snoop around the docs with that in mind. Also, FreeBSD may support your driver, but not build it into the GENERIC kernel by default. If the driver you want does not appear in the GENERIC kernel, then you will have to compile a kernel or load a kernel module. There is good documentation on building a kernel in the handbook. Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Release Schedule 7.1
What are the hoped for release dates for 7.1? (plus or minus a month) I'm debating on running 7.0 vs 7.1 and timing is a consideration. Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Scheduler in Various Docs
The comments regarding SCHED_ULE and SCHED_4BSD are inconsistent with information found in the email archives. LINT says ULE is experimental. The handbook doesn't mention ULE at all. The archives say ULE is the new recommended scheduler. If ULE is in fact the current recommendation, then a few docs need to be updated. Regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading FreeBSD Questions
Jason Slack wrote: I want to try version 7 as it has items of interest to me, but I am not one to continually wipe and reload my machine, can you upgrade from the test releases of 7 available now to the final release when ready? Or do you have to wipe? You can easily upgrade from 7.0-BETA to 7.0-RELEASE without erasing your drive. Historically, FreeBSD has always been upgradeable even through major releases, 4 to 5, 5 to 6. Sometimes that has been more painful than others. Upgrading within a major release, 6.1 to 6.2, has always been pretty easy. Later, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
-mfpmath=sse?
I am reading this document: http://gcc.gnu.org/onlinedocs/gcc-3.4.4/gcc/i386-and-x86_002d64-Options.html Does |-march=|pentium3 imply |-mfpmath=sse?| Thanks, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiler Options
O. Hartmann wrote: Daniel O'Connor wrote: On Saturday 11 November 2006 08:54, Jeremy Chadwick wrote: The kernel itself _will not_ use any SSE or MMX operations when built. This is because these optimisations are known to break the FreeBSD kernel. This applies to all i386 architectures, and probably 64-bit architectures too (not sure). I think this is mainly because the kernel has no FPU context so you can't actually use any FPU operation (including SSE MMX) without potentially trashing userland data. This is a good question to ask why. Still a relict from FreeBSDs BSD4.4 legacy root? Also, the cost of saving/restoring the context is quite high so potential benefits are largely negated. Well, this is often subject of lectures even at universities today and even it is so, modern hardware design should be aware of those disadvantages. Ans this leads to the question whether this is in FreeBSD so because it is really still a disadvantage (what I do not believe, even on i386 hardware) or it is said to be so due to nobody has taken care about that. As I remember myself, modern Linux kernels use MMX/SSE registers even for purposes of getting an advantage in speed. Peter Wemm once had this to say about that. http://lists.freebsd.org/pipermail/freebsd-amd64/2005-February/003663.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Compiler Options
I have set CPUTYPE=p3 in make.conf. When I compile my kernel I see -march=pentium3 as I expect. I also see -mno-mmx and -mno-sse are set which I do not expect given that -march=pentium3 is used. I presume that I want MMX and SSE since my processor supports it. What options do I set and where do I set them to get a kernel properly tuned for pentium3? Thanks, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Make World Fails on Man Pages
Mark Andrews wrote: From unlink(2). [ENOTDIR] A component of the path prefix is not a directory. I suppose that is why rm is not working. The question was Why don't some man pages install? I think I have found the problem. Somewhere along the way a DOCSUPFILE make variable and separate doc-supfile came into existence. I never learned this so my doc sources were out of date. That gave me errors that caused me to set NO_SHARE which resulted in groff macros not being installed which resulted man page weirdness. This answer to myself for posterity. Later, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Make World Fails on Man Pages
Here is a snippet of my failed installworld logs as I move to 6.0R: install -o root -g wheel -m 444 crypt.3.gz /usr/share/man/man3 /usr/share/man/man3/crypt_get_format.3.gz - /usr/share/man/man3/crypt.3.gz rm: /usr/share/man/man3/crypt_get_format.3: Not a directory rm: /usr/share/man/man3/crypt_get_format.3.gz: Not a directory I get the same error from a couple other man pages (e.g. bwrite) if I run make from the directory where the pages source exists. Not all man pages cause an error, just some. I tried removing /usr/obj for a fresh build since this was a former 5.4R box. Cvsup isn't fetching any new sources so I must be up to date. Any ideas why some man pages won't install? Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Network Over Backplane PCI Bus
Is there a way to run TCP/IP with the PCI bus as a network interface? I am installing FreeBSD on CompactPCI processor boards. It would be really slick if I could network the boards via the PCI backplane. Thanks, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6 kernel panic
While compiling bash for my new 6.0-BETA2 system, I received this error: ad4: detached panic: vm_fault I don't have a dump for you and I really must be going to work now. More later if I can get myself trained up on crash dumps. Later, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6 acd0: semaphore timeout
I upgraded to 6.0_BETA2 yesterday. Today I built a new kernel. While the booting, the following error is displayed. acd0: SETFEATURES SET TRANSFER MODE semaphore timout !! DANGER Will Robinson !! I recompiled the kernel without atapicd and the kernel boots fine. At some later time, that kernel panics. I will write that up in another message. Later, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Outdated lib*_p.a files
I run a homegrown script after upgrades to find outdated binaries. I have a bunch of files name /usr/lib/lib*_p.a that predate my recent upgrade to 5.4-RELEASE. What are these? Can they be deleted without harm? Thanks, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: loader.conf examples
--On Sunday, January 23, 2005 7:22 AM -0500 Matt Herzog [EMAIL PROTECTED] wrote: I'm confused about how and why modules are built and (seemingly loaded without my having specified any to load) when I have not told my kernel conf file to build anything as a module. As a former NetBSD user, I had expected a monolitic kernel . . . You can still run a monolithic kernel as I do. You can also use NO_MODULES as a make option to prevent the build and installation of modules. See also MODULES_OVERRIDE is /sys/conf/NOTES. If you never specified a module to load, then no modules should be loaded. (Ref kldstat) Maybe the default behavior has changed. I wouldn't know though since I don't use the default behavior. There are two ways to build a kernel. There is 'make buildkernel' and there is 'config KERNEL; make depend; make' Take care which options apply to which method. Later, Jason C. Wells ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd v4.2 problem
--On Tuesday, November 23, 2004 6:38 PM -0500 Harlan Stenn [EMAIL PROTECTED] wrote: In 4.1, notrust means do not trust this host/subnet for time. In 4.2, notrust means require crypto auth before believing this host/subnet for time. I have been trying on and off for some time now to figure why my server was tagged as reachable but rejected. I read all manner of stuff about how some clocks are bad for arcane protocol reasons. Now, purely by accident, I discover that the behavior of notrust has changed and that was the source of my problem. Grvy! Thanks! Later, Jason C. Wells ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Termcap Makefile Doesn't Honor DESTDIR
The makefile in /usr/src/share/termcap doesn't honor DESTDIR. Should it? Later, Jason C. Wells ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (hardware?) trouble with make buildworld on 4.5
On Tue, 2 Apr 2002, Alex Edelman wrote: My current theory on the failure places blame on the CPU; I think, it is either busted (I broke it) or it is not supported by FreeBSD. The hardware is a Shuttle SV24 (those cute mini-systems everybody raves about) and the CPU is a Via C3 866 (Ezra core or later.) I have a friend who has the same system and a slightly older/slower Via C3 (Samuel core). He upgraded to 4.5-STABLE last night without any problems. I am not sure about VIA chips. Here is the relevant snippet from his dmesg output: CPU: VIA C3 Samuel 2 (751.71-MHz 686-class CPU) Origin = CentaurHauls Id = 0x671 Stepping = 1 Features=0x803035FPU,DE,TSC,MSR,MTRR,PGE,MMX ...Here is mine, note the unrecognized CPU: CPU: IDT Unknown (864.47-MHz 686-class CPU) Origin = CentaurHauls Id = 0x678 Stepping = 8 Features=0x803035FPU,DE,TSC,MSR,MTRR,PGE,MMX Here are the last 50 lines of two separate make buildworld attempts. The few lines leading up to the 'Stop' line usually tell the needed information. Here are the last 50 lines of two separate make buildworld attempts. Both of which were done last night, after deleting all of /usr/src and /usr/obj, and grabbing fresh from cvsup7.freebsd.org. Thanks in advance for any guidance you can provide. Deleting /usr/src is not useful. Cvsup will correct a not up to date source tree. Deleting /usr/obj is accomplishes by a 'make clean' as part of a normal 'make buildworld'. 'make world' includes the make targets of 'make buildworld' and 'make installworld'. Let's look. /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c -o lib_refresh.o /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c: In function `wnoutrefresh': /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:73: syntax error before character 0323 Syntax errors here. ^^^ /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: `limit_x' undeclared (first use in this function) /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: (Each undeclared identifier is reported only once /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: for each function it appears in.) *** Error code 1 /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: `limit_x' undeclared (first use in this function) /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: (Each undeclared identifier is reported only once /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/base/lib_refresh.c:129: for each function it appears in.) *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 And also... cc -O -pipe -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -c /usr/src/lib/msun/src/k_standard.c -o k_standard.o /usr/src/lib/msun/src/k_standard.c: In function `__kernel_standard': /usr/src/lib/msun/src/k_standard.c:322: syntax error before character 0240 *** Error code 1 Stop in /usr/src/lib/msun. *** Error code 1 This says syntax error too. ^^^ I don't know why you are getting syntax errors. My guess is you supped at an inopportune moment. I would sup again and 'make buildworld'. Like I said, I don't know about VIA chips and how well they are supported. One commonly sees errors like 'kernel panic, signal 11' when there is a faulty hardware problem. If you have a custom kernel, make sure it has support for the 686 class CPU. This is shown in your dmesg output. My answers is based on an empirical guess. I think a new sup might work. It has almost always worked for me when I get a syntax error of some sort. Also, when your build fails on a certain file in a certain directory, you can change to that directory and often do a 'make clean' 'make' in that specific directory. If I get a buildworld failure, I will re-sup and do the above to see if my problem cleared up before I spend all that time waiting for 'make world' to work its way into the problematic directory. Also, if I can't figure it out, my post to -stable would have a subject like make world dies in ./libexec/telnetd. This way if a commiter just MFCed a change to telnetd, she can spot your error message quickly and investigate. These are just a couple tips to round out your self proclaimed lack of experience. HTH! Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: installworld failure
On Wed, 3 Apr 2002, Bryan Berch wrote: Alex wrote: On Wed, 3 Apr 2002, Bryan Berch wrote: I am getting the same error messages when doing make installworld, but I have the right lines in /etc/master.passwd and /etc/group from previous mergemaster. Is there something else I should try? Try deleting the entries and then use pw to put them back. Worked for me. I tried deleting the entries and using pw to put them back in, but get told that they already exist. Then I tried using pw to delete them and it tells me they do not exist. Is there another way to get the system to recognize the smmsp and mailnull? Did you use 'vipw' to edit your passwd databases? You must use 'vipw' to edit the passwd database to be sure that the shadow passwd database is updated. If not, there is also something like 'pw_mkdb' to update your databases. Later, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Ports updating... Good ways?
One way to make it easy to keep ports updated is to only cvsup the ports you need. Then you build from the top. Cvsup has pattern matching so the following code doesn't need version number suffixes. You will end up with the latest versions. I did this. #!/bin/gross_pseudocode $suplist=portpattern_1 \ portpattern_2 \ Mk and friends \ portpattern_3; cvsup $suplist cd /usr/ports make install I deleted the script some time ago. The method worked pretty well. The only problem is when a particular port added a new dependency (KDE was bad for this). The code above is gross, but the idea worked. The cool part was the all of the installing and building went pretty well. If you put your script ona floppy, then you can rebuild all of the /usr/local stuff on some other machine and come up with a near mirror. Thank you, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
PCI Modems Not Shown As Supported Hardware
I just got done chatting with Warner Losh about PCI modems. He is "pretty sure" that his PCI modem driver made its way into -stable and 4.1.1-R. The supported hardware docs and release notes do not list PCI modems as supported. (Unless I am blind in which case I will toddle along quietly, bumping into things as I go.) If someone can confirm this information then it should be in the proper docs. I will submit a PR to amend the appropriate docs. Thank you, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /stand/sysinstall cannot find any disks ?
On Tue, 15 Aug 2000, Jordan K. Hubbard wrote: Or, far better, it should be reinvented as a proper mechanism which is more conducive to updating. Everything about sysinstall and /stand right now basically sucks and needs to be shot rather than documented. :) Can you name that book? Perhaps we should rename sysinstall to Lenny. :) "A man ought not let another man shoot his dog." And another quote which I will never forget. It is not surprising that sysinstall is facing extinction after I heard this. "Caldera's installer eats my balls." I couldn't resist. I was much surprised that this particular persona actually typed these words, he being of generally austere, urbane and composed manner. A nickel for the person who guesses the author of the second quote. :) Thank you, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Warner's PCI Modem Driver
On Wed, 26 Jan 2000, Warner Losh wrote: In message [EMAIL PROTECTED] "Jason C. Wells" writes: : sio0: Generic communications device, maybe winmodem rev 0x08 int a irq : 9 on pci0.18.0 : sio2: pci sio unit 0 moved to sio2 at 0x6100 : sio2: pci unit 0 probe failed : : I am told that the modem is not a winmodem, but I don't know how to tell : by looking at it. The modem is a Phoebe. The documentation for it is : sparse. You may be being lied to, imho. :-) The probe failed means that it was unable to talk to it even as a 8250. So it turns out. My friend turned me on to a linux site that list the braindead modems. Mine was on the list. The guy at the shop said, "That's stragne. I have a policy against carrying win-modems. Apparently, there was some lack of indication that it was a winmodem. He then assumed it wasnt a winmodem. : It would seem to me that my device is configured except that pesky : "probe failed" message. Is my PCI modem working? What am I missing? : Should I move my sio device numbers around so that the PCI modem doesn't : get moved to sio2? No. That the modem likely isn't a pci controller based modem. No. The pci code does that on its own and will always do that. How much did you pay for this board? If it is $80 then you likely have a winmodem. Or at least a controllerless modem. Also, what chipset does it use? Conexant R56D/fooPCI Relax. You've done nothing wrong. I have seen Jordan climb in a couple people shorts with a hot poker on a couple occasions. When I get a good connection I'll be back! Thank you Mr. Losh, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Warner's PCI Modem Driver
On Wed, 26 Jan 2000, Alan Edmonds wrote: "Forrest W. Christian" wrote: [deleted] Geez. Life would be much easier if people would just say "Compatible with most Unix-based operating systems on the PC" on the box. Risking getting off topic, I saw a (I believe it was a USR) modem that did say "Linux compatible" on it. It's a start. I also despise winmodem. Some seem to require MMX extensions also. A couple people have mentioned USR. I may take a look at them. Thanks, Jason C. Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
world dies in doc/psd/19.curses
=== share/doc/psd/19.curses^M /usr/libexec/vfontedpr /usr/src/share/doc/psd/19.curses/../../../../lib/libcurse s/PSD.doc/ex1.c | grep -v "^'wh" ex1.gr^M no entry for language c^M *** Error code 1 I have been having this trouble lately. I pulled down a whole new source tree last night. It is probably something misconfigured. Any ideas how I can fix this? Thank You, | http://students.washington.edu/jcwells/ Jason Wells To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
