Re: Upgrading 7.1-PRERELEASE
On Fri, Oct 24, 2008 at 07:52:11AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:41:05AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. Thanks Jeremy I thought that the uname tag would change to BETA-2 I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: I got it from here http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046037.html /Leslie You've misunderstood what I said. :-) I want to know where the BETA2 string actually came **from**, meaning who or what idealised it and why. It is not a CVS tag, and it's not referred to anywhere other than the here's the ISOs mails that come from Ken. The problem is that this string generates confusion; you are not the first person who has gotten confused by this (downloading version labelled with XYZ and upon building world/kernel, seeing version ABC, inducing an Email to a mailing list asking I downloaded XYZ, but I'm seeing string ABC. Where is the tag for XYZ? I want to follow it, only to be told XYZ is actually PRERELEASE). In essence what I'm saying is we're inconsistent with the strings we use for distributions of FreeBSD. Users **barely** understand the difference between -STABLE and -RELEASE, and only a select few understand the difference between CVS tags RELENG_x and RELENG_x_y. For distributions that are not STABLE or RELEASE, we need to stick with a single string, and that string (IMHO) should be PRERELEASE-MMDD (to signify the build date). http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
El Jue 23 Oct 2008, Jeremy Chadwick escribió: On Thu, Oct 23, 2008 at 09:42:41PM -0700, Martin Alejandro Paredes Sanchez wrote: El Jue 16 Oct 2008, Jeremy Chadwick escribió: If this printer is hooked up on the network (e.g. via Ethernet), I believe you need to set the lp variable to the hostname or IP address of the printer, e.g.: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=192.168.1.100\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: Negative, leave the lp capability blank, explicitly (:lp=:). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-advanc ed.html#PRINTING-ADVANCED-NETWORK-RM Then the printcap(5) man page should reflect this; the existing explanations for both fields are painfully terse. lp str /dev/lpdevice name to open for output, or [EMAIL PROTECTED] to open a TCP socket rm str NULL machine name for remote printer I can file a PR (to doc) on this if recommended. if you are printing to a remote LPD system, you should use: :lp=:\ :rm=hostname-or-ip:\ :rp=printer-name:\ If you use [EMAIL PROTECTED], then you should not use rp and rm, but in the port of the machine should be a program that undestand LPD/LPR protocol. The printcap(5) man page has a section REMOTE PRINTING. maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calendar software wanted
Andrew Gould wrote: I currently use webcalendar (with apache, php, postgresql) for my calendar. I heard about solutions like that, maybe i implement something for my family too. Thank you guys for the hints, i'll happily test them and see if something fits my needs :-) Best regards, marco Andrew Gould wrote: On Wed, Oct 22, 2008 at 8:51 AM, Daniel Molina Wegener [EMAIL PROTECTED] wrote: Marco escribió: hello list, anybody has experience with calendar software which runs on freebsd. i maybe would integrate it also in thunderbird/mutt,but thats not necessary, or use a stand alone software. minimum requirements to the software would be making entries, getting alarms for appointments. Try kontact (the kdepim port). Have fun xD thank you for responses, marco Regards, Before I moved from my PalmPilot III (still works) to an iPhone (not 3G), I used JPilot for my PIM and Sylpheed-Claws (the name has changed?) for email. This was a good setup because there was a plugin that allowed Sylpheed-Claws to access the JPilot addressbook. I currently use webcalendar (with apache, php, postgresql) for my calendar. This is overkill for an individual; but has many advantages for family scheduling: I can add an item to my wife's calendar with an email reminder. Since my wife has a blackberry email address, the message will get pushed to her phone. When testing this feature, I would suggest starting with something like a dinner invitation rather than a grocery list. ;-) Have fun, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shutting down help
At 02:48 PM 10/23/2008, Juan Ortega wrote: I'm using FreeBSD amd64 8-0-Current I set up window maker to start by startx command, but when I exit the window maker the screen just turns black nothing works so I'm force to unplug the power each time. This happens sometimes other times the terminal shows up and I can shutdown manually. Since I'm using a snapshot version of FreeBSD is this a bug? I'm not sure what logs to copy and paste here for more information. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Use: ctrl+alt+backspace to kill your x server. I suspect you have the wrong program starting in your startx. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: man -t odd page size
Gonzalo, please cc those to whom you are responding. I had to dig this out of the digest, which breaks the threading .. On Thu, 23 Oct 2008 18:35:36 -0200 Gonzalo Nemmi [EMAIL PROTECTED] wrote: [..] On Thu, Oct 23, 2008 at 10:37 AM, Ian Smith [EMAIL PROTECTED] wrote: On Wed, 22 Oct 2008 23:35:25 -0200 Gonzalo Nemmi [EMAIL PROTECTED] wrote: [..] Does an inmensily huge majority have to walk the extra mile in order to get an ISO compliant document whereas a small minority benefits from having non ISO complaint default formats??? Gmail does a superb job of formatting quotes, eh? Gonzalo: shouldn't that be 'the extra kilometre?' :) Well, a quarter of the people on this planet live in China, so by your theory shouldn't the FreeBSD lists, docs and code all be in Chinese? No .. languages are not ISO standards... let alone the fact that we are not discussing languages in here. ISO is just another committee. I think what you're really complaining about is that the US tends to ignore international standards. We know that, it's more about politics .. also not being discussed in here :) I doubt an 'immensely huge majority' of FreeBSD systems are located outside the US (data at http://www.bsdstats.org/freebsd/countries.php notwithstanding, reckoning Australia to have the most FreeBSD users :) That's only if you take bsdstats as the ultimate and most authoritative word on the location of FreeBSD based systems. I do not. And actually Im running 3 FreeBSD systems in my place and Argentina doesn't even figure on that list. My point exactly! So where do you get your assumption that the majority of FreeBSD systems, let alone an 'immensely huge' majority, are located outside the US? I don't say the opposite, just that it's unproveable. and on a side note: will we ever get to see ISO 216 A4 as the default choice for output instead of not-standard, only usefull in the US but useless in the rest of the whole world letter page size and the likes??? I've yet to run into any printing or display software that didn't offer a wide choice of formats, including A4 and many other A* sizes, so what any particular software chooses as its 'default' scarcely matters. To you .. but not for me or for anyone who lives in a country in which non-iso-standard paper (like letter) is simply _not_available_ or costs twice as much as A4. Australia went metric in the mid '70s, and I don't know where I could find letter-size paper if I wanted any, which I don't. Nor do I find it any great inconvenience to select A4 for printing. Storm in a teacup? I undertand this may not be a problem for someone who can just man -t man | ps2pdf14 - man_getopt and get a printable pdf that uses the whole page but I have to go zcat `man -w ls` | groff -Tps -dpaper=a4 -P-pa4 -mandoc | ps2pdf - tmp.pdf in order to get a usefull output or use the first method and waste a lot of paper (wasting resources .. wich is something the, we, citizens of the third world can not afford). Oh please. I wouldn't try remembering either of those incantations, and any process complicated enough to require looking up in the man/s goes into a one or two-line script here. I can't afford wasted time either. Greetings from Germany, where A4 is the standard for more than a century now. =^_^= I really hope they do, or at least, start contemplating the fact that ISO standards are usefull as a whole or are not usefull at all .. That's not true at all; there's no 'all or nothing' about standards. What actually works and is adopted in the real world determines that. ISO 216 works (and it has worked ever since it's conception, more than 100 years ago) and is adopted in the real world, except for the US, Mexico and Canada. http://www.cl.cam.ac.uk/~mgk25/iso-paper.html Sure. We use it here. But I don't see much point in complaining about those who use something else. We drive on the left side of the road too and would still do so should ISO publish a 'standard' to the contrary :) [For North American readers, there's a list of A4 vendors on that page] Ask yourself: how come the world uses TCP/IP for internet communications rather than the OSI X.200-X.219 suite? How come we're still using SMTP plus a pile of RFCs to deliver email rather than the X.400-X.420 suite? It became a defacto standard ... Just as much as Microsoft Windows did .. Are by any chance using Windows? No, and it's 'reductio ad absurdum' to mention Windows in this context. If you'd actually read much of the OSI stuff - assuming you had a spare year or two - you'd know that TCP/IP became the standard because a) it was working long before the ISO stuff was even being formally tested or
Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
6.1-RELEASE-amd64 machine. If I add /usr/lib32 to my LD_LIBRARY_PATH it breaks all of my binaries on my 64-bit machine. what do you expect else? this will make system trying to bind 32-bit libs to 64-bit program. it can't work ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble Shutting down
On Fri, Oct 24, 2008 at 12:39 AM, Juan Ortega [EMAIL PROTECTED] wrote: On Thursday 23 October 2008 17:41:40 you wrote: On Wed, Oct 22, 2008 at 1:42 AM, Juan Ortega [EMAIL PROTECTED] wrote: I'm using FreeBSD amd64 8-0-Current I set up window maker to start by startx command, but when I exit the window maker the screen just turns black nothing works so I'm force to unplug the power each time. This happens sometimes other times the terminal shows up and I can shutdown manually. Since I'm using a snapshot version of FreeBSD is this a bug? I'm not sure what logs to copy and paste here for more information. Do you have the drivers for your graphics card installed? What type of graphics card is this? My laptop is HP Pavilion tx2510us and uses the graphics card ATI Radeon(TM) HD 3200 Graphics everything works expect even when the terminal does come up it gives this error xauth: (argv):1: bad display name replay.free-bsd.net:0 in remove command ideas? Please don't only reply to me, if your initial question was towards the list -- someone else may see something I'm missing. You never answered my initial question. Are the proper xorg drivers for your graphics card installed? I ask again, because I've seen several situations where non-existent or incorrect graphics drivers make X do bad/odd things when exiting -- I've experienced this situation myself. I know nothing about ATI, other than it doesn't play well with any of the OSes I use, so I don't buy it. -- Glen Barber 570.328.0318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-7.1, BETA2 or PRERELEASE
Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? Aston ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD-7.1, BETA2 or PRERELEASE
Onderwerp: FreeBSD-7.1, BETA2 or PRERELEASE Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? Aston If you download the cd BETA2 then you see BETA2 But if you going to csup the latest source from the RELENG_7 branch it will be named PRERELEASE again. See Beta as just a Timestamp name for the PRERELEASE branch. Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.8.2/1742 - Release Date: 23-10-2008 15:29 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.1, BETA2 or PRERELEASE
On Fri, Oct 24, 2008 at 03:07:32PM +0530, Masoom Shaikh wrote: Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? This question keeps coming up. http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/184992.html RELENG_7 == PRERELEASE. There is no BETA2 tag to follow. No one is sure at this point where the BETA2 string has come from (meaning why it was idealised or why it's being used). I'm of the belief that it's something Ken is hand-hacking in newvers.sh before building + making ISO releases and putting them up on the mirrors. And I am also of the opinion that this should stop, and we should simply name the releases PRERELEASE-MMDD to signify the build date. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DHCP server
Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks ... and then it times out, and does not configure the network. This makes me think that there may be a client issue, since the DCHP server does indeed offer an address. But I also have troubles with a Mac OS X client (although it's a little more vague about the errors). Svein Halvor ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks ... and then it times out, and does not configure the network. This makes me think that there may be a client issue, since the DCHP server does indeed offer an address. But I also have troubles with a Mac OS X client (although it's a little more vague about the errors). If the server is handing out /24 network prefixes, then once your clients bind the offered address in 10.0.0/24, they can no longer communicate with the server in 10.0.1/24. You can a) give the DHCP server an alias IP address in 10.0.0/24 on the appropriate interface b) change the network prefix to 16 bits, so that 10.0.0 and 10.0.1 (and ALL other addresses with the prefix 10.0) are in the same logical network space c) renumber your DHCP pool Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpj91QEftOyE.pgp Description: PGP signature
Re: FreeBSD-7.1, BETA2 or PRERELEASE
Masoom Shaikh skrev: Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? Aston ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I just asked the same question this morning. See the archives for the discussion and the answer that was given. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sendmail sasl problem
Hi, I'm having a strange problem after a recent saslauthd upgrade.. I can no longer authenticate to the smtp server, with saslauthd in debug mode i can see the authentication ( via getpwent) as succeeding saslauthd[54468] :rel_accept_lock : released accept lock saslauthd[54468] :do_auth : auth success: [user=smtpauth] [service=smtp] [realm=] [mech=getpwent] saslauthd[54468] :do_request : response: OK however sendmail still gives me a relaying denied i've tried this with various other system users with the same result, saslauthd says ok, sendmail says no! Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-ENHANCEDSTATUSCODES Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-PIPELINING Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-8BITMIME Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-SIZE Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-DSN Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-ETRN Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-AUTH PLAIN LOGIN Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250-DELIVERBY Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250 HELP Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: -- AUTH PLAIN AHBhdWwAcmV3N3gwMTQ0NQ== Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 235 2.0.0 OK Authenticated Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: AUTH=server, relay=87-194-184-71.bethere.co.uk [87.194.184.71], authid=paul, mech=PLAIN, bits=0 Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: -- MAIL FROM:[EMAIL PROTECTED] SIZE=20688 Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: Milter: sender: [EMAIL PROTECTED] Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: milter=clmilter, action=mail, continue Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: Milter (clmilter): time command (M), 0 Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: milter=spamassassin, action=mail, continue Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: Milter (spamassassin): time command (M), 0 Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 250 2.1.0 [EMAIL PROTECTED]... Sender ok Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: -- RCPT TO:[EMAIL PROTECTED] Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: --- 550 5.7.1 [EMAIL PROTECTED]... Relaying denied. Proper authentication required. Oct 24 11:13:01 ifdnrg18 sm-mta[57530]: m9OAD18c057530: ruleset=check_rcpt, arg1=[EMAIL PROTECTED], relay=87-194-184-71.bethere.co.uk [87.194.184.71], reject=550 5.7.1 [EMAIL PROTECTED]... Relaying denied. Proper authentication required. rc.conf #SASLAUTHD saslauthd_enable=YES #note debug mode for sasl runs the daemon in foreground #saslauthd_flags=-a getpwent -d saslauthd_flags=-a getpwent there's nothing in the access maps to reject this host, and adding myself to the access map fixes it for me ( but obv not anyone else) The same upgrade to sasl went smoothly on 2 other boxes with fairly identical setups, and both sasl and sendmail have been reinstalled with same effect. Can anyone offer any suggestions? tia Paul. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' what's your netmask? if /24 your dhcp server is misconfigured ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
Wojciech Puchar wrote: a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' what's your netmask? if /24 your dhcp server is misconfigured No, it's /23, and the dhcp server has address 10.0.1.1, and it's handing out addresses in the the 10.0.0.2-10.0.0.200 range. 10.0.0.1 is a router with static address. It also uses /23. sv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP server
Daniel Bye wrote: On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: Hi, I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: I've got a FreeBSD 7.0-p4 machine running isc-dhcp3-server-3.0.5_2 serving my home network. When my Linux (Archlinux) client request a lease, this happens: [EMAIL PROTECTED]:~]$ dhcpcd -n eth0 eth0: dhcpcd 4.0.2 starting eth0: broadcasting for a lease eth0: offered 10.0.0.176 from 10.0.1.1 `mirrorball' eth0: checking 10.0.0.176 is available on attached networks ... and then it times out, and does not configure the network. This makes me think that there may be a client issue, since the DCHP server does indeed offer an address. But I also have troubles with a Mac OS X client (although it's a little more vague about the errors). If the server is handing out /24 network prefixes, then once your clients bind the offered address in 10.0.0/24, they can no longer communicate with the server in 10.0.1/24. You can a) give the DHCP server an alias IP address in 10.0.0/24 on the appropriate interface b) change the network prefix to 16 bits, so that 10.0.0 and 10.0.1 (and ALL other addresses with the prefix 10.0) are in the same logical network space c) renumber your DHCP pool The dhcp server has netmask /23, and are also handing out this netmask to clients. I have lots of clients running FreeBSD, Windows and OS X not complaining. I do however, have one OS X client that's been constantly complaining, and recently also an Archlinux machine. It used to work on the Linux client up until recently. It might be the client, in which case I should probably ask some Lunux-folks, but since one of the apples also have a problem, I thought I might be the server. Can I diagnose this any further? sv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.1, BETA2 or PRERELEASE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Chadwick wrote: On Fri, Oct 24, 2008 at 03:07:32PM +0530, Masoom Shaikh wrote: Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? This question keeps coming up. http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/184992.html RELENG_7 == PRERELEASE. There is no BETA2 tag to follow. No one is sure at this point where the BETA2 string has come from (meaning why it was idealised or why it's being used). I'm of the belief that it's something Ken is hand-hacking in newvers.sh before building + making ISO releases and putting them up on the mirrors. And I am also of the opinion that this should stop, and we should simply name the releases PRERELEASE-MMDD to signify the build date. When you run make release you have to set BUILDNAME to something. That value then sets the value of RELEASE in sys/conf/newvers.sh, which then affects uname output. I suppose everyone has an opinion as to what to name things, a classic bikeshed item. My opinion is that if BETA2 is an arbitrary name and there's no way to know the timestamp it was built from in CVS, then replacing BETA2 with the timestamp used for the CVS checkout makes sense. Of course CVS is good down to the second, so it would have to be MMDDHHMMSS...and at that point 7.1-PRERELEASE-20081020071001 starts making BETA2 look good. - -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5ABC 11B4 26F9 01F1 27AF AECB -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFJAb2iJvkB8SevrssRAvDqAJ4glXZL7dtiMLlaU2r8glSSa3XEsgCfY2ag S7+FOqNjJ10miUOLuq/AEEQ= =VzUi -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: DHCP server
On Behalf Of Svein Halvor Halvorsen Daniel Bye wrote: On Fri, Oct 24, 2008 at 11:43:32AM +0200, Svein Halvor Halvorsen wrote: I'm not sure if this is an issue with my dhcp server or the client, but since I seem to get troubles with two different clients, I'm thinking it might be the server: The dhcp server has netmask /23, and are also handing out this netmask to clients. I have lots of clients running FreeBSD, Windows and OS X not complaining. I do however, have one OS X client that's been constantly complaining, and recently also an Archlinux machine. It used to work on the Linux client up until recently. It might be the client, in which case I should probably ask some Lunux-folks, but since one of the apples also have a problem, I thought I might be the server. Can I diagnose this any further? Set up Wireshark to capture the UDP packets. Compare a successful assignment with the unsuccessful variations. See which side stops responding in each conversation and troubleshoot that end. There may be some clues in the event log on MS-Windows or the syslog files on OS-X. Bob McConnell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.1, BETA2 or PRERELEASE
--- On Fri, 10/24/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: FreeBSD-7.1, BETA2 or PRERELEASE To: Masoom Shaikh [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Friday, October 24, 2008, 6:26 AM On Fri, Oct 24, 2008 at 03:07:32PM +0530, Masoom Shaikh wrote: Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? This question keeps coming up. http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/184992.html RELENG_7 == PRERELEASE. There is no BETA2 tag to follow. No one is sure at this point where the BETA2 string has come from (meaning why it was idealised or why it's being used). I'm of the belief that it's something Ken is hand-hacking in newvers.sh before building + making ISO releases and putting them up on the mirrors. And I am also of the opinion that this should stop, and we should simply name the releases PRERELEASE-MMDD to signify the build date. It seems likely. I've only ever seen -PRERELEASE and -STABLE, when tracking RELENG_[0-9] branch. On the other hand, I have seen -RELEASE, -BETA, -RC, etc, when installing from media. Perhaps differentiating these isn't a bad idea, however, when it comes to uname output in PR's, despite the queries it generates over here. A media install can always be safely assumed to be a given set of code, while if someone is tracking a branch via cvsup, the build time would show up in uname output, however the user may still need to be queried for rcsid's or asked to cvsup to the latest if the issue is considered to possibly be a base system and/or kernel code issue. It's probably worth discussion and consideration, though. I don't know if/how useful the utility of the current naming conventions are to folks trying to solve potential code bug PRs. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
On 2008-Oct-24 10:43:04 +0200, Wojciech Puchar [EMAIL PROTECTED] wrote: 6.1-RELEASE-amd64 machine. If I add /usr/lib32 to my LD_LIBRARY_PATH it breaks all of my binaries on my 64-bit machine. what do you expect else? Well, the rtld should be smart enough to recognize 32-bit .so's and skip them when binding a 64-bit executable. Whilst having /usr/lib32 in LD_LIBRARY_PATH doesn't make sense from a solely FreeBSD perspective, I have done similar things when writing cross-platform scripts (to avoid having to use platform-dependent code). this will make system trying to bind 32-bit libs to 64-bit program. it can't work rtld shouldn't attempt to bind 32-bit libs to 64-bit programs. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpO8GHmdRY0K.pgp Description: PGP signature
Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
On Fri, Oct 24, 2008 at 8:50 AM, Peter Jeremy [EMAIL PROTECTED] wrote: On 2008-Oct-24 10:43:04 +0200, Wojciech Puchar [EMAIL PROTECTED] wrote: 6.1-RELEASE-amd64 machine. If I add /usr/lib32 to my LD_LIBRARY_PATH it breaks all of my binaries on my 64-bit machine. what do you expect else? Well, the rtld should be smart enough to recognize 32-bit .so's and skip them when binding a 64-bit executable. Whilst having /usr/lib32 in LD_LIBRARY_PATH doesn't make sense from a solely FreeBSD perspective, I have done similar things when writing cross-platform scripts (to avoid having to use platform-dependent code). this will make system trying to bind 32-bit libs to 64-bit program. it can't work rtld shouldn't attempt to bind 32-bit libs to 64-bit programs. Bingo! I don't care what the LD_LIBRARY_PATH is, a 64-bit binary should NEVER attempt to load a 32-bit library (at least by default). If anything, rtld should just exit with can't find library exception. What its doing now in my book is just wrong in everyway. The name of the shared object is no longer enough to verify a match, it also needs to check the arch bits as well. I agree with everyone on this list that for FreeBSD, the gcc toolset initialization should always contain /lib (and in fact I am going further and saying that al *NIX platforms should probably always check /lib since its the default and its there during bootup (that was a good point btw)). I think the issue has been cross platform builds and the way Linux has it organized. I have submitted a patch to add /lib back to the Boost folks but I still want to understand this behavior on FreeBSD - what am I missing? Final note, I thought that /usr/lib would have the major number versions linked just like /usr/lib32 so the above would just work. Right now the issue is libutil.so.5 isn't found not because /lib isn't in the LD_LIBRARY_PATH, i.e If I make a symlink in /usr/lib just like the /usr/lib32 file structure, it all just works. I was just saying above that I was wondering why major numbers aren't actually available as links in /usr/lib like they are in /usr/lib32. -aps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Extract Songs from DVD
On Fri, Oct 24, 2008 at 12:57:21AM -0400, John L. Templer wrote: Under Solaris x86 or Ubuntu Linux I have to use an application like cdrecord or soundjuicer to extract the audio tracks. These applications bypass the device files and go straight to the SCSI interface layer. libparanoia is a library that handles the tricky bits of reading the data off the CD. Just using dd to copy the data from the device file often results in corrupted data. I was wondering if the BSD kernel (or devd or whatever) uses a similar method of handling all the different variations that audio format CDs have. Well, cdrecord is in the ports: /usr/ports/sysutils/cdrtools: You may need to kldload atapicam though... From /usr/ports/sysutils/cdrtools/pkg-descr: The cdrtools software includes tools to create and/or extract ISO-9660 filesystems, verify their integrity, and write them to disc. This package contains the following programs: - cdda2wav (an digital CD audio extraction program) - cdrecord (a CD-R[W] recording program) - devdump (dump a device or file in hex) - isodebug (show debug info contained in an ISO-9660 image) - isodump (dump a device or file based on ISO-9660) - isoinfo (analyze or list an ISO-9660 image) - isovfy (verify an ISO-9660 image) - mkisofs (an ISO-9660 filesystem image creator) - mkhybrid (an ISO-9660/HFS filesystem image creator) Link to mkisofs. - readcd (a data CD reading and recording program) May be used to to write to DVD-RAM and to copy Solaris boot CD's. - scgcheck (checks and validates the ABI of libscg) - rscsi (daemon providing access to local SCSI-devices over the network) WWW: http://cdrecord.berlios.de/old/private/cdrecord.html Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble Shutting down
On Fri, Oct 24, 2008 at 6:25 AM, Juan Ortega [EMAIL PROTECTED] wrote: I'm not sure, when I first installed FreeBSD X -configure did everything in KInfoCenter the X-Server seems to be ok maybe since its snapshot version of FreeBSD the graphics drivers are in testing? What driver does /etc/X11/xorg.conf have listed for your graphics driver? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-7.1, BETA2 or PRERELEASE
thanks to all those gr8 comments, I learnt. and sorry for creating noise, I was in office and thus could not put required effort. as far as liking of release names goes, I feel BETA-x naming practice serves the purpose, it makes sense to casual users. changing version with date is too fastjust my two cents if they count ;-) Aston On Fri, Oct 24, 2008 at 12:45 PM, mdh [EMAIL PROTECTED] wrote: --- On Fri, 10/24/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: FreeBSD-7.1, BETA2 or PRERELEASE To: Masoom Shaikh [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Friday, October 24, 2008, 6:26 AM On Fri, Oct 24, 2008 at 03:07:32PM +0530, Masoom Shaikh wrote: Hi folks, y'day I csuped the src and built installed the kernel from RELENG_7 I was expecting FreeBSD-BETA2 in output of `uname -a` it is still -PRERELEASE, is it by decision or I have to change something ? I greped /usr/src for PRERELEASE but cud not locate it. I guess release engineering team does that. comments ? This question keeps coming up. http://lists.freebsd.org/pipermail/freebsd-questions/2008-October/184992.html RELENG_7 == PRERELEASE. There is no BETA2 tag to follow. No one is sure at this point where the BETA2 string has come from (meaning why it was idealised or why it's being used). I'm of the belief that it's something Ken is hand-hacking in newvers.sh before building + making ISO releases and putting them up on the mirrors. And I am also of the opinion that this should stop, and we should simply name the releases PRERELEASE-MMDD to signify the build date. It seems likely. I've only ever seen -PRERELEASE and -STABLE, when tracking RELENG_[0-9] branch. On the other hand, I have seen -RELEASE, -BETA, -RC, etc, when installing from media. Perhaps differentiating these isn't a bad idea, however, when it comes to uname output in PR's, despite the queries it generates over here. A media install can always be safely assumed to be a given set of code, while if someone is tracking a branch via cvsup, the build time would show up in uname output, however the user may still need to be queried for rcsid's or asked to cvsup to the latest if the issue is considered to possibly be a base system and/or kernel code issue. It's probably worth discussion and consideration, though. I don't know if/how useful the utility of the current naming conventions are to folks trying to solve potential code bug PRs. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.3-RELEASE installing php-imap
Hi all, I have a script that required php-imap extension installed but I keep running into a 2 snags when 'making' the port (mail/php-imap)... First, I have to use the -DFORCE_PKG_REGISTER so openssl_overwtite_base won't kill the make, which seems to work, and, most importantly, when the mail/imap-php port tried to actually do the build of the imap part, it says it can't find (OpenSSLs) 'evp.h' file. I assume it is just failing on the first file it can't find. So, I guess the question is, when making the mail/imap-php port, is there a way to pass the path for the OpenSSL libraries? My libs appear to be in two places: server# locate evp.h /usr/include/openssl/evp.h /usr/src/crypto/openssl/crypto/evp/evp.h If I can pass the path, I assume I should use the /usr/include dir, but how? make -D--with-openssl=/usr/include/openssl ??? TIA, -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems getting server on line
Quoting RAY [EMAIL PROTECTED]: Greetings; I have an existing server running FreeBsd 6.3. It's running as a name/web/mail server. I have built a new server to replace it running FreeBsd 7.0. I have both servers attached to the same router, with the production server sitting in the DMZ. I have tried to switch them over by simply changing which server the DMZ points to. When I did this, the new server didn't work. I could connect to the webserver (telnet to port 80) using either localhost or the private IP address (192.168...), but not using the domain name. I could connect to the default website properly from another computer on the same router using the private ip address. My first guess was that it was the firewall on the server configured incorrectly, so I disabled PF which didn't help. Any suggestions would be very much appreciated. Ray Hi, It looks like a router problem to me, do you have some port-forwarding or somethin like that on the router you have not changed? Have you tried changing the new servers IP to the old servers and pointing the DMZ to that old IP? as in simply switching the new server for the old? Hope this helps. Mads Trolle ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
On Thu, 2008-10-23 at 22:30 -0700, Jeremy Chadwick wrote: I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. Release builds are done using whats in /usr/src/release. One of the things you can set on the command line when you run make(1) there is the BUILDNAME variable, for example BUILDNAME=7.1-BETA2 in this case. The result of doing that is to change src/sys/conf/newvers.sh inside the build environment (which is among other things a checked out source tree) before doing the build. We use BUILDNAME for the Monthly Snapshots as well, that's why src/sys/conf/newvers.sh doesn't need to be altered just for those builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion What to have in src/sys/conf/newvers.sh before we do the branch for the release (typically the BETA builds, we usually do the branch for the release at the point we shift over to Release Candidates (RCs)) is unfortunately something we can't win with no matter what we do. The truth is that branches like RELENG_7 are development branches. We try very hard to never break things (well, badly anyway... :-) in those branches once they're considered to be a stable branch. But from time to time things do get broken there. If we were a corporation RELENG_7 type branches wouldn't be available to the public - they would be a tool for the staff programmers to work in. Its the RELENG_7_0 type branches that would be considered suitable for our customers. But we're not a corporation, and we don't want to keep stuff private. The downside to that however is people who are sort-of involved in the FreeBSD community but aren't truly active participants see RELENG_7 called stable and figure its OK to run their systems on that. We tell them not to, or at least to be sure to read mailing lists like freebsd-stable@ if they're going to do that, but lots of people don't follow that advice. And someone in that situation *really* freaks out if they update a system and winds up with a system that calls itself something too strange. It was a lot worse the last couple times we tried calling a stable branch something that had the word BETA in it, and we've more or less settled on PRERELEASE with no other fiddling as a way to suggest something is going on but not freak out that set of people too much... We do bump src/sys/conf/newvers.sh in the release branches once they get created (so it will become 7.1-RC1 at the point we create RELENG_7_1). But for the BETAs the best you can do to be a bit more descriptive of when you had done a source-based update is just note the date you did the update. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 6.3-RELEASE installing php-imap
--- On Fri, 10/24/08, Grant Peel [EMAIL PROTECTED] wrote: From: Grant Peel [EMAIL PROTECTED] Subject: FreeBSD 6.3-RELEASE installing php-imap To: freebsd-questions@freebsd.org Date: Friday, October 24, 2008, 9:31 AM Hi all, I have a script that required php-imap extension installed but I keep running into a 2 snags when 'making' the port (mail/php-imap)... First, I have to use the -DFORCE_PKG_REGISTER so openssl_overwtite_base won't kill the make, which seems to work, Hmmm. This sounds indicative of a more serious problem than just something you can work around quickly. I'm not at all familiar with this port though. and, most importantly, when the mail/imap-php port tried to actually do the build of the imap part, it says it can't find (OpenSSLs) 'evp.h' file. I assume it is just failing on the first file it can't find. That is very odd. cpp(1) looks in /usr/include by default, without any -I flags specified. As you state below that you have evp.h in /usr/include/openssl/evp.h, I don't see why this would happen. So, I guess the question is, when making the mail/imap-php port, is there a way to pass the path for the OpenSSL libraries? My libs appear to be in two places: server# locate evp.h /usr/include/openssl/evp.h /usr/src/crypto/openssl/crypto/evp/evp.h If I can pass the path, I assume I should use the /usr/include dir, but how? You'd use a make command such as the following, in the port dir: make CFLAGS='-I/usr/include' install clean That shouldn't be necessary, though, for reasons stated above. make -D--with-openssl=/usr/include/openssl ??? No. If you wanted to add configure args, you'd use CONFIGURE_ARGS in a similar manner to how my previous example used CFLAGS. TIA, -Grant This is a strange situation. Did your web search for similar issues turn up anything? Is anyone else experiencing this? If so, was there a PR on it? If not, you may want to contact the port maintainer and see if they have any assistance, or file a PR if there is not one already. Also, please post a reply to the list with your `uname -a` output. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
- Warren Block [EMAIL PROTECTED] wrote: On Fri, 17 Oct 2008, [EMAIL PROTECTED] wrote: I have tried the reccomendations that you guys have suggested with no luck. Here is my current printcap. admincolor|LANIER LD160c RPCS:\ :lp=\ :mx#0:\ :sd=/var/spool/output/admincolor:\ :rm=admincolor:\ :lf=/var/log/lpd-errs:\ :if=/usr/local/libexec/crfilter:\ :sh:\ :tr=\f: Please trim your responses and don't top-post, as it makes responding to your messages difficult. The printcap still has no :rp=lp: line. HP printers aren't picky about that, but other brands sometimes are. You've also added a filter and kept the multiple printer names. Things like that make more complexity to debug. Wait until you have basic communication working. The exact suggested printcap entry: admincolor:\ :lp=:\ :sh:\ :mx#0:\ :rm=admincolor:\ :rp=lp:\ :sd=/var/spool/output/admincolor:\ :lf=/var/log/lpd-errs: Note: one printer name (who needs more than one, really?). rm= and rp= entries. No filter; I think that printer can handle PostScript and PCL. Put that printcap entry in /etc/printcap, then send a PostScript test to the printer (all one line): printf %%\!PS\n/Courier findfont 20 scalefont setfont 72 72 moveto (Test!) show showpage\f | lpr -P admincolor -Warren Block * Rapid City, South Dakota USA I tried to reply to this email, but it never got posted. After doing some more troubleshooting I found out the generic error message was indicating an authentication error. By default the printer assumes color print, but the printer was setup to require a userid from the driver to allow color printing. When the autherntication feature is disabled the printer now works. My next step is to see what and how I can supply that info in the printcap. Thanks for all the suggestions and guidance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Bellcore MGR lightweight window manager on FreeBSD?
Does anyone remember the lightweight window manager called MGR, from Bellcore? ftp://sunsite.unc.edu/pub/Linux/apps/MGR/!INDEX.html I'm curious if anyone out there has gotten this to run on FreeBSD. I used it on an older system, years ago, and it was pretty effective - and would be useful for low-res environments, etc. Thx... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
change of behaviour after reboot
I had to perform a stupidity related reboot after allowing my /var fs to get to 109%. All seems well except for the behaviour of some of my rather ancient cgi scripts which are for serving up moinmoin wikis. Prior to the reboot these all seemed to work fine they hd the #! line #!/usr/bin/env python after the reboot these scripts refused to work. The log messages say env: python: No such file or directory Premature end of script headers: zzz-wiki.cgi I tried to check that env was there and that it gave me a reasonable python (at least at the terminal). However, something had obviously changed as the scripts now only work if I use #!/usr/local/bin/python I'm worried now in case my reboot or the over usage has caused some hidden damage. Anybody have any idea what could cause this misbehaviour? -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Running legacy i386 binaries on a amd64
Hi all, I have a fresh install of FBSD 7 amd64, and I want to run some legacy binaries from my old box (Fbsd 5.x i386). Searching the archives, I found this message: On Tue, 19 Aug 2008, Oliver Fromme wrote: |Christopher Joyner wrote: | Is there some way of doing that? Running i386 software on amd64 machine? | |Yes. FreeBSD/amd64 contains a compatibility facility |for i386 binaries. It should just work out of the box, |unless disabled explicitly. When I try to run the binaries, the following error message is displayed: ELF interpreter /libexec/ld-elf32.so.1 not found Abort I found the following tip to install 32bits libraries: cd /usr/src make build32 make install32 ldconfig -32 /usr/lib32 Is that enough? Thank you, - Marcelo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
MTA on non-standard port
Hello, For various reasons, I find myself in need of an MTA accepting submission on a port other than 587 (or 25). It'd be Real Nice(tm) if sendmail could Just Do It, but I'd be willing to look at other options as well, as long as I can get a good spam solution to play nice with the server (currently I'm running dual-sendmail with Amavisd-new and spamassassin). Anyone doing such a thing, or have a few hints handy? TIA, Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MTA on non-standard port
On Fri, Oct 24, 2008 at 10:50:39AM -0500, Kevin Kinsey wrote: Hello, For various reasons, I find myself in need of an MTA accepting submission on a port other than 587 (or 25). It'd be Real Nice(tm) if sendmail could Just Do It, but I'd be willing to look at other options as well, as long as I can get a good spam solution to play nice with the server (currently I'm running dual-sendmail with Amavisd-new and spamassassin). Anyone doing such a thing, or have a few hints handy? It can do it. See the DAEMON_OPTIONS macro in your /etc/mail/hostname.mc file. (Remember: DO NOT edit sendmail.cf directly). Here's a hint: http://www.sendmail.org/~gshapiro/8.10.Training/DaemonPortOptions.html -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
duplicate a drive
Hi, My laptop died recently and to get back to work as quickly as possible I simply took the laptop ide drive and put it into an old desktop using a 2.5 - 3.5 ide adapter. After loading a few new drivers into the kernel everything is working quite well. The next thing I've tried to do, without success, is mirror the contents of the 2.5 drive to a 3.5 drive in the desktop. The 2.5 drive is sliced/partitioned like this: Filesystem SizeMounted on /dev/ad0s2a 989M / /dev/ad0s2d 989M /tmp /dev/ad0s2f 59G /usr /dev/ad0s2e 989M /var ad0s1 is a 20GB slice that I have window installed on. The drive's total capacity is 80G. The 3.5 drive is only 70G so I'll have to skip the ad0s1 slice. Ideally what I'd like to do is copy everything from the ad0s2 slice to the 3.5 and run the OS off that drive. Then, each dump the contents of the 3.5 drive to the 2.5 drive. That way if either drive dies I'll, hopefully at worst, just have to switch which drive I boot from. Can anyone with experience doing something this make suggestions? Thanks, Joey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: duplicate a drive
On Fri, Oct 24, 2008 at 01:29:18PM -0300, Joey Mingrone wrote: Hi, My laptop died recently and to get back to work as quickly as possible I simply took the laptop ide drive and put it into an old desktop using a 2.5 - 3.5 ide adapter. After loading a few new drivers into the kernel everything is working quite well. The next thing I've tried to do, without success, is mirror the contents of the 2.5 drive to a 3.5 drive in the desktop. The 2.5 drive is sliced/partitioned like this: Filesystem SizeMounted on /dev/ad0s2a 989M / /dev/ad0s2d 989M /tmp /dev/ad0s2f 59G /usr /dev/ad0s2e 989M /var ad0s1 is a 20GB slice that I have window installed on. The drive's total capacity is 80G. The 3.5 drive is only 70G so I'll have to skip the ad0s1 slice. Ideally what I'd like to do is copy everything from the ad0s2 slice to the 3.5 and run the OS off that drive. Then, each dump the contents of the 3.5 drive to the 2.5 drive. That way if either drive dies I'll, hopefully at worst, just have to switch which drive I boot from. Can anyone with experience doing something this make suggestions? ports/sysutils/cpdup? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MTA on non-standard port
On Fri 2008-10-24 10:50:39 UTC-0500, Kevin Kinsey ([EMAIL PROTECTED]) wrote: For various reasons, I find myself in need of an MTA accepting submission on a port other than 587 (or 25). From what I can tell Postfix can be configured to listen on any unused port (or multiple thereof) by editing /usr/local/etc/postfix/master.cf as per the FAQ, then running /usr/local/etc/rc.d/postfix reload. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running legacy i386 binaries on a amd64
On Fri 2008-10-24 14:03:42 UTC-0200, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: I have a fresh install of FBSD 7 amd64, and I want to run some legacy binaries from my old box (Fbsd 5.x i386). I don't run 64-bit FreeBSD but from what I've read elsewhere, you can install 32-bit binary support from your FreeBSD 7.x CD: mount /cdrom cd /cdrom/lib32 sh ./install.sh If you're running 5.x binaries you might also need to install misc/compat5x from the ports tree. I hope this is some help... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MTA on non-standard port
Jeremy Chadwick wrote: On Fri, Oct 24, 2008 at 10:50:39AM -0500, Kevin Kinsey wrote: Hello, For various reasons, I find myself in need of an MTA accepting submission on a port other than 587 (or 25). It'd be Real Nice(tm) if sendmail could Just Do It, but I'd be willing to look at other options as well, as long as I can get a good spam solution to play nice with the server (currently I'm running dual-sendmail with Amavisd-new and spamassassin). Anyone doing such a thing, or have a few hints handy? It can do it. See the DAEMON_OPTIONS macro in your /etc/mail/hostname.mc file. (Remember: DO NOT edit sendmail.cf directly). Here's a hint: http://www.sendmail.org/~gshapiro/8.10.Training/DaemonPortOptions.html And here is a snip from a box I run sendmail on port 24.. It is from the [hostname].mc file: dnl Enable for both IPv4 and IPv6 (optional) DAEMON_OPTIONS(`Name=IPv4, Family=inet') dnl DAEMON_OPTIONS(`Name=IPv6, Family=inet6, Modifiers=O') DAEMON_OPTIONS(`Port=24, Name=MTA, M=EC') ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
LIST
LIST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
root | su
Is there a way of stopping root from su'ing to another user? Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: duplicate a drive
On Fri, 24 Oct 2008, Joey Mingrone wrote: The next thing I've tried to do, without success, is mirror the contents of the 2.5 drive to a 3.5 drive in the desktop. The 2.5 drive is sliced/partitioned like this: Filesystem SizeMounted on /dev/ad0s2a 989M / /dev/ad0s2d 989M /tmp /dev/ad0s2f 59G /usr /dev/ad0s2e 989M /var ad0s1 is a 20GB slice that I have window installed on. The drive's total capacity is 80G. The 3.5 drive is only 70G so I'll have to skip the ad0s1 slice. Ideally what I'd like to do is copy everything from the ad0s2 slice to the 3.5 and run the OS off that drive. Then, each dump the contents of the 3.5 drive to the 2.5 drive. That way if either drive dies I'll, hopefully at worst, just have to switch which drive I boot from. Can anyone with experience doing something this make suggestions? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Drive Disconnection
I have an external Lacie 1Tb drive attached to a FreeBSD 6.4-PRERELEASE system via an ESATA connection. atapci0: SiI SiI 3512 SATA150 controller I cleaned off the drive by writing random data to it. The write took overnight and didn't experience any problems. I then added a filesystem to the drive and mounted it on the system. However when I perform an rsync backup from a FreeBSD 7.1 PRERELEASE system to the drive over an NFS connection the drive disconnects and the server reboots. Does anyone have an idea where to go from here? -- Mark Jacobs Time Customer Service Tampa, FL $100 placed at 7 percent interest compounded quarterly for 200 years will increase to more than $100,000,000 -- by which time it will be worth nothing. Robert A. Heinlein Time Enough for Love (1973) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
On Fri, Oct 24, 2008 at 2:06 PM, Jos Chrispijn [EMAIL PROTECTED] wrote: Is there a way of stopping root from su'ing to another user? Short of disabling the user account you are `su'ing to (or disabling root), no. Root can do anything. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
Jos Chrispijn wrote: Is there a way of stopping root from su'ing to another user? Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Root is supposed to be the almighty god on your machine (i.e. you...). No point trying to limit the abilities of root (especially if physical access is also provided). And seriously, root is a role not a person. If you find yourself trying to limit root's capabilities, you've probably surrendered the root password to the wrong person. If you need to give someone limited root access to a machine, just use security/sudo instead (with a carefully crafted sudoers file). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Extract Songs from DVD
On Wed, 22 Oct 2008 17:34:41 +0300 Odhiambo Washington [EMAIL PROTECTED] wrote: I bought an original DVD but I cannot play that in my car's audio player. Is there a tool that I can use to get the songs off the DVD in WAV format, or even MP3? If you're looking for graphical toolsI've used dvdrip to rip audio tracks into wav files. Look at the faq at http://www.exit1.org/dvdrip/ For mp3 encoding I've used k3b or any other frontend graphical tool. /usr/ports/multimedia/dvdrip /usr/ports/sysutils/k3b ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
Jos Chrispijn wrote: Is there a way of stopping root from su'ing to another user? what kind of question is this? -- en0f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
--- On Fri, 10/24/08, Manolis Kiagias [EMAIL PROTECTED] wrote: From: Manolis Kiagias [EMAIL PROTECTED] Subject: Re: root | su To: Jos Chrispijn [EMAIL PROTECTED] Cc: FreeBSD Questions freebsd-questions@freebsd.org Date: Friday, October 24, 2008, 2:25 PM Jos Chrispijn wrote: Is there a way of stopping root from su'ing to another user? Jos Chrispijn Root is supposed to be the almighty god on your machine (i.e. you...). No point trying to limit the abilities of root (especially if physical access is also provided). And seriously, root is a role not a person. If you find yourself trying to limit root's capabilities, you've probably surrendered the root password to the wrong person. If you need to give someone limited root access to a machine, just use security/sudo instead (with a carefully crafted sudoers file). That's one option. Another is to implement jails, or virtualization via something like qemu. Since the person asking didn't give any details of what he wants to do, it's hard to say, but your point is correct regardless. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Running legacy i386 binaries on a amd64
When I try to run the binaries, the following error message is displayed: ELF interpreter /libexec/ld-elf32.so.1 not found Abort I found the following tip to install 32bits libraries: cd /usr/src make build32 make install32 ldconfig -32 /usr/lib32 Is that enough? should be. unless there are no needed libs in /usr/lib32 still, then find them and copy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
en0f wrote: Jos Chrispijn wrote: Is there a way of stopping root from su'ing to another user? what kind of question is this? Obviously one that brings out of the woodwork the type of people with closed and non-inquisitive minds... probably the type of people who think that they have all of life's questions answered :) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mpd - lcp protocol rejects
Hello, I'm running mpd 4.4 on 6.3-STABLE #4. Connecting with mpd to my ISP's VPN server running poptop. Everything is ok for some time, and then all of a sudden mpd starts throwing weird protocol rejects to log file and vpn connection stops working. mpd.conf: pptp: new -i ng0 pptp pptp set iface disable on-demand set iface disable proxy-arp set iface enable tcpmssfix set iface up-script /usr/local/etc/mpd4/if_up.sh set iface down-script /usr/local/etc/mpd4/if_down.sh set iface idle 0 set bundle disable multilink set bundle yes compression set bundle disable noretry set bundle enable crypt-reqd set auth authname login_here set link accept acfcomp protocomp set link accept chap set link keep-alive 10 60 set link max-redial 0 set link accmap 0x set ipcp yes vjcomp set ccp yes mppc set ccp yes mpp-compress set ccp no mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless open mpd.links: pptp: set phys type pptp set pptp peer [ISP's vpn serv here] set pptp enable originate set pptp disable incoming set pptp enable windowing And lots of logs: Oct 19 03:06:10 tazek mpd: [pptp] PPTP call successful Oct 19 03:06:10 tazek mpd: [pptp] link: UP event Oct 19 03:06:10 tazek mpd: [pptp] link: origination is local Oct 19 03:06:10 tazek mpd: [pptp] LCP: Up event Oct 19 03:06:10 tazek mpd: [pptp] LCP: state change Starting -- Req-Sent Oct 19 03:06:10 tazek mpd: [pptp] LCP: SendConfigReq #1 Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACCMAP 0x000a Oct 19 03:06:10 tazek mpd: MRU 1460 Oct 19 03:06:10 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:10 tazek mpd: [pptp] LCP: rec'd Configure Request #1 (Req-Sent) Oct 19 03:06:10 tazek mpd: ACCMAP 0x Oct 19 03:06:10 tazek mpd: AUTHPROTO CHAP MSOFTv2 Oct 19 03:06:10 tazek mpd: MAGICNUM 0b145760 Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: [pptp] LCP: SendConfigAck #1 Oct 19 03:06:10 tazek mpd: ACCMAP 0x Oct 19 03:06:10 tazek mpd: AUTHPROTO CHAP MSOFTv2 Oct 19 03:06:10 tazek mpd: MAGICNUM 0b145760 Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: [pptp] LCP: state change Req-Sent -- Ack-Sent Oct 19 03:06:12 tazek mpd: [pptp] LCP: SendConfigReq #2 Oct 19 03:06:12 tazek mpd: ACFCOMP Oct 19 03:06:12 tazek mpd: PROTOCOMP Oct 19 03:06:12 tazek mpd: ACCMAP 0x000a Oct 19 03:06:12 tazek mpd: MRU 1460 Oct 19 03:06:12 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:12 tazek mpd: [pptp] LCP: rec'd Configure Ack #2 (Ack-Sent) Oct 19 03:06:12 tazek mpd: ACFCOMP Oct 19 03:06:12 tazek mpd: PROTOCOMP Oct 19 03:06:12 tazek mpd: ACCMAP 0x000a Oct 19 03:06:12 tazek mpd: MRU 1460 Oct 19 03:06:12 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:12 tazek mpd: [pptp] LCP: state change Ack-Sent -- Opened Oct 19 03:06:12 tazek mpd: [pptp] LCP: auth: peer wants CHAP, I want nothing Oct 19 03:06:12 tazek mpd: [pptp] LCP: LayerUp Oct 19 03:06:12 tazek mpd: [pptp] CHAP: rec'd CHALLENGE #19 Oct 19 03:06:12 tazek mpd: Name: pptpd Oct 19 03:06:12 tazek mpd: Using authname login_here Oct 19 03:06:12 tazek mpd: [pptp] CHAP: sending RESPONSE len:63 Oct 19 03:06:12 tazek mpd: [pptp] CHAP: rec'd SUCCESS #19 Oct 19 03:06:12 tazek mpd: MESG: S=376C81163CF8923DF663DC2D672D8802BBDAAD3B Oct 19 03:06:12 tazek mpd: [pptp] LCP: authorization successful Oct 19 03:06:12 tazek mpd: [pptp] Bundle up: 1 link, total bandwidth 64000 bps Oct 19 03:06:12 tazek mpd: [pptp] IPCP: Open event Oct 19 03:06:12 tazek mpd: [pptp] IPCP: state change Initial -- Starting Oct 19 03:06:12 tazek mpd: [pptp] IPCP: LayerStart Oct 19 03:06:12 tazek mpd: [pptp] CCP: Open event Oct 19 03:06:12 tazek mpd: [pptp] CCP: state change Initial -- Starting Oct 19 03:06:12 tazek mpd: [pptp] CCP: LayerStart Oct 19 03:06:12 tazek mpd: [pptp] IPCP: Up event Oct 19 03:06:12 tazek mpd: [pptp] IPCP: state change Starting -- Req-Sent Oct 19 03:06:12 tazek mpd: [pptp] IPCP: SendConfigReq #1 Oct 19 03:06:12 tazek mpd: IPADDR 192.168.1.2 Oct 19 03:06:12 tazek mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Oct 19 03:06:12 tazek mpd: [pptp] CCP: Up event Oct 19 03:06:12 tazek mpd: [pptp] CCP: state change Starting -- Req-Sent Oct 19 03:06:12 tazek mpd: [pptp] CCP: SendConfigReq #1 Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:0x0141:MPPC, MPPE(128 bits), stateless Oct 19 03:06:12 tazek mpd: [pptp] IPCP: rec'd Terminate Ack #1 (Req-Sent) Oct 19 03:06:12 tazek mpd: [pptp] CCP: rec'd Configure Nak #1 (Req-Sent) Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:0x0140:MPPE(128 bits), stateless Oct 19 03:06:12 tazek mpd: [pptp] CCP: SendConfigReq #2 Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:
mpd - lcp protocol rejects
Hello, I'm running mpd 4.4 on 6.3-STABLE #4. Connecting with mpd to my ISP's VPN server running poptop. Everything is ok for some time, and then all of a sudden mpd starts throwing weird protocol rejects to log file and vpn connection stops working. mpd.conf: pptp: new -i ng0 pptp pptp set iface disable on-demand set iface disable proxy-arp set iface enable tcpmssfix set iface up-script /usr/local/etc/mpd4/if_up.sh set iface down-script /usr/local/etc/mpd4/if_down.sh set iface idle 0 set bundle disable multilink set bundle yes compression set bundle disable noretry set bundle enable crypt-reqd set auth authname login_here set link accept acfcomp protocomp set link accept chap set link keep-alive 10 60 set link max-redial 0 set link accmap 0x set ipcp yes vjcomp set ccp yes mppc set ccp yes mpp-compress set ccp no mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless open mpd.links: pptp: set phys type pptp set pptp peer [ISP's vpn serv here] set pptp enable originate set pptp disable incoming set pptp enable windowing And lots of logs: Oct 19 03:06:10 tazek mpd: [pptp] PPTP call successful Oct 19 03:06:10 tazek mpd: [pptp] link: UP event Oct 19 03:06:10 tazek mpd: [pptp] link: origination is local Oct 19 03:06:10 tazek mpd: [pptp] LCP: Up event Oct 19 03:06:10 tazek mpd: [pptp] LCP: state change Starting -- Req-Sent Oct 19 03:06:10 tazek mpd: [pptp] LCP: SendConfigReq #1 Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACCMAP 0x000a Oct 19 03:06:10 tazek mpd: MRU 1460 Oct 19 03:06:10 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:10 tazek mpd: [pptp] LCP: rec'd Configure Request #1 (Req-Sent) Oct 19 03:06:10 tazek mpd: ACCMAP 0x Oct 19 03:06:10 tazek mpd: AUTHPROTO CHAP MSOFTv2 Oct 19 03:06:10 tazek mpd: MAGICNUM 0b145760 Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: [pptp] LCP: SendConfigAck #1 Oct 19 03:06:10 tazek mpd: ACCMAP 0x Oct 19 03:06:10 tazek mpd: AUTHPROTO CHAP MSOFTv2 Oct 19 03:06:10 tazek mpd: MAGICNUM 0b145760 Oct 19 03:06:10 tazek mpd: PROTOCOMP Oct 19 03:06:10 tazek mpd: ACFCOMP Oct 19 03:06:10 tazek mpd: [pptp] LCP: state change Req-Sent -- Ack-Sent Oct 19 03:06:12 tazek mpd: [pptp] LCP: SendConfigReq #2 Oct 19 03:06:12 tazek mpd: ACFCOMP Oct 19 03:06:12 tazek mpd: PROTOCOMP Oct 19 03:06:12 tazek mpd: ACCMAP 0x000a Oct 19 03:06:12 tazek mpd: MRU 1460 Oct 19 03:06:12 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:12 tazek mpd: [pptp] LCP: rec'd Configure Ack #2 (Ack-Sent) Oct 19 03:06:12 tazek mpd: ACFCOMP Oct 19 03:06:12 tazek mpd: PROTOCOMP Oct 19 03:06:12 tazek mpd: ACCMAP 0x000a Oct 19 03:06:12 tazek mpd: MRU 1460 Oct 19 03:06:12 tazek mpd: MAGICNUM bc85bd60 Oct 19 03:06:12 tazek mpd: [pptp] LCP: state change Ack-Sent -- Opened Oct 19 03:06:12 tazek mpd: [pptp] LCP: auth: peer wants CHAP, I want nothing Oct 19 03:06:12 tazek mpd: [pptp] LCP: LayerUp Oct 19 03:06:12 tazek mpd: [pptp] CHAP: rec'd CHALLENGE #19 Oct 19 03:06:12 tazek mpd: Name: pptpd Oct 19 03:06:12 tazek mpd: Using authname login_here Oct 19 03:06:12 tazek mpd: [pptp] CHAP: sending RESPONSE len:63 Oct 19 03:06:12 tazek mpd: [pptp] CHAP: rec'd SUCCESS #19 Oct 19 03:06:12 tazek mpd: MESG: S=376C81163CF8923DF663DC2D672D8802BBDAAD3B Oct 19 03:06:12 tazek mpd: [pptp] LCP: authorization successful Oct 19 03:06:12 tazek mpd: [pptp] Bundle up: 1 link, total bandwidth 64000 bps Oct 19 03:06:12 tazek mpd: [pptp] IPCP: Open event Oct 19 03:06:12 tazek mpd: [pptp] IPCP: state change Initial -- Starting Oct 19 03:06:12 tazek mpd: [pptp] IPCP: LayerStart Oct 19 03:06:12 tazek mpd: [pptp] CCP: Open event Oct 19 03:06:12 tazek mpd: [pptp] CCP: state change Initial -- Starting Oct 19 03:06:12 tazek mpd: [pptp] CCP: LayerStart Oct 19 03:06:12 tazek mpd: [pptp] IPCP: Up event Oct 19 03:06:12 tazek mpd: [pptp] IPCP: state change Starting -- Req-Sent Oct 19 03:06:12 tazek mpd: [pptp] IPCP: SendConfigReq #1 Oct 19 03:06:12 tazek mpd: IPADDR 192.168.1.2 Oct 19 03:06:12 tazek mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Oct 19 03:06:12 tazek mpd: [pptp] CCP: Up event Oct 19 03:06:12 tazek mpd: [pptp] CCP: state change Starting -- Req-Sent Oct 19 03:06:12 tazek mpd: [pptp] CCP: SendConfigReq #1 Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:0x0141:MPPC, MPPE(128 bits), stateless Oct 19 03:06:12 tazek mpd: [pptp] IPCP: rec'd Terminate Ack #1 (Req-Sent) Oct 19 03:06:12 tazek mpd: [pptp] CCP: rec'd Configure Nak #1 (Req-Sent) Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:0x0140:MPPE(128 bits), stateless Oct 19 03:06:12 tazek mpd: [pptp] CCP: SendConfigReq #2 Oct 19 03:06:12 tazek mpd: MPPC Oct 19 03:06:12 tazek mpd:
Re: LIST
Sorry guys, didn't pay attention on this one. Uit een eerder bericht (24-10-2008 20:07): LIST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
Since the person asking didn't give any details of what he wants to do, it's hard to say, but your point is correct regardless. The idea behind my question is this: I am responsible for a server on which an(other) idiot keeps loggin in as user root, allthough he has his own user account and is part of the wheel group. To prevent this nub to change any other user account in God mode, I am searching for a solutions on this. jc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
Jos Chrispijn wrote: Since the person asking didn't give any details of what he wants to do, it's hard to say, but your point is correct regardless. The idea behind my question is this: I am responsible for a server on which an(other) idiot keeps loggin in as user root, allthough he has his own user account and is part of the wheel group. To prevent this nub to change any other user account in God mode, I am searching for a solutions on this. Instead of using the root account, could you make him use sudo, without the ability to su? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
--- On Fri, 10/24/08, Jos Chrispijn [EMAIL PROTECTED] wrote: From: Jos Chrispijn [EMAIL PROTECTED] Subject: Re: root | su To: Cc: freebsd-questions@freebsd.org Date: Friday, October 24, 2008, 4:45 PM Since the person asking didn't give any details of what he wants to do, it's hard to say, but your point is correct regardless. The idea behind my question is this: I am responsible for a server on which an(other) idiot keeps loggin in as user root, allthough he has his own user account and is part of the wheel group. To prevent this nub to change any other user account in God mode, I am searching for a solutions on this. Disable direct access via whatever remote access method you use as root. Thus the other individual will have to login as themself, and su to root. If you do not wish them to su to root, change the root password. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root | su
On Fri, Oct 24, 2008 at 10:45:04PM +0200, Jos Chrispijn wrote: Since the person asking didn't give any details of what he wants to do, it's hard to say, but your point is correct regardless. The idea behind my question is this: I am responsible for a server on which an(other) idiot keeps loggin in as user root, allthough he has his own user account and is part of the wheel group. To prevent this nub to change any other user account in God mode, I am searching for a solutions on this. You're trying to solve a social (possibly personal?) problem with technology. Simply put, this is a bad idea. I would highly recommend you either talk to the idiot and explain to him why what he's doing is improper or foolish, or simply pull his root access entirely. If this is a work-related incident, talk to your boss about it if at all possible (but see below). If you call the shots, simply yank their access. Here's you a story, maybe to lighten up my above criticism. I hope you enjoy it. Back in the early-to-mid-90s I worked at a small ISP in Palo Alto as a combination junior SA (sans root) and phone support monkey. There were two people who had root access on the FreeBSD boxes: one fellow was a clueful, friendly, and very technical UNIX system administrator (also partial owner), and another fellow (also partial owner) who was a complete tool -- imagine Dilbert's boss with basic UNIX CLI and how to plug in Ethernet knowledge. One day, we got some phone calls from customers stating they were having authentication dial-up problems or something (I can't remember). I didn't have root access to determine what the problem was, so I called up the UNIX SA and told him what was going on. He sighed, then agreed to take a look. About 15 minutes later he called back stating he'd fixed it. The next day, we started getting calls from customers again -- same issue. I called the SA (didn't you fix this yesterday?!?!), he sighed again, and 15 minutes later had it fixed. I asked what the deal was, and all he said was I'll explain it next time I'm in the office. A few weeks later I saw him and reminded him of the incident. The other individual who had root -- who also just happened to be my boss -- had gotten on the box in the middle of the night and decided to basically screw with things, telling no one. After the UNIX SA had fixed things the first time, that night my boss went back and screwed with things a second time, leaving things in a completely broken state again -- and like before, told no one. How is this even possible? I asked. The SA explained that he had worked with my boss at previous jobs, and he was known for doing this sort of thing, hence the sighing. I believe his words were Whenever something crazy would happen to the systems at old job, we'd almost always find traces of boss having logged in and modified seemingly random config files, broke things, and left them that way. He'd often do this at absurd hours of the night, almost as if he didn't want someone catching him in the process. I asked how he dealt with the situation, and he said At the previous job? His root access was eventually removed, as it was the only way. At this job? Well, let's just say the Email conversation is quite heated and will soon be involving the guys who financially back us. Food for thought. Cheers! -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED] Re: root | su
You're trying to solve a social (possibly personal?) problem with technology. Simply put, this is a bad idea. Yep, I think that is .true. I would highly recommend you either talk to the idiot and explain to him why what he's doing is improper or foolish, or simply pull his root access entirely. If this is a work-related incident, talk to your boss about it if at all possible (but see below). If you call the shots, simply yank their access. The idiot is the boss himself and acts like an unguided missile. Just investigating before I give him a wake-up call. And that is exactly what I will do... Food for thought. Cheers! Love it, thanks for sharing (everyone)! jc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: duplicate a drive
On Fri, Oct 24, 2008 at 01:29:18PM -0300, Joey Mingrone wrote: Hi, My laptop died recently and to get back to work as quickly as possible I simply took the laptop ide drive and put it into an old desktop using a 2.5 - 3.5 ide adapter. After loading a few new drivers into the kernel everything is working quite well. The next thing I've tried to do, without success, is mirror the contents of the 2.5 drive to a 3.5 drive in the desktop. The 2.5 drive is sliced/partitioned like this: Filesystem SizeMounted on /dev/ad0s2a 989M / /dev/ad0s2d 989M /tmp /dev/ad0s2f 59G /usr /dev/ad0s2e 989M /var ad0s1 is a 20GB slice that I have window installed on. The drive's total capacity is 80G. The 3.5 drive is only 70G so I'll have to skip the ad0s1 slice. Ideally what I'd like to do is copy everything from the ad0s2 slice to the 3.5 and run the OS off that drive. Then, each dump the contents of the 3.5 drive to the 2.5 drive. That way if either drive dies I'll, hopefully at worst, just have to switch which drive I boot from. Can anyone with experience doing something this make suggestions? Are you saying that you have 70GB available on the 3.5 drive? So the 64 GB of the 2.5 drive (not counting the MS part) will fit? It is going to be really tight, but it should be doable. Maybe you can actually trim that /usr partition down a little if it isn't full. To do all of what you want (according to what you say here) you will either have to use a fixit CD boot or multiple passes with the current disks. Presuming you will just nuke that MS part, you can do the following. (you might actually be able to use a utility such as gpart or Partition Magic to squeeze that MS slice down enough to keep it if you want if /usr is not very full, or you can just leave it alone where it is) It sounds like you are currently booting from the 2.5 drive from the laptop. If that is true, you only need two major steps. First, you will need to be able to put both drives in to the desktop machine and mount their filesystems (except the ms part). Lets say, when you finally get that accomplished, that they device name out as: 2.5 MS slice = ad0s1 2.5 FreeBSD slice = ad0s2 3.5 Old drive = ad1 If the names come out differently, then you will have to adjust. Boot the system up on the 2.5 drive. Wipe and initialize the 3.5 disk with fdisk. Doing a dd to it first might make it go more smoothly. It may not be needed. dd if=/dev/zero of=/dev/ad1 bs=512 count=1000 fdisk fdisk -BI ad1 That fdisk initializes it and puts on an MBR - the standard FreeBSD one. This form makes it all in one large slice - so it creates ad1s1 Now, use bsdlabel to create the partition table and write the boot block on it. bsdlabel -w -B ad1s1 The boot block is where the system jumps from the MBR when you select to boot that slice (if there is only one slice, there is no selection, it just goes there after doing MBR stuff). Now, edit the partition table in slice one to have the partitions you want. bsdlabel -e ad1s1 This will bring up an edit screen - probably in vi unless you have set your main editor to something else. In that screen, it will show only the c: partition as containing the whole space and marked unused and a note to 'don't edit'. It will look something like this: 8 partitions: #size offset fstype [fsize bsize bps/cpg] c: 78316875 0unused 0 0 # raw part, don't edit Do not change the c partition line. But, the easiest way to make new lines is to copy it. In vi do that by putting the cursor on it and hitting dd then hitting p enough times for the number of copies you want (6 times in this case). One thing you didn't mention was swap. It is normal to make the 'b' partition be swap space. Maybe you left that out because it doesn't show up in a df. But, your system needs it. So, then change the first line to be an a partition. Make it a BSD4.2 type.Make the second line a b partition and change its type to swap Make your d, e and f partition lines. The offset for both the c and the a partions should be 0 After that you don't have to worry, because newer versions of bsdlabel (and the previous disklabel) will calculate the offsets for you. It will also calculate the size of the last partition if you want it to be a catch all for the amount of space that remains. (Usually one makes that the largest one then) To get it to do the calculations, just put an asterisk in the field. Note: the sizes are given in 512 byte blocks. You can use others such as 1G or 1024M for 1GB, but I find this easier to keep track of. It should look something like the following. This example makes r00t, swap, tmp, var all be 1GB and usr (part f) get all the rest. 8 partitions: #size offset fstype [fsize bsize bps/cpg] a: 20971520 4.2BSD2048 16384 32776 b: 2097152*
mount_cd9660 /dev/cd0 /mnt =input output error
I tried to mount my data CD by using mount_cd9660 /dev/cd0/mnt and I got input ,output error . And now ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Drive Disconnection
On Fri, Oct 24, 2008 at 02:02:41PM -0400, Mark Jacobs wrote: I have an external Lacie 1Tb drive attached to a FreeBSD 6.4-PRERELEASE system via an ESATA connection. atapci0: SiI SiI 3512 SATA150 controller I cleaned off the drive by writing random data to it. The write took overnight and didn't experience any problems. I then added a filesystem to the drive and mounted it on the system. However when I perform an rsync backup from a FreeBSD 7.1 PRERELEASE system to the drive over an NFS connection the drive disconnects and the server reboots. You've not provided enough information to help track this down. What model/brand of disk is attached to that controller? What does smartctl -a have to say about the disk? What gets printed on the console before it reboots? Do you have the same problem if you run 7.1-PRERELEASE/BETA2? Does anyone have an idea where to go from here? The only generic advice I can give you at this point) is to avoid Silicon Image controllers, particularly their SATA controllers. They have a history of causing data corruption on Linux, FreeBSD, and Windows, and some have reported other miscellaneous problems with them as well. There's not enough evidence in this thread so far to blame the SiI controller, but when I see them, I become immediately suspicious. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble Shutting down
** Forgot to CC the list, in case anyone is actually watching this thread.** Theirs nothing in the /etc/X11 folder or a xorg.conf file, I think Xorg automatically did everything Well, if you say you ran 'X -configure', it should've created an xorg.conf file. If you ran it as root (which you almost probably had to), check in /root From what you've told me before, I can pretty well guess that you don't have your necessary Xorg drivers installed for your graphics card. I suggest reading the manual on how to resolve this -- but don't expect miracles as far as ATI goes. If you don't know how to manage Xorg, I doubt you should be running -CURRENT. -- Glen Barber -- Glen Barber 570.328.0318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mount_cd9660 /dev/cd0 /mnt =input output error
On Fri, 24 Oct 2008 21:06:44 -0200, luizbcampos [EMAIL PROTECTED] wrote: I tried to mount my data CD by using mount_cd9660 /dev/cd0/mnt and I got input ,output error . And now (1) Did you try # mount -t cd9660 /dev/acd0 /mnt to check the correct working of the drive, just in case it is a ATAPI drive? If it's a SCSI drive, /dev/cd0 is completely correct. (2) Does the CD contain a data track? # cdcontrol -f /dev/cd0 info Did you check this (for redundancy) on another machine? The error message input output error usually indicates an error of this kind. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does adding /usr/lib32 to LD_LIBRARY_PATH break 64-bit binaries?
On Friday 24 October 2008 23:20:59 Peter Jeremy wrote: this will make system trying to bind 32-bit libs to 64-bit program. it can't work rtld shouldn't attempt to bind 32-bit libs to 64-bit programs. The same problem happens with the Linux run time linker - it merrily tries to link FreeBSD libraries to Linux binaries with predictable results.. One trick I use for that is to put a symlink in /compat/linux in the place the problematic FreeBSD library is.. That said it would be really nice if it ignored incompatible libraries :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
RE: Drive Disconnection
It is a Lacie d2 quadra drive but FreeBSD reports this; server kernel: ad4: 953869MB Hitachi HDS721010KLA330 GKAOA70M at ata2-master SATA150 When I perform the RSYNC I receive these errors Oct 24 12:47:13 server kernel: ad4: FAILURE - device detached Oct 24 12:47:13 server kernel: subdisk4: detached Oct 24 12:47:13 server kernel: ad4: detached Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332767232, length=131072)]error = 6 Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332898304, length=131072)]error = 6 The write failure messages keep on being issued until the server reboots. It isn't in the log, but I receive a dirty buffer panic. I don't have easy access to a 7.1 system with an ESATA port. I'm current redoing the entire process, wipe, build filesystem, mount, rsync using the USB port. If that works I'm going to junk the idea of using the ESATA card for the drive. Can you recommend an ESATA card that fits in an PCI slot since my server doesn't have a PCI-E slot? Mark Jacobs -Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] Sent: Fri 10/24/2008 7:09 PM To: Jacobs, Mark - Data Center Operations [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: Drive Disconnection On Fri, Oct 24, 2008 at 02:02:41PM -0400, Mark Jacobs wrote: I have an external Lacie 1Tb drive attached to a FreeBSD 6.4-PRERELEASE system via an ESATA connection. atapci0: SiI SiI 3512 SATA150 controller I cleaned off the drive by writing random data to it. The write took overnight and didn't experience any problems. I then added a filesystem to the drive and mounted it on the system. However when I perform an rsync backup from a FreeBSD 7.1 PRERELEASE system to the drive over an NFS connection the drive disconnects and the server reboots. You've not provided enough information to help track this down. What model/brand of disk is attached to that controller? What does smartctl -a have to say about the disk? What gets printed on the console before it reboots? Do you have the same problem if you run 7.1-PRERELEASE/BETA2? Does anyone have an idea where to go from here? The only generic advice I can give you at this point) is to avoid Silicon Image controllers, particularly their SATA controllers. They have a history of causing data corruption on Linux, FreeBSD, and Windows, and some have reported other miscellaneous problems with them as well. There's not enough evidence in this thread so far to blame the SiI controller, but when I see them, I become immediately suspicious. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
tape format
Hello all Does anyone know if the tape format produced by Seagate backup is documented? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: duplicate a drive
On Fri, 24 Oct 2008 12:19:23 -0600 (MDT) Warren Block [EMAIL PROTECTED] wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK The best way is to reinstall the OS on the new disk, then move the user data over. This is highly recommended if you have been tracking -STABLE for more than one release, or have updated a release instead of installing a new one. Highly recommended seems a very strange thing for the FAQ to be saying. It's implying that FreeBSD base-system upgrades are a bit flaky. It even goes on Should you decide not to do a fresh install, as if to say you have been warned. Unless my experience is abnormal, we seem to be publishing our own FUD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tape format
On Fri, Oct 24, 2008, Ansar Mohammed wrote: Hello all Does anyone know if the tape format produced by Seagate backup is documented? You might get a hint using ``file /dev/tapedevice'' which should show if it's a tar, cpio, or whatever archive. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax:(206) 232-9186 Once at a social gathering, Gladstone said to Disraeli, I predict, Sir, that you will die either by hanging or of some vile disease. Disraeli replied, That all depends upon whether I embrace your principles or your mistress. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Drive Disconnection
On Fri, Oct 24, 2008 at 07:44:41PM -0400, [EMAIL PROTECTED] wrote: It is a Lacie d2 quadra drive but FreeBSD reports this; server kernel: ad4: 953869MB Hitachi HDS721010KLA330 GKAOA70M at ata2-master SATA150 When I perform the RSYNC I receive these errors Oct 24 12:47:13 server kernel: ad4: FAILURE - device detached Oct 24 12:47:13 server kernel: subdisk4: detached Oct 24 12:47:13 server kernel: ad4: detached Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332767232, length=131072)]error = 6 Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332898304, length=131072)]error = 6 The write failure messages keep on being issued until the server reboots. It isn't in the log, but I receive a dirty buffer panic. It appears the disk is literally falling off of the SATA bus. The g_vfs_done errors you see are a result of that. I'll explain the reboot in a moment. There could be tons of reasons for the disk disappearing. I'll list off some the possibilities that come to mind: * Drive losing power - Shoddiness inside of the d2 Quadra enclosure, such as bad internal cabling or manufacturing defects, - AC adapter for d2 Quadra is faulty, - d2 Quadra could offer some kind of sleep mode where the unit goes into a low-power-save state, and the disk ends up falling off the bus during this time. * SATA300 vs. SATA150 compatibility issues - VIA and SiS chipsets are known to experience data corruption, disks falling off the bus, or other insanity when SATA300 disks are connected to those chipsets. The chipsets support SATA300, but are downright buggy. Workaround is to force the drive to SATA150 speed using jumpers on the disk (only *some* manufacturers offer this), - The Hitachi disk in your d2 Quadra is spec'd at SATA300, while it's obvious your Silicon Image SATA controller is only detecting SATA150 (yet LaCie claims this enclosure does SATA300). The 7K1000 series drives *do not* have a force-SATA150 jumper (I've checked), which is too bad, since forcing SATA150 might fix the problem. * d2 Quadra USB/FW/eSATA controller bug - I have no idea what chip is inside of that enclosure, but many of them are bridges, e.g. they're USB/FW controllers that have a horribly shoddy SATA emulation interface on top of them, - Could be a firmware bug with the controller used in the enclosure, - Controller may not be 100% compatible with Silicon Image devices. * Silicon Image SATA controller bugs As for why the system reboots: what you're experiencing is probably a kernel panic. On FreeBSD, when you have a filesystem that's mounted and the underlying device (disk, etc.) is yanked out from underneath, the kernel will panic; this is by design. I've been told by lower-level folks that CURRENT supposedly addresses this issue, but I haven't personally confirmed it. I would still like to see SMART stats on the drive. Why? Because SMART stats will show me if the drive is actually losing power or not (the Power_Cycle_Count attribute should increment). You'll need to install ports/sysutils/smartmontools, then run smartctl -a /dev/ad4. Save that data somewhere, then run your rsync. Your machine will reboot (a soft reset, hopefully!), and once it's back up, run the same smartctl command again, and save that data. Then you can compare the adjusted attributes and RAW_VALUEs; I can help you with reading this data if need be (people often misread it). I don't have easy access to a 7.1 system with an ESATA port. That's disappointing, as it would be useful to know if 7.1-PRERELEASE behaves the same way for you. Based on the above I'd say it probably does, but it's always good to check. I'm current redoing the entire process, wipe, build filesystem, mount, rsync using the USB port. If that works I'm going to junk the idea of using the ESATA card for the drive. I would _highly_ recommend you reconsider this. USB on FreeBSD is in an even worse state (and I am not exaggerating) than ATA/SATA is. If your disk is falling off the bus with SATA, the same will likely happen with USB, and you'll experience the same problem. Can you recommend an ESATA card that fits in an PCI slot since my server doesn't have a PCI-E slot? Promise makes the SATA300 TX4302 controller, which is PCI, and provides two eSATA ports, plus two internal SATA ports. I believe this card goes for US$70-100. Promise's website (for me) appears to be malfunctioning (webserver answers, but stalls indefinitely), so I can't easily check their products list. I don't think HighPoint makes any eSATA-capable controllers that are standard PCI or PCI-X; all appear to be PCI Express. If your motherboard has on-board SATA support that *does not* use a Silicon Image, VIA, or SiS chip and instead something like an Intel ICH or nVidia nForce controller, I would recommend buying something like this and using it instead:
Where are Lock Order Reversals
Aloha, Loading a FreeBSD 8 Current I get Lock Order Reversals. There used to be a site for looking into them. What do we do now? ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: [EMAIL PROTECTED] All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Drive Disconnection
Thanks for all the great information. I'm going to try the USB solution for now since the drive was running fine for several months on this server w/USB until I began playing with the ESATA connection. If perchance USB doesn't work I will try both getting the SMART status from the drive and getting a better SATA controller. Mark Jacobs Technical Services Time Customer Service, Tampa FL (Go Rays) -Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] Sent: Fri 10/24/2008 9:15 PM To: Jacobs, Mark - Data Center Operations [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: Drive Disconnection On Fri, Oct 24, 2008 at 07:44:41PM -0400, [EMAIL PROTECTED] wrote: It is a Lacie d2 quadra drive but FreeBSD reports this; server kernel: ad4: 953869MB Hitachi HDS721010KLA330 GKAOA70M at ata2-master SATA150 When I perform the RSYNC I receive these errors Oct 24 12:47:13 server kernel: ad4: FAILURE - device detached Oct 24 12:47:13 server kernel: subdisk4: detached Oct 24 12:47:13 server kernel: ad4: detached Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332767232, length=131072)]error = 6 Oct 24 12:47:13 server kernel: g_vfs_done():ad4s1a[WRITE(offset=144332898304, length=131072)]error = 6 The write failure messages keep on being issued until the server reboots. It isn't in the log, but I receive a dirty buffer panic. It appears the disk is literally falling off of the SATA bus. The g_vfs_done errors you see are a result of that. I'll explain the reboot in a moment. There could be tons of reasons for the disk disappearing. I'll list off some the possibilities that come to mind: * Drive losing power - Shoddiness inside of the d2 Quadra enclosure, such as bad internal cabling or manufacturing defects, - AC adapter for d2 Quadra is faulty, - d2 Quadra could offer some kind of sleep mode where the unit goes into a low-power-save state, and the disk ends up falling off the bus during this time. * SATA300 vs. SATA150 compatibility issues - VIA and SiS chipsets are known to experience data corruption, disks falling off the bus, or other insanity when SATA300 disks are connected to those chipsets. The chipsets support SATA300, but are downright buggy. Workaround is to force the drive to SATA150 speed using jumpers on the disk (only *some* manufacturers offer this), - The Hitachi disk in your d2 Quadra is spec'd at SATA300, while it's obvious your Silicon Image SATA controller is only detecting SATA150 (yet LaCie claims this enclosure does SATA300). The 7K1000 series drives *do not* have a force-SATA150 jumper (I've checked), which is too bad, since forcing SATA150 might fix the problem. * d2 Quadra USB/FW/eSATA controller bug - I have no idea what chip is inside of that enclosure, but many of them are bridges, e.g. they're USB/FW controllers that have a horribly shoddy SATA emulation interface on top of them, - Could be a firmware bug with the controller used in the enclosure, - Controller may not be 100% compatible with Silicon Image devices. * Silicon Image SATA controller bugs As for why the system reboots: what you're experiencing is probably a kernel panic. On FreeBSD, when you have a filesystem that's mounted and the underlying device (disk, etc.) is yanked out from underneath, the kernel will panic; this is by design. I've been told by lower-level folks that CURRENT supposedly addresses this issue, but I haven't personally confirmed it. I would still like to see SMART stats on the drive. Why? Because SMART stats will show me if the drive is actually losing power or not (the Power_Cycle_Count attribute should increment). You'll need to install ports/sysutils/smartmontools, then run smartctl -a /dev/ad4. Save that data somewhere, then run your rsync. Your machine will reboot (a soft reset, hopefully!), and once it's back up, run the same smartctl command again, and save that data. Then you can compare the adjusted attributes and RAW_VALUEs; I can help you with reading this data if need be (people often misread it). I don't have easy access to a 7.1 system with an ESATA port. That's disappointing, as it would be useful to know if 7.1-PRERELEASE behaves the same way for you. Based on the above I'd say it probably does, but it's always good to check. I'm current redoing the entire process, wipe, build filesystem, mount, rsync using the USB port. If that works I'm going to junk the idea of using the ESATA card for the drive. I would _highly_ recommend you reconsider this. USB on FreeBSD is in an even worse state (and I am not exaggerating) than ATA/SATA is. If your disk is falling off the bus with SATA, the same will likely happen with USB, and you'll experience the same problem. Can you recommend an ESATA card that fits in an PCI slot since my server doesn't have a PCI-E slot? Promise makes the SATA300 TX4302 controller, which is PCI, and
WINE 21.1.5 QUESTION...
Maybe somebody here can clue me in on how to get a 1998, windose3.1/w95 French-learning game to work on my newly built wine. I asked on the Ubuntu forums and altho somebody did try to help; Zip. I do not have a clue to the DOS-path; it's a CDROM and since I'm using the top CD/DVD optical drive, I'm guessing that it D:\; right? since C:\ would be the harddrive. Otherwise, no clue. The disc is due back at the library soon so I want to make the most of it ... even if it does crash every 355 minutes! tia, people, gary -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: does hardware upgrade requires reconfiguration?
Thanks. I am using amd64 port and a custom compiled kernel with ULE scheduler. As of now, the system is working fine without any changes after the upgrade. Amitabh On Thu, Oct 23, 2008 at 11:54 AM, Ivailo Tanusheff [EMAIL PROTECTED] wrote: Hi, Well, the answer is both yes and no :) If you have compiled a kernel, which supports multiple processors: options SMP or you have copied most of /sys/hardware/conf/SMP the processor will be discovered and used without any additional configurations. If you currently use all 4GB RAM - PAE config or amd64 or simmilar branch - the extra RAM will be used without any reconfiguration. If any or both of the above are not true - you have to change the options in the kernel configuration file and recompile the kernel. Hope this will help you :) Regards, Ivailo Tanusheff Deputy Head of IT Department ProCredit Bank (Bulgaria) AD Amitabh Kant [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 23.10.2008 06:52 To freebsd-questions@freebsd.org cc Subject does hardware upgrade requires reconfiguration? Hi I currently have a single processor/4gb ram machine with me which I am thinking to upgrade to dual proc and 8gb ram. Does installing extra processor requires re-configuration or re-installation of the os? The extra processor will be mounted on the same motherboard. With regards Amitabh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
restrict gnome desktop user.
How do it configure gnome to restrict users to their home directory? I don't want them to be able see any system directories or other users? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
