Re: usb identity issue
what problems? Attach kernel output messages please. Woj... The thumb/flash drive is showing in the dmesg as ad1 but it is not available to use. da1 or ad1? what exactly not available to use means? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
at behaviour and man at inconsistency
From man: The at utility allows some moderately complex time specifications. It accepts times of the form HHMM or HH:MM to run a job at a specific time of day. (If that time is already past, the next day is assumed.) Current behavior: Ξ ~ → date Tue 24 Jul 2012 09:17:36 EEST Ξ ~ → at 09:18 echo tototo Job 1 will be executed using /bin/sh Ξ ~ → at 09:15 at: trying to travel back in time zsh: exit 1 at 09:15 Five, ok, may by more years ago, I don't remember exactly. at had worked like the man explain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PCBSD9.0-x64-DVD and Intel HD Graphics 2000
On 24.07.2012 01:12, David Christensen wrote: On 07/23/2012 03:37 AM, Vladislav wrote: http://wiki.freebsd.org/Intel_GPU Okay. I wrote: I've installed PCBSD9.0-x64-DVD on the following hardware: On 07/23/2012 06:30 AM, Erich Dollansky wrote: this where the problem starts. If nothing changed since I used this, it only supports VESA on i7 CPUs. Okay. I wrote: I have updated the system using Update Manager, and the problems persist. On 07/23/2012 06:30 AM, Erich Dollansky wrote: What does this affect? Also the FreeBSD part? I don't know. I am now running FreeBSD 10 on an i7 without any problems. It should also be possible to get the same result with a current 9.0. Do the same what I have done. Use PC-BSD just to get a machine running and then update to FreeBSD. I was hoping to find an OS distribution that works OOTB. The key features I'm looking for are: 1. Full support of my hardware; notably Enhanced Speed Step, AES-NI, Intel HD Graphics 2000 dual head, and SSD TRIM. 2. ZFS on encrypted partitions, including root. I guess I'll have to wait for PC-BSD 10 or FreeBSD 10. Thanks! David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Hi, What about the new Xorg(make.conf WITH_NEW_XORG=true) and drivers Intel? I have heard that this solution works, OpenGL too... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PCBSD9.0-x64-DVD and Intel HD Graphics 2000
On Sat, Jul 21, 2012 at 6:52 AM, David Christensen dpchr...@holgerdanske.com wrote: freebsd-questions: I've installed PCBSD9.0-x64-DVD on the following hardware: ... Also: http://lists.pcbsd.org/mailman/listinfo Sophoklis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
GTK30 failed install
Hello! configure: error: *** Can't find cairo-pdf.h. You must build Cairo with the pdf *** backend enabled. === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at gn...@freebsd.org, and attach (a) /usr/obj/usr/ports/x11-toolkits/gtk30/work/gtk+-3.0.12/config.log, (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list (gn...@freebsd.org), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/x11-toolkits/gtk30. *** Error code 1 Stop in /usr/ports/x11-toolkits/gtk30. # ls -l /usr/local/include/cairo total 147 9 -r--r--r-- 1 root wheel 8698 23 июл 15:57 cairo-deprecated.h 2 -r--r--r-- 1 root wheel 884 23 июл 15:57 cairo-features.h 3 -r--r--r-- 1 root wheel 2556 23 июл 15:57 cairo-ft.h 4 -r--r--r-- 1 root wheel 3527 23 июл 15:57 cairo-gl.h 7 -r--r--r-- 1 root wheel 6212 23 июл 15:57 cairo-gobject.h 4 -r--r--r-- 1 root wheel 3108 23 июл 15:57 cairo-pdf.h 5 -r--r--r-- 1 root wheel 3590 23 июл 15:57 cairo-ps.h 5 -r--r--r-- 1 root wheel 3852 23 июл 15:57 cairo-script-interpreter.h 4 -r--r--r-- 1 root wheel 2781 23 июл 15:57 cairo-svg.h 3 -r--r--r-- 1 root wheel 2164 23 июл 15:57 cairo-tee.h 1 -r--r--r-- 1 root wheel 148 23 июл 15:57 cairo-version.h 4 -r--r--r-- 1 root wheel 3197 23 июл 15:57 cairo-xcb.h 3 -r--r--r-- 1 root wheel 2436 23 июл 15:57 cairo-xlib-xrender.h 4 -r--r--r-- 1 root wheel 3057 23 июл 15:57 cairo-xlib.h 92 -r--r--r-- 1 root wheel 93134 23 июл 15:57 cairo.h # uname -psr FreeBSD 9.0-STABLE amd64 # pkg_info |grep cairo cairo-1.10.2_4,2 Vector graphics library with cross-device output support # make config Options for cairo 1.10.2_4,2 [*] GL Enable OpenGL Support [*] XCB Enable XCB (X C-language Binding) Support [*] GLIB Enable GObject Functions Feature Does anyone have any ideas to solve this problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Locally modifying ports
Chris Ross wrote: So, I've been a NetBSD user for many years, and am looking more at FreeBSD now. Trying to build myself a system, I find that I have a long-held delta to a package on my NetBSD system, and I keep it in a patch-local-* file in NetBSD pkgsrc. I can't figure out if FreeBSD ports has a way to keep and automatically apply local patches to ports. I want to modify the way the internals of a package/port operate, and not in a way that makes sense to move up- stream. It's just my preference. Is there a way in FreeBSD ports to keep a make this change to the source code after extracting and before compiling type of thing in the tree? Ports just has been transferred to subversion. With subversion you can apply your patches to the tree and subversion will maintain them notifying you on possible conflicts. I'm already using this one for the patches to Mk that hasn't been committed for a long time. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Locally modifying ports
Chris Ross cross+free...@distal.com wrote: So, I've been a NetBSD user for many years, and am looking more at FreeBSD now. Trying to build myself a system, I find that I have a long-held delta to a package on my NetBSD system, and I keep it in a patch-local-* file in NetBSD pkgsrc. I can't figure out if FreeBSD ports has a way to keep and automatically apply local patches to ports. I want to modify the way the internals of a package/port operate, and not in a way that makes sense to move up- stream. It's just my preference. Is there a way in FreeBSD ports to keep a make this change to the source code after extracting and before compiling type of thing in the tree? I'm not aware of something similar to pkgsrc's $LOCALPATCHES, but you can still drop local patches in the files directory of the port: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/slow-patch.html Fabian signature.asc Description: PGP signature
Re: Locally modifying ports
On 2012/07/24 12:14, Fabian Keil wrote:
Chris Ross cross+free...@distal.com wrote:
So, I've been a NetBSD user for many years, and am looking more
at FreeBSD now. Trying to build myself a system, I find that I have a
long-held delta to a package on my NetBSD system, and I keep it
in a patch-local-* file in NetBSD pkgsrc.
I can't figure out if FreeBSD ports has a way to keep and automatically
apply local patches to ports. I want to modify the way the internals of
a package/port operate, and not in a way that makes sense to move up-
stream. It's just my preference.
Is there a way in FreeBSD ports to keep a make this change to the
source code after extracting and before compiling type of thing in the
tree?
I'm not aware of something similar to pkgsrc's $LOCALPATCHES, but you
can still drop local patches in the files directory of the port:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/slow-patch.html
Fabian
I use in /etc/make.conf:
...
.if ${.CURDIR:M*/ports/x11-wm/openbox}
EXTRA_PATCHES+=/home/ok/patches/openbox/patch-VK-NULL_SELF_TITLE.diff
EXTRA_PATCHES+=/home/ok/patches/openbox/patch-VK-SPEED_FOCUS.diff
.endif
...
HTH
O.K.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
On Tue, Jul 24, 2012 at 12:47 AM, Polytropon free...@edvax.de wrote: On Mon, 23 Jul 2012 23:29:38 +0800, lei yang wrote: Yes, the second version I post is using the source from you supplied, then I compiled it, but it has no -U flag like what I post, it seems a version different casued this. Yes. The version distributed by the ports collection is different from that one supplied with the base system of FreeBSD. To try _that_ version, you can download the source tarball and extract it; in the directory # wget ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.0-RELEASE/src.txz # tar xvf src.txz Thanks for the help, tar xvf src.txz tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Read 4896 bytes from src.txz tar: Error exit delayed from previous errors [lyang0@ala-lpggp2 lyang0]$ tar xvf src.txz tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Read 4896 bytes from src.txz tar: Error exit delayed from previous errors # cd cusr/src/ontrib/netcat/ # ls FREEBSD-XlistFREEBSD-vendor atomicio.h netcat.c FREEBSD-upgrade atomicio.c nc.1 socks.c # your build command(s) here Suppose gcc -o netcat netcat.c atomicio.c socks.c should work Lei You can check the FTP server for other versions of the OS (e. g. different branch and architecture, starting at ftp://ftp.freebsd.org/pub/FreeBSD/releases/, then selecting architecture and finally the OS version). There are also different ways of obtaining the sources, but the solution shown here should be sufficient. (You can use tar xvf src.txz usr/src/contrib/netcat to only extract the files for netcat instead of everything, but it _might_ be possible that the build process needs some files from other locations.) If you don't have wget installed, stock ftp location command should also work for downloading. I don't know where to find the source code in Red Hat. Me neither, but check man hier on a RH system to get the documentation about the file system hierarchy which should have detailed information on what is stored where. -- Polytropon 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 freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
On Mon, Jul 23, 2012 at 11:52 PM, Alejandro Imass a...@p2ee.org wrote: On Mon, Jul 23, 2012 at 11:29 AM, lei yang yanglei.f...@gmail.com wrote: On Mon, Jul 23, 2012 at 10:36 PM, Polytropon free...@edvax.de wrote: On Mon, 23 Jul 2012 12:59:55 +0800, lei yang wrote: On Mon, Jul 23, 2012 at 12:25 AM, Polytropon free...@edvax.de wrote: On Sun, 22 Jul 2012 22:41:57 +0800, lei yang wrote: Hi, [...] I don't know where to find the source code in Red Hat. Why don't you just toss RedHat and use FreeBSD ? Most everything you run on Linux will run on FreeBSD and there are also Desktop-friendly distros of FreeBSD such as PC-BSD which, in Linux terms, is to FreeBSD somewhat akin to what Ubuntu is to Debian. Aha,I just want to learn want to know how to build the netcat for freebsd version on a no-freebsd platform Lei Anyway, give PC-BSD a try and you won't regret it: http://www.pcbsd.org/ Cheers, -- Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
On Tue, Jul 24, 2012 at 12:03 AM, Carl Johnson ca...@peak.org wrote: lei yang yanglei.f...@gmail.com writes: On Mon, Jul 23, 2012 at 12:25 AM, Polytropon free...@edvax.de wrote: On Sun, 22 Jul 2012 22:41:57 +0800, lei yang wrote: Hi, I want to build a netcat on my local pc (ubuntu) with gcc, is it possible? I'm new to free bsd it has no -U flag, can you point me where I get this version Have you checked the other version of netcat already available? A quick check shows these four versions for Ubuntu: netcat: TCP/IP swiss army knife -- transitional package netcat-openbsd: TCP/IP swiss army knife netcat-traditional: TCP/IP swiss army knife netcat6: TCP/IP swiss army knife with IPv6 support how did you get the list? To be clear, haha, I just want to know how to build a fress bsd netcat on a no-fressbsd platform Lei -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
is it possible to install freebsd on tablet?
hi I have a question, is it possible to install freebsd (or netbsd) on an android tablet? best regards, -- mru258 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: is it possible to install freebsd on tablet?
From: Mr U mru...@yahoo.com Date: Tue, 24 Jul 2012 04:34:14 -0700 (PDT) Subject: is it possible to install freebsd on tablet? hi I have a question, is it possible to install freebsd (or netbsd) on an android tablet? Authoritative answer: Theoetically poszible? yes. Realistically doable? Maybe. And it's a _big_ maybe. It depends on the -exact- hardware details of the tablet device in question. If the particular make/model of tablet is not explicitly listed in the 'supported hardware' list ffor the vesion of FreeBSD that you are consideing, then it will take a -lot- of research to deteming whether FreeBSD will run without modification on that device. If there are 'unsupported peripherrals' inside the tablet, then a major progamming effort would be requied. The hard truth is that if you have to ask, you probably don't have the skills to deal with anything that is not expessly listed in the hadware copatibilityy list in the O/S release notes for the O/S vesion you are consideing installing. Getting 'architectual internals' details about non pc-clone hardware is generally _not_ easy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PCBSD9.0-x64-DVD and Intel HD Graphics 2000
2012/7/24 ufs u...@poniki.net On 24.07.2012 01:12, David Christensen wrote: On 07/23/2012 03:37 AM, Vladislav wrote: http://wiki.freebsd.org/Intel_**GPU http://wiki.freebsd.org/Intel_GPU Okay. I wrote: I've installed PCBSD9.0-x64-DVD on the following hardware: On 07/23/2012 06:30 AM, Erich Dollansky wrote: this where the problem starts. If nothing changed since I used this, it only supports VESA on i7 CPUs. Okay. I wrote: I have updated the system using Update Manager, and the problems persist. On 07/23/2012 06:30 AM, Erich Dollansky wrote: What does this affect? Also the FreeBSD part? I don't know. I am now running FreeBSD 10 on an i7 without any problems. It should also be possible to get the same result with a current 9.0. Do the same what I have done. Use PC-BSD just to get a machine running and then update to FreeBSD. I was hoping to find an OS distribution that works OOTB. The key features I'm looking for are: 1. Full support of my hardware; notably Enhanced Speed Step, AES-NI, Intel HD Graphics 2000 dual head, and SSD TRIM. 2. ZFS on encrypted partitions, including root. I guess I'll have to wait for PC-BSD 10 or FreeBSD 10. Thanks! David __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org Hi, What about the new Xorg(make.conf WITH_NEW_XORG=true) and drivers Intel? I have heard that this solution works, OpenGL too... I tried WITH_NEW_XORG=true and WITH_KMS=true with Core i5-3450 and 9.1-prerelease last weekend. It was so slow, that I decided to buy the cheapest Nvidia card. __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org -- AP ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Removing sendmail from an installed system
Darren Pilgrim list_free...@bluerosetech.com writes: I'm removing sendmail entirely from an installed system. I had WITHOUT_SENDMAIL in /etc/src.conf when I updated to RELENG_8_3, but that left an old version of sendmail rotting away on disk. This is the list I have so far: /etc/mail/* (excluding mailer.conf) /etc/rc.d/sendmail /usr/bin/vacation /usr/libexec/mail.local /usr/libexec/sendmail /usr/libexec/smrsh /usr/sbin/editmap /usr/sbin/mailstats /usr/sbin/makemap /usr/sbin/praliases /usr/share/sendmail /var/spool/clientmqueue /var/spool/mqueue Is this list complete? I'm intentionally leaving the stuff for mailwrapper. I'm ok with leaving /etc/rc.d/sendmail behind as well, but it looks like it's not needed by anything (i.e., nothing requires mail). make delete-old; see the section Deleting obsolete files, directories and libraries in the handbook. Even though I have WITHOUT_SENDMAIL specified and the world was built with that, mergemaster still installs /etc/mail/aliases and /etc/rc.d/sendmail. Is there a way to prevent this other than adding them to IGNORE_FILES in mergemasterrc? There are other ways, but that's the first one I would think of. Note that neither of these files can be harmful, and might (especially aliases) be used by other MTA. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
lei yang yanglei.f...@gmail.com writes: On Tue, Jul 24, 2012 at 12:03 AM, Carl Johnson ca...@peak.org wrote: lei yang yanglei.f...@gmail.com writes: On Mon, Jul 23, 2012 at 12:25 AM, Polytropon free...@edvax.de wrote: On Sun, 22 Jul 2012 22:41:57 +0800, lei yang wrote: Hi, I want to build a netcat on my local pc (ubuntu) with gcc, is it possible? I'm new to free bsd it has no -U flag, can you point me where I get this version Have you checked the other version of netcat already available? A quick check shows these four versions for Ubuntu: netcat: TCP/IP swiss army knife -- transitional package netcat-openbsd: TCP/IP swiss army knife netcat-traditional: TCP/IP swiss army knife netcat6: TCP/IP swiss army knife with IPv6 support how did you get the list? I used the surfraw package which is available on freebsd, debian, and ubuntu. In this case I just used 'debpackages -u netcat' to do access the ubuntu packages search page. There is also 'freebsd -psearch' to search freebsd ports, and debpackages without -u shows debian packages. To be clear, haha, I just want to know how to build a fress bsd netcat on a no-fressbsd platform Others have probably already mentioned this, but you are probably better off trying ports source instead. Most of those are written to be portable and are easily configured for other OSs. Freebsd port search shows the following for netcat: net/cryptcat Standard netcat enhanced with twofish encryption net/gnetcat GPL'ed re-write of the well known networking tool netcat net/nc6 Netcat clone with IPv6 support net/netcatSimple utility which reads and writes data across network connections net/sbd A netcat clone with more features and crypto net/scnc SSL Capable Netcat security/sst A simple SSL tunneling tool (uses netcat) -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Disk Errors
Just curious, I am sure the likely issue is a bad disk, but I thought there might be a chance this could be caused by possibly by something else. I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 dmesg info about the drive at connection time: ad4: 953869MB Seagate ST31000528AS CC46 at ata2-master UDMA100 SATA 3Gb/s dmesg info about one of the western digital drives: ad4: 953869MB WDC WD10EARS-00Y5B1 80.00A80 at ata2-master UDMA100 SATA 3Gb/s Before I scrap the drive I just wanted to see if anyone could either say for sure its hardware, or if something else could possibly cause this. I don't suspect the controller, cable or dock as the problems would likely occur with the western Digital drives as well if one of them were involved. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
version of clang in HEAD?
This is nominally more suited for current@, but: As of midnight US Pacific Time, what is the version of clang in HEAD? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
On 24/07/2012 14:36, kpn...@pobox.com wrote: On Tue, Jul 24, 2012 at 07:13:00PM +0800, lei yang wrote: On Tue, Jul 24, 2012 at 12:47 AM, Polytroponfree...@edvax.de wrote: On Mon, 23 Jul 2012 23:29:38 +0800, lei yang wrote: Yes, the second version I post is using the source from you supplied, then I compiled it, but it has no -U flag like what I post, it seems a version different casued this. Yes. The version distributed by the ports collection is different from that one supplied with the base system of FreeBSD. To try _that_ version, you can download the source tarball and extract it; in the directory # wget ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.0-RELEASE/src.txz # tar xvf src.txz Thanks for the help, tar xvf src.txz tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Read 4896 bytes from src.txz tar: Error exit delayed from previous errors [lyang0@ala-lpggp2 lyang0]$ tar xvf src.txz tar: This does not look like a tar archive tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: Read 4896 bytes from src.txz tar: Error exit delayed from previous errors Maybe a bad/incomplete download? %fetch ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.0-RELEASE/src.txz src.txz 100% of 89 MB 216 kBps 00m00s %md5 src.txz MD5 (src.txz) = 7cce6b045f771cef2136df277d16331f %tar xvf src.txz x usr/src/ x usr/src/usr.bin/ x usr/src/release/ x usr/src/crypto/ x usr/src/include/ x usr/src/secure/ x usr/src/rescue/ x usr/src/gnu/ x usr/src/sbin/ x usr/src/games/ x usr/src/tools/ x usr/src/contrib/ x usr/src/kerberos5/ x usr/src/share/ ... ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
Just curious, I am sure the likely issue is a bad disk, but I thought there actually not that likely. i had such problems, occuring randomly on many drives, and all problems disappeared after changing computer, with the same disk. BTW i would recommend you to turn on AHCI driver ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 dmesg info about the drive at connection time: ad4: 953869MB Seagate ST31000528AS CC46 at ata2-master UDMA100 SATA 3Gb/s dmesg info about one of the western digital drives: ad4: 953869MB WDC WD10EARS-00Y5B1 80.00A80 at ata2-master UDMA100 SATA 3Gb/s Before I scrap the drive I just wanted to see if anyone could either say for sure its hardware, or if something else could possibly cause this. I don't suspect the controller, cable or dock as the problems would likely occur with the western Digital drives as well if one of them were involved. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
In the last episode (Jul 24), dweimer said: I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 If you install the sysutils/smartmontools port, you can run smartctl -x /dev/ad4 to dump the drive's SMART attribute table and error logs. Those should give you an indication of whether the drive is going bad. If the drive is logging those write errors in its internal log, then you know it's not a cabling issue. If it's not logging errors, I suppose you might have a loose SATA plug on the drive itself, which would explain why the problem follows the drive around. dmesg info about the drive at connection time: ad4: 953869MB Seagate ST31000528AS CC46 at ata2-master UDMA100 SATA 3Gb/s dmesg info about one of the western digital drives: ad4: 953869MB WDC WD10EARS-00Y5B1 80.00A80 at ata2-master UDMA100 SATA 3Gb/s Before I scrap the drive I just wanted to see if anyone could either say for sure its hardware, or if something else could possibly cause this. I don't suspect the controller, cable or dock as the problems would likely occur with the western Digital drives as well if one of them were involved. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: amd64, 57600 serial install help
On 21/07/2012 22:06, Ihsan Junaidi Ibrahim wrote: I assume you have compiled the bootblocks as per the instruction in the handbook. Second, do you have more than one serial port on the box because FreeBSD can only work its serial console magic on only one port at a time. If you redirect your IPMI serial console or just a normal serial console, take note it's interrupt number in the BIOS. You'll need to append the 0x10 flags to your UART device in device.hints file if the you plug in the cable at a non-default port. i have submitted a PR re this as a serial install on 8.3 works fine. Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
dweimer dweimer at dweimer.net writes: ... ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ... There is a story about it: http://linux-bsd-sharing.blogspot.com/2009/03/howto-fix-sata-dma-timeout-issues-on.html But do not rush, read the comments as well: ... Tony Schwartz said... Thing is though, I have a secondary issue. This second issue is probably what caused the first issue (DMA TIMEOUTS) to begin with. My disks keep spinning down then up, every 20 seconds or so. I have no idea why this is happening, but it's not just one disk. I think that it was timing out because he disk goes to spin up and that takes too long. Any ideas here? I've used atacontrol and it's not configured to spindown. Thanks. ... Benjamin said... LoL, found the solution and feeling a little embarrassed by it. Good thing I got a GURU in the forums to look at it. It was just the power supply and my disk was spinning down cos the power wasn't sufficient to run 6 HDs and 9 fans for cooling ha ha ha. ... CyberRax said... Just for information: while this hasn't been fixed as elegantly as in the patch FreeBSD does incorporate since 8-STABLE r199158 a solution for the problem: ATA_REQUEST_TIMEOUT kernel option that be be set higher than the default 5. What is needed is adding options ATA_REQUEST_TIMEOUT=X (where X is timeout in seconds) into the kernel configuration file. Changing the timeout will need rebuilding and installing the kernel, but it's still better than nothing. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On 2012-07-24 12:50, Wojciech Puchar wrote: Just curious, I am sure the likely issue is a bad disk, but I thought there actually not that likely. i had such problems, occurring randomly on many drives, and all problems disappeared after changing computer, with the same disk. BTW i would recommend you to turn on AHCI driver Now that made me just notice something interesting, my software mirror running on the internal SATA disks that contain the Operating System on this server is using the ahci driver but the external SATA drive isn't guess I am going to have to reboot tonight and check and see if something is set on the controllers BIOS that keeps it from running AHCI. Just an FYI, the server is running entirely on commodity PC hardware, as this is my home web server. Though its running all well known major brands for hardware. It is running FreeBSD 9.0-RELEASE-P3, upgraded a few times via source from an original install of 8.2 on this hardware. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On 2012-07-24 13:04, Dan Nelson wrote: In the last episode (Jul 24), dweimer said: I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 If you install the sysutils/smartmontools port, you can run smartctl -x /dev/ad4 to dump the drive's SMART attribute table and error logs. Those should give you an indication of whether the drive is going bad. If the drive is logging those write errors in its internal log, then you know it's not a cabling issue. If it's not logging errors, I suppose you might have a loose SATA plug on the drive itself, which would explain why the problem follows the drive around. Running a long test on the drive now, doesn't seem to show anything that sticks out at me as failing right now. smartctl 5.43 2012-06-30 r3573 [FreeBSD 9.0-RELEASE-p3 amd64] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.12 Device Model: ST31000528AS Serial Number:5VP7ST1C LU WWN Device Id: 5 000c50 02f7a3bb4 Firmware Version: CC46 User Capacity:1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is:Tue Jul 24 14:29:08 2012 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM level is: 208 (intermediate), recommended: 208 APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 248) Self-test routine in progress... 80% of test remaining. Total time to complete Offline data collection:( 600) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 173) minutes. Conveyance self-test routine recommended polling time:( 2) minutes. SCT capabilities: (0x103f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGSVALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 117 099 006-145191418 3 Spin_Up_TimePO 095 095 000-0 4 Start_Stop_Count-O--CK 100 100 020-114 5 Reallocated_Sector_Ct PO--CK 100 100 036-0 7 Seek_Error_Rate
Re: Disk Errors
On 2012-07-24 13:37, jb wrote: dweimer dweimer at dweimer.net writes: ... ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ... There is a story about it: http://linux-bsd-sharing.blogspot.com/2009/03/howto-fix-sata-dma-timeout-issues-on.html But do not rush, read the comments as well: ... Tony Schwartz said... Thing is though, I have a secondary issue. This second issue is probably what caused the first issue (DMA TIMEOUTS) to begin with. My disks keep spinning down then up, every 20 seconds or so. I have no idea why this is happening, but it's not just one disk. I think that it was timing out because he disk goes to spin up and that takes too long. Any ideas here? I've used atacontrol and it's not configured to spindown. Thanks. ... Benjamin said... LoL, found the solution and feeling a little embarrassed by it. Good thing I got a GURU in the forums to look at it. It was just the power supply and my disk was spinning down cos the power wasn't sufficient to run 6 HDs and 9 fans for cooling ha ha ha. ... I wouldn't expect power as the external dock has its own power supply, I would expect this to occur on the other drives as well. Though its possible the Seagate drive requires more power than the Western Digital drives, I think I will look up the specs tonight on that, as well as do some searching on the eSATA doc to verify that there haven't been any problems with it and Seagate drives CyberRax said... Just for information: while this hasn't been fixed as elegantly as in the patch FreeBSD does incorporate since 8-STABLE r199158 a solution for the problem: ATA_REQUEST_TIMEOUT kernel option that be be set higher than the default 5. What is needed is adding options ATA_REQUEST_TIMEOUT=X (where X is timeout in seconds) into the kernel configuration file. Changing the timeout will need rebuilding and installing the kernel, but it's still better than nothing. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
dweimer dweimer at dweimer.net writes: ... 188 Command_Timeout -O--CK 100 098 000- 21475164202 ... I can not find it for Seagate; http://sourceforge.net/apps/trac/smartmontools/wiki/AttributesSeagate but for Western-Digital: http://sourceforge.net/apps/trac/smartmontools/wiki/AttributesWestern-Digital ... 188 Command Time OutA number of aborted operations due to HDD timeout. Normally this attribute value should be equal to zero and if you have values far above zero, then most likely you have some serious problems with your power supply or you have an oxidized data cable. ... jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: version of clang in HEAD?
The same as in 9-STABLE? $ cc -v FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 Target: x86_64-unknown-freebsd9.0 Thread model: posix -- View this message in context: http://freebsd.1045724.n5.nabble.com/version-of-clang-in-HEAD-tp5729532p5729576.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
dweimer wrote: [snip] SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGSVALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-- 117 099 006-145191418 [...] 7 Seek_Error_Rate POSR-- 078 060 030-77590473 [...] 195 Hardware_ECC_Recovered -O-RC- 025 023 000-145191418 [...] 241 Total_LBAs_Written -- 100 253 000-1480696469 242 Total_LBAs_Read -- 100 253 000-922627427 [snip] Really, most of the numbers don't look really bad, but I'd cast a leery eye towards the way these three correlate. Read errors from bad spots in the magnetic media are one thing, but notice how the drive is recovering data with built-in ECC routines. Then notice that the seek error rate is moving along at a similar pace. There is a possibility that this is a purely mechanical weakness in the head positioning function, just barely not bad enough for to allow the drive to attempt to hide it through ECC. When I suspect media failure I generally use the manufacturers diagnostic utility to scan for defective media. I haven't used many Seagates in a long time so mostly this means WD's wddiags, which can be downloaded as a bootable CD .iso image. Seagate will have something similar. The quick scan is meant to be non-destructive while the long scan usually is. (I just had an old Raptor drive grow 5 bad spots recently, and the long scan fixed it without destroying any data - a first for me that) As long as the remap space area on the drive is not full usually these diagnostics have a good chance to fix bad spots. If it's an infrequent affair then one may just continue to use it. If I see new bad sectors a week later it is an indication that the drive has outlived it's usefulness and I replace it. If it's another year before I get a small handful of bad spots I may just let the diags fix it and continue to use. That is - as long as the remap space is not full. Once that happens any new bad spots are permanent and cannot be done anything about. Time to replace drive. The difference here is bad spots developing in the media on the platter(s) as opposed to the problem actually stemming from head seek position-location problems. None of the diags can do anything about head seek troubles, only identify if the problem is media on the platter(s) related. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On Tue, 24 Jul 2012, dweimer wrote: Just curious, I am sure the likely issue is a bad disk, but I thought there might be a chance this could be caused by possibly by something else. I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 dmesg info about the drive at connection time: ad4: 953869MB Seagate ST31000528AS CC46 at ata2-master UDMA100 SATA 3Gb/s There are more than a few problem reports on the net concerning that drive, even on Seagate's own forums. Both hardware problems and firmware problems. Your later post says you have firmware version CC46, and Seagate has an update to CC49. That's worth a try. http://knowledge.seagate.com/articles/en_US/FAQ/213891en?language=en_US ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On 2012-07-24 16:10, Warren Block wrote: On Tue, 24 Jul 2012, dweimer wrote: Just curious, I am sure the likely issue is a bad disk, but I thought there might be a chance this could be caused by possibly by something else. I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 dmesg info about the drive at connection time: ad4: 953869MB Seagate ST31000528AS CC46 at ata2-master UDMA100 SATA 3Gb/s There are more than a few problem reports on the net concerning that drive, even on Seagate's own forums. Both hardware problems and firmware problems. Your later post says you have firmware version CC46, and Seagate has an update to CC49. That's worth a try. http://knowledge.seagate.com/articles/en_US/FAQ/213891en?language=en_US Definately going to try this firmware update, if only it would see the disk through the eSATA controller, but unfortunately it marks it as a JBOD raid instead of straight access to the disk. So this will have to wait until I put my puppy to bed for the night as she keeps trying to eat the pillow from my bed while I am working on this. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: help about free bsp version netcat to work it on ubuntu
On Tue, 24 Jul 2012 19:13:00 +0800, lei yang wrote:
On Tue, Jul 24, 2012 at 12:47 AM, Polytropon free...@edvax.de wrote:
On Mon, 23 Jul 2012 23:29:38 +0800, lei yang wrote:
Yes, the second version I post is using the source from you supplied,
then I compiled it, but it has no
-U flag like what I post, it seems a version different casued this.
Yes. The version distributed by the ports collection is different
from that one supplied with the base system of FreeBSD.
To try _that_ version, you can download the source tarball and
extract it; in the directory
# wget ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/9.0-RELEASE/src.txz
# tar xvf src.txz
Thanks for the help,
tar xvf src.txz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: Read 4896 bytes from src.txz
tar: Error exit delayed from previous errors
[lyang0@ala-lpggp2 lyang0]$ tar xvf src.txz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
tar: Read 4896 bytes from src.txz
tar: Error exit delayed from previous errors
Oh sorry I forgot: You're _not_ on a FreeBSD system!
That's why you cannot use tar (means: bsdtar) with
the xz compression support.
On your system, you first need to install xz. Use
the unxz to uncompress the archive. Then you will have
a valid tar archive which you can extract with stock
tar.
# cd cusr/src/ontrib/netcat/
# ls
FREEBSD-XlistFREEBSD-vendor atomicio.h netcat.c
FREEBSD-upgrade atomicio.c nc.1 socks.c
#
your build command(s) here
Suppose gcc -o netcat netcat.c atomicio.c socks.c should work
It seems that I pointed you to a wrong location inside
the src/ tree. Maybe try this instead:
# unxz src.txz
# tar xvf src.tar usr/src/usr.bin/nc/
# tar xvf src.tar usr/src/contrib/netcat/
# cd usr/src/usr.bin/nc/
# ls
Makefile
# cd ../../contrib/netcat/
# ls
FREEBSD-XlistFREEBSD-vendor atomicio.h netcat.c
FREEBSD-upgrade atomicio.c nc.1 socks.c
Problem: The Makefile which describes the build
process refers to bsd.prog.mk which is specific to
FreeBSD (and located in src/share/Mk which you'd
also have to extract).
The content of the Makefile is rather simple:
.PATH: ${.CURDIR}/../../contrib/netcat
PROG= nc
SRCS= netcat.c atomicio.c socks.c
CFLAGS+=-DIPSEC
LDADD= -lipsec
DPADD= ${LIBIPSEC}
.include bsd.prog.mk
Still it seems that your simplified approach could
work: Compile all the .c files.
--
Polytropon
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 freebsd-questions-unsubscr...@freebsd.org
building Samba on 8.2 fails
Hello, I had installed Samba35 and had it working with PAM and SSH, however after a reboot PAM broke. Kept getting the error; in openpam_load_module(): no /usr/local/lib/pam_winbind.so found The file was actually in that path. Never the less, I tried re-installing; portsnap extract portsnap fetch update cd /usr/ports/devel/libtool make deinstall make install clean cd /usr/ports/security/krb5 make deinstall make KRB5_HOME=/usr/local install clean and finally; cd /usr/ports/net/samba35 make KRB5_HOME=/usr/local install clean With my fingers crossed I hoped for the best and yet I received the following error during compiling; snip Compiling libsmb/libsmb_setget.c libsmb/libsmb_setget.c: In function 'smbc_getOptionUseCCache': libsmb/libsmb_setget.c:427: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) libsmb/libsmb_setget.c:427: error: (Each undeclared identifier is reported only once libsmb/libsmb_setget.c:427: error: for each function it appears in.) libsmb/libsmb_setget.c: In function 'smbc_setOptionUseCCache': libsmb/libsmb_setget.c:435: error: 'SMB_CTX_FLAG_USE_CCACHE' undeclared (first use in this function) The following command failed: cc -I/usr/local/include -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. -I/usr/ports/net/samba35/work/samba-3.5.15/source3 -I/usr/ports/net/samba35/work/samba-3.5.15/source3/iniparser/src -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -DHAVE_CONFIG_H -I/usr/local/include -I/usr/local/include -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/tevent -I./libaddns -I./librpc -I./.. -I./../lib/popt -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba35/work/samba-3.5.15/source3/lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c libsmb/libsmb_setget.c -o libsmb/libsmb_setget.o gmake: *** [libsmb/libsmb_setget.o] Error 1 *** Error code 1 Stop in /usr/ports/net/samba35. *** Error code 1 Stop in /usr/ports/net/samba35. snip Does anyone have any solutions on how I can get Samba installed and resolve the above error? Many thanks in advance. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On Tue, Jul 24, 2012 at 11:40 AM, dweimer dwei...@dweimer.net wrote: Just curious, I am sure the likely issue is a bad disk, but I thought there might be a chance this could be caused by possibly by something else. I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 This type of problem has been a consistent problem on FreeBSD until mid 8.x range. Try upgrading your system to something a little more modern. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk Errors
On 2012-07-24 21:29, Adam Vande More wrote: On Tue, Jul 24, 2012 at 11:40 AM, dweimer dwei...@dweimer.net wrote: Just curious, I am sure the likely issue is a bad disk, but I thought there might be a chance this could be caused by possibly by something else. I have three 1TB disks I use for backup, two of them are Western Digital drives I bought specifically for this purpose. One is a Seagate drive that came out of a barebones PC that I replaced with a couple smaller drives in a stripe to gain performance. I use the drives in an external SATA dock, using geom eli encryption, the western digital drives give me no problems, but the seagate drive gives me a lot of the following errors under load. ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=837397120 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=879786112 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=882931200 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=890542016 ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=902767296 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=904071296 This type of problem has been a consistent problem on FreeBSD until mid 8.x range. Try upgrading your system to something a little more modern. -- Adam Vande More Its running 9.0-RELEASE-P3 updated from source from an original install of 8.2 on this hardware. I have done the firmware update on the drive, so hopefully I will see an improvement in about 2 hours when tonights backups kick off. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
CYCAS architectural C.A.D. software
Good day FreeBSD enthusiasts. Has anyone installed and used CYCAS architectural CAD software on a FreeBSD system? Is this possible? If you have used CYCAS on a FreeBSD system, would you like to share with me your comments about your experience? Many thanks. Lee Shackelford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
