Re: Why no CDR ioctls for SCSI cds?
In message [EMAIL PROTECTED] Mike Meyer writes: : Do you claim ownership of all the drivers in cam/scsi, or can someone : with more tolerant religious convictions add a driver that's a clone : of the CD driver + MMC extensions that gets first crack at CDROM : drives, and recognizes MMC drives, but not others? Ken wrote the cd driver as well as large parts of CAM. Chances are good that what you are calling religious convictions were actually hard fought engineering decisions that have the backing of hard experience plus many more "details" that Ken might not recall off the top of his head but that lead to his views. Having said this, if you can come up with a foolproof way to get the ioctls right on all the drives that do support them, even the whacked out ones that need all kinds of quirky entries, and do it in a way that doesn't needlessly bloat the kernel for little gain (few people, in the scheme of things, have cd-r or cd-rw on their machines and use them to burn disks), then he might reconsider his views. However, much of your posts have had an "airchair quarterback" feel to them and unless and until you have working code, nobody's opinions are going to change. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
On Mon, Aug 21, 2000 at 10:50:11PM -0500, Mike Meyer wrote: Christopher Masto writes: I'd rather see cdrecord work on ATAPI CD-Rs. burncd gives me a lot of trouble. As cdrecord isn't part of FreeBSD, this is clearly the wrong place to ask about that. Joe Schilling watches [EMAIL PROTECTED], and that's the place to ask. I've been told that ATAPI CD-Rs use the same basic command set (MMC) as SCSI ones, only they don't have legacy problems - so it should be possible. Actually, that's why this would be the appropriate place. cdrecord is designed to do that sort of thing - it separates out the driver interface and has several already, including support for Linux's "ATAPI over SCSI". It just doesn't work with FreeBSD because our ATAPI driver doesn't make available the low-level communication it needs. But whatever. I've personally decided to give up on it and get a SCSI CD-R at some point. I'm just confused by the desire to avoid cdrecord, since in my experience, it has worked great. It also has a lot of nifty options. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
Warner Losh writes: Having said this, if you can come up with a foolproof way to get the ioctls right on all the drives that do support them, even the whacked out ones that need all kinds of quirky entries, and do it in a way that doesn't needlessly bloat the kernel for little gain (few people, in the scheme of things, have cd-r or cd-rw on their machines and use them to burn disks), then he might reconsider his views. However, much of your posts have had an "airchair quarterback" feel to them and unless and until you have working code, nobody's opinions are going to change. You may well be right, and there are good technical reasons for not doing this. The only real reason that's been presented for not doing MMC is that all the non-MMC drives might cause a support headache. There are sound technical reasons for *not* doing non-MMC drives, and Ken and I agree on that. If the answer from the person who would have to approve the code had come back "Ok, provide the code and we'll see how well it works in practice", I'd do the code. But when it appears the code would never make it into the tree to be used, why waste my time? mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound support in -CURRENT
From: Ruslan Ermilov [EMAIL PROTECTED] Date: Mon, 21 Aug 2000 13:04:46 +0300 :: Hi FreeBSD fans and developers... :: :: This is my first question in -CURRENT. :: :: Yesterday was the first time I tried to follow the -STABLE line. And I must :: admit that once again FreeBSD amazed me ;) :: :: Running -STABLE rite now (I used to run only -RELEASE before cause I'm :: haunted by the feeling that the upgrading process will be very complicated, :: but that's my mistake... The upgrading process was really simple and easy... :: ;) ) :: :: Now to the real question... :: I have a Compaq Deskpro EP system with onboard Intel 810e AGP VGA Card and :: onboard sound support (which maybe is AC97 or something similar). After :: running -STABLE I can use my VGA Card. How about the sound card? Does :: - -CURRENT support the sound card? Cause if -CURRENT can make my sound card :: sings, I'd love to give it a try. After all, this isn't a production :: machine. :: ::Not yet. Dan Moschuk [EMAIL PROTECTED] is working (?) on the driver. There seems to be some work done in Japan. I'm not sure if it works for 810e, but try: http://www.katsurajima.seya.yokohama.jp/ich/ich.c.gz The HomePage is in Japanese, so you have to guess what you have to do. :-) Hope this helps, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
If the answer from the person who would have to approve the code had come back "Ok, provide the code and we'll see how well it works in practice", I'd do the code. But when it appears the code would never make it into the tree to be used, why waste my time? 'coz we're taking a page from Linus. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
In message [EMAIL PROTECTED] Mike Meyer writes: : You may well be right, and there are good technical reasons for not : doing this. The only real reason that's been presented for not doing : MMC is that all the non-MMC drives might cause a support : headache. There are sound technical reasons for *not* doing non-MMC : drives, and Ken and I agree on that. Actually, the real reason is that MMC drives that mostly support the standard, but do it wrong in ways that are hard to detect. Those are going to be the worst to try to support. There are some drives out there that just hang when you issue them certain MMC commands, as an example. They shouldn't but they do and you have to be careful not to send them these commands. : If the answer from the person who would have to approve the code had : come back "Ok, provide the code and we'll see how well it works in : practice", I'd do the code. But when it appears the code would never : make it into the tree to be used, why waste my time? I think that you overstate ken's reluctance. If you can come up with a good way to deal with this and have a good error mechanism for those drives that don't support this then I think he might (and I repeat might) be talked into it. I've found Ken quite accepting of code in the past when I've gone to the trouble of doing something. I've found in the past that working code has a way of making people reconsider their opinions of things. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
Matthew Jacob writes: If the answer from the person who would have to approve the code had come back "Ok, provide the code and we'll see how well it works in practice", I'd do the code. But when it appears the code would never make it into the tree to be used, why waste my time? 'coz we're taking a page from Linus. Does Linus tell people something is a bad idea, and then use it anyway? Or does he just not bother to respond to questions about whether or not something would be a usefull addition? mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Q: encrypted swap
Hi, Last week I was at USENIX where Niels Provos talked about his implementation of encrypted swap in OpenBSD. What is does is encrypting all memory that gets swapped out, keeping the encryption keys in memory. A test showed that all kinds of interesting things wind up in the swap partition; Niels himself found several passwords and his PGP passphrase on his own laptop.. So, I think having the option to use encrypted swap on FreeBSD would be nice. Is anybody already working on this? If not, how do I get somebody to work on it? ;-) Cheers, Walter. -- Walter Belgers "Si hoc signum legere potes, operis boni in rebus [EMAIL PROTECTED] Latinis alacribus et fructuosis potiri potes!" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Question from a neophyte... Why isn't rc.local being read?
Make sure it's not commented out in rc # Run rc.devfs if readable to customize devfs # if [ -r /etc/rc.devfs ]; then sh /etc/rc.devfs fi # Do traditional (but rather obsolete) rc.local file if it exists. If you # use this file and want to make it programmatic, source /etc/defaults/rc.conf # in /etc/rc.local and add your custom variables to /etc/rc.conf, as # shown below. Please do not put local extensions into /etc/rc itself. # Use /etc/rc.local # # rc.local # if [ -r /etc/defaults/rc.conf ]; then # . /etc/defaults/rc.conf # source_rc_confs # elif [ -r /etc/rc.conf ]; then # . /etc/rc.conf # fi # # ... additional startup conditionals ... # rc.local # if [ -r /etc/rc.local ]; then echo -n 'starting local daemons:' sh /etc/rc.local echo '.' fi On 21-Aug-00 Gordon Zeigler wrote: I've added startup commands to /etc/rc.local on my 3.4 Stable machine. /usr/local/etc/webmin/start # Start webmin /usr/local/sbin/sshd# Start open ssh /etc/init.d/apachectl start # Start apache web server Yet, these are not starting at reboot... What am I missing? Probably something obvious, but it escapes me... *** REPLY SEPARATOR *** On 8/21/00 at 9:53 AM Julian Elischer wrote: since config has changed.. where do I set the flags on my debug port (sio2?) the sio man page has no hints.. it looks to me as it if is now controlled differently unles I've made a mistake julian 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 -- Unix Software Developer/Engineer E-Mail: Johan Kruger [EMAIL PROTECTED] Date: 22-Aug-00 Time: 12:38:46 All good things come to those who ... runs FreeBSD -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: error sysinstall
Probably need a newer sysinstall, now uses character devices Where did you get this sysinstall from, is in on a boot floppy ? If it is, then either the kernel with it's devices doesn't work with the sysinstall you use, or the devices do not exist. On your PC, do a make depend ; make ; make install in /usr/src/release/sysinstall then you use the sysinstall in the installed dir /stand/sysinstall Remember to remake your devices - char devices probably needed. -- Unix Software Developer/Engineer E-Mail: Johan Kruger [EMAIL PROTECTED] Date: 22-Aug-00 Time: 12:43:29 All good things come to those who ... runs FreeBSD -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Dear Sirs, JOINT VENTURE OPPORTUNITY INFOPAC Software (India) is interested in a business relationship with your company in the area of ERP / software projects and solutions: Our capability profile includes: Software projects (offshore / onshore development) ERP development Internet, e-commerce based development Manpower services Wet lease / incubation service for projects We are visiting your country shortly and would like to meet you to discuss the opportunity further. We are a 55 people company specializing in ERP and E Commerce. Please do visit our web site www.infopac-erp.com Looking forward to hearing from you, Yours Sincerely, for INFOPAC SOFTWARE LTD Ms.Bhagya Nair Intl. Business Division Infopac Software Limited, No.67, Rustam Bagh, Bangalore-560017, India, Ph:+91-80-5250767/5255461 Fax:+91-80-5262180, E mail: [EMAIL PROTECTED]
Realplayer and Yamaha 740C on current
Hi ... I have a 5.0-current .. kernel compiled of a day or so ago. When I'm using Realplayer7 or plaympeg (package smpeg) to play real audio or mpegs I just get this load "hissing" noise. When I use mpg123 to play a mp3 the sound is OK .. CD sound works fine and games too. Any idea why realaudio (even when playing a local file) and plaympeg seems to corrupt the sound ?? Somehow I recall that this used to work .. but I can't confirm it :) Thanx Reinier ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 22-Aug-00 Time: 15:16:54 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
On Mon, Aug 21, 2000 at 11:59:26PM -0500, Mike Meyer wrote: I'm curious - are there any committers who regularly use a system with LOCALBASE set to something other than /usr/local? I have LOCALBASE=/opt for a couple of years now. OTOH, I also have a symlink from /usr/local - /opt due to a small but significant number of ports that are not PREFIX clean. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Review requested for /dev/random driver improvements!
Hi All Please could those of you with the time and computrons available please review the patches for the entropy (/dev/random) driver at http://people.freebsd.org/~markm/randomdev.patch. NOTES: This code may injure your cat, your computer and/or your bank account; be careful! The code puts the responsibility of reseeding the entropy state variables into a kernel thread; this should make userland a lot snappier. There is a FIFO constructed from TAILQ's to buffer the entropy harvesting; this should further insulate userland from the internal workings. All the crypto and hashing has been broken out into a separate file to make the whole driver less dependant on particular algorithms. There is an (unresolved) issue with panics when the module is unloaded; I'm working on that, but if you get to it before me, your help would be appreciated. Not included in here is a direct tap into the random event stream to allow folks who need to "distill bits" to do their own entropy processing. This is being worked on. Other comments, patches and suggestions welcome! Many thanks to Brian Feldman for the kthreads example, and others for answering my questions online! M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Realplayer and Yamaha 740C on current - update
Dit another test ... Used mpg123 with the "-m" option for mono sound (all the thins that "broke" was in mono) and got the same noise ... seems like "mono" sound for the 740C Yamaha is broken ?? Reinier On 22-Aug-00 Reinier Bezuidenhout wrote: Hi ... I have a 5.0-current .. kernel compiled of a day or so ago. When I'm using Realplayer7 or plaympeg (package smpeg) to play real audio or mpegs I just get this load "hissing" noise. When I use mpg123 to play a mp3 the sound is OK .. CD sound works fine and games too. Any idea why realaudio (even when playing a local file) and plaympeg seems to corrupt the sound ?? Somehow I recall that this used to work .. but I can't confirm it :) Thanx Reinier ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 22-Aug-00 Time: 15:16:54 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 22-Aug-00 Time: 16:14:17 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: devfs mkIII test review please.
They can also be made by the driver using make_dev_alias(). Cool! Man page please? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: encrypted swap
So, I think having the option to use encrypted swap on FreeBSD would be nice. Is anybody already working on this? If not, how do I get somebody to work on it? ;-) Ever since the Phoenecians invented money, there has been at least one guaranteed answer to that :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with /usr/bin/awk
Tony, On Mon, Aug 21, 2000 at 07:17:31PM -0700, Tony Fleisher wrote: I have been running cvsup nightly to grab -current and -ports, and noticed some strangeness with awk that seemed to start last week sometime. When building /usr/ports/lang/guile, the build exited with an awk 'internal error' and a log on the console that awk had exited on signal 6. To test my theory that the problem was indeed awk (rather than the guile port), I copied over a copy of awk from a 4.1-R system. After doing so, the guile port was able to build and install without any problems. Interesting. I bumped into the same problem on -current, but also had the problem if I tried using gawk from the ports (d'oh. I've just realised, our awk is GNU awk). You can get around it by installed nawk from lang/nawk first, and then doing "make AWK=nawk" you build it. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Realplayer and Yamaha 740C on current - update
Reinier seems like "mono" sound for the 740C Yamaha is broken ?? I found 'mono' audio was broken on my Yamaha 724F PCI card at the weekend. Cameron said several users have reported this and he has reworked the code in -current to hopefully work around this problem. Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Realplayer and Yamaha 740C on current - update
Roger .. I cvs-ed the sources for the kernel from yesterday .. but I'll get the latest ones now .. I'm just not sure if Cameron has committed the changes yet .. but in any case ... thanx Cameron !! :) Rgds Reinier On 22-Aug-00 Roger Hardiman wrote: Reinier seems like "mono" sound for the 740C Yamaha is broken ?? I found 'mono' audio was broken on my Yamaha 724F PCI card at the weekend. Cameron said several users have reported this and he has reworked the code in -current to hopefully work around this problem. Roger ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 22-Aug-00 Time: 16:42:39 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Realplayer and Yamaha 740C on current - update
Reinier Bezuidenhout wrote: Roger .. I cvs-ed the sources for the kernel from yesterday .. but I'll get the latest ones now .. I'm just not sure if Cameron has committed the changes yet .. but in any case ... thanx Cameron !! :) Cameron changed the 'feeder' code which drives the cards. So, our cards may not work, but he said it is now much easier to work around the problem with the new feeder code. Anyway, we should be able to get this sorted out in the near future. Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone have newmidi working?
-On [2819 18:15], Brian Fundakowski Feldman ([EMAIL PROTECTED]) wrote: Newmidi doesn't seem to work. The oplsbc device handling had to be hacked a bit to support non-PnP SBs, but that's inconsequential. It probes and boots fine. It seems that newmidi is completely disconnected from actually being able to work. Doesn't work here. I could forward you my mail I sent the to the other, mayhaps our problems are quite alike. I haven't gotten any response from the author :-( Does anyone have it working? I don't see how it could with the current state of the code. Same here. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The spirit indeed is willing, but the flesh is weak... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
-On [2822 08:50], Warner Losh ([EMAIL PROTECTED]) wrote: Actually, the real reason is that MMC drives that mostly support the standard, but do it wrong in ways that are hard to detect. Those are going to be the worst to try to support. There are some drives out there that just hang when you issue them certain MMC commands, as an example. They shouldn't but they do and you have to be careful not to send them these commands. This got parsed by me as: mmc-quirk.h It wouldn't be hard to keep it tracked in a quirk file as per the SCSI disk quirk file. But I am not sure it is elegant. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl There is no joy in smallness. Joy is in the infinite... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
-On [2822 06:25], Kenneth D. Merry ([EMAIL PROTECTED]) wrote: It needs an ATAPI passthrough mechanism to work. (FreeBSD doesn't have one at the moment.) Søren, Matt and me were discussing the ATA/CAM issues so that we might be able to approach ATA through CAM. That would clear a lot. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Another morning, black sunday, coming down again... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make buildworld br0ken in libutil
Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. -=-=- === libexec/fingerd cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi ngerd.c cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil /usr/obj/src/src/i386/usr/lib/libutil.so: undefined reference to `crypt_set_form at' *** Error code 1 Stop in /src/src/libexec/fingerd. *** Error code 1 -=-=- -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl I walk, I walk alone, into the promised land... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
According to Jeroen Ruigrok van der Werven: Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. It would make even make more sense to convince the other BSD to do the same (haven't checked recently what they do) and do the merge. -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] The Postman hits! The Postman hits! You have new mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Crash - Build World - Fatal double fault: eip esp ebp
I have searched the mailing lists, to no avail (hope I did not miss the answer). I am getting the following output on make world (FreeBSD 5.0-2820-CURRENT installed, cvsup current source at 11:00AM Eastern Time).. Fatal double fault: eip = 0xc030343c esp = 0xcd025000 ebp = 0xcd025074 panic: double fault syncing disks... 577 577 577 ... I have been having some trouble getting this server up and running with latest code. It's a Dual 600EB running on a Supermicro PIIIDM3 motherboard with 2 128MB PC133 DIMMs (Non-ECC). I am using the on-board U160 SCSI with two 9GB U160 drives.. I am running the R1.5 BIOS for the motherboard.. Any ideas on why I am having trouble or possible suggestions would be much appreciated. Thank you, Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:55], Ollivier Robert ([EMAIL PROTECTED]) wrote: According to Jeroen Ruigrok van der Werven: Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. It would make even make more sense to convince the other BSD to do the same (haven't checked recently what they do) and do the merge. I very much agree. Would it be sensible for the regular cypherpunks to discuss this with the NetBSD and OpenBSD brothers? Otherwise I would be willing to open this discussion on the appropriate lists. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED]VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl The administration of justice is the firmest pillar of government... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: encrypted swap
On Tue, 22 Aug 2000, Walter Belgers wrote: Last week I was at USENIX where Niels Provos talked about his implementation of encrypted swap in OpenBSD. What is does is encrypting all memory that gets swapped out, keeping the encryption keys in memory. A test showed that all kinds of interesting things wind up in the swap partition; Niels himself found several passwords and his PGP passphrase on his own laptop.. So, I think having the option to use encrypted swap on FreeBSD would be nice. Is anybody already working on this? If not, how do I get somebody to work on it? ;-) Walter, There has been discussion and substantial interest in an encrypted swap interface on the freebsd-security mailing list in the last month or so. It was concluded that it was best to wait until Poul-Henning Kemp finished improved infrastructure, allowing the stacking of devices and layers above devices. This would allow an abstracted "encrypted device" interface, supporting everything from encrypted swap (using a randomized key) to generic protected file systems (one key per partition protecting the file system). This would give substantial protection for those of us with mobile computing devices (generally notebooks) that have a tendancy to walk off in airports, for example :-). As an interim solution, I believe we support swap over NFS, so could swap to a local CFS partition. We could also look at solutions that cause swap partitions to be blanked at shutdown, although that's an inferior solution to true encrypted swap, as one tends to trust strong crypto a little more than the ability to delete the contents of magnetic disk platters :-). So the short of it: infrastructure work is under way that should make encrypted swap an easy addition in the near future. Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kernel panic on fxp
I've been working for a while to try to figure out a problem I'm having here. I did a buildworld Sunday, and started to get kernel panics on boot when it probed fxp. So I removed fxp from my kernel and loaded it as a module (via loader.conf.local). It paniced. Then I unloaded the if_fxp.ko on startup, and it booted. But if I load the fxp module now, after a full boot, everything is great. Rebooting with fxp in the kernel or loading the module on boot will cause a panic *every* time. Thinking it might be build problem, I redid the build/install/kernel again on Monday, and am having the same problems. The panics only started on the upgrade from a -current dated sometime in early July. As you will see from below, this is an SMP machine (dual P200) with 256 Megs RAM. I am also using NETGRAPH to run PPPoE. Any ideas? Patrick The panic is: Fatal trap 12: page fault while in kernel mode mp_lock=0005; cpuid = 0; lapic.id= fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc034e304 stack pointer = 0x10:0xc038bea8 frame pointer = 0x10=0xc038bebc code segment= base 0x0, limit 0xf, type 0x1b = DPC 0, pres 1, def 32 1, gran 1 processor eflag = interrupt enabled, resume, IOPC=0 current process = 0 (swapper) interrupt mask = net tty bio cam - SMP:XXX trap number = 12 panic: page fault To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
Jeroen Ruigrok van der Werven wrote: -On [2822 17:55], Ollivier Robert ([EMAIL PROTECTED]) wrote: According to Jeroen Ruigrok van der Werven: Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. It would make even make more sense to convince the other BSD to do the same (haven't checked recently what they do) and do the merge. I very much agree. Would it be sensible for the regular cypherpunks to discuss this with the NetBSD and OpenBSD brothers? Otherwise I would be willing to open this discussion on the appropriate lists. Is there any current policy on what libc is? It certainly isn't "libc" as required by C and hasn't been for almost ever but there needs to be some rational to its existence otherwise why not fold everything into libc and not bother with any other libraries! A growing libc makes static binaries grow and makes it more difficult to strip out unneeded functionality from a minimalist system install. I'd been inclined to try and move things the other way and strip stuff out of libc into separate libraries but that's obviously not in vogue at the moment. Why does crypt need to be in libc? Not even a significant fraction of applications need crypt? Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
On Tue, 22 Aug 2000 17:25:50 +0100, Paul Richards wrote: Is there any current policy on what libc is? For some reason, I seem to remember Bruce Evans once calling it "the kitchen sink". :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. It would make sense. It would make even make more sense to convince the other BSD to do the same (haven't checked recently what they do) and do the merge. I very much agree. Would it be sensible for the regular cypherpunks to discuss this with the NetBSD and OpenBSD brothers? Otherwise I would be willing to open this discussion on the appropriate lists. Is there any current policy on what libc is? It certainly isn't "libc" as required by C and hasn't been for almost ever but there needs to be some rational to its existence otherwise why not fold everything into libc and not bother with any other libraries! A growing libc makes static binaries grow NOT! Static linking *only* brings in those symbols necessary for the file. It doesn't matter where those files are, they are only brought in if necessary. and makes it more difficult to strip out unneeded functionality from a minimalist system install. This is true. I'd been inclined to try and move things the other way and strip stuff out of libc into separate libraries but that's obviously not in vogue at the moment. For what it's worth, I'm in agreement. The 'kitchen sink' approach, although easy tends to make stuff hard to maintain, since you end up with namespace collisions, and you may end up with something you are not aware of that conflicts with routines you are using inside your program. (Think of the recent weak symbol discussion where the library is not using the correct 'global' symbol for read as an example.) Why does crypt need to be in libc? Not even a significant fraction of applications need crypt? Agreed. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. Alternatively the sentiment just rose why we couldn't just collapse the crypt/hash functions of libcrypt into libc. Agreed! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
A growing libc makes static binaries grow and makes it more difficult to strip out unneeded functionality from a minimalist system install. I'd been inclined to try and move things the other way and strip stuff out of libc into separate libraries but that's obviously not in vogue at the moment. Static binaries don't pull in the whole of libc; they just pull in what they need, be it from libc or libcrypt, so size should not change. The _shared_ libc will get bigger, but we'll lose the shared libcrypto. Why does crypt need to be in libc? Not even a significant fraction of applications need crypt? Goes for very many libc components. Quite a lot of userland needs libcrypt (not much as a proportion, but a non-insignificant number). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
On Tue, 22 Aug 2000 17:53:09 +0200, Jeroen Ruigrok van der Werven [EMAIL PROTECTED] said: -On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote: Brian, I'm afraid you broke libutil... Every program using libutil now must depend on libcrypt too. No. This is precisely why shared libraries have dependencies. For static linking, what Brian has done Just Works. For dynamic linking, libutil needs to depend on libcrypt to get its symbols resolved. (Alternatively you might be able to do it with weak symbols.) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Strange messages on -CURRENT
I am seeing these messages on the -CURRENT box as of FreeBSD kanpc.gte.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Aug 14 10:04:38 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/KANPC i386 Aug 22 13:07:40 kanpc /kernel: unexpected vn driver lock: 0xc8010d40: type VREG, usecount 2, writecount 1, refcount 25, flags (VOBJBUF) Aug 22 13:07:40 kanpc /kernel: unexpected vn driver lock: 0xc8010d40: type VREG, usecount 2, writecount 1, refcount 25, flags (VOBJBUF) Aug 22 13:07:40 kanpc /kernel: tag VT_UFS, ino 349296, on dev #ad/0x30005 (116, 196613) lock type inode: EXCL (count 1) by pid 5 Aug 22 13:07:40 kanpc /kernel: tag VT_UFS, ino 349296, on dev #ad/0x30005 (116, 196613) lock type inode: EXCL (count 1) by pid 5 -- E-Mail: Alexander N. Kabaev [EMAIL PROTECTED] Date: 22-Aug-00 Time: 13:09:40 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
One thing that's missing is the ioctl CDRIOCSETBLOCKSIZE. It would be _really_ nice if cd(4) supported that ioctl so I could just seek and read from a CD. I had knu trying out my read_cd program, and it doesn't work for SCSI CD-ROMs, seemingly because of this issue :( Would you be adverse to implementeing that ioctl? -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel panic on fxp
PLEASE read this: http://www.freebsd.org/FAQ/hackers.html#AEN4885 Basically, by just looking at the page fault message, this appears to be the dereferencing of a NULL pointer. That's all that I'm afraid pretty much anybody will be able to conclude from this unless you, at least, provide us with a backtrace as well as an assembly dump of whatever function the crash occured in. On Tue, 22 Aug 2000, Patrick Gardella wrote: I've been working for a while to try to figure out a problem I'm having here. I did a buildworld Sunday, and started to get kernel panics on boot when it probed fxp. So I removed fxp from my kernel and loaded it as a module (via loader.conf.local). It paniced. Then I unloaded the if_fxp.ko on startup, and it booted. But if I load the fxp module now, after a full boot, everything is great. Rebooting with fxp in the kernel or loading the module on boot will cause a panic *every* time. Thinking it might be build problem, I redid the build/install/kernel again on Monday, and am having the same problems. The panics only started on the upgrade from a -current dated sometime in early July. As you will see from below, this is an SMP machine (dual P200) with 256 Megs RAM. I am also using NETGRAPH to run PPPoE. Any ideas? Patrick The panic is: Fatal trap 12: page fault while in kernel mode mp_lock=0005; cpuid = 0; lapic.id= fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc034e304 stack pointer = 0x10:0xc038bea8 frame pointer = 0x10=0xc038bebc code segment= base 0x0, limit 0xf, type 0x1b = DPC 0, pres 1, def 32 1, gran 1 processor eflag = interrupt enabled, resume, IOPC=0 current process = 0 (swapper) interrupt mask = net tty bio cam - SMP:XXX trap number = 12 panic: page fault Cheers, Bosko. -- Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 [EMAIL PROTECTED] * http://www.technokratis.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compaq proliant
On 21 Aug 2000, at 21:04, [EMAIL PROTECTED] wrote: has anyone gotten freebsd (current or other) running on one of these? Which Proliant model are you talking about? i've tried 4.0, 4.1, and -current, and the kernel panics on me with the following: sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources We're running 3.4-STABLE on a Proliant 3000 here, and it's working great. Mind you, this has a Symbios 875 based controller, not 895a as in your case. Proliant 3000 with 4.1-STABLE here, working great too. -- .. David Touitouhttp://dites-le.com SysAdmin and co Solexine To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
On Tue, Aug 22, 2000 at 15:22:05 -0400, Brian Fundakowski Feldman wrote: One thing that's missing is the ioctl CDRIOCSETBLOCKSIZE. It would be _really_ nice if cd(4) supported that ioctl so I could just seek and read from a CD. I had knu trying out my read_cd program, and it doesn't work for SCSI CD-ROMs, seemingly because of this issue :( Would you be adverse to implementeing that ioctl? That's fine. As it turns out, I've had additional discussions with Mike Meyer and Matt Jacob and Mike will probably be implementing MMC CD-R support. That ioctl will probably be a part of it. The functionality you're looking for is part of a larger issue of supporting CDDA reads in the cd(4) driver. That's needed to support AudioFS. (As well as to support doing a straight read off the CD when an audio CD is in there.) The main problem is that different drives use different commands to read audio data. MMC-compliant drives are one case, but there are a lot more drives out there that use varying methods to read audio data. It'll also take some tweaking to get the driver to support blocksizes that aren't multiples of 512 bytes. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld br0ken in libutil
On Tue, 22 Aug 2000, Garrett Wollman wrote:
On Tue, 22 Aug 2000 17:53:09 +0200, Jeroen Ruigrok van der Werven
[EMAIL PROTECTED] said:
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
Brian, I'm afraid you broke libutil... Every program using libutil now must
depend on libcrypt too.
No. This is precisely why shared libraries have dependencies. For
static linking, what Brian has done Just Works. For dynamic linking,
libutil needs to depend on libcrypt to get its symbols resolved.
(Alternatively you might be able to do it with weak symbols.)
Further, I cannot see how the make world _could_ be broken! This is
strange, since I've never had the problem at all and have tested this
change in several places (5.0 and 4.1).
{"/home/green"}$ objdump --all-headers /usr/lib/libutil.so | grep NEEDED
/usr/libexec/elf/objdump: /usr/lib/libutil.so: no symbols
NEEDED libcrypt.so.2
-GAWollman
--
Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! /
[EMAIL PROTECTED]`--'
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: compaq proliant
sym0: 895a port 0x1000=0x10ff mem 0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at device 4.0 on pci1 sym0: failed to allocate RAM resources We're running 3.4-STABLE on a Proliant 3000 here, and it's working great. Mind you, this has a Symbios 875 based controller, not 895a as in your case. Proliant 3000 with 4.1-STABLE here, working great too. it's a ML330. recompiling the kernel without sym support seems to make it boot (i wasnt using the scsi controller anyway). which is an interesting data point, actually: there were no scsi devices plugged into the controller. in any event, im up and running. this may now serve as a data point for whomever is maintaining the sym driver... - j Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
Mark Murray wrote: Hi All Please could those of you with the time and computrons available please review the patches for the entropy (/dev/random) driver at http://people.freebsd.org/~markm/randomdev.patch. I'm getting some errors trying to build this. Attached is my make.log that shows the errors. -Donn linking kernel yarrow.o: In function `random_kthread': yarrow.o(.text+0x36): undefined reference to `yarrow_hash_init' yarrow.o(.text+0xe3): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x103): undefined reference to `yarrow_hash_iterate' yarrow.o: In function `reseed': yarrow.o(.text+0x317): undefined reference to `yarrow_hash_init' yarrow.o(.text+0x334): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x34b): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x37a): undefined reference to `yarrow_hash_init' yarrow.o(.text+0x392): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x3a3): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x3b6): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x3c6): undefined reference to `yarrow_hash_finish' yarrow.o(.text+0x3f5): undefined reference to `yarrow_hash_init' yarrow.o(.text+0x406): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x42c): undefined reference to `yarrow_hash_iterate' yarrow.o(.text+0x449): undefined reference to `yarrow_hash_finish' yarrow.o(.text+0x457): undefined reference to `yarrow_encrypt_init' yarrow.o(.text+0x481): undefined reference to `yarrow_encrypt' yarrow.o: In function `read_random': yarrow.o(.text+0x5d0): undefined reference to `yarrow_encrypt' yarrow.o(.text+0x645): undefined reference to `yarrow_encrypt' yarrow.o: In function `generator_gate': yarrow.o(.text+0x78b): undefined reference to `yarrow_encrypt' yarrow.o(.text+0x7a6): undefined reference to `yarrow_encrypt_init' *** Error code 1 Stop in /usr/src/sys/compile/CUSTOM.
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
On a vaguely related topic, after much searching I can't seem to see one way or the other if we can do a complete bit-by-bit copy of a cd with either cdrecord or burncd, though it's possible I'm looking in the wrong place. Laurence "Kenneth D. Merry" wrote: [snip] -- Laurence Berland Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
error with fetchmail + sendmail
Helo, yesterday i actualiced from FreeBSD 4.1 to FreeBSD 5.0 current. and i am having some problems whith sendmail and fetchmail. the sendmail version is 8.11.0. the problem began whit this file aliases.db because as the sendmail logs said, it wasnt able to see this file at /etc/mail. so i made a new one whit "makehash". but now i have got another problem. when i run fetchmail to get my e-mail it freezes. it happens in the following way: (fetchmail -v) -latest version- fetchmail: 5.4.4 interrogando machine.com (protocolo auto) en Wed, 23 Aug 2000 01:38:54 +0200 (CEST) fetchmail: 5.4.4 interrogando machine.com (protocolo IMAP) en Wed, 23 Aug 2000 01:38:54 +0200 (CEST) fetchmail: 5.4.4 interrogando machine.com (protocolo POP3) en Wed, 23 Aug 2000 01:38:55 +0200 (CEST) fetchmail: POP3 +OK QPOP (version ?) at machine.com starting. [EMAIL PROTECTED] fetchmail: POP3 USER myuser fetchmail: POP3 +OK Password required for myuser. fetchmail: POP3 PASS * fetchmail: POP3 +OK myuser has 1 visible message (0 hidden) in 2267 octets. fetchmail: POP3 STAT fetchmail: POP3 +OK 1 2267 fetchmail: POP3 LAST fetchmail: POP3 +OK 0 is the last read message. 1 mensaje para koji en machine.com (2267 octetos). fetchmail: POP3 LIST fetchmail: POP3 +OK 1 visible messages (2267 octets) fetchmail: POP3 1 2267 fetchmail: POP3 . fetchmail: POP3 TOP 1 fetchmail: POP3 +OK Message follows leyendo mensaje 1 de 1 (2267 octetos) fetchmail: SMTP 220 daemon.org ESMTP Sendmail 8.11.0/8.11.0; Wed, 23 Aug 2000 01:39:00 +0200 (CEST) fetchmail: SMTP EHLO localhost fetchmail: SMTP 250-daemon.org Hello localhost [127.0.0.1], pleased to meet you fetchmail: SMTP 250-ENHANCEDSTATUSCODES fetchmail: SMTP 250-EXPN fetchmail: SMTP 250-VERB fetchmail: SMTP 250-8BITMIME fetchmail: SMTP 250-SIZE fetchmail: SMTP 250-DSN fetchmail: SMTP 250-ONEX fetchmail: SMTP 250-ETRN fetchmail: SMTP 250-XUSR fetchmail: SMTP 250 HELP fetchmail: SMTP MAIL FROM:[EMAIL PROTECTED] SIZE=2267 fetchmail: SMTP 250 2.1.0 [EMAIL PROTECTED]... Sender ok fetchmail: SMTP RCPT TO:user@localhost and then freezes. the error that i get fron sendmail when the "fetchmail" is running is as it follows: Aug 23 01:35:28 daemon sendmail[3980]: e7MNPQG03980: lost input channel from localhost [127.0.0.1] to MTA after rcpt is there somebody who would help me whist this fail? thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
On Tue, Aug 22, 2000 at 20:43:15 -0400, Laurence Berland wrote: On a vaguely related topic, after much searching I can't seem to see one way or the other if we can do a complete bit-by-bit copy of a cd with either cdrecord or burncd, though it's possible I'm looking in the wrong place. I think cdrecord can burn CDs in disk-at-once mode, and I think cdrdao (in ports/audio) can do it as well. As far as getting an image, you can use dd to dump off an image of a CD if it is a standard ISO9660 CD. (I've used that method to clone CDs before.) If it uses a blocksize other than 2048 bytes, though, you can't use dd with the SCSI cd driver. There may be CD rippers that can pull the data off into an image, though. I don't know for sure. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld dies undefined reference to crypt_des
The `building everything' stage of make buildworld is dying as below.
The following patch fix lets my buildworld get beyond that point (but
it's still running so I don't know if there are problems elsewhere).
(I don't think the patch is the right fix, but it solved my immediate
problem).
Index: Makefile
===
RCS file: /home/CVSROOT/src/bin/csh/Makefile,v
retrieving revision 1.20
diff -u -r1.20 Makefile
--- Makefile2000/07/07 08:27:59 1.20
+++ Makefile2000/08/23 01:49:45
@@ -36,8 +36,8 @@
# utilities of the same name are handled with the associated manpage,
# builtin.1 in share/man/man1/.
-DPADD= ${LIBTERMCAP} ${LIBCRYPT}
-LDADD= -ltermcap -lcrypt
+DPADD= ${LIBTERMCAP} ${LIBCRYPT} ${LIBDESCRYPT}
+LDADD= -ltermcap -lcrypt -ldescrypt
LINKS= ${BINDIR}/csh ${BINDIR}/tcsh
cc -O -pipe -I/3.0/cvs/src/bin/csh/../../contrib/tcsh -I/3.0/cvs/src/bin/csh -I.
-D_PATH_TCSHELL='"/usr/obj/3.0/cvs/src/i386/bin/csh"' -Wall -Wformat
-I/usr/obj/3.0/cvs/src/i386/usr/include -c
/3.0/cvs/src/bin/csh/../../contrib/tcsh/tc.who.c
cc -O -pipe -I/3.0/cvs/src/bin/csh/../../contrib/tcsh -I/3.0/cvs/src/bin/csh -I.
-D_PATH_TCSHELL='"/usr/obj/3.0/cvs/src/i386/bin/csh"' -Wall -Wformat
-I/usr/obj/3.0/cvs/src/i386/usr/include -c /3.0/cvs/src/bin/csh/tc.defs.c
cc -O -pipe -I/3.0/cvs/src/bin/csh/../../contrib/tcsh -I/3.0/cvs/src/bin/csh -I.
-D_PATH_TCSHELL='"/usr/obj/3.0/cvs/src/i386/bin/csh"' -Wall -Wformat
-I/usr/obj/3.0/cvs/src/i386/usr/include -static -o csh sh.o sh.dir.o sh.dol.o
sh.err.o sh.exec.o sh.char.o sh.exp.o sh.file.o sh.func.o sh.glob.o sh.hist.o
sh.init.o sh.lex.o sh.misc.o sh.parse.o sh.print.o sh.proc.o sh.sem.o sh.set.o
sh.time.o glob.o mi.termios.o tw.help.o tw.init.o tw.parse.o tw.spell.o tw.comp.o
tw.color.o ed.chared.o ed.defns.o ed.init.o ed.inputl.o ed.refresh.o ed.screen.o
ed.xmap.o ed.term.o tc.alloc.o tc.bind.o tc.const.o tc.disc.o tc.func.o tc.os.o
tc.printf.o tc.prompt.o tc.sched.o tc.sig.o tc.str.o tc.vers.o tc.who.o tc.defs.o
-ltermcap -lcrypt
/usr/obj/3.0/cvs/src/i386/usr/lib/libcrypt.a(crypt.o)(.rodata+0x4): undefined
reference to `crypt_des'
*** Error code 1
Stop in /3.0/cvs/src/bin/csh.
*** Error code 1
Stop in /3.0/cvs/src/bin.
*** Error code 1
Stop in /3.0/cvs/src.
*** Error code 1
Stop in /3.0/cvs/src.
*** Error code 1
Stop in /3.0/cvs/src.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Q: encrypted swap
Mark Murray writes: So, I think having the option to use encrypted swap on FreeBSD would be nice. Is anybody already working on this? If not, how do I get somebody to work on it? ;-) Ever since the Phoenecians invented money, there has been at least one guaranteed answer to that :-) Actually, two. You can *always* work on something yourself! mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why no CDR ioctls for SCSI cds?
Brian Fundakowski Feldman writes: One thing that's missing is the ioctl CDRIOCSETBLOCKSIZE. It would be _really_ nice if cd(4) supported that ioctl so I could just seek and read from a CD. I had knu trying out my read_cd program, and it doesn't work for SCSI CD-ROMs, seemingly because of this issue :( Yup - none of the CDR ioctls (and that's one) are supported by cd. Would you be adverse to implementeing that ioctl? I'm planning on implementing all the CDR ioctls for SCSI cds. BTW, are those documented somewhere? I mean, I can work out what they should do, but they still ought to be on a man page. Soren? Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Review requested for /dev/random driver improvements!
I'm getting some errors trying to build this. Attached is my make.log that shows the errors. The one that's there now should fix this (I forgot to include a 1-line patch to sys/conf/files). Thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People running with LOCALBASE set to something other than /usr/local?
Jacques A. Vidrine writes: On Mon, Aug 21, 2000 at 11:59:26PM -0500, Mike Meyer wrote: I'm curious - are there any committers who regularly use a system with LOCALBASE set to something other than /usr/local? I have LOCALBASE=/opt for a couple of years now. OTOH, I also have a symlink from /usr/local - /opt due to a small but significant number of ports that are not PREFIX clean. Um - why? If you removed the setting of LOCALBASE in that case, you wouldn't change the disk layout at all. However, I was wondering if there was anyone who could fix things that weren't PREFIX clean who would also find them on a regular basis. That's not you. Thanx, mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
