Re: How now, BSD crow?
Kris Kennaway wrote: On Fri, Oct 11, 2002 at 08:12:47AM +0200, Roelof Osinga wrote: Since NETSMB support is not in GENERIC, you must have added it to your kernel yourself at some point. When you modify your kernel configuration you need to read the documentation to make sure you're adding all necessary components (otherwise you'll get a broken kernel config, like you did). The documentation is in LINT. Yep. And took it out again, would still not build. Does now though. You're not exactly being specific here, but the full upgrade/rebuild procedure is spelled out in the handbook if you're confused about how to do it. And so I once did. I guess somehow a deviation from the pattern slipped in. Which I then faithfully copied at each rebuild. Also the reason I didn't check the handbook first. My bad. Sorry for the burden and thanks for the assistence! Roelof -- ___ EBOA® est. 1982 http://www.EBOA.com/tel. +31-58-2123014 mailto:info@;EBOA.com?subject=Information_request To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 07:51:12AM +0200, Roelof Osinga wrote: > > Did you do a make installworld? > > Nope. Just the buildworld. I'm redoing the things I jotted down on my > logs on previous builds. Went ok these last three or so years ;). If you haven't been running 'make installworld' for the last 3 years then you haven't actually upgraded your FreeBSD system in those 3 years. Kris msg50361/pgp0.pgp Description: PGP signature
Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 08:12:47AM +0200, Roelof Osinga wrote: > Especially LINT. LINT is nice if you want to look something up, but it is > not a hands-on manual that leads one through all the steps needing to be > taken to implement some such thingamathing or other. Since NETSMB support is not in GENERIC, you must have added it to your kernel yourself at some point. When you modify your kernel configuration you need to read the documentation to make sure you're adding all necessary components (otherwise you'll get a broken kernel config, like you did). The documentation is in LINT. > While I'm typing this, it just occurred to me. Some years ago the world got > rocked once again. There was something about making the world versus > explicitly > building it and installing it. Later it all got changed again. Every one of > those changes was deemed important. Every one of those changes changed > things. > > People don't like changes. Monkeys don't either. Dolphins I don't know. My > pitch is way off. You're not exactly being specific here, but the full upgrade/rebuild procedure is spelled out in the handbook if you're confused about how to do it. Kris msg50360/pgp0.pgp Description: PGP signature
Re: How now, BSD crow?
Kris Kennaway wrote: > On Fri, Oct 11, 2002 at 06:41:33AM +0200, Roelof Osinga wrote: > >>Kris Kennaway wrote: >> > > You don't have these files *INSTALLED* yet. cvsupping doesn't install > them for you, 'make world' (not 'make buildworld'!) does. Yeah. But in my notes which I've written down based on actions inspired by this mailling list, sometimes somethings needed to be done before and sometimes things needed to be done after. For a poor luser it is a murky mess, indeed. For the programmers, of course, it is very clear indeed. I know. I'm one of those. But my clients will agree with me on this ;). > In LINT (the canonical place where kernel options are documented) Canons be darned. /usr/src/UPGRADING is what everybody gets told to read. Not to inspect the canons. Whatever those may be. Especially LINT. LINT is nice if you want to look something up, but it is not a hands-on manual that leads one through all the steps needing to be taken to implement some such thingamathing or other. While I'm typing this, it just occurred to me. Some years ago the world got rocked once again. There was something about making the world versus explicitly building it and installing it. Later it all got changed again. Every one of those changes was deemed important. Every one of those changes changed things. People don't like changes. Monkeys don't either. Dolphins I don't know. My pitch is way off. So I, for one, don't really pay attention. I just do. If it don't work, well gosh. Bummer. Either I can fix it or I will need to sollicit help. Either way, I don't feel ashamed. The canonical place... yeah, right! ;) Roelof PS it is 'in cannons we trust', not canons! -- ___ EBOA® est. 1982 http://www.EBOA.com/tel. +31-58-2123014 mailto:[EMAIL PROTECTED]?subject=Information_request To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How now, BSD crow?
Phil Kernick wrote: >>> You probably forgot options LIBICONV from your kernel config file, >>> which is mandatory for SMBFS support (as documented). >> > ... > > # grep SMBFS /usr/src/sys/i386/conf/LINT > # grep LIBICONV /usr/src/sys/i386/conf/LINT Ta. Making as we type. >> PS did make world first too! So there. > > Did you do a make installworld? Nope. Just the buildworld. I'm redoing the things I jotted down on my logs on previous builds. Went ok these last three or so years ;). Check. That did the job. Thanks again! Roelof -- ___ EBOA® est. 1982 http://www.EBOA.com/tel. +31-58-2123014 mailto:[EMAIL PROTECTED]?subject=Information_request To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 06:41:33AM +0200, Roelof Osinga wrote: > Kris Kennaway wrote: > >On Fri, Oct 11, 2002 at 04:35:53AM +0200, Roelof Osinga wrote: > > > >... > >You have to have an up-to-date world before other targets like > >'modules-clean' are guaranteed to work. As you show: > > > >... > > > >You don't have these files installed yet. > > Ho humph. Did so do many a CVSup stable too. You don't have these files *INSTALLED* yet. cvsupping doesn't install them for you, 'make world' (not 'make buildworld'!) does. > >You probably forgot options LIBICONV from your kernel config file, > >which is mandatory for SMBFS support (as documented). > > Assuredly, but where? > > frl:/usr/local/etc/postfix$ grep LIBICONV /usr/src/UPDATING > frl:/usr/local/etc/postfix$ In LINT (the canonical place where kernel options are documented) # NETSMB enables support for SMB protocol, it requires LIBMCHAIN and LIBICONV # options. Kris msg50357/pgp0.pgp Description: PGP signature
Re: How now, BSD crow?
>> You probably forgot options LIBICONV from your kernel config file, >> which is mandatory for SMBFS support (as documented). > > > Assuredly, but where? > > frl:/usr/local/etc/postfix$ grep LIBICONV /usr/src/UPDATING > frl:/usr/local/etc/postfix$ > > Surely not there. So where's a poor luser who would not know a bit from > a byte > find the pointer to that so highly needed bit, not byte, of information? # grep SMBFS /usr/src/sys/i386/conf/LINT # grep LIBICONV /usr/src/sys/i386/conf/LINT > For I'm just a poor ... ;) > > Roelof > > PS did make world first too! So there. Did you do a make installworld? Phil. -- _-_|\ Phil Kernick E-Mail: [EMAIL PROTECTED] / \ ROTFL Enterprises Mobile: 041 61 ROTFL \_.-*_/ v Humourist, satirist, and probably a few more 'ists to boot! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How now, BSD crow?
Kris Kennaway wrote: > On Fri, Oct 11, 2002 at 04:35:53AM +0200, Roelof Osinga wrote: > > ... > You have to have an up-to-date world before other targets like > 'modules-clean' are guaranteed to work. As you show: > > ... > > You don't have these files installed yet. Ho humph. Did so do many a CVSup stable too. [... frl:/usr/local/etc/postfix$ cat /root/cvsup/stable-supfile # from test.nisser.com # changed the NL to the UK, though *default host=cvsup.uk.FreeBSD.org #*default host=cvsup.nl.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress src-all ...] >>smb_conn.o(.text+0x7ae): undefined reference to `iconv_open' > > > You probably forgot options LIBICONV from your kernel config file, > which is mandatory for SMBFS support (as documented). Assuredly, but where? frl:/usr/local/etc/postfix$ grep LIBICONV /usr/src/UPDATING frl:/usr/local/etc/postfix$ Surely not there. So where's a poor luser who would not know a bit from a byte find the pointer to that so highly needed bit, not byte, of information? For I'm just a poor ... ;) Roelof PS did make world first too! So there. -- ___ EBOA® est. 1982 http://www.EBOA.com/tel. +31-58-2123014 mailto:[EMAIL PROTECTED]?subject=Information_request To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: How now, BSD crow?
On Fri, Oct 11, 2002 at 04:35:53AM +0200, Roelof Osinga wrote: > frl:/usr/src/sys/compile/NISSER# make modules-clean > cd ../../modules ; env MAKEOBJDIRPREFIX=/usr/src/sys/compile/NISSER/modules > MACHINE=i386 make clean > ===> accf_data > "/usr/src/sys/modules/accf_data/../../conf/kmod.mk", line 63: Could not > find bsd.init.mk > "/usr/src/sys/modules/accf_data/../../conf/kmod.mk", line 190: Could not > find bsd.links.mk > make: fatal errors encountered -- cannot continue > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 You have to have an up-to-date world before other targets like 'modules-clean' are guaranteed to work. As you show: > frl:/usr/src/sys/compile/NISSER# find / -name bsd.init.mk -print > /usr/src/share/mk/bsd.init.mk You don't have these files installed yet. > smb_conn.o(.text+0x7ae): undefined reference to `iconv_open' You probably forgot options LIBICONV from your kernel config file, which is mandatory for SMBFS support (as documented). Kris msg50353/pgp0.pgp Description: PGP signature
