Re: Next steps
Darryl Hoar wrote:
Greetings,
I have just installed 6.3-Release on brand new hardware.
In the past, I have not done much to a machine after
initial installation. What should be done to a machine
after successful installation of 6.3-release ? Do I need
to compile a custom kernel ? Do I need to apply any
patches ?
What I do is lay down an /etc/supfile[1] containing what's needed to
bring the system fully up-to-date regarding base and ports. I like to
track the -security branch (RELENG_6_3) but many just track stable
(RELENG_6).
Run csup -g -L2 /etc/supfile
Thereafter {build|install} {kernel|world} and follow with pkg_add -r
portaudit, portmaster and any other ports I find useful[2].
[1]
*default host=cvsup7.FreeBSD.org
# YMMV, try fastest_cvsup port to get a better idea
*default base=/usr
*default prefix=/usr
*default release=cvs delete use-rel-suffix compress
src-all tag=RELENG_6_3
# or RELENG_6 to track 6-STABLE
ports-all tag=.
[2]
http://conshell.net/wiki/index.php/User:Fostermarkd/Applications#FreeBSD-specific_Applications
--
Some days it's just not worth chewing through the restraints...
Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? Do I need to apply any patches ? no patches for now, but compiling custom kernel tailored to the machine is always a good practice ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Next steps
Greetings, I have just installed 6.3-Release on brand new hardware. In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? Do I need to apply any patches ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
In response to Darryl Hoar [EMAIL PROTECTED]: Greetings, I have just installed 6.3-Release on brand new hardware. In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? You don't _need_ to unless your hardware requires it (which happens occasionally) Do I need to apply any patches ? Normally, that would be the next step. There are no patches for 6.3 yet, so you don't have to in this case. Next logical step would be hardening the machine, which is a topic too large for an email. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
for me, it's compiling a custom kernel and installing apps. TFC On Jan 29, 2008 9:41 AM, Darryl Hoar [EMAIL PROTECTED] wrote: Greetings, I have just installed 6.3-Release on brand new hardware. In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? Do I need to apply any patches ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
On Tuesday 29 January 2008 18:23:17 Mark D. Foster wrote: Run csup -g -L2 /etc/supfile Hehe, -g is a no op for cvsup compat (with cvsup it disabled the GUI). Took me some months to quit typing that too :P -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
On Tuesday 29 January 2008 15:41:35 Darryl Hoar wrote: I have just installed 6.3-Release on brand new hardware. In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? Do I need to apply any patches ? The next thing would be to decide what ya gonna do with it. Then all of the above may or may not be necessary. Example: - Traffic shaping with pf/altq needs custom kernel - altq(4) If you play games or use other apps that make processes grow beyond 512MB, you also need to set kern.defdsiz and kern.maxdsiz in /boot/loader.conf to a more desirable value (if you can spare the physical ram). There's also freebsd-update, which will apply binary patches, following the security advisories. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Next steps
On Tuesday 29 January 2008 15:41:35 Darryl Hoar wrote: I have just installed 6.3-Release on brand new hardware. In the past, I have not done much to a machine after initial installation. What should be done to a machine after successful installation of 6.3-release ? Do I need to compile a custom kernel ? Do I need to apply any patches ? The next thing would be to decide what ya gonna do with it. Then all of the above may or may not be necessary. Example: - Traffic shaping with pf/altq needs custom kernel - altq(4) Its going to be an internal webserver running apache, mysql,php, and knowledgebase software. If you play games or use other apps that make processes grow beyond 512MB, you also need to set kern.defdsiz and kern.maxdsiz in /boot/loader.conf to a more desirable value (if you can spare the physical ram). I have 2GB RAM in this box, so I'm OK on physical ram. But there will be no game playing on this server. There's also freebsd-update, which will apply binary patches, following the security advisories. -- Mel -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.15/1249 - Release Date: 1/29/2008 9:51 AM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Next steps
On Tuesday 29 January 2008 23:11:35 Darryl Hoar wrote: If you play games or use other apps that make processes grow beyond 512MB, you also need to set kern.defdsiz and kern.maxdsiz in /boot/loader.conf to a more desirable value (if you can spare the physical ram). I have 2GB RAM in this box, so I'm OK on physical ram. But there will be no game playing on this server. Pending what's more important: - could set process size to 768M or 1G and let mysql eat it (faster cached queries, can handle sorting better without using tmp files). - don't increase it, instead use more forks on the webserver But this is tuning for high loads, really. Outof the box for small office internal usage, it shouldn't need tuning. The max data size for a process is just something you run into sooner rather then later. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Next steps... (long)
Hello all, I've recently retired my home Linux boxes in favor of some new challenges... one of which is building a small home LAN server on an older Panasonic CF-71 P2-300 laptop w/ 128MB RAM and a 6GB HD. Installation went pretty smoothly, w/ some minor recalibration needed to overcome several years of tinkering w/ Linux. I installed using the 4.7 mini-iso, doing a plain 'User' install. Then, since I have a slow 56k dialup line at home, I managed to arrange to use a broadband connection long enough to cvsup to RELENG_4_7, and the ports and docs as well. Downloaded a few niceties like a couple different shells, vim-lite, screen, sudo ,etc. at the same time and installed them using ports. I've built custom kernels in Linux, but it's been a while. And it appears the system upgrade process in FreeBSD is completely unlike what I'm used to. The laptop in question has a busted screen, which is why it's being relegated to headless server duty. For various reasons, it's *not* situated physically close to another computer w/ a monitor that I could hi-jack the cable from temporarily to do some of the single-user mode stuff. I *think* I understand enough about what I need to do next from looking at the Handbook and other on-line documents, but I would like some confirmation from a more knowledgeable user before I commit any further. What I believe I need to do next is: 1. Update sources via CVS **I've got separate supfiles set up to do src independent of ports independent of docs. Since this is going to be a 'production' system, using the CVS tag RELENG_4_7, it shouldn't change very often, correct? What is a good recommended interval for updating the sources via cvs in this case? Weekly, monthly, semi-annually, not until next release/upgrade? What about the ports and docs? This system isn't going to see a lot of 'interactive' user activity. Mainly a server for stuff like dns, dhcp, ntp, email, news, maybe a little bit of http/mysql stuff and bit of light programming via the shell, but that's it. Once I get the programs/services installed and setup the way I want, it's unlikely I'll be changing them very much. Do I need to bother updating the ports more than maybe once a week, or more likely, once a month? 2. Rebuild the system. I've been reviewing the material in the Handbook and at http://www.mostgraveconcern.com/freebsd/ on make world. When I get the laptop set back up, I will be digging thru /usr/src/UPDATING as recommended. I'm pretty sure I can work my way thru that part. I guess the only points needing clarification are: I assume its probably a good idea (at least for now) to do the make world step independently of futzing w/ the kernel config, correct? And as far as doing the system upgrade w/o physically hooking the laptop up to a separate monitor, etc. I need to shut down as many services/processes as is feasible, just prior to doing the make installworld step, right? Kind of related to the above question about how often to cvsup sources, but I assume that when ever I do that, I need to jump thru the same hoops here, as far as shutting everything down, and rebooting? Since my 'normal' access to this box is via network/ssh, how do I make *sure* that I will be able to get back into the machine remotely when it comes back up? 3. Configure and rebuild a custom kernel for the local machine. It runs fine w/ the GENERIC kernel for now, but it might be nice to trim things down a bit (and just mainly for the experience). 4. Again, going back to the first part: After I get to this point, I should have a freshly built system that is more or less optimized for the hardware it's running on, and the only thing I really need to update periodically is the ports tree, and watch for security updates. Speaking of which, does a make world rebuild the stuff built from ports as well, or do they each have to be done separately. Similarly, if there are security updates, do I have to cvsup the whole thing, source and ports again, and redo the whole make world/reboot dog-n-pony show, or is there a way of just updating the afflicted portion (I would assume so, but I figure it's better to find out early on) Well, that's about it for this round. Like I said, I've been looking thru a fair bit of online material, but some of it doesn't quite click as I don't have a baseline reference to relate it to, since I mainly stuck w/ binary packages in Linux, and only infrequently rebuilt the kernel. Any help, comments, or suggestions are gratefully appreciated. Thanks, nuk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Next steps... (long)
On Sat, Nov 23, 2002 at 10:25:29PM -0800, nuk wrote: Hello all, I've recently retired my home Linux boxes in favor of some new challenges... one of which is building a small home LAN server on an older Panasonic CF-71 P2-300 laptop w/ 128MB RAM and a 6GB HD. Installation went pretty smoothly, w/ some minor recalibration needed to overcome several years of tinkering w/ Linux. I installed using the 4.7 mini-iso, doing a plain 'User' install. Then, since I have a slow 56k dialup line at home, I managed to arrange to use a broadband connection long enough to cvsup to RELENG_4_7, and the ports and docs as well. Downloaded a few niceties like a couple different shells, vim-lite, screen, sudo ,etc. at the same time and installed them using ports. I've built custom kernels in Linux, but it's been a while. And it appears the system upgrade process in FreeBSD is completely unlike what I'm used to. The laptop in question has a busted screen, which is why it's being relegated to headless server duty. For various reasons, it's *not* situated physically close to another computer w/ a monitor that I could hi-jack the cable from temporarily to do some of the single-user mode stuff. I *think* I understand enough about what I need to do next from looking at the Handbook and other on-line documents, but I would like some confirmation from a more knowledgeable user before I commit any further. What I believe I need to do next is: 1. Update sources via CVS **I've got separate supfiles set up to do src independent of ports independent of docs. Since this is going to be a 'production' system, using the CVS tag RELENG_4_7, it shouldn't change very often, correct? What is a good recommended interval for updating the sources via cvs in this case? Weekly, monthly, semi-annually, not until next release/upgrade? What about the ports and docs? This system isn't going to see a lot of 'interactive' user activity. Mainly a server for stuff like dns, dhcp, ntp, email, news, maybe a little bit of http/mysql stuff and bit of light programming via the shell, but that's it. Once I get the programs/services installed and setup the way I want, it's unlikely I'll be changing them very much. Do I need to bother updating the ports more than maybe once a week, or more likely, once a month? 2. Rebuild the system. I've been reviewing the material in the Handbook and at http://www.mostgraveconcern.com/freebsd/ on make world. When I get the laptop set back up, I will be digging thru /usr/src/UPDATING as recommended. I'm pretty sure I can work my way thru that part. I guess the only points needing clarification are: I assume its probably a good idea (at least for now) to do the make world step independently of futzing w/ the kernel config, correct? And as far as doing the system upgrade w/o physically hooking the laptop up to a separate monitor, etc. I need to shut down as many services/processes as is feasible, just prior to doing the make installworld step, right? Kind of related to the above question about how often to cvsup sources, but I assume that when ever I do that, I need to jump thru the same hoops here, as far as shutting everything down, and rebooting? Since my 'normal' access to this box is via network/ssh, how do I make *sure* that I will be able to get back into the machine remotely when it comes back up? 3. Configure and rebuild a custom kernel for the local machine. It runs fine w/ the GENERIC kernel for now, but it might be nice to trim things down a bit (and just mainly for the experience). 4. Again, going back to the first part: After I get to this point, I should have a freshly built system that is more or less optimized for the hardware it's running on, and the only thing I really need to update periodically is the ports tree, and watch for security updates. Speaking of which, does a make world rebuild the stuff built from ports as well, or do they each have to be done separately. Similarly, if there are security updates, do I have to cvsup the whole thing, source and ports again, and redo the whole make world/reboot dog-n-pony show, or is there a way of just updating the afflicted portion (I would assume so, but I figure it's better to find out early on) Well, that's about it for this round. Like I said, I've been looking thru a fair bit of online material, but some of it doesn't quite click as I don't have a baseline reference to relate it to, since I mainly stuck w/ binary packages in Linux, and only infrequently rebuilt the kernel. Any help, comments, or suggestions are gratefully appreciated. Thanks, nuk 1) You somewhat answered your own question on this one. If it's just going to be a box with 4.7-RELEASE that will almost never undergo changes, then I see little reason to update your sources very frequently. In this case, you could just as
