mfsroot starts sysinstall how?
Hi all, For anyone interested, I posted a blog with regards to how sysinstall is run from mfsroot. URL is http://blog.hostileadmin.com/2012/12/18/mfsroot-starts-sysinstall-how/ -- 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: mfsroot starts sysinstall how?
On Dec 12, 2012, at 7:50 AM, Rick Miller wrote: > On Wed, Dec 12, 2012 at 10:44 AM, Rick Miller > wrote: >> Hi All, >> >> How is sysinstall invoked in a FreeBSD 8.x mfsroot.gz? > It's actually invoked in the place of init(8). > To explain more, I would like to boot into a shell as opposed to > sysinstall. safe mode and single user don't seem to. > Safe mode and single user won't work because sysinstall is acting as init and it doesn't implement those functions. To run a shell script in the place of init(8), you have to do some bootstrapping. Enter DruidBSD ( … not to be confused with previously discussed Druid [in another thread]). DruidBSD is a ~24MB ISO (~32MB if you get the version that has the extra tools like memtest86, etc.): http://druidbsd.sourceforge.net/download.shtml#DruidBSD Not only does it do what you're asking about … boot to a shell … but you can customize it. It uses the same build framework as the Druid (requiring GNU make, mkisofs, and [optionally] perl -- only required if you want the ISO to work from both CD/DVD _and_ USB thumb drive). You can download the source code, make changes to the custom /etc/rc which does the bootstrapping for you, and more -- then when finished, simply say "gmake freebsd" to produce your new custom media. It doesn't stop there… the /etc/rc that's in the mfsroot (link below): http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druidbsd/dep/freebsd/mfsroot/src/etc/rc?revision=1.1.1.1&view=markup Is designed to bust you out of the mfsroot and bootstrap you not into a derelict sh(1) prompt, but instead a [more] usable bash(1) prompt complete with hundreds of extra utilities. PRO TIP: The Druid (which is the [much] larger ~500MB FreeBSD Installer that uses the same build framework) actually has a miniature version of DruidBSD tucked into its boot loader. That is to explain that when you use the FreeBSD Druid installer, the beastie boot menu has a fancy feature where you can select a different mfsroot from the menu (if you select the "rescue_mfsroot" then you're essentially invoking a custom version of DruidBSD, which we're talking about right now w/respect to replacing sysinstall(8) in an mfsroot with a bootstrap-to-interactive-shell). -- 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: mfsroot starts sysinstall how?
On Wed, Dec 12, 2012 at 10:44 AM, Rick Miller wrote: > Hi All, > > How is sysinstall invoked in a FreeBSD 8.x mfsroot.gz? To explain more, I would like to boot into a shell as opposed to sysinstall. safe mode and single user don't seem to. -- 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"
mfsroot starts sysinstall how?
Hi All, How is sysinstall invoked in a FreeBSD 8.x mfsroot.gz? -- 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: sysinstall diskPartitionEditor Question
On Tue, Jun 26, 2012 at 10:30 AM, Rick Miller wrote: > Hi All, > > I'd like to set the offset/starting cylinder in install.cfg so that > partitions begin on appropriate boundaries. The applicable section of > install.cfg looks like the following. My assumption is that I need to > make the changes in the "partition" section. Is this correct? Is the > format of this value the same as a typical fdisk config file? After copious amounts of reading and experimenting. It seems as though diskPartitionEdit doesn't support specifying a starting cylinder. When I specify partition=all, it starts that slice at sector 63. I'd like to start it at 64 or above. Is it feasible to include gpart in the mfsroot and use that to partition the drive before sysinstall continues with the installation? -- 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"
sysinstall diskPartitionEditor Question
Hi All,
I'd like to set the offset/starting cylinder in install.cfg so that
partitions begin on appropriate boundaries. The applicable section of
install.cfg looks like the following. My assumption is that I need to
make the changes in the "partition" section. Is this correct? Is the
format of this value the same as a typical fdisk config file?
### Begin install.cfg snippet
disk=\${disk}
partition=all
bootManager=standard
diskPartitionEditor
# root
\${disk}s1-1=ufs 12582912 /
# swap
\${disk}s1-2=swap ${swap} none
# tmp
\${disk}s1-3=ufs 2097152 /tmp 1
# 2 GB var
\${disk}s1-4=ufs 4194304 /var 1
# 2 GB home
\${disk}s1-5=ufs 4194304 /home 1
diskLabelEditor
### End snippet
--
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"
Building a releng_9_0 with sysinstall, livefs and mfsroot
Good morning, Have just sent to freebsd-hackers mailing list the way of doing this. I say this because perhaps could be useful for someone... 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: sysinstall
On 03/07/12 01:01, David Walker wrote: Da Rock freebsd-questions at herveybayaustralia.com.au What tv card? Mine work fine Thread here: http://lists.freebsd.org/pipermail/freebsd-drivers/2012-February/001370.html May have to do with the cx88 port available, especially as its from 2006 (last word 2008). I would put my money on that as a solution, which is why I couldn't quite understand why you said it didn't work. CX88 has been available since 2010. Comes with apps, and also means to make all the v4l based apps (like xine, mplayer) work as well. I would doubt that that pr will ever go through for that reason. ___ 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: sysinstall
Da Rock freebsd-questions at herveybayaustralia.com.au > What tv card? Mine work fine Thread here: http://lists.freebsd.org/pipermail/freebsd-drivers/2012-February/001370.html ___ 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: sysinstall
On 03/06/12 05:23, David Walker wrote: Nikola Pavlović nzp at riseup.net OK, here goes: (in Nelson Muntz's voice) Haha, you clown, that's what you get for believing what documentation says. Use a magnetized needle and a steady hand you buffoon! There. I respect! :) Well played. It's a serious issue for me after 15 years of Windows on the desktop to change environment to FreeBSD. I've reached this point after lengthy deliberation with the intent to change once only. While I consider it disappointing and surprising that man pages are suspect (no doubt most are accurate) the bottom line is the community response which includes man page writers and you and me. Well played there too. Disregarding any hiccups, I'm running FreeBSD on my main machine, I've installed X11 and Gnome and it works better than I could have envisoned - the first video I went to on YouTube played ... roll on HTML5 ... sound works ... Fix my tv card and I'll shut up. :] What tv card? Mine work fine ___ 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: sysinstall
Nikola Pavlović nzp at riseup.net > OK, here goes: (in Nelson Muntz's voice) Haha, you clown, that's what > you get for believing what documentation says. Use a magnetized needle > and a steady hand you buffoon! > There. I respect! :) Well played. It's a serious issue for me after 15 years of Windows on the desktop to change environment to FreeBSD. I've reached this point after lengthy deliberation with the intent to change once only. While I consider it disappointing and surprising that man pages are suspect (no doubt most are accurate) the bottom line is the community response which includes man page writers and you and me. Well played there too. Disregarding any hiccups, I'm running FreeBSD on my main machine, I've installed X11 and Gnome and it works better than I could have envisoned - the first video I went to on YouTube played ... roll on HTML5 ... sound works ... Fix my tv card and I'll shut up. :] Best wishes. ___ 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: sysinstall
On Sun, Mar 04, 2012 at 07:24:23PM +1030, David Walker wrote:
> Nikola Pavlović nzp at riseup.net
> > If you did it the normal way
>
> Please define normal.
>
> As per the way you do it? Surely that's not what you mean right?
>
> As per the handbook?
> As per the man pages?
Believe it or not, reading my answer when it came back through the list
that was my thought too ('Damn, I should have been clearer what "normal"
means). :) In this particular case 'normal' meant 'as per what
bsdinstall suggested'.
>
> As per the way I usually do it?
> I'm new here so I don't have a normal way other than spending hours
> reading documentation ... and telling myself that everything that goes
> wrong is probably my fault.
> That's my normal way when I'm using new software.
>
Well, if you do everything the docs tell you to, then there is no reason
to think it's your fault.
> That's also my normal way when I'm familiar with something.
> Please tell me if that methodology is not as good as yours ...
>
> > with bsdinstall then I guess everything
> > would install correctly.
>
> I guess that also.
> Please read man sysinstall for me and point out why I should be
> guessing whether or not system utilities are intended to function as
> described.
I agree completely. This is a case of the 'no documentation is better
than wrong documentation' rule. The Handbook and man page should
clearly point out that sysinstall doesn't work with the new distribution
packaging. At any rate, once you step into 9.x land you should
forget about sysinstall. Hey, a mailing list is *a kind of*
documentation too. ;)
> Replies to the list are fine.
>
> > But anyway, you can use the other methods
> > mentioned in the handbook.
>
> ... and anyway, if cp(1) fails I can use dump(8) instead.
> Problem solved.
I don't understand why you are dumping your frustration on me. I
assure you I'm not responsible for documentation. :) And cp/dump analogy
is a bit flawed, they are different tools for different jobs, while the
other methods of installing the ports tree are just using a few
different tools that are *meant* for the job.
>
> > Doing it with
>
> > # portsnap fetch extract
>
> > seems the most straight forward way to me.
>
> Sysinstall seems the most straight forward way to me.
>
> It might be of interest to you that after spending an hour or so with
> sysinstall I proceeded to spend an hour or so with portsnap before it
> appeared to work.
What was the problem?
> My undocumented experience with it and what you apparently consider
> are normal and/or straight forward, seem, under the circumstances, of
> no import.
>
> If you want to espouse an opposing view without explanation or
> ridicule my methodology, knock yourself out but please do it like I'm
> your friend.
Um, what? What opposing view? Ridicule?! Whatisthisidonteven...
> A simple "use portsnap you clown" probably would have done it for me
> and put a smile on my face.
Why would I call you a clown if I don't think you are one? I don't
usually ridicule strangers, but when I do, I make sure there's a reason
for ridicule.
> In my experience that's the "normal" and "most straight forward" way
> someone who respects me might approach this ...
>
OK, here goes: (in Nelson Muntz's voice) Haha, you clown, that's what
you get for believing what documentation says. Use a magnetized needle
and a steady hand you buffoon!
There. I respect! :)
--
Laissez Faire Economics is the theory that if
each acts like a vulture, all will end as doves.
___
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: sysinstall
Nikola Pavlović nzp at riseup.net > If you did it the normal way Please define normal. As per the way you do it? Surely that's not what you mean right? As per the handbook? As per the man pages? As per the way I usually do it? I'm new here so I don't have a normal way other than spending hours reading documentation ... and telling myself that everything that goes wrong is probably my fault. That's my normal way when I'm using new software. That's also my normal way when I'm familiar with something. Please tell me if that methodology is not as good as yours ... > with bsdinstall then I guess everything > would install correctly. I guess that also. Please read man sysinstall for me and point out why I should be guessing whether or not system utilities are intended to function as described. Replies to the list are fine. > But anyway, you can use the other methods > mentioned in the handbook. ... and anyway, if cp(1) fails I can use dump(8) instead. Problem solved. > Doing it with > # portsnap fetch extract > seems the most straight forward way to me. Sysinstall seems the most straight forward way to me. It might be of interest to you that after spending an hour or so with sysinstall I proceeded to spend an hour or so with portsnap before it appeared to work. My undocumented experience with it and what you apparently consider are normal and/or straight forward, seem, under the circumstances, of no import. If you want to espouse an opposing view without explanation or ridicule my methodology, knock yourself out but please do it like I'm your friend. A simple "use portsnap you clown" probably would have done it for me and put a smile on my face. In my experience that's the "normal" and "most straight forward" way someone who respects me might approach this ... Best wishes. ___ 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: sysinstall
So of course I can't install source using sysinstall either ... No problem, I'll re-install (reverting a few hours of work) and do it on the install. Of course it works perfectly - I am able to install ports and src from the CD that sysinstall fails on ... As I'm getting used to though, there's more facepalming ... I'll do what I'm accustomed to do ... and partition my drive ... this should be easy. / 1GB swap 1GB /root 1GB /tmp /1GB /usr 50GB etcetera ... FreeBSD can't extract root/.profile from base.txz (or similar) avanothergo or exit ... No worries, it's a bit of dust, avanothergo ... Rinse and repeat x times - so I pull the CD out of the drive and rinse. Looks pretty clean ... try again. FreeBSD can't extract etcetera. I installed from this CD a few hours previously on a brand new (a handful of uses) drive. I remember reading somewhere that 2GB is a recommended size for / (don't ask me where, I've looked) but I've taken this into account with a separate /root right? Let's bump all of them anyway. / 2GB swap 2GB /root 2GB /tmp /2GB /usr 50GB etcetera ... FreeBSD can't extract some file from some where ... ... avanothergo and use the default partitioning scheme, it must be the CD but I'll verify that ... So after an hour or so, success. I'm interested in the reason for this. Surely not inodes? Is this considered a bug? Is there at least one reason why a separate /root slice should not be allowed? If so, I think it would be nice to see an error message that describes the situation. On 04/03/2012, David Walker wrote: > So I installed amd64 9.0 tonight and decided against installing "ports". > I'm at a point now where I'm thinking about adding it and I see sysinstall: > http://www.freebsd.org/doc/handbook/ports-using.html > Looks easy. > > For some unknown reason sysinstall spits the following: > > Warning: The disc currently in the drive is either not a FreeBSD > disc or it is an older (pre 1.2.5) FreeBSD CD which does not have a > version number on it. Do you wish to use this disc anyway? > > Like any sane person who burned this CD a few hours previously on the > same machine from within FreeBSD and then installed from it shortly > afterwards I click "Yes" ... > > So that doesn't work. > I wonder what would have happened if I had elected to install "ports" > during the initial install ... > > I'm here if anyone's bothered and wants more information. > > Best wishes. > ___ 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: sysinstall
On Sun, Mar 04, 2012 at 06:37:07AM +1030, David Walker wrote: > So I installed amd64 9.0 tonight and decided against installing "ports". > I'm at a point now where I'm thinking about adding it and I see sysinstall: > http://www.freebsd.org/doc/handbook/ports-using.html > Looks easy. > > For some unknown reason sysinstall spits the following: > > Warning: The disc currently in the drive is either not a FreeBSD > disc or it is an older (pre 1.2.5) FreeBSD CD which does not have a > version number on it. Do you wish to use this disc anyway? > It's probably because sysinstall doesn't understand the new distribution format--everything is now in /usr/freebsd-dist/ neatly packed in single archives, instead of the old way in /X.Y-RELENG_TAG/ with floppy-friendly split archives. > Like any sane person who burned this CD a few hours previously on the > same machine from within FreeBSD and then installed from it shortly > afterwards I click "Yes" ... > > So that doesn't work. > I wonder what would have happened if I had elected to install "ports" > during the initial install ... If you did it the normal way with bsdinstall then I guess everything would install correctly. But anyway, you can use the other methods mentioned in the handbook. Doing it with # portsnap fetch extract seems the most straight forward way to me. -- If you can't say anything good about someone, sit right here by me. -- Alice Roosevelt Longworth ___ 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: sysinstall
On 03/03/2012 20:07, David Walker wrote: > So I installed amd64 9.0 tonight and decided against installing "ports". > I'm at a point now where I'm thinking about adding it and I see sysinstall: > http://www.freebsd.org/doc/handbook/ports-using.html > Looks easy. > > For some unknown reason sysinstall spits the following: > > Warning: The disc currently in the drive is either not a FreeBSD > disc or it is an older (pre 1.2.5) FreeBSD CD which does not have a > version number on it. Do you wish to use this disc anyway? > > Like any sane person who burned this CD a few hours previously on the > same machine from within FreeBSD and then installed from it shortly > afterwards I click "Yes" ... > > So that doesn't work. > I wonder what would have happened if I had elected to install "ports" > during the initial install ... > > I'm here if anyone's bothered and wants more information. Once the system is up-and-running, forget about sysinstall. (Or, for those of you that keep up with the latest trends, bsdinstall). The install is done, and its job is over. Instead, choose one of the following two exciting command lines, according to taste: # csup -h cvsup.fr.freebsd.org /usr/share/examples/cvsup/ports-supfile (Choose a cvsup server near you if you don't happen to be anywhere near France) --or-- # portsnap fetch extract Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
sysinstall
So I installed amd64 9.0 tonight and decided against installing "ports". I'm at a point now where I'm thinking about adding it and I see sysinstall: http://www.freebsd.org/doc/handbook/ports-using.html Looks easy. For some unknown reason sysinstall spits the following: Warning: The disc currently in the drive is either not a FreeBSD disc or it is an older (pre 1.2.5) FreeBSD CD which does not have a version number on it. Do you wish to use this disc anyway? Like any sane person who burned this CD a few hours previously on the same machine from within FreeBSD and then installed from it shortly afterwards I click "Yes" ... So that doesn't work. I wonder what would have happened if I had elected to install "ports" during the initial install ... I'm here if anyone's bothered and wants more information. Best wishes. ___ 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: sysinstall cant seem to download the kernel source.
On Fri, 17 Feb 2012, Brent Clark wrote: I seem to have this problem with sysinstall, whereby I cant seem to download the kernel source. I tried following this example http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/ I use "Install from an FTP server" The error message I get is "Unable to transfer the sbase distribution from ftp://ftp.freebsd.org."; Does anyone know of another way to get the kernel source. Cvs or svn. Depends on the version of FreeBSD. For 9, http://forums.freebsd.org/showthread.php?t=29172 ___ 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: sysinstall cant seem to download the kernel source.
On Fri, 17 Feb 2012 11:31:39 +0200 Brent Clark wrote: > I use "Install from an FTP server" > > The error message I get is "Unable to transfer the sbase distribution > from ftp://ftp.freebsd.org."; > > Does anyone know of another way to get the kernel source. Get it with csup and be sure to set the correct tag in your supfile (probably RELENG_9_0, for the 9.0 security branch or RELENG_9 for the stable development branch). In the long term it's simplest and safest to start from an empty src directory anyway. ___ 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: sysinstall cant seem to download the kernel source.
On 02/17/12 19:31, Brent Clark wrote: Hiya I seem to have this problem with sysinstall, whereby I cant seem to download the kernel source. I tried following this example http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/ I use "Install from an FTP server" The error message I get is "Unable to transfer the sbase distribution from ftp://ftp.freebsd.org."; Does anyone know of another way to get the kernel source. Cvs or svn. A quick search of previous posts to this list should provide the answer you need. Try from last month I think :) ___ 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"
sysinstall cant seem to download the kernel source.
Hiya I seem to have this problem with sysinstall, whereby I cant seem to download the kernel source. I tried following this example http://www.cyberciti.biz/faq/freebsd-install-kernel-source-code/ I use "Install from an FTP server" The error message I get is "Unable to transfer the sbase distribution from ftp://ftp.freebsd.org."; Does anyone know of another way to get the kernel source. Cvs or svn. Regards Brent ___ 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"
8.2-RELEASE sysinstall creates duplicate rc.conf lines
Hi all, We recently discovered that sysinstall appears to be adding it's own lines to /etc/rc.conf which are duplicates of lines that we are inserting during builds. For example, on one of our hosts, we are adding "defaultrouter" and "ifconfig_em0" with certain network configurations. When we reboot the system we find that sysinstall also inserted a "defaultrouter" and "ifconfig_em0" populated with the data that existed on the interface during the build. See a sample of the rc.conf below. We are making use of the keeprcconf in the install.cfg, but this does not prevent sysinstall from adding those lines. Is there some way to prevent this behavior? # Sample rc.conf after sysinstall build defaultrouter="10.0.0.1" defaultrouter="192.168.0.1" hostname="bsdtest" ifconfig_em0="inet 10.0.0.2 netmask 255.255.252.0" ifconfig_em0="inet 192.168.0.2 netmaks 255.255.255.0" sshd_enable="YES" -- 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: Scritping sysinstall and custom iso
On Sun, 28 Aug 2011 17:20:34 +0530, Amitabh Kant wrote: > All the commands run fine and I am able to generate an iso. Now, couple of > questions that have confused me: > a) Where do I place install.cfg file for sysinstall to read without any user > intervention? In the root directory of the disc1 layout or inside > 8.2-Release / other sub directory? According to /usr/src/usr.sbin/sysinstall/install.cfg's location from which one would conclude that the sysinstall would be in /usr/sbin of the CD (as well as installed on the disk), I would assume install.cfg to be in the same directory as the sysinstall program itself - /usr/sbin. But it could also be /stand... > b) Is there a place where I can get a sample install.cfg with all the > options explained? All I could find were different examples tailored to > specific situations, most of them towards PXE boot. The file /usr/src/usr.sbin/sysinstall/install.cfg does contain some comments for explaination. Also see "man 8 sysinstall" for the "SCRIPT SYNTAX" section. > c) Is it necessary to define every step in install.cfg? I would like to keep > disk partition / label and network configuration dialogs available (root > password if necessary), while setting values for all other user dialogs and > screens. I don't think it is neccessary (as assumed by the "incomplete" install.cfg mentioned above), but consult the documentation to be sure. -- Polytropon 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"
Scritping sysinstall and custom iso
Hello I am trying to create a custom FreeBSD iso which will automate most of the steps asked in a standard installation using sysinstall. While "make release" is available, I was trying to modify disc1 iso, as it seems that I only need to have install.cfg for automating sysinstall. I downloaded the disc1 iso file (8.2 amd64 arch), created a memory disk using mdconfig, and then mounted the disk. The commands that I have run are: mdconfig -a -t vnode -f org.iso -u 0 mount_cd9660 /dev/md0 /mnt mkdir custom_iso cd custom_iso rsync -a /mnt/ . Once I am done with the changes, I plan to run the following command to recreate the iso mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/home/isotest/custom.iso . All the commands run fine and I am able to generate an iso. Now, couple of questions that have confused me: a) Where do I place install.cfg file for sysinstall to read without any user intervention? In the root directory of the disc1 layout or inside 8.2-Release / other sub directory? b) Is there a place where I can get a sample install.cfg with all the options explained? All I could find were different examples tailored to specific situations, most of them towards PXE boot. c) Is it necessary to define every step in install.cfg? I would like to keep disk partition / label and network configuration dialogs available (root password if necessary), while setting values for all other user dialogs and screens. Amitabh Kant ___ 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: sysinstall error on 8.2-PRE
On Thu, 6 Jan 2011 20:13:08 +0300 Odhiambo Washington wrote: > So, how do I fix/manoeuvre around that problem? Unfortunately you'd need to use a different tool to partition/label the disk, such as gpart. -- Bruce Cran ___ 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: sysinstall error on 8.2-PRE
On Thu, Jan 6, 2011 at 8:02 PM, Bruce Cran wrote: > On Thu, 6 Jan 2011 17:38:33 +0300 > Odhiambo Washington wrote: > > > I have a strange problem. On one system that I am running, I cannot > > use sysinstall to do partition/label for a disk. This problem seems > > peculiar to this OS, somewhere. > > When I launch sysinstall, I get some funny message appear on the > > screen (see http://lix.in/-9b7e16 for an image). > > >From there I choose custom -> partition > Select the disk then enter > > partition editor. The cursor simply refuses to move from there, though > > keyboard is active. > > The problem is that geom has been extended with additional types (e.g. > glabel, gsched) that libdisk doesn't know about - so it gets confused. > > So, how do I fix/manoeuvre around that problem? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ 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: sysinstall error on 8.2-PRE
On Thu, 6 Jan 2011 17:38:33 +0300 Odhiambo Washington wrote: > I have a strange problem. On one system that I am running, I cannot > use sysinstall to do partition/label for a disk. This problem seems > peculiar to this OS, somewhere. > When I launch sysinstall, I get some funny message appear on the > screen (see http://lix.in/-9b7e16 for an image). > >From there I choose custom -> partition > Select the disk then enter > partition editor. The cursor simply refuses to move from there, though > keyboard is active. The problem is that geom has been extended with additional types (e.g. glabel, gsched) that libdisk doesn't know about - so it gets confused. -- Bruce Cran ___ 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"
sysinstall error on 8.2-PRE
Dear people, I have a strange problem. On one system that I am running, I cannot use sysinstall to do partition/label for a disk. This problem seems peculiar to this OS, somewhere. When I launch sysinstall, I get some funny message appear on the screen (see http://lix.in/-9b7e16 for an image). >From there I choose custom -> partition > Select the disk then enter partition editor. The cursor simply refuses to move from there, though keyboard is active. What may be the cause? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ 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: Specifying "Install Root" on non interactive sysinstall
Many thanks for your answer, it helps me solving some issues. David -Message d'origine- De : owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] De la part de Devin Teske Envoyé : mardi 9 novembre 2010 18:13 À : Ramblewski David Cc : freebsd-questions@freebsd.org; freebsd-sysinst...@freebsd.org Objet : Re: Specifying "Install Root" on non interactive sysinstall On Tue, 2010-11-09 at 10:18 +0100, Ramblewski David wrote: > Hi, > > I'm looking for a solution to jumpstart FreeBSD on an non interactive way. > The solution provided by the Handbook recommend to use sysinstall program, > that's what I'm trying to do. -sysinstall@ would have been a better choice for this question. Cross-posting my reply. > The servers are using PXE boot to mount an mfsbsd filesystem, everything > works as expected until now. > I manually create the slice, labels and mount the partitions on "/mnt" > partition. You might just want to try adding "diskInteractive=YES" to your install.cfg file. That way, you don't have to manually partition/slice/label your disk _before_ you load the config. By setting diskInteractive, when installCommit is called, it will: a. if `disk' is not set (e.g. disk=da0) throw up a menu to select which disk you want to partition b. throw you into the FDISK partition editor c. throw you into diskabel e. ask which boot code you want to install (if any) to the MBR Just a suggestion. > Then I manually launch "sysinstall loadConfig" to install packages classes > but I didn't find the way to precise an "Install Root" for /mnt whereas it > works if I did it on a interactive way using the options menu. Put this into your install.cfg: # Required by distExtractAll (called indirectly by installCommit): installRoot=/mnt > Does anyone know how to solve this issue? > > Here is my install.cfg file: > -- > # Turn on extra debugging. > debug=YES > > # Ok, this ought to turn off ALL prompting, don't complain to me that you > # lost a machine because you netbooted it on the same subnet as this > # box > nonInteractive=YES > noWarn=YES > tryDHCP=YES > > # My host specific data > hostname=polbsd > domainname=priv.atos.fr > > > # Which installation device to use > nfs=10.28.222.1:/opt/local/jumpstart/tftpboot/BSD/NFS > netDev=bge0 > mediaSetNFS > > > > # Select which distributions we want. > dists= base SMP manpages ports Hmmm. Must be an older release. The SMP kernel has gone missing in FreeBSD-8.x. > distSetCustom > > > # OK, everything is set. Do it! > installCommit > > shutdown > -- > > > Thanks, > > David -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> FUN STUFF <- -BEGIN GEEK CODE BLOCK- Version 3.1 GAT/CS d(+) s: a- C++() UB$ P++() L++() !E--- W++ N? o? K- w O M+ V- PS+ PE Y+ PGP- t(+) 5? X+(++) R>++ tv(+) b+(++) DI+(++) D(+) G+>++ e>+ h r>++ y+ --END GEEK CODE BLOCK-- http://www.geekcode.com/ -> END TRANSMISSION <- ___ 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" Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and in
Re: Re: sysinstall install.cfg
Wow! Thanks for all the info and the time you spent pulling it together and
writing it out, Devin! There is a lot to digest. Right now, I do have
a "workaround" that I am currently testing out. I will be hanging onto your
email for future reference, certainly.
On Nov 11, 2010 12:19pm, Devin Teske wrote:
On Thu, 2010-11-11 at 12:12 +, vrwmil...@gmail.com wrote:
> Hi all,
>
> Hoping that someone might be able to help me here. I dynamically
generate
> much of the install.cfg by running scripts that send output to files
that
> are, in turn, loaded into install.cfg utilizing loadConfig. The scripts
> that are run are placed into the mfsroot in /stand and /. They send the
> output to /a.
>
> I do this twice before the installCommit and both scripts run and load
the
> resulting configs successfully. I also run another script after the
> InstallComit...it fails citing the script could not be found.
Before distExtractAll is called (called implicitly by installCommit if
not previously called), this is the layout of your environment:
/ -- your mfsroot
/mnt -- your newly formatted disk (empty at this time)
/mnt/dist -- your install media (beit CD/DVD, NFS, etc.)
Meanwhile, _after_ distExtractAll (or installCommit in your case), you
are chroot(2)'ed into /mnt, so this is now your environment:
/ -- your newly formatted disk (populated with FreeBSD now)
/dist -- your install media
> In troubleshooting, I found that sysinstall is removing /stand
That's right:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/install.c.diff?r1=1.360;r2=1.361;f=h
That change was made 5 years, 9 months ago.
> and doing other
> stuff to / and /var. So, I know why the script cannot be found...because
> sysinstall is removing it.
>
> The question I have then is how can I get around this? I attempted
putting
> the script above the installCommit, but the functions being performed
here
> require that the base system already be in place (I'm adding packages).
It
> seems that I have little choice, but to have this after the
installCommit.
> Unfortunately, sysinstall wipes it out.
>
> Any guidance is greatly appreciated.
You essentially have about 5 options (I'll let you choose):
1. You can patch sysinstall to keep `/stand' around.
2. You can use an older mfsroot containing an older build of sysinstall
which doesn't blow away `/stand' (not recommended)
3. You can switch using pc-sysinstall (as mentioned by krad)
4. You can create a "post_install.cfg" in the install media and have
your call loadConfig on `/dist/post_install.cfg' after installCommit
5. You can use an mfsroot already tailored specifically to your needs
available at http://druidbsd.sf.net/
Let's look at each option in detail:
1. If you want to patch sysinstall to keep `/stand' around, here's what
you need to do:
a. cvsup the FreeBSD source tree (beyond the scope of this e-mail)
b. Apply the below patch
--- /usr/src/usr.sbin/sysinstall/install.c 2010-11-11 03:05:53.0
-0800
+++ /usr/src/usr.sbin/sysinstall/install.c.orig 2010-06-13
19:09:06.0 -0700
@@ -906,6 +906,9 @@ installFixupBase(dialogMenuItem *self)
/* BOGON #5: aliases database not built for bin */
vsystem("newaliases");
+ /* BOGON #6: Remove /stand (finally) */
+ vsystem("rm -rf /stand");
+
/* Now run all the mtree stuff to fix things up */
vsystem("mtree -deU -f /etc/mtree/BSD.root.dist -p /");
vsystem("mtree -deU -f /etc/mtree/BSD.var.dist -p /var");
c. Compile a new mfsroot containing your patched sysinstall by:
i. cd /usr/src
ii. make buildworld
iii. cd /usr/src/release
iv. make release CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES
NOTE: If the `make release' fails, it can be resumed...
i. cd /usr/src/release
ii. make rerelease CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \
RELEASENOUPDATE=YES
d. Your mfsroot is at `/usr/release/R/stage/mfsroot/mfsroot.gz'
NOTE: If, after a successful release, you want to change re-build
your mfsroot, you really ought to only re-do the `make release'
step. However, that can be lengthy. If you want to patch only a
single file and rebuild, you need to first copy the modified
files from `/usr/src' to `/usr/release/usr/src' (for example,
copy `/usr/src/usr.sbin/sysinstall/install.c' to
`/usr/release/usr/src/usr.sbin/sysinstall/install.c') and then:
i. rm -f /usr/release/usr/obj/usr/src/releas
Re: sysinstall install.cfg
On Thu, 2010-11-11 at 12:12 +, vrwmil...@gmail.com wrote:
> Hi all,
>
> Hoping that someone might be able to help me here. I dynamically generate
> much of the install.cfg by running scripts that send output to files that
> are, in turn, loaded into install.cfg utilizing loadConfig. The scripts
> that are run are placed into the mfsroot in /stand and /. They send the
> output to /a.
>
> I do this twice before the installCommit and both scripts run and load the
> resulting configs successfully. I also run another script after the
> InstallComit...it fails citing the script could not be found.
Before distExtractAll is called (called implicitly by installCommit if
not previously called), this is the layout of your environment:
/ -- your mfsroot
/mnt -- your newly formatted disk (empty at this time)
/mnt/dist -- your install media (beit CD/DVD, NFS, etc.)
Meanwhile, _after_ distExtractAll (or installCommit in your case), you
are chroot(2)'ed into /mnt, so this is now your environment:
/ -- your newly formatted disk (populated with FreeBSD now)
/dist -- your install media
> In troubleshooting, I found that sysinstall is removing /stand
That's right:
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/sysinstall/install.c.diff?r1=1.360;r2=1.361;f=h
That change was made 5 years, 9 months ago.
> and doing other
> stuff to / and /var. So, I know why the script cannot be found...because
> sysinstall is removing it.
>
> The question I have then is how can I get around this? I attempted putting
> the script above the installCommit, but the functions being performed here
> require that the base system already be in place (I'm adding packages). It
> seems that I have little choice, but to have this after the installCommit.
> Unfortunately, sysinstall wipes it out.
>
> Any guidance is greatly appreciated.
You essentially have about 5 options (I'll let you choose):
1. You can patch sysinstall to keep `/stand' around.
2. You can use an older mfsroot containing an older build of sysinstall
which doesn't blow away `/stand' (not recommended)
3. You can switch using pc-sysinstall (as mentioned by krad)
4. You can create a "post_install.cfg" in the install media and have
your call loadConfig on `/dist/post_install.cfg' after installCommit
5. You can use an mfsroot already tailored specifically to your needs
available at http://druidbsd.sf.net/
Let's look at each option in detail:
1. If you want to patch sysinstall to keep `/stand' around, here's what
you need to do:
a. cvsup the FreeBSD source tree (beyond the scope of this e-mail)
b. Apply the below patch
--- /usr/src/usr.sbin/sysinstall/install.c 2010-11-11 03:05:53.0
-0800
+++ /usr/src/usr.sbin/sysinstall/install.c.orig 2010-06-13 19:09:06.0
-0700
@@ -906,6 +906,9 @@ installFixupBase(dialogMenuItem *self)
/* BOGON #5: aliases database not built for bin */
vsystem("newaliases");
+ /* BOGON #6: Remove /stand (finally) */
+ vsystem("rm -rf /stand");
+
/* Now run all the mtree stuff to fix things up */
vsystem("mtree -deU -f /etc/mtree/BSD.root.dist -p /");
vsystem("mtree -deU -f /etc/mtree/BSD.var.dist -p /var");
c. Compile a new mfsroot containing your patched sysinstall by:
i. cd /usr/src
ii. make buildworld
iii. cd /usr/src/release
iv. make release CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES
NOTE: If the `make release' fails, it can be resumed...
i. cd /usr/src/release
ii. make rerelease CHROOTDIR=/usr/release EXTSRCDIR=/usr/src \
NODOC=YES NO_FLOPPIES=YES NOCDROM=YES NOPORTS=YES \
RELEASENOUPDATE=YES
d. Your mfsroot is at `/usr/release/R/stage/mfsroot/mfsroot.gz'
NOTE: If, after a successful release, you want to change re-build
your mfsroot, you really ought to only re-do the `make release'
step. However, that can be lengthy. If you want to patch only a
single file and rebuild, you need to first copy the modified
files from `/usr/src' to `/usr/release/usr/src' (for example,
copy `/usr/src/usr.sbin/sysinstall/install.c' to
`/usr/release/usr/src/usr.sbin/sysinstall/install.c') and then:
i. rm -f /usr/release/usr/obj/usr/src/release/release.4
ii. rm -f /usr/release/usr/obj/usr/src/release/release.8
iii. cd /usr/src/release
iv. make rerelease CHROOTDIR=/usr/release \
EXTSRCDIR=/usr/src NODOC=YES NO_FLOPPIES=YES \
NOCDROM=YES NOPORTS=YES RELEASENOUPDATE=YES
NOTE: If it looks like you're going to go this route, pl
Re: sysinstall install.cfg
On Thu, Nov 11, 2010 at 10:34 AM, Ross wrote: > vgc> I do this twice before the installCommit and both scripts run and load > the > vgc> resulting configs successfully. I also run another script after the > vgc> InstallComit...it fails citing the script could not be found. In > vgc> troubleshooting, I found that sysinstall is removing /stand and doing > other > vgc> stuff to / and /var. So, I know why the script cannot be found...because > vgc> sysinstall is removing it. > > sysinstall basically does a chroot into the newly installed root after > doing the installcommit, and then remounts the installation source as > /dist (not quite true, you can mount other sources at this time, but > always to /dist). > > After the installcommit, you basically are now at a normal freebsd > installation (ie: /usr/bin and the like are available). You lose > access to your original mfsroot distribution at this point. Thank you, Ross. Your explanation of what was happening lead me to combine the 2nd of the 2 scripts prior to the installCommit and the 3rd script that I was running after the installCommit. The result of the code in the scripts plus the lines in the install.cfg were echoed out to a file and subsequently loaded via loadConfig. This produced the desired result. -- 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: sysinstall install.cfg
vgc> I do this twice before the installCommit and both scripts run and load the vgc> resulting configs successfully. I also run another script after the vgc> InstallComit...it fails citing the script could not be found. In vgc> troubleshooting, I found that sysinstall is removing /stand and doing other vgc> stuff to / and /var. So, I know why the script cannot be found...because vgc> sysinstall is removing it. sysinstall basically does a chroot into the newly installed root after doing the installcommit, and then remounts the installation source as /dist (not quite true, you can mount other sources at this time, but always to /dist). After the installcommit, you basically are now at a normal freebsd installation (ie: /usr/bin and the like are available). You lose access to your original mfsroot distribution at this point. R. -- ___ 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: sysinstall install.cfg
On 11 November 2010 12:12, wrote: > Hi all, > > Hoping that someone might be able to help me here. I dynamically generate > much of the install.cfg by running scripts that send output to files that > are, in turn, loaded into install.cfg utilizing loadConfig. The scripts that > are run are placed into the mfsroot in /stand and /. They send the output to > /a. > > I do this twice before the installCommit and both scripts run and load the > resulting configs successfully. I also run another script after the > InstallComit...it fails citing the script could not be found. In > troubleshooting, I found that sysinstall is removing /stand and doing other > stuff to / and /var. So, I know why the script cannot be found...because > sysinstall is removing it. > > The question I have then is how can I get around this? I attempted putting > the script above the installCommit, but the functions being performed here > require that the base system already be in place (I'm adding packages). It > seems that I have little choice, but to have this after the installCommit. > Unfortunately, sysinstall wipes it out. > > Any guidance is greatly appreciated. > ___ > 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" > have a look at the pc-bsd installer as it will let you do far more advanced installations, and probably easier. Its been commited to head as it looks like it going to become the standard bsd installer in the future. ___ 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"
sysinstall install.cfg
Hi all, Hoping that someone might be able to help me here. I dynamically generate much of the install.cfg by running scripts that send output to files that are, in turn, loaded into install.cfg utilizing loadConfig. The scripts that are run are placed into the mfsroot in /stand and /. They send the output to /a. I do this twice before the installCommit and both scripts run and load the resulting configs successfully. I also run another script after the InstallComit...it fails citing the script could not be found. In troubleshooting, I found that sysinstall is removing /stand and doing other stuff to / and /var. So, I know why the script cannot be found...because sysinstall is removing it. The question I have then is how can I get around this? I attempted putting the script above the installCommit, but the functions being performed here require that the base system already be in place (I'm adding packages). It seems that I have little choice, but to have this after the installCommit. Unfortunately, sysinstall wipes it out. Any guidance is greatly appreciated. ___ 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: Specifying "Install Root" on non interactive sysinstall
On Tue, 2010-11-09 at 10:18 +0100, Ramblewski David wrote: > Hi, > > I'm looking for a solution to jumpstart FreeBSD on an non interactive way. > The solution provided by the Handbook recommend to use sysinstall program, > that's what I'm trying to do. -sysinstall@ would have been a better choice for this question. Cross-posting my reply. > The servers are using PXE boot to mount an mfsbsd filesystem, everything > works as expected until now. > I manually create the slice, labels and mount the partitions on "/mnt" > partition. You might just want to try adding "diskInteractive=YES" to your install.cfg file. That way, you don't have to manually partition/slice/label your disk _before_ you load the config. By setting diskInteractive, when installCommit is called, it will: a. if `disk' is not set (e.g. disk=da0) throw up a menu to select which disk you want to partition b. throw you into the FDISK partition editor c. throw you into diskabel e. ask which boot code you want to install (if any) to the MBR Just a suggestion. > Then I manually launch "sysinstall loadConfig" to install packages classes > but I didn't find the way to precise an "Install Root" for /mnt whereas it > works if I did it on a interactive way using the options menu. Put this into your install.cfg: # Required by distExtractAll (called indirectly by installCommit): installRoot=/mnt > Does anyone know how to solve this issue? > > Here is my install.cfg file: > -- > # Turn on extra debugging. > debug=YES > > # Ok, this ought to turn off ALL prompting, don't complain to me that you > # lost a machine because you netbooted it on the same subnet as this > # box > nonInteractive=YES > noWarn=YES > tryDHCP=YES > > # My host specific data > hostname=polbsd > domainname=priv.atos.fr > > > # Which installation device to use > nfs=10.28.222.1:/opt/local/jumpstart/tftpboot/BSD/NFS > netDev=bge0 > mediaSetNFS > > > > # Select which distributions we want. > dists= base SMP manpages ports Hmmm. Must be an older release. The SMP kernel has gone missing in FreeBSD-8.x. > distSetCustom > > > # OK, everything is set. Do it! > installCommit > > shutdown > -- > > > Thanks, > > David -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> FUN STUFF <- -BEGIN GEEK CODE BLOCK- Version 3.1 GAT/CS d(+) s: a- C++() UB$ P++() L++() !E--- W++ N? o? K- w O M+ V- PS+ PE Y+ PGP- t(+) 5? X+(++) R>++ tv(+) b+(++) DI+(++) D(+) G+>++ e>+ h r>++ y+ --END GEEK CODE BLOCK-- http://www.geekcode.com/ -> END TRANSMISSION <- ___ 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"
Specifying "Install Root" on non interactive sysinstall
Hi, I'm looking for a solution to jumpstart FreeBSD on an non interactive way. The solution provided by the Handbook recommend to use sysinstall program, that's what I'm trying to do. The servers are using PXE boot to mount an mfsbsd filesystem, everything works as expected until now. I manually create the slice, labels and mount the partitions on "/mnt" partition. Then I manually launch "sysinstall loadConfig" to install packages classes but I didn't find the way to precise an "Install Root" for /mnt whereas it works if I did it on a interactive way using the options menu. Does anyone know how to solve this issue? Here is my install.cfg file: -- # Turn on extra debugging. debug=YES # Ok, this ought to turn off ALL prompting, don't complain to me that you # lost a machine because you netbooted it on the same subnet as this # box nonInteractive=YES noWarn=YES tryDHCP=YES # My host specific data hostname=polbsd domainname=priv.atos.fr # Which installation device to use nfs=10.28.222.1:/opt/local/jumpstart/tftpboot/BSD/NFS netDev=bge0 mediaSetNFS # Select which distributions we want. dists= base SMP manpages ports distSetCustom # OK, everything is set. Do it! installCommit shutdown -- Thanks, David Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? du groupe Atos Origin ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___ 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: sysinstall(8) && bsdlabel a new disk
In freebsd-questions Digest, Vol 335, Issue 3, Message: 2 On Tue, 2 Nov 2010 07:04:08 +0100 Matthias Apitz wrote: > El día Monday, November 01, 2010 a las 10:03:58PM -0700, > per...@pluto.rain.com escribió: > > > Devin Teske wrote: > > > > > sysinstall probes hardware when it starts. Therefore, after making > > > changes (specifically after writing) to the disk in the FDISK > > > partition editor, you need to Ctrl-C and Abort-out and relaunch > > > sysinstall so that it probes the new disk devices (ad4s1, ad4s2, > > > etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, > > > etc.) to the slice (aka partition). > > > > > > This has been an age-old problem (hmmm, perhaps get could some mad > > > karma for fixing it). > > > > At least in 8.1, there is a sysinstall operation somewhere to > > re-probe devices, presumably to cover exactly this sort of > > situation. Does it not work? Options menu: Rescan Devices works to pick up devices like a USB disk or memstick that you may even have booted off but sysinstall then fails to find, as it does with some older kit and/or slow devices (here memsticks on USB1 ports). > My situation was in 9-CURRENT. When running sysinstall(8) as init from a CD/DVD/memstick boot, you can do mostly what you like to the disk/s in terms of slicing - fdisk and like boot0cfg under the hood - and partitioning of slices - bsdlabel under the hood, or rather sysinstall's version of those utilities; it still uses libdisk(3) rather than libgeom(3), at 8-STABLE anyway. When running sysinstall from a booted system (where you could exit after any committed steps and restart it, as mentioned above) you need to have previously set sysctl kern.geom.debugflags=16 (the 'foot-shooting' bit) if you want to be able to write to sector 0 (the boot sector including MBR) or to any non-boot slice - even unmounted - on the boot disk. Sysinstall doesn't let you know when you've failed to modify the disk, sadly, hence mysterious problems such as the above. It's fairly obvious when it fails to newfs some partitions you think you've nicely set up :) Same goes for sade(8). Neither manpage mentions kern.geom.debugflags, but boot0cfg(8) does, and points to the fuller description in geom(4). I haven't checked up on new work on sysinstall on -CURRENT for a while, but suspect that you'll still have to set that flag to write to any disk that's in use. Don't forget to set it back to 0 later! cheers, Ian___ 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: sysinstall(8) && bsdlabel a new disk
El día Monday, November 01, 2010 a las 10:03:58PM -0700, per...@pluto.rain.com escribió: > Devin Teske wrote: > > > sysinstall probes hardware when it starts. Therefore, after making > > changes (specifically after writing) to the disk in the FDISK > > partition editor, you need to Ctrl-C and Abort-out and relaunch > > sysinstall so that it probes the new disk devices (ad4s1, ad4s2, > > etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, > > etc.) to the slice (aka partition). > > > > This has been an age-old problem (hmmm, perhaps get could some mad > > karma for fixing it). > > At least in 8.1, there is a sysinstall operation somewhere to > re-probe devices, presumably to cover exactly this sort of > situation. Does it not work? My situation was in 9-CURRENT. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ 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: sysinstall(8) && bsdlabel a new disk
Devin Teske wrote: > sysinstall probes hardware when it starts. Therefore, after making > changes (specifically after writing) to the disk in the FDISK > partition editor, you need to Ctrl-C and Abort-out and relaunch > sysinstall so that it probes the new disk devices (ad4s1, ad4s2, > etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, > etc.) to the slice (aka partition). > > This has been an age-old problem (hmmm, perhaps get could some mad > karma for fixing it). At least in 8.1, there is a sysinstall operation somewhere to re-probe devices, presumably to cover exactly this sort of situation. Does it not work? ___ 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: sysinstall(8) && bsdlabel a new disk
On Mon, 2010-11-01 at 23:48 +, Bruce Cran wrote: > On Mon, 01 Nov 2010 09:04:15 -0700 > Devin Teske wrote: > > > I'll be the first to admit that sysinstall(8) could be a little easier > > to use in the userland. It should be noted that sade(8) (System > > Administrator's Disk Editor) is no different -- sade, at this point at > > least, is nothing more than the `Partition' and `Label' menus ripped > > straight from sysinstall(8)'s `Custom' menu (with some minor other > > differences, like the fact that the Ctrl-C menu doesn't work whereas > > it does in sysinstall(8) -- really ought to file a PR on that one). > > There's a new version of sade being worked on by ae@ in svn /user/ae > that fixes lots of the problems. Excellent! I'll have to check it out. (should we then save our PR's for ae and neglect any problems in sade? I wonder what `ae' stands for, "alas, edamame?!", I kid). > With pc-sysinstall getting all the > attention I doubt sysinstall will have any more work done on it. I'm _very_ pleased to see from... http://www.youtube.com/watch?v=Z0yOuDelXUU ...that pc-sysinstall will support scripted installation using a syntax similar to sysinstall's own install.cfg. I thought I was going to have to lose sleep over this. -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- ___ 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: sysinstall(8) && bsdlabel a new disk
On Mon, 01 Nov 2010 09:04:15 -0700 Devin Teske wrote: > I'll be the first to admit that sysinstall(8) could be a little easier > to use in the userland. It should be noted that sade(8) (System > Administrator's Disk Editor) is no different -- sade, at this point at > least, is nothing more than the `Partition' and `Label' menus ripped > straight from sysinstall(8)'s `Custom' menu (with some minor other > differences, like the fact that the Ctrl-C menu doesn't work whereas > it does in sysinstall(8) -- really ought to file a PR on that one). There's a new version of sade being worked on by ae@ in svn /user/ae that fixes lots of the problems. With pc-sysinstall getting all the attention I doubt sysinstall will have any more work done on it. -- Bruce Cran ___ 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: sysinstall(8) && bsdlabel a new disk
On Sun, 2010-10-31 at 21:02 +0100, Matthias Apitz wrote: > Hello, > > I installed a 9-CURRENT from an USB key to a hard disk of a laptop and > encountered a strange problem: I booted the USB key to normal > multiuser mode and wanted to wipe out the Windows on the disk, create > one slice ad4s1 and partitions in it for /, /usr, /var, ... > > I thought the simplest way would be just run sysinstall(8) and use the > FDISK and BSDLABEL from the post-install dialog. FDISK went fine and in > the BSDLABEL dialog I just used 'A' (auto defaults). On 'W' (write to > disk) the sysinstall(8) complained about 'unable to open /dev/ad4s1a sysinstall probes hardware when it starts. Therefore, after making changes (specifically after writing) to the disk in the FDISK partition editor, you need to Ctrl-C and Abort-out and relaunch sysinstall so that it probes the new disk devices (ad4s1, ad4s2, etc.) before you can start adding BSD disklabels (ad4s1a, ad4s1b, etc.) to the slice (aka partition). This has been an age-old problem (hmmm, perhaps get could some mad karma for fixing it). I imagine that sade has this problem too. Though, what annoys me about sade is that the Ctrl-C menu doesn't work -- the "Restart" option does nothing and though "Continue" works, I'm seething over the lack of an "Abort" option (hmmm, perhaps should file a PR on that one). > and > so on for all the created partitions a...f. And also in the dev fs > there were no entries created for /dev/ad4s1[a-f]. They apeared after a > reboot of the system from the USB key. Reboot should not be required. Just exit sysinstall(8) and go back into it. I've made it a habit to (when using sysinstall(8) as a userland utility to format disks): 1. Launch sysinstall(8) (as root) 2. Main Menu 3. Custom 4. Partition 5. (if more than one disk is present in the system you'll be prompted to select the disk... use spacebar to select disk, then TAB over to OK and hit ENTER) 6. partition the disk in whatever manner required 7. Press `W' to write out the changes 8. (select which boot manager or None) 9. Press Ctrl-C after partition table is successfully written 10. Select `Abort' and hit ENTER then 1. Relaunch sysinstall(8) (as root) 2. Main Menu 3. Custom 4. Partition 5. (if more than one disk is present in the system, use spacebar to select disk, then TAB over to OK and hit ENTER) NOTE: This is required to select which disk to operate on within the disklabel editor 6. Press `Q' to quit-out of the FDISK partition editor (this time, we don't want to make any changes, we just needed to indicate that this is the disk that we're going to operate on within the disklabel editor) 7. (select which boot manager or None) NOTE: This time around, since we're not going to write the partition table again, it really doesn't matter what you select here NOTE: you're now back at the custom menu from step 3/4. 8. Label 9. Now use the FreeBSD Disklabel Editor to allocate FreeBSD partitions from the BIOS partition ad0s1 (or whatever your partition was named) 10. When finished, press `W' to write out changes, perform newfs actions, and mount the devices as necessary > > How this is supposed to work using sysinstall(8) > or should one use only bsdlabel(8) directly in such a case? > I'll be the first to admit that sysinstall(8) could be a little easier to use in the userland. It should be noted that sade(8) (System Administrator's Disk Editor) is no different -- sade, at this point at least, is nothing more than the `Partition' and `Label' menus ripped straight from sysinstall(8)'s `Custom' menu (with some minor other differences, like the fact that the Ctrl-C menu doesn't work whereas it does in sysinstall(8) -- really ought to file a PR on that one). > Thanks > > matthias -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- ___ 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: sysinstall(8) && bsdlabel a new disk
On 01.11.10 01:03, Bruce Cran wrote: > On Sunday 31 October 2010 20:02:58 Matthias Apitz wrote: > > sysinstall isn't really intended for post-install use: you should probably > learn how to use gpart instead - e.g. > Maybe sade (sysadmins disk editor) would help too... looks like sysinstall's disk part.. Beat ___ 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: sysinstall(8) && bsdlabel a new disk
On Monday 01 November 2010 09:06:53 Matthias Apitz wrote: > I'm unsure about the 3rd command (gpart create -s bsd ad4s1), should it > use 'ad4' as you say above, or 'ad4s1' as in the August's post? Since you're creating the bsd scheme inside the freebsd container, you would use ad4s1. -- Bruce Cran ___ 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: sysinstall(8) && bsdlabel a new disk
El día Monday, November 01, 2010 a las 12:03:54AM +, Bruce Cran escribió: > On Sunday 31 October 2010 20:02:58 Matthias Apitz wrote: > > > How this is supposed to work using sysinstall(8) > > or should one use only bsdlabel(8) directly in such a case? > > sysinstall isn't really intended for post-install use: you should probably > learn how to use gpart instead - e.g. > > gpart create -s mbr /dev/disk > gpart add -t freebsd /dev/disk > gpart create -s bsd /dev/disk > gpart add -t freebsd-ufs /dev/disks1 > > newfs /dev/disks1a Combining the above and your posting in http://lists.freebsd.org/pipermail/freebsd-fs/2010-August/009176.html for my case I should have done: # gpart create -s mbr ad4 # Init the disk with an MBR # gpart add -t freebsd ad4# Create a BSD container # gpart create -s bsd ad4s1 # Init with a BSD scheme # gpart add -t freebsd-ufs -s 1G ad4s1 # 1GB for / # gpart add -t freebsd-swap -s 2G ad4s1 # 2GB for swap # gpart add -t freebsd-ufs -s 2G ad4s1 # 2GB for /var # gpart add -t freebsd-ufs -s 1G ad4s1 # 1GB for /tmp # gpart add -t freebsd-ufs ad4s1 # all rest for /usr Right? I'm unsure about the 3rd command (gpart create -s bsd ad4s1), should it use 'ad4' as you say above, or 'ad4s1' as in the August's post? In any case, next time whene I have an empty disk to initialize, I will play around with this. Thanks again matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ 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: sysinstall(8) && bsdlabel a new disk
On Monday 01 November 2010 06:09:51 Matthias Apitz wrote: > Thanks for the reply. Is there any document explaining this in more > detail as the man page of gpart(8). The FreeBSD Handbook in chaptar 18.3 > points still to sysinstall(8) and bsdlabel(8)... The documentation for gpart is still rather poor, and I'm not aware of any official documentation. I wrote a more detailed post in http://lists.freebsd.org/pipermail/freebsd-fs/2010-August/009176.html which explains the commands. -- Bruce Cran ___ 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: sysinstall(8) && bsdlabel a new disk
El día Monday, November 01, 2010 a las 12:03:54AM +, Bruce Cran escribió: > On Sunday 31 October 2010 20:02:58 Matthias Apitz wrote: > > > How this is supposed to work using sysinstall(8) > > or should one use only bsdlabel(8) directly in such a case? > > sysinstall isn't really intended for post-install use: you should probably > learn how to use gpart instead - e.g. > > gpart create -s mbr /dev/disk > gpart add -t freebsd /dev/disk > gpart create -s bsd /dev/disk > gpart add -t freebsd-ufs /dev/disks1 > > newfs /dev/disks1a Bruce, Thanks for the reply. Is there any document explaining this in more detail as the man page of gpart(8). The FreeBSD Handbook in chaptar 18.3 points still to sysinstall(8) and bsdlabel(8)... Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ 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: sysinstall(8) && bsdlabel a new disk
On Sunday 31 October 2010 20:02:58 Matthias Apitz wrote: > How this is supposed to work using sysinstall(8) > or should one use only bsdlabel(8) directly in such a case? sysinstall isn't really intended for post-install use: you should probably learn how to use gpart instead - e.g. gpart create -s mbr /dev/disk gpart add -t freebsd /dev/disk gpart create -s bsd /dev/disk gpart add -t freebsd-ufs /dev/disks1 newfs /dev/disks1a -- Bruce Cran ___ 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"
sysinstall(8) && bsdlabel a new disk
Hello, I installed a 9-CURRENT from an USB key to a hard disk of a laptop and encountered a strange problem: I booted the USB key to normal multiuser mode and wanted to wipe out the Windows on the disk, create one slice ad4s1 and partitions in it for /, /usr, /var, ... I thought the simplest way would be just run sysinstall(8) and use the FDISK and BSDLABEL from the post-install dialog. FDISK went fine and in the BSDLABEL dialog I just used 'A' (auto defaults). On 'W' (write to disk) the sysinstall(8) complained about 'unable to open /dev/ad4s1a and so on for all the created partitions a...f. And also in the dev fs there were no entries created for /dev/ad4s1[a-f]. They apeared after a reboot of the system from the USB key. How this is supposed to work using sysinstall(8) or should one use only bsdlabel(8) directly in such a case? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ ___ 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"
sysinstall list not part of main mailing-list search engine
It appears that our beloved -sysinstall@ mailing-list does not appear on the main search page where one can search the archives. http://www.freebsd.org/search/search.html#mailinglists Is anyone on this list capable of getting it added? -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> FUN STUFF <- -BEGIN GEEK CODE BLOCK- Version 3.1 GAT/CS d(+) s: a- C++() UB$ P++() L++() !E--- W++ N? o? K- w O M+ V- PS+ PE Y+ PGP- t(+) 5? X+(++) R>++ tv(+) b+(++) DI+(++) D(+) G+>++ e>+ h r>++ y+ --END GEEK CODE BLOCK-- http://www.geekcode.com/ -> END TRANSMISSION <- ___ 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"
partitioning a gmirror (was Re: sysinstall vs gmirror)
binE6c8fkIE6U.bin Description: Binary data ___ 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: sysinstall with Fixit option and RootOnZFS/GPTZFSBoot caused kernel panic on Vmware machine!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/09/2010, at 7:29 PM, Phan Quoc Hien wrote: > Hi everyone! > > I followed tut at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ to install > FreeBSD Root on ZFS using GPT on my VMWARE virtual machine. > When I go to step "Install FreeBSD to zroot" kernel-panic appeared! It sounds like you are either low on ram, or are using i386. Look at http://wiki.freebsd.org/ZFSTuningGuide and follow the steps here in the loader prompt on the live system, and also add the same options to your loader.conf when you install the system. > My virtual machine detail: > RAM: 512MB HDD: 10GB vmware workstation: 7.1.0 build-261024 with FreeBSD > 8.1-REL! > See more detail about panic on image attached file. > Please let me know how to solve this problem. > Best regards, > Mr.Hien > > Hope this helps you. I think buwping the amount of ram in your VM wouldnt hurt either, ZFS really needs 1GB minimum, 2GB or more is preferred iirc. > > > -- > Mr.Hien > E-mail: phanquoch...@gmail.com > Website: www.mrhien.info > ___ > 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" William Brown pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iQIcBAEBAgAGBQJMmN1FAAoJEHF16AnLoz6JYiMP/3xU6a3pd90kEsWIOgaWfQZ5 ff0tCYdMoMTmIZ9zgB7u7/YA7kIEp4o7zM8MbYPRt8OcC+9oWQBjbCvVeKXLEOil 6faRrYR3CxBSa1CIUxTsfPS3OR3rOB8GlTMJObW/UrOPonVgpyD6RMW/J3wMbme9 pN0V2xOSwOv9rgdFWwHgAOT4eBpzmFeOAbLERFMcv3sUm2l1k56IUpgEDQNoHVPY wp8Cxsl8QClP5bTpl2iSXvt0krCvo16HA64G4I1Bm6FSAY/aP45L5zouABHyHyIT RCZjTzCaaWHHXvwErAdQfx6oBFuyAxzwgb1ZRdYMDoFHs1swJd3D0pWIYcjQ9ILz 3AR1YFY5t1SE+kP03Fssoz/HNpq2lO3IgjJsg/T8bsMEbb2/6zJlCKF5wAsMZHdY 1kj+75IsZ+phbzaPrpdL8kjfTWBP1De3WWH7sN85wGAw2c1mQCFLg9bsC2Ahxe1V S/kRWwKDoJPvBaEEdo5LM7CLfoneXOR3taa3mqLvgkWAwyTG0iEtwwxhxMMFSmpp InMWYplq/zu4au27+ujW+f6Mj3GhpSzaMNAfGkGdpsn4D4muBWgrLt04nSxuvjX6 K3ZoGAMlnH9rOLwZLvu2uaxKGZnyf/TYndgPQtpNm3iq7liXoSYnNl3B4NeNjI7j l5wz40a62K6b2J/G/cIa =6/hT -END PGP SIGNATURE- ___ 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"
sysinstall with Fixit option and RootOnZFS/GPTZFSBoot caused kernel panic on Vmware machine!
Hi everyone! I followed tut at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/ to install FreeBSD Root on ZFS using GPT on my VMWARE virtual machine. When I go to step "Install FreeBSD to zroot" kernel-panic appeared! My virtual machine detail: RAM: 512MB HDD: 10GB vmware workstation: 7.1.0 build-261024 with FreeBSD 8.1-REL! See more detail about panic on image attached file. Please let me know how to solve this problem. Best regards, Mr.Hien -- Mr.Hien E-mail: phanquoch...@gmail.com Website: www.mrhien.info ___ 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: sysinstall vs gmirror
On Sat, Sep 18, 2010 at 1:20 AM, wrote: > Adam Vande More wrote: [SNIP] > The question is, how do I go about partitioning gm0 from Fixit? > I've seen nothing so far that describes how to go about creating > multiple partitions on a gmirror (or on anything else, for that > matter) without either using sysinstall or having to understand > gpart. I've used something like this from the Fixit console (using /dev/ad0 as an example): Fixit# kldload /dist/boot/kernel/geom_mirror.ko Fixit# gmirror -v -b round-robin gm0 /dev/ad0 Fixit# fdisk -v -B -I /dev/mirror/gm0 Fixit# bsdlabel -w -B /dev/mirror/gm0s1 Partition with: # bsdlabel -e /dev/mirror/gm0s1 Create a UFS file system (with Soft Updates): Fixit# newfs -U /dev/mirror/gm0s1a Mount the newly created file system: Fixit# mount /dev/mirror/gm0s1a /mnt ...then follow one of the procedures for doing a "manual" install from fixit, e.g. Fixit# cd /dist/8.1-* Fixit# export DESTDIR=/mnt Fixit# for dir in base catpages dict doc games info lib32 manpages ports; \ do (cd $dir ; ./install.sh) ; done Fixit# cd src ; ./install.sh all Fixit# cd ../kernels ; ./install.sh generic Fixit# cd /mnt/boot ; cp -Rlp GENERIC/* /mnt/boot/kernel/ [taken from http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror] > OK, given the system's age I will presume that it is not, thus > (I suppose) no reason to deal with gpart. I've used GPT partitioning on all of my machines, ranging from a circa-2000 Toshiba Pentium 3 junker to a new i7 Quad Core beast. No problem so far, and it is a lot more logical (IMHO) than the fdisk/bsdlabel method. Also, the "manual" installation method demonstrated above hasn't failed me yet. Having stated all of this, I will say that I spent time reading the handbook, quite a few man pages, and a a wiki article here and there -- and I still feel only slightly more comfortable than I did after my first successful attempt! It is starting to "come together" for me now, finally :) Well, I hope this helps you get unstuck... Good Luck! -Brandon ___ 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: sysinstall vs gmirror
Adam Vande More wrote: > On Fri, Sep 17, 2010 at 11:09 PM, wrote: > > > Next fdisk/gpart accordingly (don't forget to make it bootable). > > > > This is where I get stuck. I've partitioned the physical drives > > using sysinstall, but how do I go about partitioning gm0? > > Your problem is that you are still using sysinstall. No, I'm not. > You can't for your purposes(this was pointed out earlier). > Fixit only! The question is, how do I go about partitioning gm0 from Fixit? I've seen nothing so far that describes how to go about creating multiple partitions on a gmirror (or on anything else, for that matter) without either using sysinstall or having to understand gpart. > Notice in the example it creates some basic filesystems/diretories using gpart and ZFS > ... > > > If your setup if GPT compatible, I recommend using it. > > > > How do I find out whether this setup is GPT compatible? > > Hardware(BIOS) dependent. OK, given the system's age I will presume that it is not, thus (I suppose) no reason to deal with gpart. ___ 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: sysinstall vs gmirror
On Fri, Sep 17, 2010 at 11:09 PM, wrote: > > Next fdisk/gpart accordingly (don't forget to make it bootable). > > This is where I get stuck. I've partitioned the physical drives > using sysinstall, but how do I go about partitioning gm0? > Your problem is that you are still using sysinstall. You can't for your purposes(this was pointed out earlier). Fixit only! Notice in the example it creates some basic filesystems/diretories and then chroot's and extracts the dist's manually. You must do the same after you do the gmirror/gjournal setup to your liking and have created the appropriate fs's and mounted them. > > > If your setup if GPT compatible, I recommend using it. > > How do I find out whether this setup is GPT compatible? > Hardware(BIOS) dependent. > For starters there seem to be at least 6 kernel options, of > which I guess I may need 3: GEOM_PART_BSD, GEOM_PART_GPT, and > GEOM_PART_MBR; there's apparently no "edit" function; and one > has to puzzle out what is meant by a "protective MBR" as part > of understanding how to make a GPT partition bootable. > Yeah, there is no label editor or resize functionality, yet anyway. You don't need to worry about any of those kernel options yet, just get it working by loading from loader.conf. You can customize your kernel later. I think the "protective MBR" part relates to GPT/MBR hybrid style which is not what I think you should do, but maybe it works haven't tried it. You'll use gpart to create(and label) at least 3 parttitions, the boot, swap, and freebsd-ufs filesystem. You'll have to create more if you want seperate /usr /var /tmp etc. Once the fs's are created and mounted, extract, edit the /boot/loader.conf in the chroot to load gmirror, gjournal, and anything else you need, Note about the bootloader part, use gpart to install the boot code to the boot partition you create, I don't think you'll need to do anything special other than that. This example may also be helpful because it deals with GPT/UFS manual install, but doesn't use any other geom classes. http://wiki.freebsd.org/RootOnZFS/UFSBoot -- Adam Vande More ___ 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: sysinstall vs gmirror
Adam Vande More wrote: > On Sun, Sep 12, 2010 at 11:14 PM, wrote: > > The part I don't know how to do is partitioning gm0 by hand. > > (I suppose it would require some sort of arcane incantations > > involving bsdlabel.) For all its limitations, sysinstall > > seems at least to know how to translate a reasonably human- > > readable representation of the desired slice and partition > > layout into the necessary fdisk and bsdlabel commands. > > I don't know of any exact howto, but the general principles are > laid out here: > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I finally had time to (try to) read through that, and I'm having trouble locating a description of how to partition a gmirror. (The page seems oriented almost entirely to ZFS and gpart, the only mention of gmirror being in connection with swap.) I'm quite sure I don't want to attempt ZFS on a machine with only 512MB, and I'm not at all sure that a BIOS of this age would understand gpart. > It shows how to load geom modules from usb stick I had already figured out that part :) Fixit# ln -s /dist/boot/kernel /boot Fixit# gmirror load which is all I think I need until I get the mirror partitioned. > Next fdisk/gpart accordingly (don't forget to make it bootable). This is where I get stuck. I've partitioned the physical drives using sysinstall, but how do I go about partitioning gm0? > If your setup if GPT compatible, I recommend using it. How do I find out whether this setup is GPT compatible? > IMO, it's significantly more straightforward than the old > mbr style. I sure did not get that impression from reading gpart(8) :( For starters there seem to be at least 6 kernel options, of which I guess I may need 3: GEOM_PART_BSD, GEOM_PART_GPT, and GEOM_PART_MBR; there's apparently no "edit" function; and one has to puzzle out what is meant by a "protective MBR" as part of understanding how to make a GPT partition bootable. ___ 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: sysinstall vs gmirror
On Sun, Sep 12, 2010 at 11:14 PM, wrote: > The part I don't know how to do is partitioning gm0 by hand. > (I suppose it would require some sort of arcane incantations > involving bsdlabel.) For all its limitations, sysinstall > seems at least to know how to translate a reasonably human- > readable representation of the desired slice and partition > layout into the necessary fdisk and bsdlabel commands. > I don't know of any exact howto, but the general principles are laid out here: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror It shows how to load geom modules from usb stick, once they are loaded you can then setup geom, Next fdisk/gpart accordingly(don't forget to make it bootable). If your setup if GPT compatible, I recommend using it. IMO, it's significantly more straightforward than the old mbr style. once you've got your partitions setup the way you want, create your filesystems and use the instrustions on the page to extract the distrobution on to them. Obviously they need to be mounted for this to occur, so adapt the example to your own use. Note, I've never tried to boot from a gjournaled geom, but I think it will work. -- Adam Vande More ___ 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: sysinstall vs gmirror
Matthew Seaman wrote: > On 12/09/2010 05:09:04, per...@pluto.rain.com wrote: > > How do I get sysinstall to recognize a gmirror? > > ... > I don't think sysinstall will do what you want. It certainly has been less than totally cooperative so far :( > However, what is your ultimate goal? > To install a system with a gmirror root drive? No, to install a system with each of /, /usr, and /var mirrored and journalled, with each journal kept in the same (mirrored) partition as its FS -- diagram below. IIUC, to put the journal in the same partition with the FS I have to create the journal while the FS is empty, hence before installing. (This is all UFS -- 512MB seems a bit small for ZFS.) The plan after partitioning the mirror is to create the journals, then install onto the journalled FS's, and finally to insert the second half of the mirror after everything else is up and running. > ... you can boot into the Fixit system, set up mirroring etc. and > then work through the rest of the installation process by hand. > The install sets are just split up tarballs and it's pretty easy > to extract a copy of a system from them. The part I don't know how to do is partitioning gm0 by hand. (I suppose it would require some sort of arcane incantations involving bsdlabel.) For all its limitations, sysinstall seems at least to know how to translate a reasonably human- readable representation of the desired slice and partition layout into the necessary fdisk and bsdlabel commands. Someone suggested using the PC-BSD installer, which knows how to do stuff like this, but when I asked how to do that from a memstick (rather than from a CD or DVD) I didn't get an answer. ad0s2 FreeBSD ad2s2 FreeBSD ad0s2a <- gm0 -> ad2s2a | +-+ | v gm0 gm0a gm0a.journal [gjournal label gm0a gm0a] rootFS gm0d gm0d.journal [gjournal label gm0a gm0a] /var gm0e gm0e.journal [gjournal label gm0a gm0a] /usr There's more to it than this, but I think I know how to do the rest. The current sticking point is getting the mirror partitioned. ___ 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: sysinstall vs gmirror
On 12/09/2010 05:09:04, per...@pluto.rain.com wrote:
> How do I get sysinstall to recognize a gmirror?
>
> I've created the mirror -- which currently has only one provider --
> using Fixit#, followed by
>
> Fixit# ln -s /dist/boot/kernel /boot
> Fixit# gmirror load
>
> after which /dev/mirror/gm0{,a,b} exist. However, even after
> rescanning the disks, sysinstall doesn't include gm0 in its
> drive list. I also tried:
>
> Fixit# ( cd /dev && ln -s mirror/* . && ll gm* )
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0@ -> mirror/gm0
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0a@ -> mirror/gm0a
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0b@ -> mirror/gm0b
>
> in case sysinstall looks only in /dev itself and not in any
> subdirectories, and that didn't help. I even tried:
>
> Fixit# ( cd /dev && ln -s mirror/gm0 ar0 \
>&& for p in a b d e ; \
>do ln -s mirror/gm0$p ar0$p ; done && ll ar* )
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0@ -> mirror/gm0
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0a@ -> mirror/gm0a
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0b@ -> mirror/gm0b
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0d@ -> mirror/gm0d
> lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0e@ -> mirror/gm0e
>
> in case sysinstall looks only for names of known disk drivers,
> and that didn't help either.
I don't think sysinstall will do what you want.
However, what is your ultimate goal? To install a system with a gmirror
root drive? You can do that by installing direct to one of your drives
(ie ad0s1* or da0s1*) in the usual way and then converting the system
into a gmirror. The Onlamp article by Dru Lavigne is the best
referrence here:
http://onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html
Or else you can boot into the Fixit system, set up mirroring etc. and
then work through the rest of the installation process by hand. The
install sets are just split up tarballs and it's pretty easy to extract
a copy of a system from them.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
sysinstall vs gmirror
How do I get sysinstall to recognize a gmirror?
I've created the mirror -- which currently has only one provider --
using Fixit#, followed by
Fixit# ln -s /dist/boot/kernel /boot
Fixit# gmirror load
after which /dev/mirror/gm0{,a,b} exist. However, even after
rescanning the disks, sysinstall doesn't include gm0 in its
drive list. I also tried:
Fixit# ( cd /dev && ln -s mirror/* . && ll gm* )
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0@ -> mirror/gm0
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0a@ -> mirror/gm0a
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 gm0b@ -> mirror/gm0b
in case sysinstall looks only in /dev itself and not in any
subdirectories, and that didn't help. I even tried:
Fixit# ( cd /dev && ln -s mirror/gm0 ar0 \
&& for p in a b d e ; \
do ln -s mirror/gm0$p ar0$p ; done && ll ar* )
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0@ -> mirror/gm0
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0a@ -> mirror/gm0a
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0b@ -> mirror/gm0b
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0d@ -> mirror/gm0d
lrwxr-xr-x 1 root 0 10 Sep 6 10:48 ar0e@ -> mirror/gm0e
in case sysinstall looks only for names of known disk drivers,
and that didn't help either.
___
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: sysinstall fails when adding distributions
This has been fixed. Get a newer RC. -- randi On Fri, Jul 2, 2010 at 6:49 AM, Kristaps Kūlis wrote: > Hi, > On FreeBSD 8.1-RELEASE (i386) on IBM T43, sysinstall fails when trying to > add src distribution to already installed system (when starting to download > them from FTP). No network activity is observed. > coredump: http://www.ltn.lv/~kristapskulis/sysinstall.core > dmesg: http://www.ltn.lv/~kristapskulis/dmesg > > What I`m doing wrong and how to fix it ? > > Kristaps Kūlis > ___ > 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: Automated sysinstall install.cfg
On 2 July 2010 15:48, Ross wrote: > TT> is there a person who can help me to solve some problems with > TT> sysinstall and its install.cfg. > > TT> How can i manage that my mfsroot executes custom commands ? > > Before the "installCommit" command you generally only have access to > statically compiled commands (generally in the /stand directory) from > the mfsroot image used. > > -= example lines in install.cfg > # Sleep for 15 seconds to stabilize things. > command=/stand/sleep 15 > system > -= > > After the "installCommit" command, a chroot will have occurred to the > installation mount point, and you must then use your installed binaries > to do work. Specify full paths for everything and note that there are > other oddities since not all things are online/configured, so try and > keep it as simple as possible. > > -- > > ___ > 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" > Alternatively you could look at the pc-bsd installer. It will do advanced setups very easily, most of which are not possible with sysinstall (geom stuff, zfs etc). It will install standard freebsd, from a variety of formats. With a little tinkering you should be able to detach the installer program from the standard pcbsd image and use your own custom live os on a usb stick. You would then have a lot of power. ___ 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: Automated sysinstall install.cfg
TT> is there a person who can help me to solve some problems with TT> sysinstall and its install.cfg. TT> How can i manage that my mfsroot executes custom commands ? Before the "installCommit" command you generally only have access to statically compiled commands (generally in the /stand directory) from the mfsroot image used. -= example lines in install.cfg # Sleep for 15 seconds to stabilize things. command=/stand/sleep 15 system -= After the "installCommit" command, a chroot will have occurred to the installation mount point, and you must then use your installed binaries to do work. Specify full paths for everything and note that there are other oddities since not all things are online/configured, so try and keep it as simple as possible. -- ___ 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"
sysinstall fails when adding distributions
Hi, On FreeBSD 8.1-RELEASE (i386) on IBM T43, sysinstall fails when trying to add src distribution to already installed system (when starting to download them from FTP). No network activity is observed. coredump: http://www.ltn.lv/~kristapskulis/sysinstall.core dmesg: http://www.ltn.lv/~kristapskulis/dmesg What I`m doing wrong and how to fix it ? Kristaps Kūlis ___ 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"
Automated sysinstall install.cfg
Hello, is there a person who can help me to solve some problems with sysinstall and its install.cfg. How can i manage that my mfsroot executes custom commands ? -- Viele Grüsse aus Menden Thomas Toka Webmaster, Administrator, Webhoster, Gameserverhoster Serverman Webhosting Thomas Toka Droste-Hülshoff-Str. 11 58708 Menden Office: +49 (0) 2373 389140 (Festnetz) Mobil: +49 (0) 171 2772896 (D1) Fax: +49 (0) 2373 389142 (Festnetz) Internet: http://www.serverman.de Steuer-Nummer: DE240010739 Inhaber: Thomas Toka Serverstandort: Newcolo GmbH. Mainzer Landstrasse 351-353, 60326 Frankfurt am Main Die in dieser eMail enthaltenen Informationen sind vertraulich und können von rechtlicher Relevanz sein. Diese Mail ist ausschliesslich für den im Quelltext genannten Empfänger bestimmt und jeglicher Zugriff durch andere Personen ist nicht authorisiert. Falls Sie nicht der rechtmäßige Empfänger sind, ist jegliche Veröffentlichung, Vervielfältigung, Verteilung oder sonstige in diesem Zusammenhang stehende Handlung untersagt und unter Umständen strafbar. Sollten Sie diese Mail irrtümlich erhalten haben, leiten Sie diese bitte an webmas...@serverman.de weiter und löschen Ihre Kopien dieser Mail unverzüglich. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee and access to the e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you have received this e-mail in error please forward to webmas...@serverman.de and delete all local copies of this mail. ___ 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: Problem running fdisk via sysinstall
Excellent, I'm glad everything worked out. It may have been a leftover secondary GPT. From g_part_gpt.c: /* No primary? Check that there's a secondary. */ buf = g_read_data(cp, pp->mediasize - pp->sectorsize, pp->sectorsize, &error); This would seem to suggest that the secondary GPT is stored in the last block of the drive. Zeroing that block would probably have worked too. On Thu, Jun 24, 2010 at 12:41 PM, Mark Costlow wrote: > Nick, that worked! I zero'd the whole disk, then everything worked > like normal. > > Thanks, > > Mark > > On Wed, Jun 23, 2010 at 07:15:13PM -0600, Mark Costlow wrote: > > Since I don't have any other ideas yet, I'll give that a try. I'll > > let you know if it works tomorrow if it has finished by then :-) > > > > Mark > > > > On Wed, Jun 23, 2010 at 07:46:38PM -0400, Nicholas Mills wrote: > > >Mark, > > >I'm certainly no expert, but I think I can point you in the right > > >direction. The system appears to be attempting to read from a GPT > > >stored on the disk from when you used it on Linux. I'm not sure of > the > > >specifics, but I do know that some GPT info is stored near the end > of > > >the drive. The easy (but slow) solution would be to use dd to write > > >zeros to the entire drive (da1). > > >Hope this helps, > > >Nick > > >On Wed, Jun 23, 2010 at 7:28 PM, Mark Costlow <[1]che...@swcp.com> > > >wrote: > > > > > > I hope this question isn't too stupid. > > > I have a machine with a 3Ware RAID card, with 4 SATA drives > > > attached. > > > 2 drives are 250GB in a RAID1 volume, and act as the boot disk > with > > > a standard freebsd partiction map (/, /var, /usr, and swap on this > > > disk). > > > The other 2 drives are 1TB in a RAID1 volume, intended to be > mounted > > > as a separate data partition. At boot both volumes are > recognized: > > > Jun 22 18:38:51 ebi7 kernel: da0 at twa0 bus 0 target 0 lun 0 > > > Jun 22 18:38:51 ebi7 kernel: da0: > Fixed > > > Direct Access SCSI-5 device > > > Jun 22 18:38:51 ebi7 kernel: da0: 100.000MB/s transfers > > > Jun 22 18:38:51 ebi7 kernel: da0: 238408MB (488259584 512 byte > > > sectors: 255H 63S/T 30392C) > > > Jun 22 18:38:51 ebi7 kernel: da1 at twa0 bus 0 target 1 lun 0 > > > Jun 22 18:38:51 ebi7 kernel: da1: > Fixed > > > Direct Access SCSI-5 device > > > Jun 22 18:38:51 ebi7 kernel: da1: 100.000MB/s transfers > > > Jun 22 18:38:51 ebi7 kernel: da1: 953664MB (1953103872 512 byte > > > sectors: 255H 63S/T 121575C) > > > da0 is fine, and the system boots off of it with no problem. > > > When I try to add da1 to the system, I get the following: > > > * Run systinstall, Configure, Fdisk, select da1 > > > * Get the friendly warning about the large geometry, click "Yes" > > > * Hit "A" to use entire disk. Hit "W" to save, click "Yes", > > > select "None" for boot record. > > > * Fdisk says: "Wrote FDISK partition information out > successfully." > > > * Per handbook, get out of sysinstall and re-run it, then > > > try to Label. In the label editor, it knows nothing about > > > da1 (the device can be selected when going into the label > > > editor, but I can't create any partitions). > > > At the time when Fdisk says "Wrote FDISK partition information > out, > > > successfully." this gets logged to /var/log/messages: > > > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: corrupt or invalid GPT > > > detected. > > > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: GPT rejected -- may not be > > > recoverable. > > > I've tried several variations, including running the command-line > > > equivalents, but keep hitting this same error (fdisk thinks > > > everything > > > is good, but the GPT error is logged). I've also noticed that > > > /dev/da1 exists, but there is no /dev/da1s1 or /dev/da1s1e ... I'm > > > not sure when those should get created. > > > And the final possibly-relevant tidbit: these drives used to be > > > part of a different RAID on a linux system. They've been > > > re-initialized > &g
Re: Problem running fdisk via sysinstall
On Wed, Jun 23, 2010 at 11:17:50PM -0500, Adam Vande More wrote: > >On Wed, Jun 23, 2010 at 6:28 PM, Mark Costlow <[1]che...@swcp.com> >wrote: > > I hope this question isn't too stupid. > Any hints or clue-by-fours? > >What's the output of 'gpart show'? Zeroing the whole drive fixed the problem. Before that, "gpart show" displayed info for da0, but nothing at all for da1. Thanks, Mark -- Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 che...@swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 abq-strange.com -- Interesting photos taken in Albuquerque, NM Last post: Shoe Pole - 2009-07-07 20:18:22 ___ 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: Problem running fdisk via sysinstall
Nick, that worked! I zero'd the whole disk, then everything worked like normal. Thanks, Mark On Wed, Jun 23, 2010 at 07:15:13PM -0600, Mark Costlow wrote: > Since I don't have any other ideas yet, I'll give that a try. I'll > let you know if it works tomorrow if it has finished by then :-) > > Mark > > On Wed, Jun 23, 2010 at 07:46:38PM -0400, Nicholas Mills wrote: > >Mark, > >I'm certainly no expert, but I think I can point you in the right > >direction. The system appears to be attempting to read from a GPT > >stored on the disk from when you used it on Linux. I'm not sure of the > >specifics, but I do know that some GPT info is stored near the end of > >the drive. The easy (but slow) solution would be to use dd to write > >zeros to the entire drive (da1). > >Hope this helps, > >Nick > >On Wed, Jun 23, 2010 at 7:28 PM, Mark Costlow <[1]che...@swcp.com> > >wrote: > > > > I hope this question isn't too stupid. > > I have a machine with a 3Ware RAID card, with 4 SATA drives > > attached. > > 2 drives are 250GB in a RAID1 volume, and act as the boot disk with > > a standard freebsd partiction map (/, /var, /usr, and swap on this > > disk). > > The other 2 drives are 1TB in a RAID1 volume, intended to be mounted > > as a separate data partition. At boot both volumes are recognized: > > Jun 22 18:38:51 ebi7 kernel: da0 at twa0 bus 0 target 0 lun 0 > > Jun 22 18:38:51 ebi7 kernel: da0: Fixed > > Direct Access SCSI-5 device > > Jun 22 18:38:51 ebi7 kernel: da0: 100.000MB/s transfers > > Jun 22 18:38:51 ebi7 kernel: da0: 238408MB (488259584 512 byte > > sectors: 255H 63S/T 30392C) > > Jun 22 18:38:51 ebi7 kernel: da1 at twa0 bus 0 target 1 lun 0 > > Jun 22 18:38:51 ebi7 kernel: da1: Fixed > > Direct Access SCSI-5 device > > Jun 22 18:38:51 ebi7 kernel: da1: 100.000MB/s transfers > > Jun 22 18:38:51 ebi7 kernel: da1: 953664MB (1953103872 512 byte > > sectors: 255H 63S/T 121575C) > > da0 is fine, and the system boots off of it with no problem. > > When I try to add da1 to the system, I get the following: > > * Run systinstall, Configure, Fdisk, select da1 > > * Get the friendly warning about the large geometry, click "Yes" > > * Hit "A" to use entire disk. Hit "W" to save, click "Yes", > > select "None" for boot record. > > * Fdisk says: "Wrote FDISK partition information out successfully." > > * Per handbook, get out of sysinstall and re-run it, then > > try to Label. In the label editor, it knows nothing about > > da1 (the device can be selected when going into the label > > editor, but I can't create any partitions). > > At the time when Fdisk says "Wrote FDISK partition information out, > > successfully." this gets logged to /var/log/messages: > > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: corrupt or invalid GPT > > detected. > > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: GPT rejected -- may not be > > recoverable. > > I've tried several variations, including running the command-line > > equivalents, but keep hitting this same error (fdisk thinks > > everything > > is good, but the GPT error is logged). I've also noticed that > > /dev/da1 exists, but there is no /dev/da1s1 or /dev/da1s1e ... I'm > > not sure when those should get created. > > And the final possibly-relevant tidbit: these drives used to be > > part of a different RAID on a linux system. They've been > > re-initialized > > into the RAID card on this system, and I've zero'd the first 1k of > > the volume with dd, so I don't *think* that should be a factor. > > I've worked with about a dozen systems with the same hardware in > > the configuration outlined above and haven't seen this problem > > before. But I'm usually using fresh new disks so maybe it matters. > > I've googled this issue and found several people reporting similar > > symptoms over the years, but haven't found any posted solutions > > aside from telling people to read geom(8). > > Any hints or clue-by-fours? > > Mark > > -- > > Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 > > [2]che...@swcp.com | Web: [3
Re: Problem running fdisk via sysinstall
On Wed, Jun 23, 2010 at 6:28 PM, Mark Costlow wrote: > I hope this question isn't too stupid. > > Any hints or clue-by-fours? > > What's the output of 'gpart show'? -- Adam Vande More ___ 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: Problem running fdisk via sysinstall
Since I don't have any other ideas yet, I'll give that a try. I'll let you know if it works tomorrow if it has finished by then :-) Mark On Wed, Jun 23, 2010 at 07:46:38PM -0400, Nicholas Mills wrote: >Mark, >I'm certainly no expert, but I think I can point you in the right >direction. The system appears to be attempting to read from a GPT >stored on the disk from when you used it on Linux. I'm not sure of the >specifics, but I do know that some GPT info is stored near the end of >the drive. The easy (but slow) solution would be to use dd to write >zeros to the entire drive (da1). >Hope this helps, >Nick >On Wed, Jun 23, 2010 at 7:28 PM, Mark Costlow <[1]che...@swcp.com> >wrote: > > I hope this question isn't too stupid. > I have a machine with a 3Ware RAID card, with 4 SATA drives > attached. > 2 drives are 250GB in a RAID1 volume, and act as the boot disk with > a standard freebsd partiction map (/, /var, /usr, and swap on this > disk). > The other 2 drives are 1TB in a RAID1 volume, intended to be mounted > as a separate data partition. At boot both volumes are recognized: > Jun 22 18:38:51 ebi7 kernel: da0 at twa0 bus 0 target 0 lun 0 > Jun 22 18:38:51 ebi7 kernel: da0: Fixed > Direct Access SCSI-5 device > Jun 22 18:38:51 ebi7 kernel: da0: 100.000MB/s transfers > Jun 22 18:38:51 ebi7 kernel: da0: 238408MB (488259584 512 byte > sectors: 255H 63S/T 30392C) > Jun 22 18:38:51 ebi7 kernel: da1 at twa0 bus 0 target 1 lun 0 > Jun 22 18:38:51 ebi7 kernel: da1: Fixed > Direct Access SCSI-5 device > Jun 22 18:38:51 ebi7 kernel: da1: 100.000MB/s transfers > Jun 22 18:38:51 ebi7 kernel: da1: 953664MB (1953103872 512 byte > sectors: 255H 63S/T 121575C) > da0 is fine, and the system boots off of it with no problem. > When I try to add da1 to the system, I get the following: > * Run systinstall, Configure, Fdisk, select da1 > * Get the friendly warning about the large geometry, click "Yes" > * Hit "A" to use entire disk. Hit "W" to save, click "Yes", > select "None" for boot record. > * Fdisk says: "Wrote FDISK partition information out successfully." > * Per handbook, get out of sysinstall and re-run it, then > try to Label. In the label editor, it knows nothing about > da1 (the device can be selected when going into the label > editor, but I can't create any partitions). > At the time when Fdisk says "Wrote FDISK partition information out, > successfully." this gets logged to /var/log/messages: > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: corrupt or invalid GPT > detected. > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: GPT rejected -- may not be > recoverable. > I've tried several variations, including running the command-line > equivalents, but keep hitting this same error (fdisk thinks > everything > is good, but the GPT error is logged). I've also noticed that > /dev/da1 exists, but there is no /dev/da1s1 or /dev/da1s1e ... I'm > not sure when those should get created. > And the final possibly-relevant tidbit: these drives used to be > part of a different RAID on a linux system. They've been > re-initialized > into the RAID card on this system, and I've zero'd the first 1k of > the volume with dd, so I don't *think* that should be a factor. > I've worked with about a dozen systems with the same hardware in > the configuration outlined above and haven't seen this problem > before. But I'm usually using fresh new disks so maybe it matters. > I've googled this issue and found several people reporting similar > symptoms over the years, but haven't found any posted solutions > aside from telling people to read geom(8). > Any hints or clue-by-fours? > Mark > -- > Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 > [2]che...@swcp.com | Web: [3]www.swcp.com | Voice: +1-505-232-7992 > [4]abq-strange.com -- Interesting photos taken in Albuquerque, NM >Last post: Shoe Pole - 2009-07-07 20:18:22 > ___ > [5]freebsd-questi...@freebsd.org mailing list > [6]http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[7]freebsd-questions-unsubscr...@freebsd.org" > > References > >1. mailto:che...@swcp.com >2.
Re: Problem running fdisk via sysinstall
Mark, I'm certainly no expert, but I think I can point you in the right direction. The system appears to be attempting to read from a GPT stored on the disk from when you used it on Linux. I'm not sure of the specifics, but I do know that some GPT info is stored near the end of the drive. The easy (but slow) solution would be to use dd to write zeros to the entire drive (da1). Hope this helps, Nick On Wed, Jun 23, 2010 at 7:28 PM, Mark Costlow wrote: > I hope this question isn't too stupid. > > I have a machine with a 3Ware RAID card, with 4 SATA drives attached. > > 2 drives are 250GB in a RAID1 volume, and act as the boot disk with > a standard freebsd partiction map (/, /var, /usr, and swap on this disk). > > The other 2 drives are 1TB in a RAID1 volume, intended to be mounted > as a separate data partition. At boot both volumes are recognized: > > Jun 22 18:38:51 ebi7 kernel: da0 at twa0 bus 0 target 0 lun 0 > Jun 22 18:38:51 ebi7 kernel: da0: Fixed Direct > Access SCSI-5 device > Jun 22 18:38:51 ebi7 kernel: da0: 100.000MB/s transfers > Jun 22 18:38:51 ebi7 kernel: da0: 238408MB (488259584 512 byte sectors: > 255H 63S/T 30392C) > Jun 22 18:38:51 ebi7 kernel: da1 at twa0 bus 0 target 1 lun 0 > Jun 22 18:38:51 ebi7 kernel: da1: Fixed Direct > Access SCSI-5 device > Jun 22 18:38:51 ebi7 kernel: da1: 100.000MB/s transfers > Jun 22 18:38:51 ebi7 kernel: da1: 953664MB (1953103872 512 byte sectors: > 255H 63S/T 121575C) > > da0 is fine, and the system boots off of it with no problem. > > When I try to add da1 to the system, I get the following: > > * Run systinstall, Configure, Fdisk, select da1 > * Get the friendly warning about the large geometry, click "Yes" > * Hit "A" to use entire disk. Hit "W" to save, click "Yes", > select "None" for boot record. > * Fdisk says: "Wrote FDISK partition information out successfully." > * Per handbook, get out of sysinstall and re-run it, then > try to Label. In the label editor, it knows nothing about > da1 (the device can be selected when going into the label > editor, but I can't create any partitions). > > At the time when Fdisk says "Wrote FDISK partition information out, > successfully." this gets logged to /var/log/messages: > > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: corrupt or invalid GPT detected. > Jun 23 17:11:18 ebi7 kernel: GEOM: da1: GPT rejected -- may not be > recoverable. > > > I've tried several variations, including running the command-line > equivalents, but keep hitting this same error (fdisk thinks everything > is good, but the GPT error is logged). I've also noticed that > /dev/da1 exists, but there is no /dev/da1s1 or /dev/da1s1e ... I'm > not sure when those should get created. > > And the final possibly-relevant tidbit: these drives used to be > part of a different RAID on a linux system. They've been re-initialized > into the RAID card on this system, and I've zero'd the first 1k of > the volume with dd, so I don't *think* that should be a factor. > I've worked with about a dozen systems with the same hardware in > the configuration outlined above and haven't seen this problem > before. But I'm usually using fresh new disks so maybe it matters. > > I've googled this issue and found several people reporting similar > symptoms over the years, but haven't found any posted solutions > aside from telling people to read geom(8). > > Any hints or clue-by-fours? > > Mark > -- > Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 > che...@swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 > > abq-strange.com -- Interesting photos taken in Albuquerque, NM > Last post: Shoe Pole - 2009-07-07 20:18:22 > ___ > 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"
Problem running fdisk via sysinstall
I hope this question isn't too stupid. I have a machine with a 3Ware RAID card, with 4 SATA drives attached. 2 drives are 250GB in a RAID1 volume, and act as the boot disk with a standard freebsd partiction map (/, /var, /usr, and swap on this disk). The other 2 drives are 1TB in a RAID1 volume, intended to be mounted as a separate data partition. At boot both volumes are recognized: Jun 22 18:38:51 ebi7 kernel: da0 at twa0 bus 0 target 0 lun 0 Jun 22 18:38:51 ebi7 kernel: da0: Fixed Direct Access SCSI-5 device Jun 22 18:38:51 ebi7 kernel: da0: 100.000MB/s transfers Jun 22 18:38:51 ebi7 kernel: da0: 238408MB (488259584 512 byte sectors: 255H 63S/T 30392C) Jun 22 18:38:51 ebi7 kernel: da1 at twa0 bus 0 target 1 lun 0 Jun 22 18:38:51 ebi7 kernel: da1: Fixed Direct Access SCSI-5 device Jun 22 18:38:51 ebi7 kernel: da1: 100.000MB/s transfers Jun 22 18:38:51 ebi7 kernel: da1: 953664MB (1953103872 512 byte sectors: 255H 63S/T 121575C) da0 is fine, and the system boots off of it with no problem. When I try to add da1 to the system, I get the following: * Run systinstall, Configure, Fdisk, select da1 * Get the friendly warning about the large geometry, click "Yes" * Hit "A" to use entire disk. Hit "W" to save, click "Yes", select "None" for boot record. * Fdisk says: "Wrote FDISK partition information out successfully." * Per handbook, get out of sysinstall and re-run it, then try to Label. In the label editor, it knows nothing about da1 (the device can be selected when going into the label editor, but I can't create any partitions). At the time when Fdisk says "Wrote FDISK partition information out, successfully." this gets logged to /var/log/messages: Jun 23 17:11:18 ebi7 kernel: GEOM: da1: corrupt or invalid GPT detected. Jun 23 17:11:18 ebi7 kernel: GEOM: da1: GPT rejected -- may not be recoverable. I've tried several variations, including running the command-line equivalents, but keep hitting this same error (fdisk thinks everything is good, but the GPT error is logged). I've also noticed that /dev/da1 exists, but there is no /dev/da1s1 or /dev/da1s1e ... I'm not sure when those should get created. And the final possibly-relevant tidbit: these drives used to be part of a different RAID on a linux system. They've been re-initialized into the RAID card on this system, and I've zero'd the first 1k of the volume with dd, so I don't *think* that should be a factor. I've worked with about a dozen systems with the same hardware in the configuration outlined above and haven't seen this problem before. But I'm usually using fresh new disks so maybe it matters. I've googled this issue and found several people reporting similar symptoms over the years, but haven't found any posted solutions aside from telling people to read geom(8). Any hints or clue-by-fours? Mark -- Mark Costlow| Southwest Cyberport | Fax: +1-505-232-7975 che...@swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 abq-strange.com -- Interesting photos taken in Albuquerque, NM Last post: Shoe Pole - 2009-07-07 20:18:22 ___ 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: Re : Display country selected during sysinstall
De: Aiza Subject: Display country selected during sysinstall "FreeBSD Questions" Date: Jeudi 22 avril 2010, 10h11 How do I display or change the country selected at start of sysinstall? ___ >Alexandre L. wrote: > I think this is what your are searching for >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-sysinstall.html > Go to 'KEYMAP' and change it. > > If your system is already installed, you can edit /etc/rc.conf and see > what keymap is configured. > > --- En date de : Jeu 22.4.10, Aiza a écrit : > The handbook is very out of date with the new sysinstall now part of 8.0. I have no keymap in my rc.conf. The new 8.0 sysinstall shows a country selection menu even before the main sysinstall menu is shown. ___ 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 : Display country selected during sysinstall
I think this is what your are searching for http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-sysinstall.html Go to 'KEYMAP' and change it. If your system is already installed, you can edit /etc/rc.conf and see what keymap is configured. --- En date de : Jeu 22.4.10, Aiza a écrit : > De: Aiza > Objet: Display country selected during sysinstall > À: "FreeBSD Questions" > Date: Jeudi 22 avril 2010, 10h11 > How do I display or change the > country selected at start of sysinstall? > ___ > 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"
Display country selected during sysinstall
How do I display or change the country selected at start of sysinstall? ___ 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: PXE + sysinstall(8) install.cfg: DHCP Attribute to map install config/policy to system MAC?
On 21/04/10 21:59, Brian A. Seklecki (CFI NOC) wrote: All: The install.cfg mechanism is pretty wicked. Unfortunately, there doesn't seem to be a really efficient way to provide new clients (or class of clients) an install.cfg without rebuilding an MFSROOT image. Possibly a TFTP or NFS URL passed from the DHCP server -> boot loader -> kernel sysctl -> sysinstall(8). Thoughts or other ideas? You can configure sysinstall in your install.cfg to execute shell commands, including any fetch-like command. Some scripting should be possible to do what you require. I wrote about it here: http://www.locolomo.org/howto/pxeboot/automatic-installation.html However, I never really went on and tested this, let me know if this works. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.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"
PXE + sysinstall(8) install.cfg: DHCP Attribute to map install config/policy to system MAC?
All:
The install.cfg mechanism is pretty wicked.
Unfortunately, there doesn't seem to be a really efficient way
to provide new clients (or class of clients) an install.cfg
without rebuilding an MFSROOT image.
At least with pxeboot(8), in TFTP-only-mode, using
dhcpd.conf(5) client{} entries, there isn't a way
to differentiate policies.
It's just going to go looking for /boot/loader.rc
and /boot/loader.conf from wherever DHCP told PXE
to fetch pxeboot(8) from.
From there, you need to custom compile a 5 meg
mfsroot image for each [class of] client.
With an NFS stage-2 boot, I suppose you could set:
option root-path "/export/${client}Root" etc.,
but then your 5 meg mfsroot is just extracted
1-per-client.
Still seems a bit ugly. It seems like we could teach
sysinstall(8) to fetch install.cfg by some standard
mechanism.
Possibly a TFTP or NFS URL passed from the DHCP server
-> boot loader -> kernel sysctl -> sysinstall(8).
For example, the Sun SPARC4s would TFTP fetch their
stage 1 boot loader via TFTP with a filename req
of their MAC address in HEX format, so one could
just put symlinks in place.
Thoughts or other ideas?
~BAS
PS: our in-tree tftpd(8) is an unending source of sorrow and misery and
clinical despair. ports/net/freebsd-tftp is a lifesaver (it actually
has debugging)
___
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"
sysinstall: "You need to assign disk labels before you can proceed with the installation"
Hello, Having run into various problems trying to upgrade from 7.2 to 8.0, I'm instead trying to perform a clean install using sysintall. I've downloaded 8.0-RELEASE-amd64-memstick.img, modifed it to use a serial console and flashed it to a USB drive. This boots quite happily, and presents me with the sysintall screen. I'm intending to install to a pair of drives, mirrored with gmirror and partitioned with GPT. I therefore immediately drop into the fixit shell, create the mirror, partition it, and mount the new partitions under /newroot/, /newroot/usr etc. I then exit back to sysinstall, select custom install, point install root to /newroot and choose distribution, media. On selecting commit, sysinstall immediately presents the message "You need to assign disk labels before you can proceed with the installation", and won't proceed. It seems this only happens when sysinstall is running in single user mode. I have manged to make some progress with tricking sysintall into getting past this message. If I run sysinstall within the fixit shell (rather than exiting), I get a new instance of sysinstall with a pid other than 1. Symlinking /usr/bin to /stand, seems to provide most of the binaries it needs, and it proceeeds part of the way through installing the system before getting stuck on the documentation. I avoided this problem when installing 7.2 by creating an mfsbsd image, booting that, and then running sysinstall from there, but I'd rather not have the hassle of doing this for every future release. Moreover, creating an mfsbsd image may not even be an option in the event of a diasaster. Is anyone aware of any way of installing using sysintall from the standard FreeBSD media, but without using sysintall to partition and label the target disks? Kind regards, Christopher Key ___ 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: sysinstall: download via pure http
> For the initial install? Yes -- you're right: there's no obvious > 'install via HTTP' option. Trying to install via HTTP proxy and saying > ftp.freebsd.org:80 when prompted seems like it should work to me, but I > haven't verified that. Next time I install I'll try this - I was just wondering if this was an option > One handy hint when installing is *don't feel you have to do everything > from within sysinstall*. Your priority should be to get the OS up and > running: everything else you can do from within the OS, which is a far > more flexible and powerful platform than sysinstall. Exactly the same as my own sentiments > If you're trying to install packages via HTTP rather than FTP, then try > setting PACKAGEROOT in your environment. Like this: I don't use binary packages - only ports. Thanks ___ 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: sysinstall: download via pure http
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13/03/2010 14:22:58, Eitan Adler wrote: >> >> You can just access ftp.freebsd.org by HTTP > > but sysinstall doesn't give me that option - or at least I can't find it For the initial install? Yes -- you're right: there's no obvious 'install via HTTP' option. Trying to install via HTTP proxy and saying ftp.freebsd.org:80 when prompted seems like it should work to me, but I haven't verified that. Otherwise, your options are to download the disk1 or DVD .iso images, and install from those -- they have everything you need to install the base system -- or else to download the install sets out-of-band to a local filesystem and install that way. One handy hint when installing is *don't feel you have to do everything from within sysinstall*. Your priority should be to get the OS up and running: everything else you can do from within the OS, which is a far more flexible and powerful platform than sysinstall. That power comes at the cost of maybe not being particularly obvious exactly how to do what you want, but that is why the Handbook exists. If you're trying to install packages via HTTP rather than FTP, then try setting PACKAGEROOT in your environment. Like this: PACKAGEROOT=http://ftp.freebsd.org ; export PACKAGEROOT (Borne-shell) or setenv PACKAGEROOT http://ftp.freebsd.org (Csh-alikes) then use 'pkg_add -r pkgname' in the usual way. See login.conf(5) and cap_mkdb(1) for one way of setting such variables in the environment automatically when you login. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkubzNwACgkQ8Mjk52CukIyG6QCcDQxl5QdnQp1Ne206sCNTHZwZ y+YAn3dU9g1XUBKRwhXaeva8/FP7E7zn =H9jT -END PGP SIGNATURE- ___ 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: sysinstall: download via pure http
> > You can just access ftp.freebsd.org by HTTP but sysinstall doesn't give me that option - or at least I can't find it ___ 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: sysinstall: download via pure http
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/2010 15:07:07, Eitan Adler wrote: > instead of "ftp through an http proxy" is it possible to get a pure http > mirror? Yes happy-idiot-talk:~:% HEAD -uSe http://ftp.freebsd.org/pub/FreeBSD/ HEAD http://ftp.freebsd.org/pub/FreeBSD/ HEAD http://ftp.freebsd.org/pub/FreeBSD/ --> 200 OK Connection: close Date: Thu, 11 Mar 2010 17:37:05 GMT Server: lighttpd/1.4.26 Content-Length: 6656 Content-Type: text/html; charset=utf-8 Client-Date: Thu, 11 Mar 2010 17:37:06 GMT Client-Peer: 87.51.34.132:80 Client-Response-Num: 1 You can just access ftp.freebsd.org by HTTP Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuZKqMACgkQ8Mjk52CukIyo0gCeLRaRGrAvU/RRuHXumeCwcUO7 pJYAn3IVpiwdujPr/0IyZAtaEfUmVjFA =h+XG -END PGP SIGNATURE- ___ 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"
sysinstall: download via pure http
instead of "ftp through an http proxy" is it possible to get a pure http mirror? ___ 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"
[SOLVED]Re: Sysinstall Post-install System Management
On 02/19/10 15:34, Adam Vande More wrote: > On Fri, Feb 19, 2010 at 3:30 PM, Programmer In Training < > p...@joseph-a-nagy-jr.us> wrote: > >> Everytime I run portsnap update it says it's up to date. So I just >> fetched it and am extracting it right now. I'd run freebsd-udpate but >> that errors out, too. >> >> You have to run portsnap fetch update (assuming you've run a portsnap > extract earlier) > > freebsd-update will do you no go here. > > Probably not, but that's an issue I do need to get resolved. Also, flash is installed. Thanks for the help. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Sysinstall Post-install System Management
On 02/19/10 15:27, Adam Vande More wrote: > > Better yet, update your ports tree and install the current version > Everytime I run portsnap update it says it's up to date. So I just fetched it and am extracting it right now. I'd run freebsd-udpate but that errors out, too. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Sysinstall Post-install System Management
On 02/19/10 14:48, Frank Wißmann wrote: > Hello! > > Programmer In Training schrieb: >> On 02/19/10 13:50, Polytropon wrote: >>> On Fri, 19 Feb 2010 13:42:09 -0600, Programmer In Training >>> wrote: It's really past the point where I can just wipe the system and reinstall, making sure to opt for linux emulation from the get go. >>> It is not needed to reinstall the whole OS just because you > >> [r...@heaven]pkg_add linux_base-fc10 >> pkg_add: can't stat package file 'linux_base-fc10' > > Well, here you have to pass the "-r"-flag to "pkg_add". Don't forget > this, or are you installing from a local FS? > > Greetings Frank > I did forget that but I grabbed it from ports instead. Teeny-tiny install. Even with all dependencies (I went ahead and installed nspluginwrapper since linux_base-f10 is a dependency) and it took less then 15 minutes. Thanks. (: -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Sysinstall Post-install System Management
On 02/19/10 14:26, Programmer In Training wrote: > On 02/19/10 13:50, Polytropon wrote: >> And don't miss the documentation about getting "Flash" >> stuff running: >> >> http://www.freebsd.org/doc/handbook/desktop-browsers.html That all worked except for the last command: nspluginwrapper -v -a -i Even directly symlinking to /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so Isn't helping (it's not showing up in about plugins). Creating the directory ~/.mozilla/plugins and symlinking the file there (or running nspluginwrapper -v -a -i) doesn't help, either. -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: sysinstall on fedora?
Mehul Ved wrote: On Tue, Feb 23, 2010 at 1:45 AM, kalin m wrote: thanks.. i'm not going to use it. i have a remote access and just need to mount a usb drive (through a scsi interface?!?!) attached to it so i can copy over some stuff. i was done with redhat when they went "enterprise" and started modifying the core code basically i just need some command lines like mkfs and such which i couldn't find. i'll check this part command see what it's doing... In that case you should check fdisk for partitions mkfs for filesystem. You'd be most probably looking for mkfs.ext3 or mkfs.vfat cool. thanks.. that's what i was looking for ___ 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: sysinstall on fedora?
On Tue, Feb 23, 2010 at 1:45 AM, kalin m wrote: > > > thanks.. i'm not going to use it. i have a remote access and just need to > mount a usb drive (through a scsi interface?!?!) attached to it so i can > copy over some stuff. i was done with redhat when they went "enterprise" and > started modifying the core code > > basically i just need some command lines like mkfs and such which i couldn't > find. i'll check this part command see what it's doing... In that case you should check fdisk for partitions mkfs for filesystem. You'd be most probably looking for mkfs.ext3 or mkfs.vfat ___ 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: sysinstall on fedora?
thanks.. i'm not going to use it. i have a remote access and just need to mount a usb drive (through a scsi interface?!?!) attached to it so i can copy over some stuff. i was done with redhat when they went "enterprise" and started modifying the core code basically i just need some command lines like mkfs and such which i couldn't find. i'll check this part command see what it's doing... thanks again... Ross Cameron wrote: On Mon, Feb 22, 2010 at 9:36 PM, kalin m wrote: hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? To be honest considering its sooo OLD you're best option is backup and reinstall. And preferably not Fedora of all things, its too dev happy.. CentOS 5.4 will probably serve you better if you have need to run a Linux OS on that device. ___ 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: sysinstall on fedora?
On Mon, Feb 22, 2010 at 9:36 PM, kalin m wrote: > > hi all... realizing this is a bit OT but i have to deal with this old > fedora core 2 machine - making file system, slices, etc... what would be > the equivalent utility of sysinstall on fedora? To be honest considering its sooo OLD you're best option is backup and reinstall. And preferably not Fedora of all things, its too dev happy.. CentOS 5.4 will probably serve you better if you have need to run a Linux OS on that device. -- "Opportunity is most often missed by people because it is dressed in overalls and looks like work." Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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: sysinstall on fedora?
On Tue, Feb 23, 2010 at 1:06 AM, kalin m wrote: > > hi all... realizing this is a bit OT but i have to deal with this old > fedora core 2 machine - making file system, slices, etc... what would be > the equivalent utility of sysinstall on fedora? Does http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/s1-diskpartsetup-x86.html help? If you want to automate it, there's kickstart http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Installation_Guide/ch-kickstart2.html ___ 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"
sysinstall on fedora?
hi all... realizing this is a bit OT but i have to deal with this old fedora core 2 machine - making file system, slices, etc... what would be the equivalent utility of sysinstall on fedora? thanks.. ___ 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: Sysinstall Post-install System Management
On Friday 19 of February 2010 21:58:53 Erik Norgaard wrote: > On 19/02/10 20:42, Programmer In Training wrote: > > Any clues or alternate ways of getting this done? > > IIRC you first need to load the linux and linprocfs kernel modules and > mount linproc. > > BR, Erik > If you have never used the portsnap system before, the first thing you have to do is: portsnap fetch extract Then every time you need to update the portsnap you have to use the command: portsnap fetch update I fyou want to install the linux compatibility system you must first load the linux kernel module using (as root): kldload linux In /etc/fstab you have to add the following two lines: linproc /usr/compat/linux/proc linprocfs rw 0 0 proc /proc procfsrw 0 0 then mount these filesystems using: mount linproc mount proc as root Then you should be able to install the linux ports you want for the flash player, emulators/linux_base-f10 and www/linux-f10-flashplugin10 Regards, Elias ___ 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: Sysinstall Post-install System Management
On Fri, Feb 19, 2010 at 3:30 PM, Programmer In Training < p...@joseph-a-nagy-jr.us> wrote: > Everytime I run portsnap update it says it's up to date. So I just > fetched it and am extracting it right now. I'd run freebsd-udpate but > that errors out, too. > > You have to run portsnap fetch update (assuming you've run a portsnap extract earlier) freebsd-update will do you no go here. -- Adam Vande More ___ 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: Sysinstall Post-install System Management
> > Of course I did forget to install > www/linux-f10-flashplugin10 > > BUT, it doesn't matter that I forgot it. > > [r...@heaven]make install clean > ===> Vulnerability check disabled, database not found > => install_flash_player_10_linux.tar.gz doesn't seem to exist in > /usr/ports/distfiles/flashplugin/10.0r42. > => Attempting to fetch from > http://fpdownload.macromedia.com/get/flashplayer/current/. > fetch: > > http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_10_linux.tar.gz > : > size mismatch: expected 4050308, actual 4050435 > => Attempting to fetch from > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r42/. > fetch: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r42/install_flash_player_10_linux.tar.gz > : > File unavailable (e.g., file not found, no access) > => Couldn't fetch it - please try to retrieve this > => port manually into /usr/ports/distfiles/flashplugin/10.0r42 and try > again. > *** Error code 1 > > Stop in /usr/ports/www/linux-f10-flashplugin10. > [r...@heaven] > > Using Filezilla I ftp'd in and tried to retrieve it manually but > > ftp.freebsd.org/usr/ports/distfiles/flashplugin/ is an empty directory > > Anybody have this port in their local distfiles that I could download? > Better yet, update your ports tree and install the current version -- Adam Vande More ___ 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: Sysinstall Post-install System Management
On 02/19/10 14:50, Programmer In Training wrote: > That all worked except for the last command: > > nspluginwrapper -v -a -i > > Even directly symlinking to > > /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so > > Isn't helping (it's not showing up in about plugins). > > Creating the directory ~/.mozilla/plugins and symlinking the file there > (or running nspluginwrapper -v -a -i) doesn't help, either. Of course I did forget to install www/linux-f10-flashplugin10 BUT, it doesn't matter that I forgot it. [r...@heaven]make install clean ===> Vulnerability check disabled, database not found => install_flash_player_10_linux.tar.gz doesn't seem to exist in /usr/ports/distfiles/flashplugin/10.0r42. => Attempting to fetch from http://fpdownload.macromedia.com/get/flashplayer/current/. fetch: http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_10_linux.tar.gz: size mismatch: expected 4050308, actual 4050435 => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r42/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r42/install_flash_player_10_linux.tar.gz: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/flashplugin/10.0r42 and try again. *** Error code 1 Stop in /usr/ports/www/linux-f10-flashplugin10. [r...@heaven] Using Filezilla I ftp'd in and tried to retrieve it manually but ftp.freebsd.org/usr/ports/distfiles/flashplugin/ is an empty directory Anybody have this port in their local distfiles that I could download? -- Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Sysinstall Post-install System Management
On Fri, 19 Feb 2010 14:26:29 -0600, Programmer In Training wrote: > On 02/19/10 13:50, Polytropon wrote: > > On Fri, 19 Feb 2010 13:42:09 -0600, Programmer In Training > > wrote: > >> It's really past the point where I can just wipe the system and > >> reinstall, making sure to opt for linux emulation from the get go. > > > > It is not needed to reinstall the whole OS just because you > > accidentally forgot to install an additional package. We're > > not in MICROS~1 land here. :-) > > I know, but it seems almost easier to do it then instead of later. No problem - I'm often installing needed stuff right away when still in sysinstall from the CD. > FreeBSD 8.0-RELEASE > > [r...@heaven]portsnap update > Ports tree is already up to date. > > Should I just fetch and extract anyway? If you're copy of the ports tree is from the CD, then it matches the version 8.0 of the OS from the CD. If you update your system AND the ports tree, it's easy to install linux-base_fc10 along with "Flash" and anything else you need from ports. If you're installing from precompiled packages - which are usually at a version near the current ports tree - it's often useful to have an updated system, too. You can compile it yourself or use freebsd-update for that. > Just trying to be as helpful as possible. Figured someone would know > where the "debug window" is. This refers to the normal behaviour of sysinstall when run from the installation CD. The debug screen is one of the virtual terminals, usually on Alt+PF2, if I remember correctly. On this terminal, diagnostic messages are output. > >> Any clues or alternate ways of getting this done? > > > > You could try to > > > > a) install linux_base-fc10 via pkg_add > > > [r...@heaven]pkg_add linux_base-fc10 > pkg_add: can't stat package file 'linux_base-fc10' See "man pkg_add"; you have to use -r to get the file via Internet. If you're just specifying the name, pkg_add assumes it to be present in the current directory; see the manual about PACKAGESITE, too. This enables you the ability to get "archived" binary packages (for older versions of the OS). > > or > > > > b) install it through the port; > >in this case you should update system and > >ports tree before compiling. > > [r...@heaven]cd /usr/ports/emulators/linux_base-fc10 > /usr/ports/emulators/linux_base-fc10: No such file or directory. > > Figured out from the below linked page it's linux_base-f10, no problems. > I'm good on my way. Thanks! Yes, it is f10. :-) > Is that the most recent flash version available for linux via Adobe? The port's name is linux-f10-flashplugin10, if I remember correctly. > From another email: > > On 02/19/10 13:58, Erik Norgaard wrote: > >> On 19/02/10 20:42, Programmer In Training wrote: > >> > >>> Any clues or alternate ways of getting this done? > >> > >> IIRC you first need to load the linux and linprocfs kernel modules and > >> mount linproc. > >> > >> BR, Erik > >> > > Just did that, thanks for the heads up. Yes, that's neccessary, too. Important advice. -- Polytropon 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"
