32 bit to 64 bit
I'm upgrading a 7.3 -STABLE installation to 8.x, then 9- Stable over the next few days. The hardware is a Dell 2950 that is capable of running 64 bit FreeBSD. The original installation was i386 32 bit and that is what it is running now. Will the buildworld --- buildkernel KERNCONF=FOO64 allow a 32 bit installation to build a 64 bit kernel? I'd like to upgrade this machine to 64 bit AMD and I'd prefer not to do it from a DVD if I can do it from source. Has anyone tried this and succeeded (or failed spectacularly) on a remote install/upgrade? Tim Kellers ___ 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: llvm/clang 3.1
If you really want/need clang 3.1 you should be tracking 9-STABLE, source branch not RELEASE. Port system is separate from base system, and installs things only in /usr/local/*. -- View this message in context: http://freebsd.1045724.n5.nabble.com/llvm-clang-3-1-tp5722315p5722483.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
shell scripting: grepping multiple patterns, logically ANDed
hello, I'm not sure if this is the right forum for this question, but here goes. I have the following in a shell script: #!/bin/sh if [ $# -eq 0 ]; then find /foo fi if [ $# -eq 1 ]; then find /foo | grep -i $1 fi if [ $# -eq 2 ]; then find /foo | grep -i $1 | grep -i $2 fi if [ $# -eq 3 ]; then find /foo | grep -i $1 | grep -i $2 | grep -i $3 fi Is there an easier/shorter way to do this? If there are 15 arguments supplied on the command line, I don't necessarily want to build 15 if statements. Thanks in advance for your answers. ___ 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: 32 bit to 64 bit
It has been done, it's just rally not recommended. Sorry, don't know what was exact procedure/ if it works currently. -- View this message in context: http://freebsd.1045724.n5.nabble.com/32-bit-to-64-bit-tp5722481p5722485.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: 32 bit to 64 bit
On 6/27/2012 9:37 AM, Tim Kellers wrote: Will the buildworld --- buildkernel KERNCONF=FOO64 allow a 32 bit installation to build a 64 bit kernel? I'd like to upgrade this machine to 64 bit AMD and I'd prefer not to do it from a DVD if I can do it from source. Has anyone tried this and succeeded (or failed spectacularly) on a remote install/upgrade? I have seen posts of people who have done it, but when we contemplated it a while back it was more trouble than it was worth. It was easier and safer to build a new image on a separate disk, install all the apps from the ports, and then migrate the customer data over. Even if the box is remote, it might be easier to ship the drive there and have someone change it out for you. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.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: 32 bit to 64 bit
On Wed, Jun 27, 2012 at 4:37 PM, Tim Kellers timot...@devel.njit.eduwrote: I'm upgrading a 7.3 -STABLE installation to 8.x, then 9- Stable over the next few days. The hardware is a Dell 2950 that is capable of running 64 bit FreeBSD. The original installation was i386 32 bit and that is what it is running now. Will the buildworld --- buildkernel KERNCONF=FOO64 allow a 32 bit installation to build a 64 bit kernel? I'd like to upgrade this machine to 64 bit AMD and I'd prefer not to do it from a DVD if I can do it from source. Has anyone tried this and succeeded (or failed spectacularly) on a remote install/upgrade? Please just don't do it. Backup, Install new, restore configs and data! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. ___ 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: shell scripting: grepping multiple patterns, logically ANDed
On 06/27/2012 10:25 AM, Tim Daneliuk wrote: On 06/27/2012 09:25 AM, Aleksandr Miroslav wrote: hello, I'm not sure if this is the right forum for this question, but here goes. I have the following in a shell script: #!/bin/sh if [ $# -eq 0 ]; then find /foo fi if [ $# -eq 1 ]; then find /foo | grep -i $1 fi if [ $# -eq 2 ]; then find /foo | grep -i $1 | grep -i $2 fi if [ $# -eq 3 ]; then find /foo | grep -i $1 | grep -i $2 | grep -i $3 fi Is there an easier/shorter way to do this? If there are 15 arguments supplied on the command line, I don't necessarily want to build 15 if statements. Thanks in advance for your answers. The following solution relies on the fact that you can include multiple patterns for grep to match with the '-e' argument: #!/bin/sh PATTERNS=`echo $* | sed s/\ /\ -e\ /g` find /foo | grep $PATTERNS Notice that when constructing the $PATTERNS string out of the command line args, you have to quote them with a prepended space character. That's because the subsequent 'sed' substitution needs to find a space *before* each argument which it then replaces with -e . Whoops, I just realized that I ORed them and you want them ANDed. Hmmm ... must go think on that... ___ 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: shell scripting: grepping multiple patterns, logically ANDed
On 06/27/2012 09:25 AM, Aleksandr Miroslav wrote: hello, I'm not sure if this is the right forum for this question, but here goes. I have the following in a shell script: #!/bin/sh if [ $# -eq 0 ]; then find /foo fi if [ $# -eq 1 ]; then find /foo | grep -i $1 fi if [ $# -eq 2 ]; then find /foo | grep -i $1 | grep -i $2 fi if [ $# -eq 3 ]; then find /foo | grep -i $1 | grep -i $2 | grep -i $3 fi Is there an easier/shorter way to do this? If there are 15 arguments supplied on the command line, I don't necessarily want to build 15 if statements. Thanks in advance for your answers. The following solution relies on the fact that you can include multiple patterns for grep to match with the '-e' argument: #!/bin/sh PATTERNS=`echo $* | sed s/\ /\ -e\ /g` find /foo | grep $PATTERNS Notice that when constructing the $PATTERNS string out of the command line args, you have to quote them with a prepended space character. That's because the subsequent 'sed' substitution needs to find a space *before* each argument which it then replaces with -e . --- Tim Daneliuk ___ 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: shell scripting: grepping multiple patterns, logically ANDed
On 06/27/2012 10:33 AM, Tim Daneliuk wrote: On 06/27/2012 10:25 AM, Tim Daneliuk wrote: On 06/27/2012 09:25 AM, Aleksandr Miroslav wrote: hello, I'm not sure if this is the right forum for this question, but here goes. I have the following in a shell script: #!/bin/sh if [ $# -eq 0 ]; then find /foo fi if [ $# -eq 1 ]; then find /foo | grep -i $1 fi if [ $# -eq 2 ]; then find /foo | grep -i $1 | grep -i $2 fi if [ $# -eq 3 ]; then find /foo | grep -i $1 | grep -i $2 | grep -i $3 fi Is there an easier/shorter way to do this? If there are 15 arguments supplied on the command line, I don't necessarily want to build 15 if statements. Thanks in advance for your answers. The following solution relies on the fact that you can include multiple patterns for grep to match with the '-e' argument: #!/bin/sh PATTERNS=`echo $* | sed s/\ /\ -e\ /g` find /foo | grep $PATTERNS Notice that when constructing the $PATTERNS string out of the command line args, you have to quote them with a prepended space character. That's because the subsequent 'sed' substitution needs to find a space *before* each argument which it then replaces with -e . Whoops, I just realized that I ORed them and you want them ANDed. Hmmm ... must go think on that... OK, here is an ANDing version: #!/bin/sh PATMATCH=`echo $* | sed s/' '/' | grep '/g` eval find ./ $PATMATCH -- --- Tim Daneliuk ___ 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: shell scripting: grepping multiple patterns, logically ANDed
On 6/27/2012 11:25 AM, Tim Daneliuk wrote: On 06/27/2012 09:25 AM, Aleksandr Miroslav wrote: hello, I'm not sure if this is the right forum for this question, but here goes. I have the following in a shell script: #!/bin/sh if [ $# -eq 0 ]; then find /foo fi if [ $# -eq 1 ]; then find /foo | grep -i $1 fi if [ $# -eq 2 ]; then find /foo | grep -i $1 | grep -i $2 fi if [ $# -eq 3 ]; then find /foo | grep -i $1 | grep -i $2 | grep -i $3 fi Is there an easier/shorter way to do this? If there are 15 arguments supplied on the command line, I don't necessarily want to build 15 if statements. Thanks in advance for your answers. The following solution relies on the fact that you can include multiple patterns for grep to match with the '-e' argument: #!/bin/sh PATTERNS=`echo $* | sed s/\ /\ -e\ /g` find /foo | grep $PATTERNS Notice that when constructing the $PATTERNS string out of the command line args, you have to quote them with a prepended space character. That's because the subsequent 'sed' substitution needs to find a space *before* each argument which it then replaces with -e . This will build a multi-grep string for any number of arguments (within reason), functionally a boolean AND search: #!/bin/sh final_cmd=find /foo while [ $# -gt 0 ] do final_cmd=$final_cmd | grep -i $1 shift done $final_cmd May need quoting changes, but it worked on this sample, with this result: cmdline: ./testshift 1 1 2 3 4 5 result: find /foo | grep -i 1 | grep -i 1 | grep -i 2 | grep -i 3 | grep -i 4 | grep -i 5 HTH Brad ___ 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: sysinstall diskPartitionEditor Question
On Tue, Jun 26, 2012 at 10:30 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, I'd like to set the offset/starting cylinder in install.cfg so that partitions begin on appropriate boundaries. The applicable section of install.cfg looks like the following. My assumption is that I need to make the changes in the partition section. Is this correct? Is the format of this value the same as a typical fdisk config file? After copious amounts of reading and experimenting. It seems as though diskPartitionEdit doesn't support specifying a starting cylinder. When I specify partition=all, it starts that slice at sector 63. I'd like to start it at 64 or above. Is it feasible to include gpart in the mfsroot and use that to partition the drive before sysinstall continues with the installation? -- Take care Rick Miller ___ 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
