Server setup
I am setting up a new server and have a question. This server has three 8GB SCSIs, and one 160 GB IDE. I was interested in striping the SCSIs, which I have done. After installing FreeBSD 7 on the IDE, I set up the stripe and moved /var over to it. So, my first question would be whether I should put /var on the stripe or /usr ? My next question might be whether it was even worth striping the SCSI's and just installing, say, /var/log to one drive, /usr/home to another, etc Final question, assuming I go ahead with putting /var on the SCSI's, how do I now recover the partition that was being used by /var? There's about 3 Gb on there. Perhaps I could just mount it as /usr/ports? or should I choose a different approach? Thanks for any input. OH! BTW. This is going to be a backup server using BackupPC, so I will be installing an additional IDE later. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
removing phpMyAdmin
Well, I wanted to remove phpMyAdmin from my 5.3 server. Usually I would just go to the port location under /usr/ports/ and type make deinstall. However, phpMyAdmin apparently isn't here anymore. I don't even know exactly where it should be be but judging by freebsd's website, it should be under /usr/ports/www/ but it's not. In fact a locate and find for phpMyAdmin turns up nothing in the /usr/ports/ directory, except under /usr/ports/distfiles which is, of course, not what I need. Has phpMyAdmin been removed or has an update of ports gone astray? Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
removing phpMyAdmin
Well, I wanted to remove phpMyAdmin from my 5.3 server. Usually I would just go to the port location under /usr/ports/ and type make deinstall. However, phpMyAdmin apparently isn't here anymore. I don't even know exactly where it should be be but judging by freebsd's website, it should be under /usr/ports/www/ but it's not. In fact a locate and find for phpMyAdmin turns up nothing in the /usr/ports/ directory, except under /usr/ports/distfiles which is, of course, not what I need. Has phpMyAdmin been removed or has an update of ports gone astray? Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
removing phpMyAdmin
Well, I wanted to remove phpMyAdmin from my 5.3 server. Usually I would just go to the port location under /usr/ports/ and type make deinstall. However, phpMyAdmin apparently isn't here anymore. I don't even know exactly where it should be be but judging by freebsd's website, it should be under /usr/ports/www/ but it's not. In fact a locate and find for phpMyAdmin turns up nothing in the /usr/ports/ directory, except under /usr/ports/distfiles which is, of course, not what I need. Has phpMyAdmin been removed or has an update of ports gone astray? Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
removing phpMyAdmin
Well, I wanted to remove phpMyAdmin from my 5.3 server. Usually I would just go to the port location under /usr/ports/ and type make deinstall. However, phpMyAdmin apparently isn't here anymore. I don't even know exactly where it should be be but judging by freebsd's website, it should be under /usr/ports/www/ but it's not. In fact a locate and find for phpMyAdmin turns up nothing in the /usr/ports/ directory, except under /usr/ports/distfiles which is, of course, not what I need. Has phpMyAdmin been removed or has an update of ports gone astray? Curtis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
postfix w/pam
Can anyone tell me whether I have to install/build postfix w/pam support (if I want it to use pam). Or can I just do a make install of postfix, as well as of pam_ldap and nss_ldap, edit the appropriate files in /etc/pam.d/ and it should work? I have installed map_ldap and nss_ldap and have edited: /usr/local/etc/ldap.conf /etc/nsswitch.conf files within /etc/pam.d, particularly /etc/pam.d/ldap, ./imap and ./sshd and ./su /usr/local/etc/nss_ldap.conf But nonetheless it's not working with postfix (smtp) or with courier-imap (ssh works fine with pam). Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Opening ports
Forget all my questions! I was right. Postfix was choking on my access file (or the lack thereof). Once I got it fixed then postfix started working and listening on port 25. Curtis On 17 Dec, 2004, at 10:37, Lucas Holt wrote: Does courier-imap do smtp? Sendmail doesn't listen for outside mail by default, but in some cases it does listen on port 25 witout accepting connections. look at /etc/rc.conf and see what you have enabled. (firewall, courier and sendmail related variables) On Fri, 17 Dec 2004, Curtis Vaughan wrote: On 17 Dec, 2004, at 09:24, Curtis Vaughan wrote: I realized that apparently by default most all ports are closed on my 5.3-Release box. The reason I say this is because besides port 22, 80 and 1 no other port seems to be open (based on a port scan). I just installed postfix and courier-imap and wanted to test ports 25 and 110, but they do not respond even though postfix is running, I have enabled the ports in master.cf. Also they are in /etc/services. Looking over documents and checking my install, /etc/rc.firewall is not enabled in /etc/defaults/rc.conf. I assume I could go through rc.firewall and set it up for those ports I need opened, and enable it in rc.conf, but whereas we have a gatewall/firewall for our company, I don't see a lot of reason for having all the ports closed down on this server. Is there an easy way to enable them all? Curtis OK, I've got courier-imap running now and it opened port 143, but there is still no reply on 25. Which makes me think that the problem isn't the fact that ports are closed, but that nothing is listening. However, netstat shows: cod# netstat -na | grep LISTEN tcp4 0 0 *.143 *.* LISTEN tcp6 0 0 *.143 *.* LISTEN tcp4 0 0 *.80 *.* LISTEN tcp4 0 0 *.25 *.* LISTEN tcp4 0 0 *.1*.* LISTEN tcp4 0 0 *.22 *.* LISTEN tcp6 0 0 *.22 *.* LISTEN So, something is listening on port 25, but why no response to telnet requests? Curtis ___ [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: Opening ports
On 17 Dec, 2004, at 09:24, Curtis Vaughan wrote: I realized that apparently by default most all ports are closed on my 5.3-Release box. The reason I say this is because besides port 22, 80 and 1 no other port seems to be open (based on a port scan). I just installed postfix and courier-imap and wanted to test ports 25 and 110, but they do not respond even though postfix is running, I have enabled the ports in master.cf. Also they are in /etc/services. Looking over documents and checking my install, /etc/rc.firewall is not enabled in /etc/defaults/rc.conf. I assume I could go through rc.firewall and set it up for those ports I need opened, and enable it in rc.conf, but whereas we have a gatewall/firewall for our company, I don't see a lot of reason for having all the ports closed down on this server. Is there an easy way to enable them all? Curtis OK, I've got courier-imap running now and it opened port 143, but there is still no reply on 25. Which makes me think that the problem isn't the fact that ports are closed, but that nothing is listening. However, netstat shows: cod# netstat -na | grep LISTEN tcp4 0 0 *.143 *.* LISTEN tcp6 0 0 *.143 *.* LISTEN tcp4 0 0 *.80 *.* LISTEN tcp4 0 0 *.25 *.* LISTEN tcp4 0 0 *.1*.* LISTEN tcp4 0 0 *.22 *.* LISTEN tcp6 0 0 *.22 *.* LISTEN So, something is listening on port 25, but why no response to telnet requests? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Opening ports
I realized that apparently by default most all ports are closed on my 5.3-Release box. The reason I say this is because besides port 22, 80 and 1 no other port seems to be open (based on a port scan). I just installed postfix and courier-imap and wanted to test ports 25 and 110, but they do not respond even though postfix is running, I have enabled the ports in master.cf. Also they are in /etc/services. Looking over documents and checking my install, /etc/rc.firewall is not enabled in /etc/defaults/rc.conf. I assume I could go through rc.firewall and set it up for those ports I need opened, and enable it in rc.conf, but whereas we have a gatewall/firewall for our company, I don't see a lot of reason for having all the ports closed down on this server. Is there an easy way to enable them all? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CPU, RAM, information
Where do I find information in 5.3 about my cpu, ram, etc? Like under Linux I would go to /proc/ and look at files like cpuinfo and meminfo. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.3-Beta1 to 5.3-RELEASE
o update from cvs # cd /usr/src # make update o build world/kernel in your normal or single-user mode # cd /usr/obj # rm -rf * # cd /usr/src # make buildworld # make buildkernel KERNCONF=YOURKERNEL o install kernel/world in single user mode # reboot [ Choose single User Mode ] # cd /usr/src # make installkernel KERNCONF=YOURKERNEL # make installworld o run mergemaster -p # mergemaster -p o reboot # reboot It's fairly straight-forward once you get the gist :) Following Adam's suggestion, I have now gotten to the point where I rebooted into Single-User Mode, entered the /usr/src directory and then entered the command: make installkernel KERNCONF=MYKERNEL But it almost immediately comes back with errors about the fact that certain directories don't exist and problems with the fact that the file system is read only. Perhaps I entered Single User Mode wrong? On a reboot, I chose not to boot into any system, but to go directly to the loader prompt (something like that). Then I entered the command: boot -s Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.3-Beta1 to 5.3-RELEASE
Maybe you can disregard that. Looking at "The Complete FreeBSD" I see that you can just use GENERIC, if you want. So, I typed: make buildworld KERNCONF=GENERIC and off it went. Any reason why I wouldn't want to use GENERIC? I haven't compiled anything special for my kernel. On 18 Nov, 2004, at 12:12, Curtis Vaughan wrote: So basically: o update from cvs # cd /usr/src # make update o build world/kernel in your normal or single-user mode # cd /usr/obj # rm -rf * # cd /usr/src # make buildworld # make buildkernel KERNCONF=YOURKERNEL Adam! Sorry to bother you again, but I got as for as make buildworld, after which I typed "make buildkernel KERNCONF=MYKERNEL" and I got: cod# make buildkernel KERNCONF=MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). false *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any ideas why? Curtis o install kernel/world in single user mode # reboot [ Choose single User Mode ] # cd /usr/src # make installkernel KERNCONF=YOURKERNEL # make installworld o run mergemaster -p # mergemaster -p o reboot # reboot It's fairly straight-forward once you get the gist :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.3-Beta1 to 5.3-RELEASE
So basically: o update from cvs # cd /usr/src # make update o build world/kernel in your normal or single-user mode # cd /usr/obj # rm -rf * # cd /usr/src # make buildworld # make buildkernel KERNCONF=YOURKERNEL Adam! Sorry to bother you again, but I got as for as make buildworld, after which I typed "make buildkernel KERNCONF=MYKERNEL" and I got: cod# make buildkernel KERNCONF=MYKERNEL ERROR: Missing kernel configuration file(s) (MYKERNEL). false *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any ideas why? Curtis o install kernel/world in single user mode # reboot [ Choose single User Mode ] # cd /usr/src # make installkernel KERNCONF=YOURKERNEL # make installworld o run mergemaster -p # mergemaster -p o reboot # reboot It's fairly straight-forward once you get the gist :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: Upgrading 5.3-Beta1 to 5.3-RELEASE
Begin forwarded message: From: Adam Smith <[EMAIL PROTECTED]> Date: 17 November, 2004 16:10:29 PST To: Curtis Vaughan <[EMAIL PROTECTED]> Subject: Re: Upgrading 5.3-Beta1 to 5.3-RELEASE On Wed, Nov 17, 2004 at 03:50:03PM -0800, Curtis Vaughan said: Thanks! You say, go to /usr/src and enter the command make update. But there is nothing in my /usr/src directory. So, either I've done something wrong at some point, or I need to issue the command from a different directory. You didn't install the FreeBSD source code when you first installed your system. But I'm not sure how you install it once the system has been installed :( Maybe check it out on the FreeBSD site... You may just be able to download it as a tgz file an then extract it. Then run make update. Can anyone help me with this? Where do I go to get the source code to put in /usr/src ? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to reconfigure a port installation?
I was installing a port (make && make install) during which it asked me about some configuration information. Because I made a wrong choice at one point, the install failed. Now, I want to run make install again in order to chose the right options. Unfortunately, I can't just issue that command, as it apparently proceeds with what information I gave it the first time. Out of curiosity I tried make deinstall and pkg_delete, but they don't work as the port was never installed. So, what command to I need to issue? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: Upgrading 5.3-Beta1 to 5.3-RELEASE
On 08 Nov, 2004, at 17:38, Adam Smith wrote:
On Mon, Nov 08, 2004 at 04:49:42PM -0800, Curtis Vaughan said:
Just want to be sure that I do the right thing.
So, my version at present is 5.3-BETA1 and I want to install 5.3.
I supposed I could just install 5.3 over my current version, but
wouldn't an upgrade work just as well?
Finally, want to make sure I have the procedure right:
??? go to: /usr/local/etc/cvsup
??? issue the following command: /usr/local/bin/cvsup -g -L 2
stable-supfile
??? once finished, then go to: /usr/src
??? enter the commands:
There are some nicer ways to do this. Check
http://www.bugman.cx/cvsup/
for my make.conf, release-supfile and ports-supfile for examples. You
can
copy these three files into your /etc directory, and using the
make.conf
file, you can now just 'cd /usr/src' and then issue a 'make update'.
Your
make.conf flags will tell CVSup what to do.
Make sure you edit the three files carefully, as you'll want to specify
a
local CVSup server *and* you'll want to make sure the make.conf flags
are
correct. Remember that whenever you run 'make', the commands in
make.conf
are passed as options to the make command. That means if you have
'WITHOUT_X11=true' in your make.conf file, that will get passed to
every
single port build you perform.
If you already have a make.conf file you might want to just copy out
the
MASTER_ lines and all of the SUP lines (including PORTSSUPFILE) and put
them into your own make.conf.
Based on information Adam Smith wrote in his last letter to my request
on this subject I just wanted to be sure that I have done everything
correctly.
I have edited 2 of the files, but am not certain about whether I have
edited them right.
So, here they are one by one:
make.conf
MASTER_SITE_BACKUP?=\
ftp://ftp2.au.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/
MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP}
MASTER_SORT_REGEX?= ^file:
^ftp://ftp\.FreeBSD\.org/pub/FreeBSD/ports/local-distfiles/
://[^/]*\.au/ ://[^/]*\.au\.
SUP_UPDATE=yes
SUP=/usr/local/bin/cvsup
SUPFLAGS=-g -L 2 -r 0
SUPHOST=mirror.internode.on.net
SUPFILE=/etc/release-supfile
PORTSSUPFILE=/etc/ports-supfile
WITHOUT_GUI=true
WITHOUT_X11=true
WITHOUT_CUPS=false
[In the make.conf file I edited only the last line as I wanted CUPS on
the server. Was that a mistake. Also, I am uncertain where to put the
CVS server in this file.]
-
ports-supfile
*default host=cvsup10.us.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
ports-all tag=.
[I have removed all the commented out stuff. I have made this reflect
my ports-supfile, which works. Hence I changed default base, default
release. I think those are the only changes I made]
release-supfile
*default host=cvsup10.us.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_5_3
*default delete use-rel-suffix
src-all
[Now I have never used such a supfile before, but I made changes
similar to those in the ports-supfile: i.e., I changed the default
host. But I wasn't sure about the default base. Then as for default
release, I assume it is now 5_3?]
I really appreciate your input and help.
Curtis Vaughan
PS. You have no link to your release-supfile on your site, but do a
link to a src-supfile, which doesn't work. However, by typing in
release-supfile in my browser I was able to get your release-supfile.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrading 5.3-Beta1 to 5.3-RELEASE
Just want to be sure that I do the right thing. So, my version at present is 5.3-BETA1 and I want to install 5.3. I supposed I could just install 5.3 over my current version, but wouldn't an upgrade work just as well? Finally, want to make sure I have the procedure right: go to: /usr/local/etc/cvsup issue the following command: /usr/local/bin/cvsup -g -L 2 stable-supfile once finished, then go to: /usr/src enter the commands: make buildworld KERNCONF=yourkernelname (for name, look to config file found in /usr/src/sys/i386/conf/) make buildkernel KERNCONF=yourkernelname (look to / ) make installkernel KERNCONF=yourkernelname reboot You should boot in single user mode (using boot -s from loader prompt for example). Then continue with: mergemaster -p go to /usr/src and type: make installworld mergemaster update /dev (for 4.x only) reboot ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Port upgrading - my way
Oh, I must have had Donald's letter go into my bit bucket as I only saw this message with his reply. (Donald, you reply, "Touché", as I was just joking.) Anyhow, I did do it Donald's "my way" and I just like this other way better for some reason. Sorry Curtis On 23 Sep, 2004, at 22:42, Günther Dippe wrote: Hi all, It seems like the message below doesn't belong on this list unless I completely misunderstood the purpose of it. If I'm wrong please let me know. Cheers Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. >>> OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. ___ [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: Port upgrading - my way
Oh, I must have had Donald's letter go into my bit bucket as I only saw this message with his reply. (Donald, you reply, "Touché", as I was just joking.) Anyhow, I did do it Donald's "my way" and I just like this other way better for some reason. Sorry Curtis On 23 Sep, 2004, at 22:42, Günther Dippe wrote: Hi all, It seems like the message below doesn't belong on this list unless I completely misunderstood the purpose of it. If I'm wrong please let me know. Cheers Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. >>> OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. ___ [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: Port upgrading - my way
There might be something to be said for doing it "my way", after all, Frank Sinatra made a fortune in that manner... You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne ;-) Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l "<" [to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Port upgrading - my way
OK, I took Donald on with his test and this is what I got: Here's my INDEX-5 info before running portversion 4947853 Mar 15 2004 INDEX-5 and here it is after 5804696 Sep 21 13:54 INDEX-5 So, a definite change. And when I ran portversion -vL= the first time, I got the info provided immediately below. But the second time I ran portversion -vL= there was not output. So, what exactly does that mean? and does that mean that now I should run portupgrade -a now? apache-1.3.31_6 > succeeds port (port has 1.3.29_3) bandwidthd-1.2.1> succeeds port (port has 1.2.0_1) bash-2.05b.007_2> succeeds port (port has 2.05b.007) bsdiff-4.2 > succeeds port (port has 4.1) expat-1.95.8> succeeds port (port has 1.95.7) ezm3-1.2> succeeds port (port has 1.1_1) freebsd-update-1.6 > succeeds port (port has 1.5) freetype2-2.1.7_3 > succeeds port (port has 2.1.5_2) gd-2.0.25,1 > succeeds port (port has 2.0.15_1,1) jpeg-6b_3 > succeeds port (port has 6b_1) libiconv-1.9.2_1> succeeds port (port has 1.9.1_3) libtool-1.5.8 > succeeds port (port has 1.5.2_1) m4-1.4.1> succeeds port (port has 1.4_1) openldap-client-2.2.15 > succeeds port (port has 2.2.6) p5-Net-SSLeay-1.25 > succeeds port (port has 1.23) pam_ldap-1.7.1_1> succeeds port (port has 1.6.7_1) perl-5.8.5 > succeeds port (port has 5.8.2_5) png-1.2.6 > succeeds port (port has 1.2.5_3) popt-1.7> succeeds port (port has 1.6.4_2) portupgrade-20040701_3 > succeeds port (port has 20040208) postfix-2.1.4,1 > succeeds port (port has 2.0.18,1) rsync-2.6.2_3 > succeeds port (port has 2.6.0) ruby-1.8.2.p2_1 > succeeds port (port has 1.8.1_2) samba-2.2.11_1 > succeeds port (port has 2.2.8a_1) sudo-1.6.8.1> succeeds port (port has 1.6.7.5) unzip-5.51 > succeeds port (port has 5.50_2) webmin-1.150_5 > succeeds port (port has 1.130_10) On 21 Sep, 2004, at 12:22, Donald J. O'Neill wrote: On Tuesday 21 September 2004 12:40 pm, Curtis Vaughan wrote: I just want to know whether there is any reason I shouldn't be doing it this way. In other words, by doing it this way is there a potential problem or error that my result? <<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>> Yes, there is. As far as I can tell from what you've given, you're depending on INDEX-5 to be up to date after your ports upgrade. I don't believe it is and you need to run make index or some other means of getting INDEX-5 to be up to date.. Try this experiment: cvsup your ports note the date and size of /usr/ports/INDEX-5 run " portversion -vL=" or portversion -rRvc keep track of that output now cd /usr/ports make index note the date and size of INDEX-4 run portversion -vL= or portverstion -rRvc I think you'll see a lot more of your installed stuff needs updating. Don -- Donald J. O'Neill [EMAIL PROTECTED] ___ [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]"
Port upgrading - my way
I got a lot of feedback earlier about ways to do port upgrades and I really appreciate it. I know everyone has their own way. For now, I am doing it the following way. I just want to know whether there is any reason I shouldn't be doing it this way. In other words, by doing it this way is there a potential problem or error that my result? First I run: /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile My ports-supfile reads: *default host=cvsup10.us.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all tag=. Then I run: portupgrade -a That's it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.3 stable when?
Isn't 5.3 supposed to be going stable here soon? Any time line? Also, since I have 5.3-BETA1 and I see it's at 5.3-BETA5, should I worry about upgrading to BETA5 or just wait till it goes stable? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bandwidthd web access
So, I just installed bandwidthd on FreeBSD 5.3-Beta. I don't have Apache installed on this system, however, and maybe that's why I can't access the web page for this from another computer. I was thinking that it maybe provided it's own web engine as I would like to avoid installing apache on this system. Nonetheless, if I go to /usr/local/bandwidthd/htdocs and use lynx to view the html pages there, then I see bandwidthd is working and collecting information as it should. So, what is it that I'm missing to get these pages served internal to our LAN? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
What to backup
I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Setting up pam_ldap & nss_ldap
On 5.3-Beta I have installed pam_ldap and nss_ldap. Then I edited the following files: /usr/local/etc/ldap.conf /etc/nsswitch.conf files within /etc/pam.d particularly /etc/pam.d/ldap and ./sshd and ./su /usr/local/etc/nss_ldap.conf I think that's it. I can provide each of those files if necessary. Nonetheless authentication for users not local to this system is not occurring (which would normally occur for me under Linux). I have tried authenticating the following ways: 1) through ssh; 2) through su. I have noticed, however, that the way I do this under Linux is not the same as for FreeBSD. So, it's quite possible that I have left something out. Anyhow, I would appreciate any input into what needs to be configured to get this to work. Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1, 5.2, or 5.3???
On 01 Sep, 2004, at 11:44, Charles Swiger wrote: On Sep 1, 2004, at 1:58 PM, Curtis Vaughan wrote: So, I have been told that I shouldn't put 5.x on a production box, but on the other hand I need pam_ldap, nss_ldap support on my box, which I have also been told is only available in 5.x. If you have reason to need PAM & NSS support for LDAP, yes, you need to be running 5.x, or else you might consider some Linux flavor as better serving your requirements. Whereas this is to be a Postfix server, I would like to know, which version of 5.x should I install, or perhaps there is a way to use linux emulation for pam and nss under 4.x? If, however, 5.x I must install, which would people recommend and what problems will I be facing by putting it into production? Quite possibly, you won't encounter any problems. BTW, if your only requirement driving the need for LDAP is mail users, one can set up Postfix and SASL to talk to LDAP, as well as configuring IMAP/POP to use LDAP-based accounts. pam_ldap lets one have authenticated Unix-level users from LDAP accounts; if you don't need LDAP shell accounts, 4.x will be enough. Do not install 5.1; it's too old, too many bugs. 5.2.1 is probably the most stable version available now, but there are significant bumps between it and the 5.3 betas now available which make upgrading to what will be 5-STABLE somewhat difficult. If you've got the time to test the system, install a 5.3 beta. If you can wait two weeks, 5.3 will become the preferred choice. -- -Chuck Just out of curiosity, what is going to happen in 2 weeks? Actually, I have 5.3-Beta installed on it right now. So, maybe I'll just keep it, but wait to put it into production. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.1, 5.2, or 5.3???
So, I have been told that I shouldn't put 5.x on a production box, but on the other hand I need pam_ldap, nss_ldap support on my box, which I have also been told is only available in 5.x. Whereas this is to be a Postfix server, I would like to know, which version of 5.x should I install, or perhaps there is a way to use linux emulation for pam and nss under 4.x? If, however, 5.x I must install, which would people recommend and what problems will I be facing by putting it into production? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.x - which to install? (Was Re: LDAP, pam, nss)
On 30 Aug, 2004, at 22:16, Konrad Heuer wrote: On Mon, 30 Aug 2004, Curtis Vaughan wrote: In order to get centralized logins to work on my Linux Debian computers (authenticating of a RedHat Samba server), I have to: install libnss-ldap libpam-ldap. Perform some configuration on the of /etc/libnss-ldap.conf and /etc/pam-ldap.conf files. Edit the /etc/nnsswitch.conf file. Then I can check that the packages have been installed by issuing the command nscd. Finally to get authentication happening in specific applications, I go to the directory /etc/pam.d/ and edit the service files there though which I want such authentication to occur. Now, of course, no one here is looking for instructions on how to do something on Linux, but I was now wondering what it is I need to do on my FreeBSD server to get this functionality working? I can't seem to find anything similar so far in my searches. Thanks for any pointers in the right direction. With FreeBSD 4.x, you won't get very far. But beginning with 5.x (not to say 5.2.1-R), it's very similar. Install the following ports: /usr/ports/security/pam_ldap /usr/ports/net/nss_ldap Edit /usr/local/etc/ldap.conf, build /etc/nsswitch.conf, and edit the files within /etc/pam.d. Regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, [EMAIL PROTECTED] Taking into consideration that I want this server to be a Postfix server w/Courier IMAP and as stable as possible and the aforementioned, of course, which version of 5.x should I install? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LDAP, pam, nss
In order to get centralized logins to work on my Linux Debian computers (authenticating of a RedHat Samba server), I have to: install libnss-ldap libpam-ldap. Perform some configuration on the of /etc/libnss-ldap.conf and /etc/pam-ldap.conf files. Edit the /etc/nnsswitch.conf file. Then I can check that the packages have been installed by issuing the command nscd. Finally to get authentication happening in specific applications, I go to the directory /etc/pam.d/ and edit the service files there though which I want such authentication to occur. Now, of course, no one here is looking for instructions on how to do something on Linux, but I was now wondering what it is I need to do on my FreeBSD server to get this functionality working? I can't seem to find anything similar so far in my searches. Thanks for any pointers in the right direction. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Messed up port updating (Was Re: Updated to 4.10, now portupgrade?)
On 26 Aug, 2004, at 16:10, Kevin D. Kinsey, DaleCo, S.P. wrote: Curtis Vaughan wrote: Ok, first off I didn't follow the instructions above verbatim. What I did do is copy ports-supfile, edited it, and perform a cvsup using it. All it seemed to do, however, is delete everything in the ports directory. Here's how I edited my ports-supfile *default host=cvsup10.us.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix ports-all Did I do something horribly wrong? Yes. Well, not horrible, but this was pilot error. As I think you've been told once already recently (or at least someone has told someone else within the last 48 hours or so) you ***must*** use: *default release=cvs tag=. (that's a dot or 'period'), because the ports tree isn't tagged like the RELENG branches are. So, in your case, cvsup replaced your extant ports tree with all the ones from the release it couldn't find, which happened to be nil ... and your ports collection is now blank. Kevin Kinsey Now after running a successful cvsup with ports-supfile, I went to /usr/src/ and typed make update, which didn't really seem to do anything. The prompt returned immediately. So, I typed portsdb -U and its running. However, I notice there are a number of "make: fatal errors encountered..." and "*** Error code 1: malformed entry: ***" . Is this something to be worried about? On the other hand it looks as though they may have something to do with other language ports (german, french, etc.). And I had the default refuse file under /sup/ in order not to download other language ports. So, this makes me think that it doesn't really matter. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Messed up port updating (Was Re: Updated to 4.10, now portupgrade?)
On 25 Aug, 2004, at 17:44, Steven Friedrich wrote: On Wednesday 25 August 2004 08:01 pm, Curtis Vaughan wrote: So now that I'm running 4.10, I understand I need to do a portupgrade on all ports? and then I'll install the ports I want. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Nope. What you want to do is cvsup the ports collection, and probably the src-all collection. There are many ways to do it but here's how I do it. Here's my /etc/make.conf. Notice the lines regarding the three sup files: # LIGHTNING: /etc/make.conf # # CPUTYPE doesn't work in 4.x yet, except openssh #CPUTYPE=p4 # X_WINDOW_SYSTEM=xfree86-4 # BDECFLAGS= -W -Wall -amsi -pedantic -Wbad-function-cast -Wcast-align \ -Wcast-qual -Wchar-subscripts -Winline \ -Wmissing-prototypes -Wnested-externs -Wpointer-arith \ -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings # # To avoid building various parts of the base system: NOPROFILE= true # Avoid compiling profiled libraries # # If you're resident in the USA, this will help various ports to determine # whether or not they should attempt to comply with the various U.S. # export regulations on certain types of software which do not apply to # anyone else in the world. # USA_RESIDENT= YES # # CVSup update flags. Edit SUPFILE settings to reflect whichever distribution # file(s) you use on your site (see /usr/share/examples/cvsup/README for more # information on CVSup and these files). To use, do "make update" in /usr/src. # SUP_UPDATE= yes # SUP=/usr/local/bin/cvsup #SUPFLAGS= -g -L 2 SUPHOST=cvsup.FreeBSD.org SUPFILE=/root/cvsup/stable-supfile PORTSSUPFILE= /root/cvsup/ports-supfile DOCSUPFILE= /root/cvsup/doc-supfile # # Documentation # # The list of languages and encodings to build and install # DOC_LANG= en_US.ISO8859-1 # cups-lpr requirements #CUPS_OVERWRITE_BASE=yes #NO_LPR=yes # # -- use.perl generated deltas -- # # Created: Sun Aug 8 11:13:32 2004 # Setting to use base perl from ports: #PERL_VER=5.8.5 #PERL_VERSION=5.8.5 #PERL_ARCH=mach #NOPERL=yo #NO_PERL=yo #NO_PERL_WRAPPER=yo You can use find to find these files on your machine: find / -name ports-supfile You should also use find to look for an example make.conf. There's knowledge in there. Don't be offended if you're familiar with find, I have no idea about your expertise. And within the ports-supfile, you'll probably let it say ports-all. So then you go to /usr/src and say: make update And if you have if set up right, it'll connect to the cvsup server of your choice and download the latest changes. Please refer to the handbook for more details for what I've discussed so far and/or ask questions. After cvsupping the ports skeleton (a collection of Makefiles, etc.) you need to run portsdb -U. All the preceeding requires at least two ports already be installed, cvsup (or cvsup-without-gui if you don't have X windows installed) and portupgrade. Once you've cvsupped the ports skeleton, you'll be able to install the latest version of any port (on occasion they're broke though). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Ok, first off I didn't follow the instructions above verbatim. What I did do is copy ports-supfile, edited it, and perform a cvsup using it. All it seemed to do, however, is delete everything in the ports directory. Here's how I edited my ports-supfile *default host=cvsup10.us.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix ports-all Did I do something horribly wrong? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Updated to 4.10, now portupgrade?
So now that I'm running 4.10, I understand I need to do a portupgrade on all ports? and then I'll install the ports I want. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.8 > 4.10 successful. Now > 5.x?
4.x is really a great unix. Very stable and plenty capable. If the software you're hoping to run REQUIRES features in 5.x, I recommend installing it directly. Meantime, I'd use mobile racks and install 4.x on one so I could learn more about maintaining FreeBSD, installing ports/packages, etc. I have two identical boxes at home with RAID pairs. So on one pair I have WinBlows xp (which can only run in one of the two boxes because if WinBlows detects hardware changes, they'll disable the OS and you'll have to call them to get back in). Other pairs include: lightning - FreeBSD 4.10-STABLE daemon - FreeBSD 4.10-STABLE gandalf - FreeBSD 5.2.1-CURRENT freakinBSD - FreeBSD 5.2.1-CURRENT So these pairs can be slid into EITHER box and run just fine (talk about recovering from a hardware failure quickly!) 5.x is bleeding edge and too many inexperienced people are running it. I track it merely for the learning experience. I started as a data systems tech in the Navy in 1976. I've been a field service engineer, level-3 tech support, tech writer, programmer, sys admin, and janitor 8oP, and I am challenged trying to track -CURRENT. People who want production machines shoudn't be tracking -CURRENT or -STABLE, IMHO. They should jump from release to release, i.e., run 4.9 until 4.10 has been out for a couple months, etc. Let OTHER people be beta sites. YMMV. _ Whereas I intend to run this server as a Postfix server w/ Courier IMAP, authentication through PAM/LDAP it would seem that I should stay at 4.10 then. Is this correct or not? Also, if this server goes into production, then how much of a pain in the ass is it going to be to move to 5.x when it's stable? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.8 > 4.10 successful. Now > 5.x?
On 25 Aug, 2004, at 12:11, Kevin D. Kinsey, DaleCo, S.P. wrote: Curtis Vaughan wrote: Ok, it looks as though cvsup from 4.8 to 4.10 has been successful. Now, first off I want to say that I want this server to be a second Postfix / Courier IMAP server (our other is on a RedHat server, but that's irrelevant). I feel that I should go ahead and first upgrade to 5.x and then install Postfix and everything else I will need (e.g., PAM/LDAP authentication, user folders, Samba, etc.). Otherwise, I'm afraid I stop at 4.10 and install all the applications I need, then when I really want to upgrade to 5.x I may find myself in trouble. But I am interested in what the rest of you think. Curtis For various reasons, most of us mere mortals are advised to simply backup and install 5.x to a new disk (or a cleaned one, anyway). I started to say why ... I find that I can make a list of new features in 5.x, but am not necessarily aware of which features make a complete reinstallation desirable. I do know that you can't use ufs2 unless you reinstall Kevin Kinsey So, which of the 5.x should I install? 5.1, 5.2.1, 5.3? I want to be as Stable as possible. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.8 > 4.10 successful. Now > 5.x?
Ok, it looks as though cvsup from 4.8 to 4.10 has been successful. Now, first off I want to say that I want this server to be a second Postfix / Courier IMAP server (our other is on a RedHat server, but that's irrelevant). I feel that I should go ahead and first upgrade to 5.x and then install Postfix and everything else I will need (e.g., PAM/LDAP authentication, user folders, Samba, etc.). Otherwise, I'm afraid I stop at 4.10 and install all the applications I need, then when I really want to upgrade to 5.x I may find myself in trouble. But I am interested in what the rest of you think. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup
On 25 Aug, 2004, at 06:39, Ilker OZUPAK wrote: On Wednesday 25 August 2004 02:49, Warren Block wrote: On Tue, 24 Aug 2004, Curtis Vaughan wrote: BTW! After updating to 4-STABLE do I then perform all the following steps? Go to /usr/src enter the command: make buildworld KERNCONF=yourkernelname in your mail you asked about a good name. actully the name mantioned here is the name of config file for your kernel which is located at /usr/src/sys/i386/conf/ Well, since I have already done: make buildworld KERNCONF=kernel.STABLE does that in any way mess up the process of upgrading? That is, do I need to start this process over? If so, how? I noticed that nonetheless I now have a kernel and a kernel.GENERIC file in my root directory. BTW, how come I can't scroll on the terminal. In Linux I am used to using PGUP and PGDN in order to scroll up and down my terminal. I can't figure out that functionality under FreeBSD. Even under bash this doesn't work. (NB. I am not using X windows of any sort) Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup
On 24 Aug, 2004, at 16:07, stheg olloydson wrote: it was said: Ok, just to be certain about this. I have 4.8 installed and am about to do a cvsup here is my stable-supfile *default host=cvsup1.us.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix src-all And I put my refuse file in /usr/local/etc/cvsup/sup/ Am I ready to roll? Hello, If you mean are you ready to update your base system to 4-STABLE, then yes, you're ready to roll. If you mean are you ready to update your entire system to the latest production release, then, no, you're not ready to roll. What are you trying to accomplish? Regards, Stheg Right, just to 4-STABLE for now. After this I want to then try to upgrade to 5.x. Let's see how this goes first. Thanks! BTW! After updating to 4-STABLE do I then perform all the following steps? Go to /usr/src enter the command: make buildworld KERNCONF=yourkernelname then: make kernel reboot go to /usr/src and type: make installworld And what is a good kernel name? Maybe in this case, kernel.STABLE ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup
Ok, just to be certain about this. I have 4.8 installed and am about to do a cvsup here is my stable-supfile *default host=cvsup1.us.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix src-all And I put my refuse file in /usr/local/etc/cvsup/sup/ Am I ready to roll? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reinstalling, then upgrading
On 23 Aug, 2004, at 13:16, Robert Huff wrote: Curtis Vaughan writes: Finally, while I'm reinstalling 4.8, I would like to know something about the following. It seems to me that cvsup is actually downloading the entire repository of packages for FreeBSD. Is that really what one has to do to perform an upgrade? Cvsup updates what you tell it to update - if you ask correctly, as little as a single file. It seems like what you would need to do is merely upgrade those packages necessary for the latest kernel, "world". then upgrade the kernel, "kernel". then upgrade all installed packages. (Packages meaning ports, right?) "ports". And that's right, except Once you've installed the ports tree (say from CD) do one run of cvsup to bring the tree up to date. This may be a fairly large update, but will not be everything because some ports haven't changed in years. Afterwards, you can run another update once a week, or once a month. (Once a month is stretching it, because some popular ports get updated very frequently.) If there are parts of the ports tree you don't care about (e.g. vietnamese or mbone) there are ways to tell cvsup to ignore that entire sub-tree. Did this answer your question? (And if not, can you be more specific?) Robert Huff I think so for now. Thanks! Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reinstalling, then upgrading (Was Re: Salvageable? (Was Re: make installworld error))
Thanks to everyone who has been answering my questions over the past several days (weeks) concerning installing and upgrading FreeBSD. I am now going to try again. I am installing v. 4.8 on a server. This server is to be a Postfix w/Courier IMAP server integrated into a Linux-based network, authentication centralized using PAM & LDAP. That's about it. Now, some people might say, don't install 4.8 go straight for 5.x. The reason I am doing this, however, is because I want to not only know how to perform upgrades, but I want hands on experience. So, hopefully I am not making this too difficult for me. Finally, while I'm reinstalling 4.8, I would like to know something about the following. It seems to me that cvsup is actually downloading the entire repository of packages for FreeBSD. Is that really what one has to do to perform an upgrade? It seems like what you would need to do is merely upgrade those packages necessary for the latest kernel, then upgrade the kernel, then upgrade all installed packages. (Packages meaning ports, right?) Thanks again! Curtis On 23 Aug, 2004, at 11:10, Steven Friedrich wrote: On Monday 23 August 2004 01:58 pm, Curtis Vaughan wrote: On 23 Aug, 2004, at 10:51, Steven Friedrich wrote: On Monday 23 August 2004 01:39 pm, Curtis Vaughan wrote: So, could someone tell me if my system is salvageable or not and what I need to do? Or, should I just start over? Curtis On 21 Aug, 2004, at 17:06, Curtis Vaughan wrote: So, it is my understanding that I did in fact do things right (or that is to say that The Complete FreeBSD had the right directions. But that something else went wrong. BTW, I installed 4.8 from scratch. Then spent a couple of days preparing to do a cvsup making sure that I set everything up right (sources: Complete FreeBSD, freebsd.org, and this list. Then I did the cvsup. Everything else I've already written about in a previous letter. Unfortunately, it doesn't seem that booting into an old kernel is an option. I have looked at the files on my system and there is no kernel.old or anything like it. There is only a kernel directory under the /boot/ directory. What information do I need to provide to perhaps salvage this system? And what steps did I possibly miss? Curtis "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]> writes: Yup. Go back to the top --- I missed where in your list of steps you actually *installed* the new kernel... That would be where he said: make kernel which is equivalent to "make buildkernel installkernel". It doesn't explain quite what's happening here, though -- and he didn't even *hint* at such basic clues as what version he was updating from or to (there may be extra steps for large updating jumps). Booting the old kernel is certainly worth a try before starting over, though; the system is quite likely to be salvageable. ___ [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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Try to boot into single-user mode, i.e., when the system boots, it'll display a 10 second countdown. Hit spacebar to abort the countdown. Then type boot -s and it'll boot into single-user mode with only the root partition mounted. type mount -a to get the other partitions mounted. Then redo your buildworld,etc., but skip mergemaster stuff. Here's the steps: cd /usr/src make buildworld make buildkernel KERNCONF=yourkernelname (you DID copy GENERIC and customize it didn't you?) make installkernel KERNCONF=yourkernelname make installworld reboot Skipping the mergemaster stuff will mean that any recent changes to various config files will be missing, but you should be able to come up multi-user. If these steps fail, it'll probably be easier to just reinstall. As I wrote in an earlier letter, I can't get into single-user mode. Here's what happens after using the boot -s option: It's asks: Enter full pathname of shell or RETURN for /bin/sh But when I hit RETURN, it says: pid 7 (ssh), uid -: exited on signal 12 Aug 20 08:41:58 init: single user shell terminated, restarting and then it asks again: Enter full path I have tried also manually entering in: /bin/sh /bin/csh /bin/chsh /usr/local/bin/bash etc. etc. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscrib
Re: Salvageable? (Was Re: make installworld error)
On 23 Aug, 2004, at 10:51, Steven Friedrich wrote: On Monday 23 August 2004 01:39 pm, Curtis Vaughan wrote: So, could someone tell me if my system is salvageable or not and what I need to do? Or, should I just start over? Curtis On 21 Aug, 2004, at 17:06, Curtis Vaughan wrote: So, it is my understanding that I did in fact do things right (or that is to say that The Complete FreeBSD had the right directions. But that something else went wrong. BTW, I installed 4.8 from scratch. Then spent a couple of days preparing to do a cvsup making sure that I set everything up right (sources: Complete FreeBSD, freebsd.org, and this list. Then I did the cvsup. Everything else I've already written about in a previous letter. Unfortunately, it doesn't seem that booting into an old kernel is an option. I have looked at the files on my system and there is no kernel.old or anything like it. There is only a kernel directory under the /boot/ directory. What information do I need to provide to perhaps salvage this system? And what steps did I possibly miss? Curtis "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]> writes: Yup. Go back to the top --- I missed where in your list of steps you actually *installed* the new kernel... That would be where he said: make kernel which is equivalent to "make buildkernel installkernel". It doesn't explain quite what's happening here, though -- and he didn't even *hint* at such basic clues as what version he was updating from or to (there may be extra steps for large updating jumps). Booting the old kernel is certainly worth a try before starting over, though; the system is quite likely to be salvageable. ___ [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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Try to boot into single-user mode, i.e., when the system boots, it'll display a 10 second countdown. Hit spacebar to abort the countdown. Then type boot -s and it'll boot into single-user mode with only the root partition mounted. type mount -a to get the other partitions mounted. Then redo your buildworld,etc., but skip mergemaster stuff. Here's the steps: cd /usr/src make buildworld make buildkernel KERNCONF=yourkernelname (you DID copy GENERIC and customize it didn't you?) make installkernel KERNCONF=yourkernelname make installworld reboot Skipping the mergemaster stuff will mean that any recent changes to various config files will be missing, but you should be able to come up multi-user. If these steps fail, it'll probably be easier to just reinstall. As I wrote in an earlier letter, I can't get into single-user mode. Here's what happens after using the boot -s option: It's asks: Enter full pathname of shell or RETURN for /bin/sh But when I hit RETURN, it says: pid 7 (ssh), uid -: exited on signal 12 Aug 20 08:41:58 init: single user shell terminated, restarting and then it asks again: Enter full path I have tried also manually entering in: /bin/sh /bin/csh /bin/chsh /usr/local/bin/bash etc. etc. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Salvageable? (Was Re: make installworld error)
So, could someone tell me if my system is salvageable or not and what I need to do? Or, should I just start over? Curtis On 21 Aug, 2004, at 17:06, Curtis Vaughan wrote: So, it is my understanding that I did in fact do things right (or that is to say that The Complete FreeBSD had the right directions. But that something else went wrong. BTW, I installed 4.8 from scratch. Then spent a couple of days preparing to do a cvsup making sure that I set everything up right (sources: Complete FreeBSD, freebsd.org, and this list. Then I did the cvsup. Everything else I've already written about in a previous letter. Unfortunately, it doesn't seem that booting into an old kernel is an option. I have looked at the files on my system and there is no kernel.old or anything like it. There is only a kernel directory under the /boot/ directory. What information do I need to provide to perhaps salvage this system? And what steps did I possibly miss? Curtis "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]> writes: Yup. Go back to the top --- I missed where in your list of steps you actually *installed* the new kernel... That would be where he said: make kernel which is equivalent to "make buildkernel installkernel". It doesn't explain quite what's happening here, though -- and he didn't even *hint* at such basic clues as what version he was updating from or to (there may be extra steps for large updating jumps). Booting the old kernel is certainly worth a try before starting over, though; the system is quite likely to be salvageable. ___ [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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make installworld error
So, it is my understanding that I did in fact do things right (or that is to say that The Complete FreeBSD had the right directions. But that something else went wrong. BTW, I installed 4.8 from scratch. Then spent a couple of days preparing to do a cvsup making sure that I set everything up right (sources: Complete FreeBSD, freebsd.org, and this list. Then I did the cvsup. Everything else I've already written about in a previous letter. Unfortunately, it doesn't seem that booting into an old kernel is an option. I have looked at the files on my system and there is no kernel.old or anything like it. There is only a kernel directory under the /boot/ directory. What information do I need to provide to perhaps salvage this system? And what steps did I possibly miss? Curtis > "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]> writes: > >> Yup. Go back to the top --- I missed where >> in your list of steps you actually *installed* >> the new kernel... > > That would be where he said: > >> > make kernel > > which is equivalent to "make buildkernel installkernel". > > It doesn't explain quite what's happening here, though -- and he > didn't even *hint* at such basic clues as what version he was updating > from or to (there may be extra steps for large updating jumps). > > Booting the old kernel is certainly worth a try before starting over, > though; the system is quite likely to be salvageable. > ___ > [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: make installworld error
> Curtis Vaughan wrote: > >> After going through a cvsup >> make buildworld >> make kernel >> reboot >> >> I am now on make installworld >> > > A little too quickly, it seems. > >> I had to do a mergemaster -p in order to get make installworld to run, > > > And the reason for that you may see in a minute ... > >> but finally after seemingly corrected all the changes wtih >> mergemaster, make installworld ran. >> >> Well, it ran for a good while but then errored out with: >> >> install -o root -g wheel -m 444 test.1.gz /usr/share/man/man1 >> *** Signal 12 >> >> Now I'm really screwed. >> > > Yup. Go back to the top --- I missed where > in your list of steps you actually *installed* > the new kernel... > > From the handbook: > > Warning: While it is possible to update only parts of your > source tree, the only supported update procedure is to > update the entire tree and recompile both userland (i.e., > all the programs that run in user space, such as those in > /bin and /sbin) and kernel sources. Updating only part of > your source tree, only the kernel, or only userland will > often result in problems. These problems may range > from compile errors to kernel panics or data corruption. > > And also, the section entitled "The Canonical way to update your system": > > To update your system, you should use the following procedure: > > # make buildworld > # make buildkernel > # make installkernel (emphasis mine) > # reboot > > You should boot in single user mode (using boot -s from loader > prompt for example). Then run: > > # mergemaster -p > # make installworld > # mergemaster > # reboot > > I'm not sure what to advise; your world is calling for > system calls your (old) kernel doesn't have. Either > reinstall on a new or blanked HDD and restore your > backed up data, or see if you can mount the drive on > another box and move all the kernel stuff (the new stuff) > to where it belongs, or stick around and see if someone > smarter than me (I'm afraid I'm not very knowledgeable > re: such things) has a better plan. > > Kevin Kinsey > DaleCo, S.P. > Well, that really sucks. I hate to say this, but I was going by the instructions provided in the 4th edition of The Complete FreeBSD. There is not a step for: make installkernel I guess I'll start all over. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make installworld error
On 20 Aug, 2004, at 14:19, kstewart wrote: On Friday 20 August 2004 02:06 pm, Curtis Vaughan wrote: After going through a cvsup make buildworld make kernel reboot I am now on make installworld I had to do a mergemaster -p in order to get make installworld to run, but finally after seemingly corrected all the changes wtih mergemaster, make installworld ran. Well, it ran for a good while but then errored out with: install -o root -g wheel -m 444 test.1.gz /usr/share/man/man1 *** Signal 12 Stop in /usr/src/bin/test. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. And that's it. Any ideas as to what is going on? Wait a minute. I just noticed that, whereas I've made bash my default shell, I don't think it understands any commands now. And now I just rebooted and it can't find a shell to boot into. Now I'm really screwed. You are supposed to hit the spacebar at the twirling thing and do a boot -s It will ask you if sh is ok and you use that. Kent -- Kent Stewart Richland, WA No, it's asking: Enter full pathname of shell or RETURN for /bin/sh But when I hit RETURN, it says: pid 7 (ssh), uid -: exited on signal 12 Aug 20 08:41:58 init: single user shell terminated, restarting and then it asks again: Enter full path I have tried also manually entering in: /bin/sh /bin/csh /bin/chsh /usr/local/bin/bash etc. etc. but nothing works ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
make installworld error
After going through a cvsup make buildworld make kernel reboot I am now on make installworld I had to do a mergemaster -p in order to get make installworld to run, but finally after seemingly corrected all the changes wtih mergemaster, make installworld ran. Well, it ran for a good while but then errored out with: install -o root -g wheel -m 444 test.1.gz /usr/share/man/man1 *** Signal 12 Stop in /usr/src/bin/test. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. And that's it. Any ideas as to what is going on? Wait a minute. I just noticed that, whereas I've made bash my default shell, I don't think it understands any commands now. And now I just rebooted and it can't find a shell to boot into. Now I'm really screwed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup install
Made a big mistake today. I was reading in a book that I needed to install cvsup for doing updates. Good. So, I started installing it. Meanwhile I began perusing the FreeBSD website information about cvsup and there I read, if you not using a gui, then don't install cvsup, but cvsup-without-gui. So, is there a way to back out the cvsup which I did do as it apparently has installed a lot of stuff I don't need on this server. Or do I have to just uninstall all those packages individually? Is there a way then to identify which packages were installed by installing cvsup? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CVSup install
Made a big mistake today. I was reading in a book that I needed to install cvsup for doing updates. Good. So, I started installing it. Meanwhile I began perusing the FreeBSD website information about cvsup and there I read, if you not using a gui, then don't install cvsup, but cvsup-without-gui. So, is there a way to back out the cvsup which I did do as it apparently has installed a lot of stuff I don't need on this server. Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
using cvsup
I'm a little confused about using cvsup. I'm referring to 2 resources (The Complete FreeBSD - 4th edition, and www,freebsd.org manual for cvsup). BTW, I currently have FreeBSD 4.8 installed. Ok, so, I know I need to edit a supfile and I have found all the examples. But it seems to me that it is advisable to put my own edited supfile in a particular directory. What is the best or more common practice? Maybe in the base directory: i.e., /usr/local/etc/cvsup/ ? Note that I will not be using the gui. I have not installed X windows (XFree86) as this is to be a server and I no intention of using any gui interface. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup install
Made a big mistake today. I was reading in a book that I needed to install cvsup for doing updates. Good. So, I started installing it. Meanwhile I began perusing the FreeBSD website information about cvsup and there I read, if you not using a gui, then don't install cvsup, but cvsup-without-gui. So, is there a way to back out the cvsup which I did do as it apparently has installed a lot of stuff I don't need on this server. Or do I have to just uninstall all those packages individually? Is there a way then to identify which packages were installed by installing cvsup? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
