Re: Customized Remote Install
On Wed, Apr 22, 2009 at 07:47:43AM +0200, Polytropon wrote: > On Tue, 21 Apr 2009 18:47:11 -0400, Jerry McAllister wrote: > > On Tue, Apr 21, 2009 at 11:51:32PM +0200, Polytropon wrote: > > > > > On Tue, 21 Apr 2009 14:42:32 -0600, Scott Seekamp > > > wrote: > > > > My hope was that I could make an automated install CD/DVD that > > > > configured all the options I want AND change some base config files so > > > > I can actually get to the box (or install an SSH key). > > > > [...] > > > > I'm open to other options if someone has gone down this road before! > > > > > > I'd like to advertize a method that I think is very comfortable > > > in such a setting. It's worth mentioning that this method > > > usually requires (a) modern enough PCs or (b) you to know what > > > is the hardware profile of the PC. > > > > > > The method works as follows: > > > > > > First create a FreeBSD as you want it to be on the clients. > > > Install and configure everything as you intend. > > > > > > Then dump the created partitions onto a CD or DVD and create > > > a simple script that: > > > 1. initializes the client's hard disk > > > 2. slices the disk and newfses the partitions > > > 3. dumps the partition images onto the disks > > > 4. reboots the machine into operating state. > > > > > > After this, you should be able to SSH into the client and > > > change settings that need to be changed. > > > > This works very well. > > I just realize that I missed something: Better than dd, I think > dump & restore are the preferred tools to create the partition > images. When you're done on your "template system", umount its > partitions (in SUM) and use dump to dump them into files. These > files go to the installation DVD and are later on restored onto > the (empty) partitions using the restore command. This will > preserve any permissions and other file properties. > > > > > I have done essentially the same many times. > > The one thing missing is that you need to have something to set the > > network information -- hostname, IP address, gateway, netmask > > and name-server.These will be different for each machine. > > So, your script will have to accomodate this - read console > > input for these items and plug them in to the proper places > > before rebooting. > > That's correct. I always used a kind of "CHANGE THIS!" items > to do so, or, if none are given, they are automatically created > so the system boots up and runs, but then again, require service > afterwards. This can be made work this way: When the "incomplete" > system is up and running, it mails the distant administrator (or > contacts him in another way) requiring him to finish the settings. > But I think it's the best solution to propmt for these > specific settings at "installation time" (read, when the > restore job is done, the partitions can be mounted -o rw and > the files neccessary to be changed can be created or modified). > > The "installation" will then continue and finish. > > Of course, the dump & restore method lacks a lot of bling, > blitzen, eye candy, bells and whistles, but it honours the > abstinence to such stuff with speed and easyness of use. But > it's still neccessary to read (and understand) and press a > few keys on the keyboard. :-) the dump/restore method's best and biggest bling and bell and whistle is that it works correctly and is the most straight forward and easy. jerry > > > > -- > Polytropon > From Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Customized Remote Install
On Tue, Apr 21, 2009 at 11:42 PM, Scott Seekamp wrote: > I've done a lot of searching and maybe this capability doesn't exist, but I > am looking to do this: > > I am at my company's HQ, we have a new field office that I am setting up a > FreeBSD server. The technical knowledge at the site windows only, so I > basically have someone I can have put a CD in a drive and power a machine > on. > > My problem is that the default install of FreeBSD has password > authentication turned off, and root SSH disabled. Being a small office, they > don't have a IP KVM or some way for me to get to the box to configure it. > > My hope was that I could make an automated install CD/DVD that configured > all the options I want AND change some base config files so I can actually > get to the box (or install an SSH key). > > I know I can do the scripted sysinstall, but from what I could find I would > need a floppy or additional CD to put the answer file on. > > I'm open to other options if someone has gone down this road before! All you need is that the guy at the field office knows something about PC hardware and can type a few commands on any command line. Then there should be a phone. FreeBSD is not as silly as Linux when you move a disk from one box to another. If it is a "server" box (which requires no GUI) then the only changes you are likely to make are on the network configurations (ifconfig_* in rc.conf and resolv.conf) and the rest will remain pretty much the same. What I have done is that I have a prototype, which is a SATA disk. I am pretty much okay of the next machine I want to install has a SATA disk, but I am also not worried if it has PATA disk as I know I will only need a change in /etc/fstab. So what I normally do is this: Attach my prototype disk as master on the machine to install, while slaving the disk that the machine had. I enter sysinstall and disklable/newfs the slave disk. I make the disk bootable, enable softupdates on it and I normally create the root mount point (/). Once done, I change the mount point again to, say, /newdisk, so the slave disk is now mounted on /newdisk. After this: dump L0af - / | (cd /newdisk/; restore -rf -) # BTW, I have the habit of creating only / and swap! So now I have a duplicate system on the slave disk. cd /newdisk; ee etc/rc.conf ; ee etc/fstab; ee etc/resol.conf Here I change the ifconfig_ line for the network device (as seen from dmesg.boot), ensure that fstab refers to the correct device names and voila! I save, shutdown, remove my prototype disk, restore the slave disk to master position and reboot and I have a system identical to the proto. Once connected to a live network, I can ssh to it from anywhere I want using my own account and the su to root if needed, though I always prefer sudo. Now, if only you can follow my way, you only need to ship your prototype disk to the field office and get the windows lunnie to do the disk connections, type the commands, etc and you have a server running at the field office in no time! Of course tell him to pack your prototype disk safely and return it to you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "Clothes make the man. Naked people have little or no influence on society." -- Mark Twain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Customized Remote Install
Can you explain in more detail how to make a CD boot up FreeBSD and run a script? I haven't find any good resource on google. Alternatively, if you can provide a link. -- View this message in context: http://www.nabble.com/Customized-Remote-Install-tp23165397p23171529.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Customized Remote Install
On Tue, 21 Apr 2009 18:47:11 -0400, Jerry McAllister wrote: > On Tue, Apr 21, 2009 at 11:51:32PM +0200, Polytropon wrote: > > > On Tue, 21 Apr 2009 14:42:32 -0600, Scott Seekamp > > wrote: > > > My hope was that I could make an automated install CD/DVD that > > > configured all the options I want AND change some base config files so > > > I can actually get to the box (or install an SSH key). > > > [...] > > > I'm open to other options if someone has gone down this road before! > > > > I'd like to advertize a method that I think is very comfortable > > in such a setting. It's worth mentioning that this method > > usually requires (a) modern enough PCs or (b) you to know what > > is the hardware profile of the PC. > > > > The method works as follows: > > > > First create a FreeBSD as you want it to be on the clients. > > Install and configure everything as you intend. > > > > Then dump the created partitions onto a CD or DVD and create > > a simple script that: > > 1. initializes the client's hard disk > > 2. slices the disk and newfses the partitions > > 3. dumps the partition images onto the disks > > 4. reboots the machine into operating state. > > > > After this, you should be able to SSH into the client and > > change settings that need to be changed. > > This works very well. I just realize that I missed something: Better than dd, I think dump & restore are the preferred tools to create the partition images. When you're done on your "template system", umount its partitions (in SUM) and use dump to dump them into files. These files go to the installation DVD and are later on restored onto the (empty) partitions using the restore command. This will preserve any permissions and other file properties. > I have done essentially the same many times. > The one thing missing is that you need to have something to set the > network information -- hostname, IP address, gateway, netmask > and name-server.These will be different for each machine. > So, your script will have to accomodate this - read console > input for these items and plug them in to the proper places > before rebooting. That's correct. I always used a kind of "CHANGE THIS!" items to do so, or, if none are given, they are automatically created so the system boots up and runs, but then again, require service afterwards. This can be made work this way: When the "incomplete" system is up and running, it mails the distant administrator (or contacts him in another way) requiring him to finish the settings. But I think it's the best solution to propmt for these specific settings at "installation time" (read, when the restore job is done, the partitions can be mounted -o rw and the files neccessary to be changed can be created or modified). The "installation" will then continue and finish. Of course, the dump & restore method lacks a lot of bling, blitzen, eye candy, bells and whistles, but it honours the abstinence to such stuff with speed and easyness of use. But it's still neccessary to read (and understand) and press a few keys on the keyboard. :-) -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Customized Remote Install
On Tue, Apr 21, 2009 at 11:51:32PM +0200, Polytropon wrote: > On Tue, 21 Apr 2009 14:42:32 -0600, Scott Seekamp wrote: > > My hope was that I could make an automated install CD/DVD that > > configured all the options I want AND change some base config files so > > I can actually get to the box (or install an SSH key). > > [...] > > I'm open to other options if someone has gone down this road before! > > I'd like to advertize a method that I think is very comfortable > in such a setting. It's worth mentioning that this method > usually requires (a) modern enough PCs or (b) you to know what > is the hardware profile of the PC. > > The method works as follows: > > First create a FreeBSD as you want it to be on the clients. > Install and configure everything as you intend. > > Then dump the created partitions onto a CD or DVD and create > a simple script that: > 1. initializes the client's hard disk > 2. slices the disk and newfses the partitions > 3. dumps the partition images onto the disks > 4. reboots the machine into operating state. > > After this, you should be able to SSH into the client and > change settings that need to be changed. This works very well. I have done essentially the same many times. The one thing missing is that you need to have something to set the network information -- hostname, IP address, gateway, netmask and name-server.These will be different for each machine. So, your script will have to accomodate this - read console input for these items and plug them in to the proper places before rebooting. jerry > > You always have your "reference machine" at hand, because it's > exactly installed and configured as the clients. > > Under controlled conditions, it's even possible to build the > needed system in a virtualized environment. > > > > > -- > Polytropon > >From Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Customized Remote Install
On Tue, 21 Apr 2009 14:42:32 -0600, Scott Seekamp wrote: > My hope was that I could make an automated install CD/DVD that > configured all the options I want AND change some base config files so > I can actually get to the box (or install an SSH key). > [...] > I'm open to other options if someone has gone down this road before! I'd like to advertize a method that I think is very comfortable in such a setting. It's worth mentioning that this method usually requires (a) modern enough PCs or (b) you to know what is the hardware profile of the PC. The method works as follows: First create a FreeBSD as you want it to be on the clients. Install and configure everything as you intend. Then dump the created partitions onto a CD or DVD and create a simple script that: 1. initializes the client's hard disk 2. slices the disk and newfses the partitions 3. dumps the partition images onto the disks 4. reboots the machine into operating state. After this, you should be able to SSH into the client and change settings that need to be changed. You always have your "reference machine" at hand, because it's exactly installed and configured as the clients. Under controlled conditions, it's even possible to build the needed system in a virtualized environment. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Customized Remote Install
I've done a lot of searching and maybe this capability doesn't exist, but I am looking to do this: I am at my company's HQ, we have a new field office that I am setting up a FreeBSD server. The technical knowledge at the site windows only, so I basically have someone I can have put a CD in a drive and power a machine on. My problem is that the default install of FreeBSD has password authentication turned off, and root SSH disabled. Being a small office, they don't have a IP KVM or some way for me to get to the box to configure it. My hope was that I could make an automated install CD/DVD that configured all the options I want AND change some base config files so I can actually get to the box (or install an SSH key). I know I can do the scripted sysinstall, but from what I could find I would need a floppy or additional CD to put the answer file on. I'm open to other options if someone has gone down this road before! Thanks! Scott Seekamp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: pkg_add: remote install (-r) broken
Colin Brace wrote: Hi all, At some point after my original installation of v.7-BETA3 in late November and a subsquent upgrade to BETA4 with Colin Percival's freebsd-update, installing packages remotely with pkg_add on my system broke. For example: <<< 550 Cannot connect to 78.27.2.208:53572 - Unknown error: 0. I guess that is your IP. You have a firewall and are not using passive mode FTP? It should be the default unless you edited your login.conf. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pkg_add: remote install (-r) broken
Hi all, At some point after my original installation of v.7-BETA3 in late November and a subsquent upgrade to BETA4 with Colin Percival's freebsd-update, installing packages remotely with pkg_add on my system broke. For example: $ sudo pkg_add -vr rtorrent scheme: [ftp] user: [] password: [] host: [ftp.freebsd.org] port: [0] document: [/pub/FreeBSD/ports/i386/packages-7-current/Latest/rtorrent.tbz] ---> ftp.freebsd.org:21 looking up ftp.freebsd.org connecting to ftp.freebsd.org:21 <<< 220 ftp.FreeBSD.org NcFTPd Server (licensed copy) ready. >>> USER anonymous <<< 331 Guest login ok, send your complete e-mail address as password. >>> PASS [EMAIL PROTECTED] <<< 230-You are user #181 of 1000 simultaneous users allowed. <<< 230- <<< 230 Logged in anonymously. >>> PWD <<< 257 "/" is cwd. >>> CWD pub/FreeBSD/ports/i386/packages-7-current/Latest <<< 250 "/pub/FreeBSD/ports/i386/packages-7-current/Latest" is new cwd. >>> MODE S <<< 200 Mode okay. >>> TYPE I <<< 200 Type okay. binding data socket >>> PORT 172,19,3,3,209,68 <<< 200 PORT command successful. initiating transfer >>> RETR rtorrent.tbz <<< 550 Cannot connect to 78.27.2.208:53572 - Unknown error: 0. Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/Latest/rtorrent.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/Latest/rtorrent.tbz' by URL pkg_add: 1 package addition(s) failed Now, I *know* the package and host are online; I can copy and paste the URL from the screen to grab it with wget: wget ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/Latest/rtorrent.tbz This works. What could be going wrong with add_pkg here? As I indicate above, I am currently at 7.0-BETA4 Thanks. -- Colin Brace Amsterdam http://lim.nl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
Also see my post to doc about restoring dump files over an http connection, in case your existing systems' partitions don't have enough room to temporarily store them. http://lists.freebsd.org/pipermail/freebsd-doc/2007-February/012190.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
On Fri, Mar 09, 2007 at 11:39:31AM -0500, David Robillard wrote: > >OK. First, it was someone else who posted. I was one of the responders. > > My mistake! Sorry about this. > > > >That can be a good way of doing it. I have posted a list of steps > >for doing essentially that (slightly different circumstances) a > >couple of times in the past. > > > >But there is one disadvantage in this particular case. Since the OP > >is running 4.xx and wants to move to 6.xx, he would probably also want > >to take advantage of the new UFS2 filesystem improvements. But, if > >he builds the file system using the 4.xx fdisk and disklabel (before > >bsdlabel replaced it) then it will use the older file system missing > >some performance and feature improvements. So, he will want to find > >a way to fdisk and bsdlabel using a 6.xx system if at all possible. > > > >Of course, it is not the end of the world to be stuck with the older > >file system, but is less than optimal. > > > >It would be possible for the person to sort of double up on your > >suggestion and do a first build with the existing fdisk and bsdlabel > >and then restore 6.2 dumps. Then build a 6.2 system that can run from > >memory that includes the essentials such as fdisk, bsdlabel and newfs > >and tink with booting to boot to that memory system, which would > >then allow that second disk to remain unmounted or accessed anywhere > > -- essential for building the file systems. Then use that memory > >mounted system to build the file systems and finally do the restores > >from dumps. It should work, but will take some figuring out. > > > >The last time I built anything resembling that was back in > >about FreeBSD 4.9 and I made a file of it and burned it to CD and > >did the boots from CD. But it should be possible to get it to > >run from a memory file system. > > Indeed, you're absolutely right. > > An easy way to circumvent this filesystem issue would be to mount the > ISO image of a 6.2 install CD as a virtual filesystem and use the > binaries from there. This shows you how to proceed: > http://www.freebsddiary.org/iso-mount.php > > Of course, you'll need a fair bit of RAM to do this. That can work. Make sure you check the added comments as well, although those refer to FreeBSD 5.xxx and you are still on 4.xxx. You will want to know it will be different once you start running the new one. Make sure that the ISO image is not stored on the drive to be fdisk-ed, bsdlabel-ed and newfs-ed. In this person's case, the system is already running on another disk, and he wants to put the 6.xx system on a second disk, so he just has to make sure to write the ISO to that first disk somewhere there is room and unmount anything on that second disk. > > There's also this from Colin Percival that can be usefull: > http://www.daemonology.net/depenguinator/ This reference is really a different subject. jerry > > HTH, > > David > -- > David Robillard > UNIX systems administrator & Oracle DBA > CISSP, RHCE & Sun Certified Security Administrator > Montreal: +1 514 966 0122 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
OK. First, it was someone else who posted. I was one of the responders. My mistake! Sorry about this. That can be a good way of doing it. I have posted a list of steps for doing essentially that (slightly different circumstances) a couple of times in the past. But there is one disadvantage in this particular case. Since the OP is running 4.xx and wants to move to 6.xx, he would probably also want to take advantage of the new UFS2 filesystem improvements. But, if he builds the file system using the 4.xx fdisk and disklabel (before bsdlabel replaced it) then it will use the older file system missing some performance and feature improvements. So, he will want to find a way to fdisk and bsdlabel using a 6.xx system if at all possible. Of course, it is not the end of the world to be stuck with the older file system, but is less than optimal. It would be possible for the person to sort of double up on your suggestion and do a first build with the existing fdisk and bsdlabel and then restore 6.2 dumps. Then build a 6.2 system that can run from memory that includes the essentials such as fdisk, bsdlabel and newfs and tink with booting to boot to that memory system, which would then allow that second disk to remain unmounted or accessed anywhere -- essential for building the file systems. Then use that memory mounted system to build the file systems and finally do the restores from dumps. It should work, but will take some figuring out. The last time I built anything resembling that was back in about FreeBSD 4.9 and I made a file of it and burned it to CD and did the boots from CD. But it should be possible to get it to run from a memory file system. Indeed, you're absolutely right. An easy way to circumvent this filesystem issue would be to mount the ISO image of a 6.2 install CD as a virtual filesystem and use the binaries from there. This shows you how to proceed: http://www.freebsddiary.org/iso-mount.php Of course, you'll need a fair bit of RAM to do this. There's also this from Colin Percival that can be usefull: http://www.daemonology.net/depenguinator/ HTH, David -- David Robillard UNIX systems administrator & Oracle DBA CISSP, RHCE & Sun Certified Security Administrator Montreal: +1 514 966 0122 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
On Fri, Mar 09, 2007 at 10:30:44AM -0500, David Robillard wrote: > >I have a remote machine running 4.8-p21. The system has two disks in > >it, but only one is used on a daily basis (the other is filled via dd > >every now and then). > > > >I want to get this remote machine running 6.2, so I figured I'ld > >install the new OS on the second disk, then boot off the second disk, > >leaving the original first disk with all the user data on it (plus as > >a way to back out). > > > >When I try to use /stand/sysinstall for this it seg-faults > >early in the installation, but after the "Commit" step. > > Hi Jerry, > > If you have a 6.2 machine handy, you can create dump files of each > filesystem using dump(8), cpio(1) or pax(1) or whatever you're used > to. > > Ship those dump files to your 4.8 machine via scp(1). Then use > bsdlabel(8) to partition your second hard disk (the one you whish to > install 6.2 on). Create filesystems on those new partitions. Mount > those new filesystems into a chroot, for example /mnt/root, /mnt/usr, > /mnt/var, etc. Then extract your dump files onto those new partitions. > Don't forget to install a boot block on your disk with `bsdlabel -B` > or with boot0cfg(8). That should do it. > > If you need more detailed step-by-step instructions, just say so, I'll > send something on the list. OK. First, it was someone else who posted. I was one of the responders. That can be a good way of doing it. I have posted a list of steps for doing essentially that (slightly different circumstances) a couple of times in the past. But there is one disadvantage in this particular case. Since the OP is running 4.xx and wants to move to 6.xx, he would probably also want to take advantage of the new UFS2 filesystem improvements. But, if he builds the file system using the 4.xx fdisk and disklabel (before bsdlabel replaced it) then it will use the older file system missing some performance and feature improvements. So, he will want to find a way to fdisk and bsdlabel using a 6.xx system if at all possible. Of course, it is not the end of the world to be stuck with the older file system, but is less than optimal. It would be possible for the person to sort of double up on your suggestion and do a first build with the existing fdisk and bsdlabel and then restore 6.2 dumps. Then build a 6.2 system that can run from memory that includes the essentials such as fdisk, bsdlabel and newfs and tink with booting to boot to that memory system, which would then allow that second disk to remain unmounted or accessed anywhere -- essential for building the file systems. Then use that memory mounted system to build the file systems and finally do the restores from dumps. It should work, but will take some figuring out. The last time I built anything resembling that was back in about FreeBSD 4.9 and I made a file of it and burned it to CD and did the boots from CD. But it should be possible to get it to run from a memory file system. jerry > > Have fun, > > David > -- > David Robillard > UNIX systems administrator & Oracle DBA > CISSP, RHCE & Sun Certified Security Administrator > Montreal: +1 514 966 0122 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
I have a remote machine running 4.8-p21. The system has two disks in it, but only one is used on a daily basis (the other is filled via dd every now and then). I want to get this remote machine running 6.2, so I figured I'ld install the new OS on the second disk, then boot off the second disk, leaving the original first disk with all the user data on it (plus as a way to back out). When I try to use /stand/sysinstall for this it seg-faults early in the installation, but after the "Commit" step. Hi Jerry, If you have a 6.2 machine handy, you can create dump files of each filesystem using dump(8), cpio(1) or pax(1) or whatever you're used to. Ship those dump files to your 4.8 machine via scp(1). Then use bsdlabel(8) to partition your second hard disk (the one you whish to install 6.2 on). Create filesystems on those new partitions. Mount those new filesystems into a chroot, for example /mnt/root, /mnt/usr, /mnt/var, etc. Then extract your dump files onto those new partitions. Don't forget to install a boot block on your disk with `bsdlabel -B` or with boot0cfg(8). That should do it. If you need more detailed step-by-step instructions, just say so, I'll send something on the list. Have fun, David -- David Robillard UNIX systems administrator & Oracle DBA CISSP, RHCE & Sun Certified Security Administrator Montreal: +1 514 966 0122 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
Mark Messier wrote: > I have a remote machine running 4.8-p21. The system has two disks in > it, but only one is used on a daily basis (the other is filled via dd > every now and then). > > I want to get this remote machine running 6.2, so I figured I'ld > install the new OS on the second disk, then boot off the second disk, > leaving the original first disk with all the user data on it (plus as > a way to back out). > > When I try to use /stand/sysinstall for this it seg-faults > early in the installation, but after the "Commit" step. You could try to mount a 6.2 iso-file and use the sysinstall from there, if that does not work due to library dependencies you could partition the disk by hand using fdisk and disklabel (or do that with the 4.8 sysinstall). After mounting the new disk to /mnt etc. you can extract the kernel and userland using the install.sh script you will find at the set directories in ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/. I think you only need base and a kernel. Only drawback is you will not be able to use UFS2 I guess, because the 4.8 newfs doesn't know about that. But maybe someone has a solution to that. You could also use qemu to prepare a freebsd6 system and use dd to write it onto the second disk. greetings, philipp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
On Thu, Mar 08, 2007 at 05:19:57PM -0500, Jerry McAllister wrote: > On Thu, Mar 08, 2007 at 01:50:27PM -0800, Mark Messier wrote: > > > I have a remote machine running 4.8-p21. The system has two disks in > > it, but only one is used on a daily basis (the other is filled via dd > > every now and then). > > > > I want to get this remote machine running 6.2, so I figured I'ld > > install the new OS on the second disk, then boot off the second disk, > > leaving the original first disk with all the user data on it (plus as > > a way to back out). > > > > When I try to use /stand/sysinstall for this it seg-faults > > early in the installation, but after the "Commit" step. > > > > I figure this is because the install process has changed a bit > > since 4.8. > > > > Is there a way to fix this and/or what is the best way to achieve > > my goal... which is: install 6.2 on a remote system without hammering > > the current system disk? > > Are you using an install CD? > Use that to boot the machine - download the ISO and burn it if needed > or buy one. > > Boot it up and do the install to the second disk. > I know you can make it work from another disk if you unmount > the second one and do things just right. But, it is easier > to just make the CD and do the install on the second disk. Ahhh, I overlooked the part about being a remote install. Well, if you can get someone to stick in a CD and then take it out when it comes time for reboot, that would still be the easier way. Otherwise someone is going to have to take some time and think about what the problem is. It is true that /stand/sysinstall has changed since 4.x. I am not sure just how much it would mangle things to use the old one. jerry > > jerry > > > > > Thanks, > > -mark > > > > ___ > > 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]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of 6.2
On Thu, Mar 08, 2007 at 01:50:27PM -0800, Mark Messier wrote: > I have a remote machine running 4.8-p21. The system has two disks in > it, but only one is used on a daily basis (the other is filled via dd > every now and then). > > I want to get this remote machine running 6.2, so I figured I'ld > install the new OS on the second disk, then boot off the second disk, > leaving the original first disk with all the user data on it (plus as > a way to back out). > > When I try to use /stand/sysinstall for this it seg-faults > early in the installation, but after the "Commit" step. > > I figure this is because the install process has changed a bit > since 4.8. > > Is there a way to fix this and/or what is the best way to achieve > my goal... which is: install 6.2 on a remote system without hammering > the current system disk? Are you using an install CD? Use that to boot the machine - download the ISO and burn it if needed or buy one. Boot it up and do the install to the second disk. I know you can make it work from another disk if you unmount the second one and do things just right. But, it is easier to just make the CD and do the install on the second disk. jerry > > Thanks, > -mark > > ___ > 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]"
remote install of 6.2
I have a remote machine running 4.8-p21. The system has two disks in it, but only one is used on a daily basis (the other is filled via dd every now and then). I want to get this remote machine running 6.2, so I figured I'ld install the new OS on the second disk, then boot off the second disk, leaving the original first disk with all the user data on it (plus as a way to back out). When I try to use /stand/sysinstall for this it seg-faults early in the installation, but after the "Commit" step. I figure this is because the install process has changed a bit since 4.8. Is there a way to fix this and/or what is the best way to achieve my goal... which is: install 6.2 on a remote system without hammering the current system disk? Thanks, -mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install
Arden <[EMAIL PROTECTED]> writes: > I have some old machines (amd400s) which I'm using for education > > I only have the one spare monitor and I don't have a KVM switch at the > mo and I'm sick of moving the connectors > > they are all on the same network as my BSD and Linux box is it > possible to reload the os using remote log-in ssh or the like ? Sure, especially if you're not making to big a version jump . After all, you *can* plug in a monitor if something goes wrong, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
remote install
hi folks I have some old machines (amd400s) which I'm using for education I only have the one spare monitor and I don't have a KVM switch at the mo and I'm sick of moving the connectors they are all on the same network as my BSD and Linux box is it possible to reload the os using remote log-in ssh or the like ? thanks in advance Arden ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd remote install howto
On Mon, Jan 03, 2005 at 01:05:26AM +0530, Sunil Sunder Raj wrote: > Hi, > Had to install freebsd on a machine without a floppy disk nor a cd drive. > This machine is on the lan. Is there any way I can install freebsd from > another freebsd machine in the lan. You could try a pxeboot(8)-based method, if your machine supports PXE: http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html I've done something similar to install FreeBSD 5.2.1 on a Soekris net4801 board that comes without keyboard, floppy drives, CD drives, nor VGA; just a serial console and ethernet ports. It was amazingly simple and effective. Good luck! > Regards > SSR Cheers, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Freebsd remote install howto
Hi, Had to install freebsd on a machine without a floppy disk nor a cd drive. This machine is on the lan. Is there any way I can install freebsd from another freebsd machine in the lan. Regards SSR _ Redefine team work. Discover your true potential. http://www.microsoft.com/india/office/experience/ With the MS product suite. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: remote install of freebsd via ssh
hi, I agree, best way would be to do as suggested. then ssh that way, the only thing you may have to do is walk the user on entering single user mode to do a make installworld if you're updating your system. -Jose lima --- JJB <[EMAIL PROTECTED]> wrote: > Install FBSD on local pc and when completed, remove > HD and send to > remote site to be swapped with HD there. Then you > can ssh into box > and do what ever you want to fine tune install. > Anything else is > just asking for problems and down time. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Behalf Of Brian > Sent: Thursday, April 08, 2004 7:21 AM > To: [EMAIL PROTECTED] > Subject: remote install of freebsd via ssh > > Hello, > Is there a way (or what is the best way) for > installing freebsd > remotely? I > have a nontechnical person at the site that can put > in a cd or enter > a few > commands, but the thought of walking through a full > install via the > phone is > not fun. I would prefer to be able to use ssh for > configuring. Any > suggestions would be a great help. > > Thanks, > Brian D. > > ___ > [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]" __ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of freebsd via ssh
> From: Brian > Sent: April 8, 2004 05:21 > > Hello, > Is there a way (or what is the best way) for installing freebsd > remotely? I have a nontechnical person at the site that can put > in a cd or enter a few commands, but the thought of walking > through a full install via the phone is not fun. I would prefer > to be able to use ssh for configuring. Any suggestions would be > a great help. Burn a freesbie[1] and mail it to them. Have them boot up in it. Have them start sshd if it isn't. You can log in and take over. [1] http://www.freesbie.org/ Cory -- Cory Petkovsek Adapting Information Adaptable IT ConsultingTechnology to Your (858) 705-1655 Business [EMAIL PROTECTED] www.AdaptableIT.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: remote install of freebsd via ssh
> From: Brian > Sent: April 8, 2004 05:21 > > Hello, > Is there a way (or what is the best way) for installing freebsd > remotely? I have a nontechnical person at the site that can put > in a cd or enter a few commands, but the thought of walking > through a full install via the phone is not fun. I would prefer > to be able to use ssh for configuring. Any suggestions would be > a great help. If the system is already running Linux, you can try the depenguinator. http://www.daemonology.net/depenguinator/ I haven't used this and make no warranty or claim yadda yadda. However, anything you're going to be able to do remotely is likely going to be more difficult than guiding your Johnny on the spot through the install. The core install is pretty simple. -Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of freebsd via ssh
Marc G. Fournier wrote: On Thu, 8 Apr 2004, Brian wrote: Hello, Is there a way (or what is the best way) for installing freebsd remotely? I have a nontechnical person at the site that can put in a cd or enter a few commands, but the thought of walking through a full install via the phone is not fun. I would prefer to be able to use ssh for configuring. Any suggestions would be a great help. Pick up a webcam and aim it at the screen? :) :-) that might be an option, Some people prefer Terminals, if your system support a terminal (serial connection) perhaps you can use a terminal server. You can connect to it through tcp/ip use the appropiate port and end up at the sytems console. We use it at some of our Sun machines to get remote access to it when something goes terribly wrong. Note that that aint secure if not firewalled etc. Also it might happen that you don't have these options, then the advice about the HardDisk is also a good one (never thought of that yet :-)) Cheers -- Kind regards, Remko Lodder Elvandar.org/DSINet.org www.mostly-harmless.nl A Dutch community for helping newcomers on the hackerscene ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: remote install of freebsd via ssh
On Thu, 8 Apr 2004, Brian wrote: > Hello, > Is there a way (or what is the best way) for installing freebsd remotely? I > have a nontechnical person at the site that can put in a cd or enter a few > commands, but the thought of walking through a full install via the phone is > not fun. I would prefer to be able to use ssh for configuring. Any > suggestions would be a great help. Pick up a webcam and aim it at the screen? :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: remote install of freebsd via ssh
Install FBSD on local pc and when completed, remove HD and send to remote site to be swapped with HD there. Then you can ssh into box and do what ever you want to fine tune install. Anything else is just asking for problems and down time. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brian Sent: Thursday, April 08, 2004 7:21 AM To: [EMAIL PROTECTED] Subject: remote install of freebsd via ssh Hello, Is there a way (or what is the best way) for installing freebsd remotely? I have a nontechnical person at the site that can put in a cd or enter a few commands, but the thought of walking through a full install via the phone is not fun. I would prefer to be able to use ssh for configuring. Any suggestions would be a great help. Thanks, Brian D. ___ [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]"
remote install of freebsd via ssh
Hello, Is there a way (or what is the best way) for installing freebsd remotely? I have a nontechnical person at the site that can put in a cd or enter a few commands, but the thought of walking through a full install via the phone is not fun. I would prefer to be able to use ssh for configuring. Any suggestions would be a great help. Thanks, Brian D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
