Good PCI Firewire Card?
Can anyone reccomend a good PCI Firewire card that has good support in FreeBSD 5.2.1? -- Mike Barrett | We have veggie bacon, why don't we have [EMAIL PROTECTED] | meat fruit? www.daboyz.org |-- My ex-coworker, Ben +--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hot Swap Serial ATA Drives?
I've been tasked with coming up with an archiving solution for my company for very large datafiles (100+ gigs). With the low price of hard drives, it seems that using some sort of hot swappable Serial ATA Hard drive in an enclosure would be the best cheapest way to go about doing something like this. Does anyone have any experience using atacontrol to hot swap out serial ata drives in FreeBSD? If so, can you tell me what hardware you've tried/had luck with? Thanks for all your help. -- Mike Barrett | We have veggie bacon, why don't we have [EMAIL PROTECTED] | meat fruit? www.daboyz.org |-- My ex-coworker, Ben +--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Set Fragment Size via sysinstall/install.cfg
I have a PXE boot build system that works great. I am about to make a database that will grow very large, so I thought it might be a good idea to create a partition for that database that has a large fragment block size (to save time on fsck's and the like). Does anyone know how to do this via install.cfg for sysinstall? Is it even possible? The documentation doesn't mention it. Thanks. -- Mike Barrett | We have veggie bacon, why don't we have [EMAIL PROTECTED] | meat fruit? www.daboyz.org |-- My ex-coworker, Ben +--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
No Description In ports search
Hi, so I recently went to look for a mp3 ripper/encoder program in the ports collection and I noticed something odd. For some reason, whenever I do a make search of any sort, all the ports it lists have their Info: field set to ** No Description. Anyone have any idea why that is? It doesn't seem to matter what I search for, or if I use keys or name to search, nothing has any info about it. I know that it didn't have this behavior before, and it's really kind of bothersome. Thanks for any help you can give. -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Xft-2.1 port problems
I've currently got the XFree86-4.2.0_1,1 port installed. On Wed, Feb 05, 2003 at 02:54:31AM -0500, Joe Marcus Clarke wrote: On Wed, 2003-02-05 at 02:39, Michael Barrett wrote: Hi, So tonight I went to try and upgrade my gkrellm2 port, and found that it failed when dealing with a file that was part of my Xft port. I currently have Xft-2.0_1 installed. I went to do a portupgrade of Xft, and this is the error I keep getting: gcc -O -pipe -I. -DHAVE_CONFIG_H -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -fPIC -DPIC -c xftdpy.c -o xftdpy.o xftdpy.c: In function `XftDefaultSubstitute': xftdpy.c:484: `FC_RGBA_UNKNOWN' undeclared (first use in this function) xftdpy.c:484: (Each undeclared identifier is reported only once xftdpy.c:484: for each function it appears in.) gmake: *** [xftdpy.o] Error 1 *** Error code 2 Stop in /usr/ports/x11-fonts/Xft. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade93740.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! x11-fonts/Xft (Xft-2.0_1) (compiler error) = Anyone have any idea what might be causing this? I've tried going into /usr/ports/x11-fonts/Xft and doing a make deinstall, but my ports no longer point at Xft-2.0_1, they point to 2.1 and so it doesn't seem to think Xft is installed (even though I see it installed in /var/db/pkg). Anyways, any help I can get on this would be much appreciated. Thanks in advance. What version of XFree86 do you have installed? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Xft-2.1 port problems
That seems to have been the problem. Thanks a ton :) On Wed, Feb 05, 2003 at 01:43:50PM -0500, Joe Marcus Clarke wrote: On Wed, 2003-02-05 at 11:59, Michael Barrett wrote: I've currently got the XFree86-4.2.0_1,1 port installed. Make sure you have the latest version of fontconfig installed before installing Xft. Joe On Wed, Feb 05, 2003 at 02:54:31AM -0500, Joe Marcus Clarke wrote: On Wed, 2003-02-05 at 02:39, Michael Barrett wrote: Hi, So tonight I went to try and upgrade my gkrellm2 port, and found that it failed when dealing with a file that was part of my Xft port. I currently have Xft-2.0_1 installed. I went to do a portupgrade of Xft, and this is the error I keep getting: gcc -O -pipe -I. -DHAVE_CONFIG_H -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -fPIC -DPIC -c xftdpy.c -o xftdpy.o xftdpy.c: In function `XftDefaultSubstitute': xftdpy.c:484: `FC_RGBA_UNKNOWN' undeclared (first use in this function) xftdpy.c:484: (Each undeclared identifier is reported only once xftdpy.c:484: for each function it appears in.) gmake: *** [xftdpy.o] Error 1 *** Error code 2 Stop in /usr/ports/x11-fonts/Xft. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade93740.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! x11-fonts/Xft (Xft-2.0_1) (compiler error) = Anyone have any idea what might be causing this? I've tried going into /usr/ports/x11-fonts/Xft and doing a make deinstall, but my ports no longer point at Xft-2.0_1, they point to 2.1 and so it doesn't seem to think Xft is installed (even though I see it installed in /var/db/pkg). Anyways, any help I can get on this would be much appreciated. Thanks in advance. What version of XFree86 do you have installed? Joe -- PGP Key : http://www.marcuscom.com/pgp.asc -- PGP Key : http://www.marcuscom.com/pgp.asc -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Xft-2.1 port problems
Hi, So tonight I went to try and upgrade my gkrellm2 port, and found that it failed when dealing with a file that was part of my Xft port. I currently have Xft-2.0_1 installed. I went to do a portupgrade of Xft, and this is the error I keep getting: gcc -O -pipe -I. -DHAVE_CONFIG_H -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -fPIC -DPIC -c xftdpy.c -o xftdpy.o xftdpy.c: In function `XftDefaultSubstitute': xftdpy.c:484: `FC_RGBA_UNKNOWN' undeclared (first use in this function) xftdpy.c:484: (Each undeclared identifier is reported only once xftdpy.c:484: for each function it appears in.) gmake: *** [xftdpy.o] Error 1 *** Error code 2 Stop in /usr/ports/x11-fonts/Xft. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade93740.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! x11-fonts/Xft (Xft-2.0_1) (compiler error) = Anyone have any idea what might be causing this? I've tried going into /usr/ports/x11-fonts/Xft and doing a make deinstall, but my ports no longer point at Xft-2.0_1, they point to 2.1 and so it doesn't seem to think Xft is installed (even though I see it installed in /var/db/pkg). Anyways, any help I can get on this would be much appreciated. Thanks in advance. -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86 keysyms?
Howdy, I upgraded to XFree-86-libraries-4.2.1_5 recently using portupgrade, and just today I noticed that in the file /usr/X11R6/include/X11/keysymdefs.h some entries that were there before are now missing. Specifically, I see the problem when I go to do the following (from my .Xmodmap) keycode 176 = XF86AudioRaiseVolume keycode 174 = XF86AudioLowerVolume keycode 160 = XF86AudioMute keycode 162 = XF86AudioPlay keycode 164 = XF86AudioStop keycode 153 = XF86AudioNext keycode 144 = XF86AudioPrev keycode 236 = XF86Mail keycode 237 = XF86Sleep Any ideas why the Audio keys were removed? Any idea how to add them back? Thanks for all your help. -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Vim+Mutt+Backspace
That did it. Any idea why that would be needed for mutt but not for regular vi? Thanks a ton for your help. Wow, it's so nice to be able to use the backspace when I typo. :) On Thu, Jan 23, 2003 at 03:02:27PM +0100, Toni Schmidbauer wrote: On Thu, Jan 23, 2003 at 12:16:00AM -0800, Michael Barrett wrote: Anyways, when I run vim from the command line, if I'm in insert mode and I hit the backspace key it acts normally. IE: It erases the character to the left of the cursor. try these two options in your .vimrc set t_kb=^H fixdel for ^H you have to press CTRL-V and then hit the backspace key. toni -- Terror ist der Krieg der Armen, | [EMAIL PROTECTED] Krieg ist der Terror der Reichen. | Toni Schmidbauer - Sir Peter Ustinov | -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
aterm, screen, and backspace
Howdy, I just recently got into freebsd and everything has been running great. Tonight I decided to change the compile time options that I set aterm up with and ran into some problems. Before doing this I went ahead and ran cvsup to make sure I had the latest and greatest port of aterm. I don't know if anything got updated, but I only built my machine about a month ago with the latest ports. I haven't seen any changes to the aterm port, but maybe I'm using the port changes search engine wrong. Anyways, after making sure I had the latest port info I then de-installed my copy of aterm, and then did a make install clean to re-install it, using the standard Makefile. Everything seemed fine till I went and ran screen. When I ran screen, I found that I could no longer use backspace. Instead of backspacing, it would instead simply cause my terminal to beep. I hit ^V then the backspace key and this is the code it's returning: ^[[3~ . I looked around the newsgroups and couldn't find a whole lot of answers in regards to this. I found something about .inputrc, a file which I use to give me vi bindings in the python interpreter. Here's the extent of my .inputrc file: set editing-mode vi I wouldn't imagine this would cause many problems, yet when I went ahead and moved the .inputrc to .inputrc.old and started up screen, then my backspace key printed a ~ and would cause my terminal to beep. Hitting ^V backspace now reported ^[[3~ as well. Anyways I quite plainly 'don't get it'. Nothing else has changed on my system. I am running the following software: Screen version 3.09.13 (FAU) 5-Sep-02 aterm version 0.4.2 Has anyone else had this problem? Thanks in advance for any help you can give me. I use screen and aterm a lot, so losing the combo really really hurts. Thanks again. -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: aterm, screen, and backspace
Ok, please ignore my question. I'm still not 100% sure what happened, but somehow a version of aterm was left in /usr/local/bin/aterm from when I edited the Makefile and removed the entries for --enable-utmp and --enable-wtmp. That version seemed to be messing up screen, and I'm not sure why. When I removed that version manually and did a make deinstall and then make clean, and then make install (inside the aterm port dir) everything seems to be working fine again. This brings up another question I had however: Say I see a configuration in a ports Makefile that I want to change. What is the proper way to go about doing this? In this example, I saw the following line in /usr/ports/x11/aterm/ CONFIGURE_ARGS+= \ --enable-transparency --enable-background-image \ --disable-delete-key --disable-backspace-key \ --enable-fading --enable-utmp --enable-wtmp I wanted to get rid of the utmp and wtmp features, so I erased that line as well as the preceeding \. I had tried using: make install CONFIGURE_ARGS=args I wanted, but the others seemed to be added no matter what (I believe due to the fact that in the makefile it's using += rather than just =). Anyways, what would be the best way of going about this? Thanks again for all your help. On Wed, Dec 18, 2002 at 11:26:40PM -0800, Michael Barrett wrote: Howdy, I just recently got into freebsd and everything has been running great. Tonight I decided to change the compile time options that I set aterm up with and ran into some problems. Before doing this I went ahead and ran cvsup to make sure I had the latest and greatest port of aterm. I don't know if anything got updated, but I only built my machine about a month ago with the latest ports. I haven't seen any changes to the aterm port, but maybe I'm using the port changes search engine wrong. Anyways, after making sure I had the latest port info I then de-installed my copy of aterm, and then did a make install clean to re-install it, using the standard Makefile. Everything seemed fine till I went and ran screen. When I ran screen, I found that I could no longer use backspace. Instead of backspacing, it would instead simply cause my terminal to beep. I hit ^V then the backspace key and this is the code it's returning: ^[[3~ . I looked around the newsgroups and couldn't find a whole lot of answers in regards to this. I found something about .inputrc, a file which I use to give me vi bindings in the python interpreter. Here's the extent of my .inputrc file: set editing-mode vi I wouldn't imagine this would cause many problems, yet when I went ahead and moved the .inputrc to .inputrc.old and started up screen, then my backspace key printed a ~ and would cause my terminal to beep. Hitting ^V backspace now reported ^[[3~ as well. Anyways I quite plainly 'don't get it'. Nothing else has changed on my system. I am running the following software: Screen version 3.09.13 (FAU) 5-Sep-02 aterm version 0.4.2 Has anyone else had this problem? Thanks in advance for any help you can give me. I use screen and aterm a lot, so losing the combo really really hurts. Thanks again. -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Mike Barrett | I used to read, now I go to raves. [EMAIL PROTECTED] | -- Random MUNI Rider, speaking www.daboyz.org |to my friend Allison. +--- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
