Re: need info builing ports properly
Mark Felder wrote: > My second suggestion is to please never ever ever mess with CFLAGS on > FreeBSD. You can get away with it on some Linux distros, but FreeBSD > strongly discourages it. Not true. eg I've set various CFLAGS for years. What FreeBSD requires is if one sets either CFLAGS or env vars then experiences problems, one should Unset them & try again before reporting bugs. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, & indent with "> ". Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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: need info builing ports properly
On Wed, 28 Mar 2012, icemac wrote: I wasn't after fiddling or optimizing much and just want to to build ports i need and have them as reliable and stable as possibile, but i misunderstood the function of that setting in make.conf. I actually had thought that that was required and in turn assumed, ( in retrospect) , that the defaults would be more aggressive and that that setting would restrict any wild optimization. also didnt realize it was an override to all. thanks. p.s. So this was probably the reason for my flakey setups? Possible but unlikely. ___ 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: need info builing ports properly
On 03/28/12 18:52, Matthew Seaman wrote: On 28/03/2012 15:40, icemac wrote: At the moment my /etc/make.conf just has 1 line with the Perl version entry, should i always leave cflags out? I think that not setting CLFAGS would be sensible. There's plenty of other stuff you can fiddle with in /etc/make.conf or /etc/src.conf if that's what interests you. OTOH, the default settings are pretty good and leaving well alone will help you get a put together a stable and reliable system without excessive pain. Cheers, Matthew Ok, i get it now thanks to these replies. I wasn't after fiddling or optimizing much and just want to to build ports i need and have them as reliable and stable as possibile, but i misunderstood the function of that setting in make.conf. I actually had thought that that was required and in turn assumed, ( in retrospect) , that the defaults would be more aggressive and that that setting would restrict any wild optimization. also didnt realize it was an override to all. thanks. p.s. So this was probably the reason for my flakey setups? ___ 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: need info builing ports properly
On 28/03/2012 15:40, icemac wrote: > Thanks for your quick reply, but can you clarify what you mean about not > messing with the CFLAGS? > I mean I had only ever used that one setting taken from the example in > /usr/share/examples/etc/make.conf, and the only experimentation i did is > either with it in make.conf, or nothing at all. Modifying CFLAGS like that is something that sounds attractive; an easy win in making your system perform better. However, you should ask yourself if it's really such a good idea, then why isn't it already the default? I can tell you that if there weren't some significant downsides to maxing out the optimization levels, then that would certainly be the case. In actuality, the optimization level (-O2, etc) has an inconsistent effect and is very much dependent on the nature of the code being compiled. In fact, for the FreeBSD kernel specifically it is known that it can be counter-productive. Much of the time for ports, it doesn't really make a great deal of difference what the setting is. Ports that can benefit will frequently have OPTIONS to turn up the optimization level, to be set on a per-port basis. One of the few things that is known to have a generally beneficial effect is to set the CPUTYPE variable appropriately. You can just say: CPUTYPE=native and the compiler will work out exactly what CPU you have automatically. The downside, of course, is that you make anything compiled on your system specific to particular CPU variants, so it's not something that could be done for software intended to be generally installable anywhere. > Do mean its proper not to have it at all in /etc/make.conf or about > changing it's values? Setting CFLAGS is not really improper, but it is not the panacea many people seem to think it is. It takes patience, plenty of trial and error, a deep understanding of compilers and so forth to achieve much. > At the moment my /etc/make.conf just has 1 line with the Perl version > entry, should i always leave cflags out? I think that not setting CLFAGS would be sensible. There's plenty of other stuff you can fiddle with in /etc/make.conf or /etc/src.conf if that's what interests you. OTOH, the default settings are pretty good and leaving well alone will help you get a put together a stable and reliable system without excessive pain. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: need info builing ports properly
On 03/28/12 17:30, Warren Block wrote: On Wed, 28 Mar 2012, icemac wrote: I only ever had this option set CFLAGS= -O2 -fno-strict-aliasing -pipe Setting that in make.conf is counterproductive. First, those are the defaults, so they don't improve anything. Second, that overrides settings made elsewhere. Consider a port like Gimp, which wants to use special CFLAGS for better performance. But it can't, because make.conf forces those CFLAGS. Ok, thanks. i had misunderstood the procedure then. ___ 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: need info builing ports properly
On Wed, 28 Mar 2012, icemac wrote: I only ever had this option set CFLAGS= -O2 -fno-strict-aliasing -pipe Setting that in make.conf is counterproductive. First, those are the defaults, so they don't improve anything. Second, that overrides settings made elsewhere. Consider a port like Gimp, which wants to use special CFLAGS for better performance. But it can't, because make.conf forces those CFLAGS. ___ 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: need info builing ports properly
On 03/28/12 16:22, Mark Felder wrote: My first suggestion is to begin using portmaster which can be found here: /usr/ports/ports-mgmt/portmaster My second suggestion is to please never ever ever mess with CFLAGS on FreeBSD. You can get away with it on some Linux distros, but FreeBSD strongly discourages it. My third suggestion is to keep at it and keep asking questions because we'd be glad to help :) ___ 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 for your quick reply, but can you clarify what you mean about not messing with the CFLAGS? I mean I had only ever used that one setting taken from the example in /usr/share/examples/etc/make.conf, and the only experimentation i did is either with it in make.conf, or nothing at all. Do mean its proper not to have it at all in /etc/make.conf or about changing it's values? At the moment my /etc/make.conf just has 1 line with the Perl version entry, should i always leave cflags out? thanks, ___ 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: need info builing ports properly
My first suggestion is to begin using portmaster which can be found here: /usr/ports/ports-mgmt/portmaster My second suggestion is to please never ever ever mess with CFLAGS on FreeBSD. You can get away with it on some Linux distros, but FreeBSD strongly discourages it. My third suggestion is to keep at it and keep asking questions because we'd be glad to help :) ___ 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"
need info builing ports properly
Hi, I am fairly new to fbsd and not a linux user, just windows and osx. My first install was version 7.1 for a short while and had 7.2, but only just came back to it with 9.0-r (amd64). I have a bit of an issue with the port system and was hoping to get some basic info as to what i might be doing wrong or missing before i go mess up my install. Basically, i know the basics of installing, maintaining ports, etc, but I seem to always end up with a rather flakey system, apps not running properly and so on. The one time I was really happy with my system is when i had tinderbox set up (on ver 7.x) and built everything in there, but was still using the same make.conf options in there as my /etc/make.conf I only ever had this option set CFLAGS= -O2 -fno-strict-aliasing -pipe and have tried without anything in /etc/make.conf ( apart from perl version entry from the port). So far i have never concerned myself while ldconfig or related stuff, as i am green on that, and have always had either default or whatever gets updated automatically. Would that be an issue, or my only issue? is there something else i need to set up properly on my system, or are my fingers just too big for my keyboard? At the moment i have 9.0-r installed, using packages only, with un-updated ports (so i can delete/add packages with portupgrade -PP and have no version issues), then i have tinderbox set up again, with latest ports tree (csup'ed last night) and plan to rebuild all the packages i'm using, but i don't want to have to avoid straight "make install clean" for every small thing later. Can someone give me some direction? I am still learning to use fbsd, and starting C, so i dont mind reading/testing. I dont mind running "pkg_delete -fav" every other day either atm. Thanks in advance ___ 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: Need info about FreeBSD and interrupted system calls for MySQL code
Dan, your info is very valuable - thanks: Dan Nelson wrote: > In the last episode (Apr 30), Joerg Bruehe said: >> Dan Nelson wrote: >>> In the last episode (Apr 29), Joerg Bruehe said: For some long, unknown time, the MySQL code contains a variable "net_retry_count" which is by default set to 10 (ten) for all platforms, but to 100 (1 million) for FreeBSD (during configure phase). The source code comment about this variable reads If a read on a communication port is interrupted, retry this many times before giving up. [[...]] >>> I'm pretty sure this is a holdover from when FreeBSD only had a user >>> pthreads package (libc_r). [[...]] >> Interesting information - thanks. I never heard that before, but it >> explains a lot. > > This may also have been due to a bug in the early libc_r code. Appropriate > use of sigwait() and pthread_sigmask() should let the pthreads library know > which read() calls it can silently retry on behalf of threads that are > ignoring signals (and thus shouldn't have their syscalls aborted with > EINTR). I have email records talking about libc_r problems with signal > masking from the FreeBSD 2.2.7 days (~1998). It's possible that later > libc_r versions had fixed the bug. I used to have copies of the ancient > mysql source code around (3.22 and 3.23 era), but have since deleted them, > so I don't know when the 100 workaround was added. The readily available revision control history of the MySQL source code goes back to the year 2000 only (the system used was changed back then, without history transfer), but a colleague checked that this workaround is documented in the manual of 3.22. All this seems to be a good indication we should get rid of this. Thanks for your help, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com (+49 30) 417 01 487 Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz Amtsgericht Muenchen: HRB161028 ___ 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: Need info about FreeBSD and interrupted system calls for MySQL code
In the last episode (Apr 30), Joerg Bruehe said: > Dan Nelson wrote: > > In the last episode (Apr 29), Joerg Bruehe said: > >> For some long, unknown time, the MySQL code contains a variable > >> "net_retry_count" which is by default set to 10 (ten) for all platforms, > >> but to 100 (1 million) for FreeBSD (during configure phase). > >> > >> The source code comment about this variable reads > >>If a read on a communication port is interrupted, retry this many > >>times before giving up. > >> > >> [[...]] > > > > I'm pretty sure this is a holdover from when FreeBSD only had a user > > pthreads package (libc_r). libc calls that would normally block got > > converted into non-blocking versions and a select() loop would execute > > threads as the events they were waiting on occurred. Incoming signals > > would cause all threads waiting on read() to return EINTR. If you have > > other threads doing work and sending/receiving signals, this can add up > > to a lot of extra EINTR's. > > Interesting information - thanks. I never heard that before, but it > explains a lot. This may also have been due to a bug in the early libc_r code. Appropriate use of sigwait() and pthread_sigmask() should let the pthreads library know which read() calls it can silently retry on behalf of threads that are ignoring signals (and thus shouldn't have their syscalls aborted with EINTR). I have email records talking about libc_r problems with signal masking from the FreeBSD 2.2.7 days (~1998). It's possible that later libc_r versions had fixed the bug. I used to have copies of the ancient mysql source code around (3.22 and 3.23 era), but have since deleted them, so I don't know when the 100 workaround was added. -- 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: Need info about FreeBSD and interrupted system calls for MySQL code
Dan, thanks for your reply: Dan Nelson wrote: > In the last episode (Apr 29), Joerg Bruehe said: >> For some long, unknown time, the MySQL code contains a variable >> "net_retry_count" which is by default set to 10 (ten) for all platforms, >> but to 100 (1 million) for FreeBSD (during configure phase). >> >> The source code comment about this variable reads >>If a read on a communication port is interrupted, retry this many >>times before giving up. >> >> [[...]] > > I'm pretty sure this is a holdover from when FreeBSD only had a user > pthreads package (libc_r). libc calls that would normally block got > converted into non-blocking versions and a select() loop would execute > threads as the events they were waiting on occurred. Incoming signals would > cause all threads waiting on read() to return EINTR. If you have other > threads doing work and sending/receiving signals, this can add up to a lot > of extra EINTR's. Interesting information - thanks. I never heard that before, but it explains a lot. > > FreeBSD 5.0 (released in 2003) was the first version to have kernel-based > pthread support, so the original reason for raising net_retry_count has long > since disappeared. It is quite possible that nobody checked this: "If it ain't broken ..." > > A related question might be, though: Should that variable even exist? > EINTR isn't technically a failure, and most programs that read from sockets > simply wrap their read()s in a loop that retries when EINTR is received. > Only mysql actually counts the number of times through the loop. I know and agree that EINTR is no failure if a system call takes long, like read() or write() from/to a socket (or other slow device) on sufficiently large data. But my current action is not to change the code, rather it is a cleanup in the build system (you may have heard we are changing from the autotools to cmake), so currently I won't change that loop dealing with possible system call interruptions (by not counting). So you are saying it might all be obsolete, and current versions of FreeBSD don't need this special setting. This sounds like I should do a build without it and then run tests. Thanks! Regards, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz Amtsgericht Muenchen: HRB161028 ___ 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: Need info about FreeBSD and interrupted system calls for MySQL code
In the last episode (Apr 29), Joerg Bruehe said: > For some long, unknown time, the MySQL code contains a variable > "net_retry_count" which is by default set to 10 (ten) for all platforms, > but to 100 (1 million) for FreeBSD (during configure phase). > > The source code comment about this variable reads >If a read on a communication port is interrupted, retry this many >times before giving up. > > The documentation (manual) has this sentence in addition: >This value should be set quite high on FreeBSD because internal >interrupts are sent to all threads. > > I read that as > "On FreeBSD, a thread may receive many more interrupts than on other > platforms, so an operation which may take some time (like network I/O) > may be interrupted much more often than on other platforms, and hence > the retry count should be higher." > > I trust that this comment was valid at the time it was written - > is it still true for current versions of FreeBSD, or did things change? I'm pretty sure this is a holdover from when FreeBSD only had a user pthreads package (libc_r). libc calls that would normally block got converted into non-blocking versions and a select() loop would execute threads as the events they were waiting on occurred. Incoming signals would cause all threads waiting on read() to return EINTR. If you have other threads doing work and sending/receiving signals, this can add up to a lot of extra EINTR's. FreeBSD 5.0 (released in 2003) was the first version to have kernel-based pthread support, so the original reason for raising net_retry_count has long since disappeared. A related question might be, though: Should that variable even exist? EINTR isn't technically a failure, and most programs that read from sockets simply wrap their read()s in a loop that retries when EINTR is received. Only mysql actually counts the number of times through the loop. -- 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"
Need info about FreeBSD and interrupted system calls for MySQL code
Hi Groggy (whom I didn't contact for too long a time), everybody, following the advice on your page, I include the FreeBSD list, even though I'm not subscribed there (hoping it will allow me to post) - so please, whoever replies, could you please cc: me directly? Of course, I tried Google, but I didn't find any answers to my question. For some long, unknown time, the MySQL code contains a variable "net_retry_count" which is by default set to 10 (ten) for all platforms, but to 100 (1 million) for FreeBSD (during configure phase). The source code comment about this variable reads If a read on a communication port is interrupted, retry this many times before giving up. The documentation (manual) has this sentence in addition: This value should be set quite high on FreeBSD because internal interrupts are sent to all threads. I read that as "On FreeBSD, a thread may receive many more interrupts than on other platforms, so an operation which may take some time (like network I/O) may be interrupted much more often than on other platforms, and hence the retry count should be higher." I trust that this comment was valid at the time it was written - is it still true for current versions of FreeBSD, or did things change? Thanks for all your hints, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com (+49 30) 417 01 487 Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz Amtsgericht Muenchen: HRB161028 ___ 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: Need Info?
DeAtH KnIgHt wrote: Hi, Ive noticed that there are different iso images within the ftp servers and i need to know which one do i actually need within these ftp servers? is there a difference between these different files? how do i install freebsd? Generally for each RELEASE, there is a "mini" ISO, and a multiple disc set that includes enough stuff to get up with X and about a zillion ports. (Well, OK, that's an exaggeration, but) I don't know much about the "bootonly" ISO. If you want to set up a bunch of Desktop machines with 5.2.1, for example, and have bandwidth to burn, the 2 CD set would do it. The "mini" CD should be enough to get going at the CLI; perhaps you'd say a "skeleton" install: /bin, /sbin, /usr/bin, /usr/sbin, /, /stand, /etc, /var, and the crypto and contrib* parts of the base distrubution. No docs, no source code, no ports tree. Just a classic Unix-like environment, from which you can, with a 'Net connection, build whatever you want (just about) As for me, I've never dl'ed an ISO; I just grab "two freshly formatted floppies and these instructions" as noted on the index page of www.freebsd.org, used /stand/sysinstall to install cvsup-no-gui as a package, and then cvsup'd /usr/src, /usr/ports, and do the buildworld/kernel cycle and then build ports. Some people prefer to use packages instead HTH, Kevin Kinsey DaleCo, S.P. *Yeah, I probably left something out, but hey, why overwhelm anybody? :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Need Info?
Hi, Ive noticed that there are different iso images within the ftp servers and i need to know which one do i actually need within these ftp servers? is there a difference between these different files? how do i install freebsd? - Do you Yahoo!? Yahoo! Search - Find what youre looking for faster. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: need info on hostname
> I want to know what the FBSD operating > system does with it. FBSD uses the name for network related functions, such as using it in mail related functions when communicating with foreign mail servers, offering the name to services your computer offers, and listening on certain network sockets for connections based on that name. > More explicatively during the install of FBSD > when asked to fill in the hostname prompt, what informative > information should be given to the user so they can enter the > correct stuff. The correct 'stuff' would first and foremost: be the FQDN of the box, if it has one, thereafter, it would be whatever name designation you give it to comply with the other computers on the network. For instance, my domain is northnetworks.ca, and my IBM thinkpad (which I am typing this on) is named ptp. This designation has no correspoinding DNS entry in my DNS for my domain because it is mobile and never is in one spot or on one single network, but when I send myself an email from this box to my real email account, I will be reminded that it came from '[EMAIL PROTECTED]'. Many services rely on the hostname, regardless of what it is. I notice when I need a gui app, I #startx, and it tells me that the display name relates to my pc name. Beyond this, I don't know what else to tell you, perhaps someone else on the list will have a more detailed analysis on what the name is used for. > Reading the /etc/hosts file provides no useful info. > Is there any place in FBSD that explains how to fill in the install > hostname prompt during the install? Considering as far as Free is concerned, there is no right answer. The filling of these fields resides within the information that your computer or network admin has given you. > Something like > > FBSD uses this hostname internally to name the PC running this FBSD > operating system. It has to be us this format of an fully qualified > domain name in the format of thisPCname.fakeDOMAINname.tld > > Where thisPCname came be any name you want to identify this > particular pc on your LAN. > > Where .fakeDOMAINname can be any name you want as long as it's not > an registered domain on the public internet unless it's registered > to you. Using FBSDyourlastname is an safe domain name to use here. > > Were .tld can be any of the standard TLD's currently in use. Such as > .com or .usa or .info or .cc I think this answer has already been provided. Perhaps you may consider contributing your definition above to the documentation team for inclusion if you wish to see it in future releases :o) ps. The tld does NOT have to be a standard tld if used on a private net. Steve > > > > > > > > -Original Message- > From: Kevin D. Kinsey, DaleCo, S.P. [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 20, 2003 3:04 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] ORG > Subject: Re: need info on hostname > > Quid pro quo: > > I'm not an expert, and don't play one on TV. > > fbsd_user wrote: > > >During the install you are asked for the host name which adds the > >following line to rc.conf. > >hostname="gateway.homepc.com" > > > >What does FBSD use this for? > > > > > > DNS? Same stuff as any other system, with the > possible exception of that stuff from Redmond. > > Since 'Nix is/has always been very network > oriented, this is its primary means of human > readable identification. Or something like that ;) > > >Did I use the correct format for the host name? > > > > > > Yes, more or less. Since homepc.com seems > to actually exist, this could either be a good > or bad choice, depending on whether or > not you own 'homepc.com'. If the machine is > on a private network and will do all it's connecting > via another box, it could probably get away with > 'foo.bar.baz' if you set up your DNS correctly. > > >What are the rules for creating the hostname name? > > > > > > See /etc/hosts. paraphrase ---"If you're directly > connected to the internet, you can't just make it up" > > >Are the rules published anywhere? > > > > > > > I'd check RFC's if I was *real* concerned. > > The good news? If something about your > selected hostname is causing problems, > all you have to do (as root) > > $hostname my.new.name > > > HTH, > > Kevin Kinsey > DaleCo, S.P. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: need info on hostname
On Nov 20, 2003, at 5:34 PM, fbsd_user wrote: Thanks for your reply, but you missed the meaning of my question. I am not interested in how hostname is used on the public internet and DNS stuff, I know that stuff. I want to know what the FBSD operating system does with it. Nothing, particularly. The FreeBSD operating system doesn't care what hostname you set, or even whether you set one at all: you could use localhost to refer to the current machine (via the 127.0.0.1 loopback interface) if the hostname was not explicitly set. More explicatively during the install of FBSD when asked to fill in the hostname prompt, what informative information should be given to the user so they can enter the correct stuff. Reading the /etc/hosts file provides no useful info. Is there any place in FBSD that explains how to fill in the install hostname prompt during the install? If you're configuring a standalone machine, the hostname doesn't matter. If one is configuring a machine to run on a network, one asks your local network admin, or ISP, or whoever is responsible for that network to provide you with the "network configuration" information. Often, simply using DHCP (run "dhclient" from the command line) to configure the machine will set all of this for you. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: need info on hostname
Thanks for your reply, but you missed the meaning of my question. I am not interested in how hostname is used on the public internet and DNS stuff, I know that stuff. I want to know what the FBSD operating system does with it. More explicatively during the install of FBSD when asked to fill in the hostname prompt, what informative information should be given to the user so they can enter the correct stuff. Reading the /etc/hosts file provides no useful info. Is there any place in FBSD that explains how to fill in the install hostname prompt during the install? Something like FBSD uses this hostname internally to name the PC running this FBSD operating system. It has to be us this format of an fully qualified domain name in the format of thisPCname.fakeDOMAINname.tld Where thisPCname came be any name you want to identify this particular pc on your LAN. Where .fakeDOMAINname can be any name you want as long as it's not an registered domain on the public internet unless it's registered to you. Using FBSDyourlastname is an safe domain name to use here. Were .tld can be any of the standard TLD's currently in use. Such as .com or .usa or .info or .cc -Original Message- From: Kevin D. Kinsey, DaleCo, S.P. [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 3:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] ORG Subject: Re: need info on hostname Quid pro quo: I'm not an expert, and don't play one on TV. fbsd_user wrote: >During the install you are asked for the host name which adds the >following line to rc.conf. >hostname="gateway.homepc.com" > >What does FBSD use this for? > > DNS? Same stuff as any other system, with the possible exception of that stuff from Redmond. Since 'Nix is/has always been very network oriented, this is its primary means of human readable identification. Or something like that ;) >Did I use the correct format for the host name? > > Yes, more or less. Since homepc.com seems to actually exist, this could either be a good or bad choice, depending on whether or not you own 'homepc.com'. If the machine is on a private network and will do all it's connecting via another box, it could probably get away with 'foo.bar.baz' if you set up your DNS correctly. >What are the rules for creating the hostname name? > > See /etc/hosts. paraphrase ---"If you're directly connected to the internet, you can't just make it up" >Are the rules published anywhere? > > > I'd check RFC's if I was *real* concerned. The good news? If something about your selected hostname is causing problems, all you have to do (as root) $hostname my.new.name HTH, Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: need info on hostname
Quid pro quo: I'm not an expert, and don't play one on TV. fbsd_user wrote: During the install you are asked for the host name which adds the following line to rc.conf. hostname="gateway.homepc.com" What does FBSD use this for? DNS? Same stuff as any other system, with the possible exception of that stuff from Redmond. Since 'Nix is/has always been very network oriented, this is its primary means of human readable identification. Or something like that ;) Did I use the correct format for the host name? Yes, more or less. Since homepc.com seems to actually exist, this could either be a good or bad choice, depending on whether or not you own 'homepc.com'. If the machine is on a private network and will do all it's connecting via another box, it could probably get away with 'foo.bar.baz' if you set up your DNS correctly. What are the rules for creating the hostname name? See /etc/hosts. paraphrase ---"If you're directly connected to the internet, you can't just make it up" Are the rules published anywhere? I'd check RFC's if I was *real* concerned. The good news? If something about your selected hostname is causing problems, all you have to do (as root) $hostname my.new.name HTH, Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: need info on hostname
> During the install you are asked for the host name which adds the > following line to rc.conf. > hostname="gateway.homepc.com" This is a Fully Qualified Domain Name (FQDN) of the computer following the standards of the DNS system. > What does FBSD use this for? Locating your computer by it's name on a network, as opposed to the IP. The name is translated into an IP address by a DNS server. > Did I use the correct format for the host name? Sure. On an internal network, you can use anything you like, but on the Internet, you would use one that actually has a real DNS entry. This is why you can see the FreeBSD website when you type www.freebsd.org into your browser. > What are the rules for creating the hostname name? Follow the DNS standards using the following convention: computername.domain.top_level_domain ie: mypc.homenetwork.com or: www.freebsd.org > Are the rules published anywhere? Sure. You can review one of the DNS rfc's here: http://www.faqs.org/rfcs/rfc1034.html Cheers, Steve > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
need info on hostname
During the install you are asked for the host name which adds the following line to rc.conf. hostname="gateway.homepc.com" What does FBSD use this for? Did I use the correct format for the host name? What are the rules for creating the hostname name? Are the rules published anywhere? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: I need info
On Thu, Mar 06, 2003 at 11:21:54AM -0600, JOSE D HERNANDEZ-TORRES wrote: > I am trying to install popa3d0.6.1 on a FreeBDS 4.7. I can not find > any documentation in your website. Can you tell me where I can find > installation and configuration documantation about it. Thak you popa3d is not part of FreeBSD, it's a port of third party software. Please contact the authors with support questions instead. Kris pgp0.pgp Description: PGP signature
I need info
I am trying to install popa3d0.6.1 on a FreeBDS 4.7. I can not find any documentation in your website. Can you tell me where I can find installation and configuration documantation about it. Thak you Sincerely, Jose Hernandez To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
