Re: seeking help on "adding a disk"
> > > --- Jerry McAllister <[EMAIL PROTECTED]> wrote: > > [snip] > > > > # newfs -U /dev/ad2s1e > > > > Newfs used to require the raw device name, as in > > > >newfs -U /dev/rad2s1e > > > > but I see the man page doesn't show that in its example now, so > > maybe it no long does. Try it once and see. > > > > > The newfs should then work after the bsdlabel is fixed up. > > > > > > Nope. Same error. Retries of newfs causes crashes at random > > sectors. > > > I am guessing that the 40-wire cable is causing poor signaling. I > > also > > > tried changing the offset of 'e' to 0 and modifying the 'size' so > > that > > > it matches 'c'. > > > > Could be. If using rad2s1e doesn't help, then maybe that is your > > problem. > > > This is all I have: > > $ ls -lh /dev/r* > crw-rw-rw- 1 root wheel0, 10 Apr 9 15:55 /dev/random > > No raw devices. Yes. devices don't just show up and stay there any more. They are managed by devfs. I haven't studied that to see just how it works yet, so I don't know at which point it should start showing up in /dev if ever. I just figured trying a newfs with the /dev/r... might be something to try out to see what happened - sort of an experiment and if that doesn't do it, then maybe the thing to pursue is your concern about the cables. If that doesn't work, I think this has gone beyond any problems I have ever had so I don't know what else to suggest. Hopefully someone else will have some thing to say. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Wanted: Flash player for ....
[Hoping this isn't too OT for the list] So... now that www/linux-flashplugin* are gone, I was hoping to get opinions on which alternative flashplayer(s) are reasonably good. I use firefox and would prefer a plugin for it... but am generally interested in the state of any flash player. I know there are a handful in ports, just wanted some opinions. Could anyone please offer their opinion on - which alternative they are using - why - comment(s) on installation ease (or lack thereof) - is it a standalone or plugin Thanks. -- Regards, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need /bin/sh script help
On Tuesday 11 April 2006 06:30, Garrett Cooper wrote: > cd /usr/src; > if [ -n `grep -e s/KERNCONF=/ /etc/make.conf` ] # want to look for > KERNCONF in /etc/make.conf if [ `make -V KERNCONF` ] > read KERNCONF; > KC="KERNCONF=$KERNCONF"; > fi You need to check that KC actually exists. IIRC a typo will cause GENERIC to build. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ClamAV question
Greetings, I am running Freebsd 6-release. I have been following the qmailrocks.org document for setting up qmail, squirrel, spamassasssin & clamav (& misc) on Freebsd. Everything has gone fine, but I am having a small problem. When I run the test_installation.sh -doit which sends a regular email, a spam email & 2 virus emails (safe of course) , ClamAV places the messages in the quarantine directory, but never delevers the warning message to the intended recepient notifying them of the email being quarantines. From my reading, that is what is suppose to happen. I have googled, I have posted to the forums at qmailrocks.org, I have IRC'd on the clamav channel with no help. Any ideas ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upcoming release 6.1: old version of some core components
[EMAIL PROTECTED]@mgEDV.net wrote: during testing the 6.1-BETA4 i found only one major thing i really like to discuss on the list for my understanding. why are some major parts of the os are not updated to the current versions (see examples beyond)? code-improvements and security-/functionality-fixes come to my mind here. examples given: zlib (v1.2.2, 10/2004; current 1.2.3, 07/2005) openssl (v0.9.7e, 10/2004; current 0.9.7i, 10/2005) openssh (v4.2p1, 01/2005, current 4.3p2 02/2006) for openssh, the code-freeze of freebsd was before the release of 4.3, this makes sense, but what about the rest? I can't answer you main question, but I would say that you can bet your shirt on the fact that there will be no known security issues in the older packages. At least for openssl and openssh you can get latest versions through the ports. Not an option for everything -- I see no zlib for example and I don't believe there's a standard cvs port either. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upcoming release 6.1: old version of some core components
On Tue, 11 Apr 2006 14:55:06 +0200 "[EMAIL PROTECTED]@mgEDV.net" <[EMAIL PROTECTED]> wrote: > > hi together, > > during testing the 6.1-BETA4 i found only one major thing > i really like to discuss on the list for my understanding. > > why are some major parts of the os are not updated to the > current versions (see examples beyond)? code-improvements > and security-/functionality-fixes come to my mind here. > > examples given: > zlib (v1.2.2, 10/2004; current 1.2.3, 07/2005) > openssl (v0.9.7e, 10/2004; current 0.9.7i, 10/2005) > openssh (v4.2p1, 01/2005, current 4.3p2 02/2006) > > for openssh, the code-freeze of freebsd was before the > release of 4.3, this makes sense, but what about the rest? While you'd have to contact the maintainers of the specific packages, I assume that you mostly answered your own question. There are limited resources to develop FreeBSD, and a large number of contributed packages that have to be maintained. Each time a contrib is updated, it must be thoroughly tested before being merged into a production release. This takes man hours. Do you know of any specific security issues that have not been addressed relating to these packages? If so, you should contact the security officer directly to get the issues on the top of the priority list. If it's just feature improvements, then it will be a matter of who has enough time and motivation to get the new versions imported. OpenSSL is a non-trivial part of FreeBSD, so upgrading is not something to be taken lightly. Regardless, it would be worthwhile for you to see if there is an outstanding PR and file one if there isn't. Sometimes developers get so busy that they don't notice that software is getting old. -- Bill Moran Collaborative Fusion Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
upcoming release 6.1: old version of some core components
hi together, during testing the 6.1-BETA4 i found only one major thing i really like to discuss on the list for my understanding. why are some major parts of the os are not updated to the current versions (see examples beyond)? code-improvements and security-/functionality-fixes come to my mind here. examples given: zlib (v1.2.2, 10/2004; current 1.2.3, 07/2005) openssl (v0.9.7e, 10/2004; current 0.9.7i, 10/2005) openssh (v4.2p1, 01/2005, current 4.3p2 02/2006) for openssh, the code-freeze of freebsd was before the release of 4.3, this makes sense, but what about the rest? br & cu... ps: just reply 2 the list please... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Toggling port dependencies
On Tuesday 11 April 2006 11:39, Erik Norgaard wrote: > Hi: > > Some ports exists in multiple versions such as OpenLDAP, the most recent > and recommended is 2.3, but some other ports depends on another version > for example jabberd that requires 2.2. Some ports will let you choose > which version to compile against but jabberd don't. > > How to I make a port compile against the installed version or a version > of my choice? > > I know that it may fail, but I'd like to try. > You could try setting USE_OPENLDAP_VER=23 for the port. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Timescale for 6.1-RELEASE...
Thanks for the reply Nikolas - that's helpful. I ended up upgrading my laptop to 6.1-PRERELEASE (from 6.0-RELEASE) anyway, and haven't had any problems since. After your feedback I'll probably do the desktop shortly. The only thing that's holding me back from moving my home server from 5.3-RELEASE is that I've successfully got ndis working on it using the 'old' ndiscvt method and I'm a little reluctant to risk not being able to replicate my success with ndisgen under 6.x Thanks again, Peter Harrison >-Original Message- >From: Nikolas Britton [mailto:[EMAIL PROTECTED] >Sent: 11 April 2006 12:06 >To: Harrison Peter CSA BIRKENHEAD >Cc: freebsd-questions@freebsd.org >Subject: Re: Timescale for 6.1-RELEASE... > > >On 3/30/06, Harrison Peter CSA BIRKENHEAD ><[EMAIL PROTECTED]> wrote: >> I realise the answer to this question is "when it's ready", >but does anyone have a rough idea how close to being ready 6.1 is? >> > >The 6.1 branch was cut on the 5th, this means you can cvsup to >RELENG_6_1 branch and rebuild world to 6.1-RC. As for the release date >of the official 6.1-RC1 builds... It should have happened yesterday, >so expect it any time this week. 6.1-RELEASE should be released at the >end of this month or the beginning of next month If you look at >the schedule everything has been shifted out 1 month. > >If you want my opinion on 6.1, it's ready right now, I've been running >a production server on 6.1 since BETA2, my main workstation at work >since BETA4 and my main workstation at home has been running 6.1 since >before BETA1 (tracking 6-STABLE). I've had no problems and feel that >It's far superior to FreeBSD 5.x, It's also alot faster then 5.x. The >more tester we have for the 6.1 release candidate runs the better >6.1-RELEASE will be! >http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributin g/index.html -- BSD Podcasts @ http://bsdtalk.blogspot.com/ PLEASE NOTE: THE ABOVE MESSAGE WAS RECEIVED FROM THE INTERNET. On entering the GSi, this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable & Wireless in partnership with MessageLabs. In case of problems, please call your organisational IT helpdesk. ** This document is strictly confidential and is intended only for use by the addressee. If you are not the intended recipient, any disclosure, copying, distribution or other action taken in reliance of the information contained in this e-mail is strictly prohibited. Any views expressed by the sender of this message are not necessarily those of the Department for Work and Pensions. If you have received this transmission in error, please use the reply function to tell us and then permanently delete what you have received. Please note: Incoming and outgoing e-mail messages are routinely monitored for compliance with our policy on the use of electronic communications. ** The original of this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable & Wireless in partnership with MessageLabs. On leaving the GSi this email was certified virus-free. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Timescale for 6.1-RELEASE...
On 3/30/06, Harrison Peter CSA BIRKENHEAD <[EMAIL PROTECTED]> wrote: > I realise the answer to this question is "when it's ready", but does anyone > have a rough idea how close to being ready 6.1 is? > The 6.1 branch was cut on the 5th, this means you can cvsup to RELENG_6_1 branch and rebuild world to 6.1-RC. As for the release date of the official 6.1-RC1 builds... It should have happened yesterday, so expect it any time this week. 6.1-RELEASE should be released at the end of this month or the beginning of next month If you look at the schedule everything has been shifted out 1 month. If you want my opinion on 6.1, it's ready right now, I've been running a production server on 6.1 since BETA2, my main workstation at work since BETA4 and my main workstation at home has been running 6.1 since before BETA1 (tracking 6-STABLE). I've had no problems and feel that It's far superior to FreeBSD 5.x, It's also alot faster then 5.x. The more tester we have for the 6.1 release candidate runs the better 6.1-RELEASE will be! http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/index.html -- BSD Podcasts @ http://bsdtalk.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SIGCHLD and sockets HELP!
Keith Bottner wrote: I am having a problem with SIGCHLD signals and their interaction with sockets. I have an application that forks modules in separate processes and use UNIX domain sockets for communication. The main application handles the SIGCHLD signal so that it can detect when/if a module crashes and if so restart that specific module. The problem arises when the module crashes and before the main application is notified with the SIGCHLD signal the socket will continue to allow writes. I expected that there would be occasions when the SIGCHLD signal would occur after my attempt to write into the socket, but I also expected the socket to return an error at which point I could then mark the module for restart as well. My question is, has anybody else had this problem? Does anybody know exactly what is going on an why? And most importantly, does anybody have a solution? Thanks in advance for your time, it is quite an interesting problem so I am hoping to get some insightful answers. No-one is chiming in so maybe it would help if you posted a code fragment that shows the write to the socket which you expect to fail, but which doesn't seem to. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Toggling port dependencies
Hi: Some ports exists in multiple versions such as OpenLDAP, the most recent and recommended is 2.3, but some other ports depends on another version for example jabberd that requires 2.2. Some ports will let you choose which version to compile against but jabberd don't. How to I make a port compile against the installed version or a version of my choice? I know that it may fail, but I'd like to try. Thanks, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [freebsd-questions] ndis setup
hernan <[EMAIL PROTECTED]> wrote: [Quoting adjusted, please don't top post.] > On 4/9/06, Fabian Keil <[EMAIL PROTECTED]> wrote: > > hernan <[EMAIL PROTECTED]> wrote: > > > > > Hey folks. I'm setting up FreeBSD 6.0-RELEASE and I'm having a > > > little trouble getting my wireless NIC recognized. The card is a > > > Linksys WMP64G and I'm trying to set things up to run with the > > > FreeBSD NDISulator as described in the FreeBSD handbook > > > (http://www.freebsd.org/doc/handbook/network-wireless.html). > > > > This chapter is outdated. > > > > > Here's what I'm doing (as root): > > > > > > 1) Verifying with 'pciconf -lv' that the PCI card is there. > > > Also, I know the card works, it was running fine on Windows. > > > > > > 2) Building ndis itself: > > > > > 3) Building the if_ndis module: > > > > > 4) Loading the ndis and if_ndis modules: > > > kldload ndis > > > I verify at this point using kldstat that both ndis and if_ndis > > > are in fact loaded. > > > > > > I see nothing in dmesg or in my console during the kldload. > > > Also, it doesn't appear that the driver found the card, there's > > > no signs of life. I've tried using ndisgen, and have had the > > > same results (with much less typing). In either case, I get > > > nothing in dmesg and no usable enabled NIC. > > > > After you run ndisgen you should have a third kernel module with > > a name similar to the name of your sys file. If you load > > this module you should at least get an error message. > Thanks Fabian, that helped me move forward. My next question is how > to interpret the segfault I get when loading the new kernel module I > created with ndisgen. The error happens when I do the 'kldload' on > the new module, my machine dies and reboots. > > Does this mean I'm out of luck with using NDIsulator? Let me know if > you have any hints. My hint is to post slightly more information. While I probably won't be able to help any further, there a lot of knowledgeable people on this list who could help if they had a better description of your problem. You could start with: - the relevant output of pciconf -lv - which .inf and .sys file you used - an exact description what you did to get to the reboot - why you are sure it was caused by a segfault Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: DVD-Slideshow
Chris, congratulations on you wedding, i hope the best for the two of you. read back the thread yourself: you will need the dvd-slideshow from ports + - patch for the wc --lines ( or wc --chars, i can't remember ). these are 1 of 2 instances in the script. - back in this thread i have given multiple solutions for a replacement "seq". this is the key to proper fading. maybe it is easier afterall to run the script in linux-compat mode: you will need no patches at all. i for one do not know how to accomplish this easy however ( never had the need ). oh (w/h)ell, you'll just need to start it from a linux-shell i assume. good luck, and please try to notify the portmaintainer about the problem and solution. i am off on a mini-break myself, so you are on your own now. regards, usleep On 4/11/06, Chris Maness <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Chris, > > > > > >> or you could symlink to: ( if you have linux compat enabled ) > >> > >> /usr/compat/linux/usr/bin/seq > >> > >> > > > > will you let me know if this helped you? > > > > will you relay the seq-patches to the portmaintainer? > > > > regards, > > > > usleep > > > > > I am back from my honeymoon (lots of pics to try out with the script). > > What version did you want me to try? Did you have 1.7.5 patched for > wc? I could try that. > > Thanks > Chris Maness > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Timescale for 6.1-RELEASE...
martinko wrote: > i'm afraid todo page is not updated very often. at least this was the > case when i was watching it during previous releases. so one was/is left > to search through mailing lists for occasional background info.. :-( > > btw, there used to be a great site publishing summaries of current > development -- http://www.xl0.org/FreeBSD/ -- it's been dead for more > than 1 yr though :( According to the last schedule the tree has been tagged, you can cvsup RELENG_6_1, changes may still be committed depending on the experiences of RC1 and RC2. http://www.freebsd.org/releases/6.1R/schedule.html Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Bge Kernel Compile Issues
--- Wil Hatfield <[EMAIL PROTECTED]> wrote: > > > Check your RAM lately? Kernel and world compiles > usually make RAM issues > > > evident. > > RAM checked out fine. > > > /usr/src/sys/dev/bge/if_bge.c > > /usr/src/sys/dev/bge/if_bge.c: In function > `bge_newbuf_jumbo': > > /usr/src/sys/sys/mbuf.h:513: warning: 'zone' might > be used > > uninitialized in > > this function > > The problems with GENERIC build, the BGE 'zone' > issue, and half a dozen > other similar uninitialized variable errors were all > caused by this: > > options RESTARTABLE_PANICS > > Turning it off made it all build just fine on > multiple machines. Always > something right in front of your face isn't it? > > Now my question is with the RESTARTABLE_PANICS > turned off are my machines > going to hang at kernel panics? What is the deal > with that? Still waiting > for an answer on that one. > > -- > Wil Hatfield Hey there, Not sure what Freebsd you're trying to build but here's a report found two years ago: http://lists.freebsd.org/pipermail/freebsd-bugs/2004-September/009307.html Did a google search and that option appears to allow the kernel to return from a panic. Looks like a few users over the years have complained about the RESTARTABLE_PANICS being broken. Might still be. Hope that helps. ~Mr. Anderson __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
