Re: about unatteneded installation
Hi Devin, On 12/20/12 1:10 PM, Devin Teske devin.te...@fisglobal.com wrote: For now, people that prefer sysinstall can use my FreeBSD Druid pre-built install media: For 9.0: http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b60.iso/download For 8.3: http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download As for 10.0 (when it comes out), expect bsdinstall to surpass sysinstall (in many many great ways) in every way (unlike the current status in 9.x). I had begun evaluating FreeBSD Druid and DruidBSD, but was sidetracked with a different project. I'm hoping to return to this in the coming weeks. Having said that, I am wondering what disk partition utilities FreeBSD Druid/DruidBSD use when installing 9.x. Is it using fdisk/bsdlabel or gpart? -- Take care Rick Miller ___ 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: about unatteneded installation
On Thu, 14 Feb 2013, Rick Miller wrote: Hi Devin, On 12/20/12 1:10 PM, Devin Teske devin.te...@fisglobal.com wrote: For now, people that prefer sysinstall can use my FreeBSD Druid pre-built install media: For 9.0: http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b60.iso/download For 8.3: http://sourceforge.net/projects/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download As for 10.0 (when it comes out), expect bsdinstall to surpass sysinstall (in many many great ways) in every way (unlike the current status in 9.x). I had begun evaluating FreeBSD Druid and DruidBSD, but was sidetracked with a different project. I'm hoping to return to this in the coming weeks. Having said that, I am wondering what disk partition utilities FreeBSD Druid/DruidBSD use when installing 9.x. Is it using fdisk/bsdlabel or gpart? Hi Rick, No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: + libdisk ( see, for example, Set_Boot_Mgr(3) within case 'W' of switch (toupper(key)) in function diskPartition() of file stable/9/usr.sbin/sysinstall/disks.c lines 630-693) http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/disks.c?revision=225736view=markup and ... + phk code (see, for example, slice_wizard() function in file stable/9/usr.sbin/sysinstall/wizard.c lines 65-201, in-use for case '|' of the same switch above, same function, lines 695-707 of stable/9/usr.sbin/sysinstall/disks.c) http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/disks.c?revision=225736view=markup http://svnweb.freebsd.org/base/stable/9/usr.sbin/sysinstall/wizard.c?revision=225736view=markup But wait, there's more... The FreeBSD 9 version of my FreeBSD Druid has a patch to perform (only when doing automated/scripted installs): gpart -F destroy ${dest_disk} The reason for this is that if you, say for example, were to try the bsdinstall based media and then want to try sysinstall based media, you're actually prevented from re-formatting that disk into a usable MBR layout until you destroy the GPT backup label stored at the end of the disk. So the FreeBSD Druid for 9.x is basically the same as for 8.x with an additional twist, it has gpart in the mfsroot so that it can do a destroy on the GPT backup data before formatting the disk in automated installations (this destroy command is not done for non-scripted installs). You can see the code here: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/freebsd/menu/etc/all_install?r1=1.2r2=1.3 http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/freebsd/menu/etc/all_install?revision=1.3view=markup -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: about unatteneded installation
On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? -- Take care Rick Miller ___ 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: about unatteneded installation
-Original Message- From: vrwmil...@gmail.com [mailto:vrwmil...@gmail.com] On Behalf Of Rick Miller Sent: Thursday, February 14, 2013 10:39 AM To: Teske, Devin Cc: FreeBSD Questions Subject: Re: about unatteneded installation On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? As previously mentioned, the FreeBSD Druid for FreeBSD 9.x contains gpart in the mfsroot. To make this work under sysinstall, you'd essentially tell sysinstall to use what's already there (and by already there, I mean have a script pre-create the partition layout with gpart prior to installation). There are places (like the all_install script) in the FreeBSD Druid that would make this a simple proposition, but I'm afraid that the better solution (according to the article) is to use a true 4K-only drive (the article mentions that the problem only comes into play with drives that advertise both 512 and 4K sector sizes). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: about unatteneded installation
On Thu, 14 Feb 2013, dte...@freebsd.org wrote: -Original Message- From: vrwmil...@gmail.com [mailto:vrwmil...@gmail.com] On Behalf Of Rick Miller Sent: Thursday, February 14, 2013 10:39 AM To: Teske, Devin Cc: FreeBSD Questions Subject: Re: about unatteneded installation On Thu, Feb 14, 2013 at 12:34 PM, Teske, Devin devin.te...@fisglobal.com wrote: On Thu, 14 Feb 2013, Rick Miller wrote: No worries on time lapse. In fact, I had been needing to get back to you on assuaging those 4 failed patch hunks on your sysinstall work. FreeBSD Druid (both 8.x and 9.x) use sysinstall for disk partitioning. What does sysinstall use, you say? Glad you asked. sysinstall(8) uses a combination of: I anticipated this. I am under the impression one cannot force proper slice alignment on 4K sector drives with sysinstall (see http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector-drives.html). Is it safe to assume that this also applies to 9.x when utilizing sysinstall based installer? As previously mentioned, the FreeBSD Druid for FreeBSD 9.x contains gpart in the mfsroot. To make this work under sysinstall, you'd essentially tell sysinstall to use what's already there (and by already there, I mean have a script pre-create the partition layout with gpart prior to installation). Yes, but neither fdisk(8) nor gpart(8) can align slices to arbitrary (aligned) locations. They will always be aligned to CHS values, equivalent to using -a63 in gpart. gpart(8) can align FreeBSD partitions inside a slice, though. ___ 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: about unattended installation
Good morning, El 19/12/2012, a las 19:59, Devin Teske devin.te...@fisglobal.com escribió: On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. Hold on a moment. You might want to wait until 9.2. (read more below) Well in the ftp can be seen : FreeBSD-9.1-RELEASE-amd64-disc1.iso downloadable file…. so I assume it's a release??? I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the user interface (partedit) as one could sysinstall. (read below about 9.2) So I suppose that till the new installer is able to handle this in a similar way to sysinstall (although the syntax to be different or whatever)…. or partitioning can be achieved in some non interactive way, to maintain the possibility of rebuilding one's own release in order to be able to use sysinstall and to be able to maintain working unattended installation systems…. because this is essential for some of us….. and of course sysinstall to still continue working :)... So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. The answer is (unfortunately) yes… that is until (hopefully) 9.2. It's an on-going significant amount of work to make add backward compatibility (so bsdinstall can load sysinstall install.cfg files). I'm not going to discuss the specifics here or yet, but I'm actively working on it. No docs on how to mangle the auto script to do what you want (that I know of). Ok then :) Apart from all this… is Sysinstall going to be maintained in parallel?. Sysinstall is dead. Devin, sysinstall should not be died till the new installer allows or exists a way of doing same thing than before we did in some manner or other one….. because else… don't know... can this commands be translated to gpart for example??… and to act in a non interactive way??. But apart from the own gpart the are later other parts of the installation which should be done too… like selecting which distributions to install in a non interactive way for example….. if that is not possible to be done… in a non interactive way…. sysinstall should not disappear…. The bsdinstall you know can be considered the first generation and accordingly is a bit spartan. I'm working hard on the next generation. My plan is to have 10.0 with bsdinstall able to run sysinstall scripts (for backward compatibility; can't yet say what 9.x release will be MFC'd to, but that could be 9.2). I'm planning one helluva BSDCan-2013 presentation. -- Devin Thanks a lot for all !! Best regards, ___ 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: about unattended installation
On Dec 20, 2012, at 3:34 AM, Egoitz Aurrekoetxea Aurre wrote: Good morning, El 19/12/2012, a las 19:59, Devin Teske devin.te...@fisglobal.com escribió: On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. Hold on a moment. You might want to wait until 9.2. (read more below) Well in the ftp can be seen : FreeBSD-9.1-RELEASE-amd64-disc1.iso downloadable file…. so I assume it's a release??? Of course it's a release… it just may not be the release that solves your problem w/respect to scripting bsdinstall like sysinstall. That will come in a future release (like 9.2). I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the user interface (partedit) as one could sysinstall. (read below about 9.2) So I suppose that till the new installer is able to handle this in a similar way to sysinstall (although the syntax to be different or whatever)…. or partitioning can be achieved in some non interactive way, to maintain the possibility of rebuilding one's own release in order to be able to use sysinstall and to be able to maintain working unattended installation systems…. because this is essential for some of us….. and of course sysinstall to still continue working :)… You got it. This is a sign to the releng team and everybody else that 10.0 should most-likely not see the light of day until bsdinstall can pass the sniff-test for those of us (like you and I) which rely on the ability to script the installation process fully. So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. The answer is (unfortunately) yes… that is until (hopefully) 9.2. It's an on-going significant amount of work to make add backward compatibility (so bsdinstall can load sysinstall install.cfg files). I'm not going to discuss the specifics here or yet, but I'm actively working on it. No docs on how to mangle the auto script to do what you want (that I know of). Ok then :) Apart from all this… is Sysinstall going to be maintained in parallel?. Sysinstall is dead. Devin, sysinstall should not be died till the new installer allows or exists a way of doing same thing than before we did in some manner or other one….. And, you're absolutely right. Some facts/history: a. I'm not the one that killed it (on the contrary, like yourself, I was vehemently arguing against its death -- like you say, UNTIL whatever replacement could offer the same features). ASIDE: You can see my arguing the same points your making now at the below link to the mailing-list archives: http://lists.freebsd.org/pipermail/freebsd-sysinstall/2011-February/000369.html ASIDE: There's a lot of arguments for keeping sysinstall in the above-linked mailing-list, but at the end of the day, we have to realize that sysinstall was not being worked on to provide the features that the angry mob of users was demanding (GPT, ZFS, Geli, etc.) so the 15-year inertia that sysinstall enjoyed had to be ended. There will be people like yourself and me that disagree with the timeline of events that led to the demise of sysinstall in the 10.0-CURRENT line, but all I can say is that there is Ron McDowell (may he rest in peace) vehemently recognized the short-coming and dedicated our lives to filling it (and for Ron, actually the final year of his life was spent working on this project -- a truly selfless act if there ever was one). b. It's officially dead in the 10.0-CURRENT line (read:
Re: about unattended installation
Won't be able to help you much, but bsdinstall seems to be using gpart rather than fdisk. This page has a nice explanation on how to use gpart: http://www.wonkity.com/~wblock/docs/html/disksetup.html As for sysinstall, it's not being mainitned officially, but http://druidbsd.sourceforge.net/ is using sysinstall Amitabh On Wed, Dec 19, 2012 at 11:36 PM, Egoitz Aurrekoetxea Aurre ego...@ramattack.net wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. Apart from all this… is Sysinstall going to be maintained in parallel?. Thank you very much, Best regards! ___ 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: about unattended installation
On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. Hold on a moment. You might want to wait until 9.2. (read more below) I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the user interface (partedit) as one could sysinstall. (read below about 9.2) So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. The answer is (unfortunately) yes… that is until (hopefully) 9.2. It's an on-going significant amount of work to make add backward compatibility (so bsdinstall can load sysinstall install.cfg files). I'm not going to discuss the specifics here or yet, but I'm actively working on it. No docs on how to mangle the auto script to do what you want (that I know of). Apart from all this… is Sysinstall going to be maintained in parallel?. Sysinstall is dead. The bsdinstall you know can be considered the first generation and accordingly is a bit spartan. I'm working hard on the next generation. My plan is to have 10.0 with bsdinstall able to run sysinstall scripts (for backward compatibility; can't yet say what 9.x release will be MFC'd to, but that could be 9.2). I'm planning one helluva BSDCan-2013 presentation. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: about unattended installation
On Thu, Dec 20, 2012 at 12:29 AM, Devin Teske devin.te...@fisglobal.comwrote: On Dec 19, 2012, at 10:06 AM, Egoitz Aurrekoetxea Aurre wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. Hold on a moment. You might want to wait until 9.2. (read more below) I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. You're correct. In 9.0 and 9.1, it's just not feasible to man-handle the user interface (partedit) as one could sysinstall. (read below about 9.2) So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. The answer is (unfortunately) yes… that is until (hopefully) 9.2. It's an on-going significant amount of work to make add backward compatibility (so bsdinstall can load sysinstall install.cfg files). I'm not going to discuss the specifics here or yet, but I'm actively working on it. No docs on how to mangle the auto script to do what you want (that I know of). Apart from all this… is Sysinstall going to be maintained in parallel?. Sysinstall is dead. The bsdinstall you know can be considered the first generation and accordingly is a bit spartan. I'm working hard on the next generation. My plan is to have 10.0 with bsdinstall able to run sysinstall scripts (for backward compatibility; can't yet say what 9.x release will be MFC'd to, but that could be 9.2). I'm planning one helluva BSDCan-2013 presentation. -- Devin Interesting Devin. I have played around with bsdinstall script files and partedit source files to certain extent. Was able to achieve a bit of success. One of the major stumbling blocks for me still is including custom scripts and packages. Just can't seem to understand where and how to place them, so that it is available to auto script for further processing. Amitabh ___ 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: about unattended installation
On Dec 19, 2012, at 10:52 AM, Amitabh Kant wrote: Won't be able to help you much, but bsdinstall seems to be using gpart rather than fdisk. This page has a nice explanation on how to use gpart: http://www.wonkity.com/~wblock/docs/html/disksetup.html As for sysinstall, it's not being mainitned officially, but http://druidbsd.sourceforge.net/ is using sysinstall Cool! I'm the maintainer of FreeBSD Druid (sysinstall-based 9.x installer). When 9.1 is officially announced, I'll start rolling a new 9.1 based installer (right now, still just 8.3 and 9.0 are the latest offerings). I'm also the maintainer of bsdconfig. I'd like to also think I'm that last unofficial maintainer of sysinstall (I've actually patched it in stable/9 in the past 90 days). And, as-of the last DevSummit, I've been nominated the new maintainer of bsdinstall (with nwhitehorn's blessing). So… At some point, you'll see me go rabid on all the PR's in the freebsd-sysinstall pool, but right now I'm still in the coal-mines dredging out the framework to accept all these missing features. -- Devin On Wed, Dec 19, 2012 at 11:36 PM, Egoitz Aurrekoetxea Aurre ego...@ramattack.net wrote: Good afternoon, One little question… I'm trying to have ready our new unattended FreeBSD installation system. Until now, I have been using Sysinstall scripting file but now with 9.1 out I think it's moment to start using BSDInstaller in the unattended installation process. I have seen the new installer, works basically like an script…. my real question is… before I did in install.cfg something like : disk=da0 partition=all bootManager=standard diskPartitionEditor da0s1-1=ufs 3072000 / da0s1-2=swap 8096000 none da0s1-3=ufs 20485760 /var 1 da0s1-4=ufs 30720760 /usr 1 da0s1-5=ufs 0 /expert 1 diskLabelEditor Now I assume there's no way of getting this same through any command like… 'bsdinstall partedit ___' am I wrong??. So I assume all should be done by hand like this example of the Handbook : # dd if=/dev/zero of=/dev/da1 bs=1k count=1 # fdisk -BI da1 #Initialize your new disk # bsdlabel -B -w da1s1 auto #Label it. # bsdlabel -e da1s1 # Edit the bsdlabel just created and add any partitions. # mkdir -p /1 # newfs /dev/da1s1e # Repeat this for every partition you created. # mount /dev/da1s1e /1 # Mount the partition(s) # vi /etc/fstab # Add the appropriate entry/entries to your /etc/fstab. In the auto script…. am I wrong?. If the answer is yes… could you point me to some documentation in order to be able to complete all this doc. Apart from all this… is Sysinstall going to be maintained in parallel?. Thank you very much, Best regards! ___ 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 _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: About FreeBSD installation
It depends on what you really want. If you don't want 64-bit version OS, I don't think you'll have problems at all. Recently, my PC got fucked up, I've changed the mother board, switched from 32 bit AMD Athlon to a 64 bit AMD Turion, and successfully booted from the previously installed FreeBSD 4.9Release on the hard drive. If you want the 64 bit version of the OS, further investigation from you are needed. Check this out: http://www.freebsd.org/platforms/amd64.html Best Regards, Vladimir On 04/07/07, Yordan Yordanov [EMAIL PROTECTED] wrote: Hello I want to install the last stable release of FreeBSD Unix on my desktop machine with AMD64 processor. Are there any differences in the FreeBSD ports for these two platform: FreeBSD/i386 and amd64? In the FreeBSD handbook I saw a workaround which should be applied to set up FreeBSD for some chipsets. If I have such a problem can I try to install i386 version on my machine. There is no reason not to work, but I want to be sure that this is possible. Greetings from Bulgaria Yordan - С бензин в кръвта! http://auto-motor-und-sport.bg/ ___ 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: Re: About FreeBSD installation
Quoting Vladimir Tsvetkov [EMAIL PROTECTED]: It depends on what you really want. If you don't want 64-bit version OS, I don't think you'll have problems at all. Recently, my PC got fucked up, I've changed the mother board, switched from 32 bit AMD Athlon to a 64 bit AMD Turion, and successfully booted from the previously installed FreeBSD 4.9Release on the hard drive. If you want the 64 bit version of the OS, further investigation from you are needed. Check this out: http://www.freebsd.org/platforms/amd64.html About two weeks ago, I lost two amd-32 servers and replaced them with amd-64 and am running off the old disks beautifully, and much, much faster. I have over 500 ports on both. One was and is running up to date Stable and the other up to date Current. I was planning on going to AMD64 but with the current results, I really doubt that I will make the change until well after the current 7.0 release. I made this decision based on recommendations made on this list a few days ago. You might want to search the mailing lists if you need more assurance and if no just enjoy the AMD64. I'm happy with their performance and price. enjoy, ed Best Regards, Vladimir On 04/07/07, Yordan Yordanov [EMAIL PROTECTED] wrote: Hello I want to install the last stable release of FreeBSD Unix on my desktop machine with AMD64 processor. Are there any differences in the FreeBSD ports for these two platform: FreeBSD/i386 and amd64? In the FreeBSD handbook I saw a workaround which should be applied to set up FreeBSD for some chipsets. If I have such a problem can I try to install i386 version on my machine. There is no reason not to work, but I want to be sure that this is possible. Greetings from Bulgaria Yordan - С бензин в кръвта! http://auto-motor-und-sport.bg/ ___ 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: About FreeBSD installation
Yordan Yordanov wrote: Hello I want to install the last stable release of FreeBSD Unix on my desktop machine with AMD64 processor. Are there any differences in the FreeBSD ports for these two platform: FreeBSD/i386 and amd64? In the FreeBSD handbook I saw a workaround which should be applied to set up FreeBSD for some chipsets. If I have such a problem can I try to install i386 version on my machine. There is no reason not to work, but I want to be sure that this is possible. Greetings from Bulgaria Yordan - С бензин в кръвта! http://auto-motor-und-sport.bg/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Yordan, This FreeBSD box I am using to email you is a dual AMD 64 running on i386 7.0 CURRENT. It runs just finefast. The AMD64 version of the os gave me many errors and wouldn't run the video card so I switched to the i386. top -S shows it is running efficiently. Aloha ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] + + http://internetohana.org - Supporting - FreeBSD 6.* - 7.* + All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: about the installation
Generally what happens on an install, if you select to install the freebsd boot loader, is that you'll get a menu upon boot that looks similar to: F1 ?? F2 Disk 1 Pressing F1 will boot Windows 2000 (or XP) and pressing F2 will show a menu such as: F1 FreeBSD F2 Disk 0 These menus will just go back and forth if you keep pressing F2. You should not need to install Windows 2000 again. Just make sure you don't delete that partition. HTH Eric F Crist President AdTech Integrated Systems, Inc (612) 998-3588 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge L. Valenzuela Sent: Sunday, June 13, 2004 1:24 AM To: [EMAIL PROTECTED] Subject: about the installation Hi I'd like to try the freebsd on my computer. I've three partitions, the first has win98, the second win2000 and I use the last one as a data disk. I don't care about my win98 O/S, but I don't know what will happend, if I install the freeBSD, with my win2000 cuz I need it to work. This is my question: I'm always asked for the O/S to use at the start. If I delete my win98 partitiion will I be asked to use the FreeBSD or win2000 O/S? Do I need to reinstall the win2000 after installing the freeBSD? Thanks, Jorge Valenzuela _ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.click-url.com/go/onm00200362ave/direct/01/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/free bsd-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]