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"
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
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"
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"
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/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=Y
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, please keep
reading. The last suggestion is to use my DruidBSD platform which
already has such patches applied, compiled, and ready to download.
2. Using a
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"
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"
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"
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
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: 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"
[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"
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"
Re: Sysinstall Post-install System Management
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 -- GU d- s:+ a+ C+>$ UBS>$ 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? When pack meets pack in the jungle and no one will move from the trail wait till the leaders have spoken it may be fair words shall prevail (Rudyard Kipling) ___ 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 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. >> So >> I'm attempting to use sysinstall to install it on my present system. >> Every time I run it, though, I get the following error message during >> the download: > > Your message is: > > Add of package linux_base-fc6-6_6 aborted, > error code 1 > > That's why it would be helpful to know which version of > FreeBSD you're installing. In case you want "Flash" and > "Skype", going with fc10 is highly recommended. FreeBSD 8.0-RELEASE [r...@heaven]portsnap update Ports tree is already up to date. Should I just fetch and extract anyway? >> This is run from an xterm session. (uxterm -sb -rv) > > That should not be the problem. Just trying to be as helpful as possible. Figured someone would know where the "debug window" is. >> 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' > 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! > And don't miss the documentation about getting "Flash" > stuff running: > > http://www.freebsd.org/doc/handbook/desktop-browsers.html > > It is 6.2.3/4. Is that the most recent flash version available for linux via Adobe? 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. -- 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 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 -- 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"
Re: Sysinstall Post-install System Management
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. :-) > So > I'm attempting to use sysinstall to install it on my present system. > Every time I run it, though, I get the following error message during > the download: Your message is: Add of package linux_base-fc6-6_6 aborted, error code 1 That's why it would be helpful to know which version of FreeBSD you're installing. In case you want "Flash" and "Skype", going with fc10 is highly recommended. > This is run from an xterm session. (uxterm -sb -rv) That should not be the problem. > Any clues or alternate ways of getting this done? You could try to a) install linux_base-fc10 via pkg_add or b) install it through the port; in this case you should update system and ports tree before compiling. And don't miss the documentation about getting "Flash" stuff running: http://www.freebsd.org/doc/handbook/desktop-browsers.html It is 6.2.3/4. -- 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"
Re: sysinstall and mfs Great News and another Question
Please create a PR for any problems you find here or additions to install.cfg that you would like to see, and I'll take a look at it. -- randi On Mon, Feb 8, 2010 at 7:41 PM, Martin McCormick wrote: > I really hate to give up on anything and I finally found > out my problem with getting sysinstall to use the hard drive > rather than garbaging up mfs every time. The problem is not > something you can set in the partition editor or disklabel > editor. It is found in the very first menu which oddly is > numbered 2 and is the options editor. The option that makes it > all work is one that lets you specify where you want the > distribution to go on the drive. It is always set for you when > using the CDROM unless you were formatting another disk so it is > kind of easy to miss. I missed it for a week and a half. > > Now the question. There are a bunch of functions that > can be set in sysinstall such as the bsdlabel editor, partition > editor and dists to name a few. It would be nice to be able to > set that mount point in install.cfg because I am trying to make > a script that coworkers can run to configure a system quickly > without having to waste a week of their own trying to figure it > all out. > > It turns out that one can format the disk, mount > /dev/ad0s1a on /mnt and then one must set the root option to > /mnt and things work so much better! > > Occasionally, /var fills up and I haven't figured out > why but it appears that ftp gets ahead of the ability to store > the files. Whatever it happening, it is now more right than > wrong. > > Again, thanks for all your help. > > Martin McCormick WB5AGZ Stillwater, OK > Systems Engineer > OSU Information Technology Department Telecommunications Services Group > ___ > 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: sysinstall and mfs Great News and another Question
On Thu, Feb 11, 2010 at 3:44 AM, Martin McCormick wrote: > J65nko writes: >> IMHO it is easier to to install FreeBSD without using sysinstall at all. >> >> See the "FreeBSD Install Without Sysinstall" guide at >> http://www.daemonforums.org/showthread.php?t=1538 > > This looks very possible with a couple of changes. Am I > right in my reading of the man page of mdconfig that the memory > disk image will gobble up at least as much RAM as the image, > itself? In this case, that's about 600 times more than I have > available. mfsbsd seems as solid as a rock as long as you don't > do something that needs lots of buffer space as there is only > about a megabyte or two left over. tar works fine and I can copy > either an iso image or a tar ball made from the file system over > to the newly-formatted drive where it can be unpacked. It may > be necessary to run chroot /mnt so as not to munch mfs when > running the install.sh scripts but I think this should install > the system. > > I really have given up on sysinstall for this purpose. > It is hard to script and it appears that if you use the custom > installation, you almost get a system but the effort is hardly > worth it. One still has to install the kernel and many of the > configuration files like /etc/rc.conf. I don't know why but > another artickel I read on remote installation of FreeBSD that > uses sysinstall describes this so I know it isn't just me doing > something stupid. I feel kind of stupid spending almost 3 weeks > finding out what doesn't work. > > When using mfsbsd, one already has enough information in > the interface configuration and resolv.conf to populate /etc/rc.conf, > /etc/hosts and /etc/resolv.conf to match the present network > configuration. The local time zone is a copy of one of the rule > sets for computing time placed as /etc/localtime. In the middle > of the United States, it is /usr/share/zoneinfo/America/Chicago > copied, not linked, to /etc/localtime. > > The goal is to run the script I will build under mfsbsd > and then boot the system in working order as if it had been > installed via sysinstall by someone sitting at a console. > > Martin McCormick WB5AGZ Stillwater, OK > Systems Engineer > OSU Information Technology Department Telecommunications Services Group > ___ > 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: sysinstall and mfs Great News and another Question
J65nko writes: > IMHO it is easier to to install FreeBSD without using sysinstall at all. > > See the "FreeBSD Install Without Sysinstall" guide at > http://www.daemonforums.org/showthread.php?t=1538 This looks very possible with a couple of changes. Am I right in my reading of the man page of mdconfig that the memory disk image will gobble up at least as much RAM as the image, itself? In this case, that's about 600 times more than I have available. mfsbsd seems as solid as a rock as long as you don't do something that needs lots of buffer space as there is only about a megabyte or two left over. tar works fine and I can copy either an iso image or a tar ball made from the file system over to the newly-formatted drive where it can be unpacked. It may be necessary to run chroot /mnt so as not to munch mfs when running the install.sh scripts but I think this should install the system. I really have given up on sysinstall for this purpose. It is hard to script and it appears that if you use the custom installation, you almost get a system but the effort is hardly worth it. One still has to install the kernel and many of the configuration files like /etc/rc.conf. I don't know why but another artickel I read on remote installation of FreeBSD that uses sysinstall describes this so I know it isn't just me doing something stupid. I feel kind of stupid spending almost 3 weeks finding out what doesn't work. When using mfsbsd, one already has enough information in the interface configuration and resolv.conf to populate /etc/rc.conf, /etc/hosts and /etc/resolv.conf to match the present network configuration. The local time zone is a copy of one of the rule sets for computing time placed as /etc/localtime. In the middle of the United States, it is /usr/share/zoneinfo/America/Chicago copied, not linked, to /etc/localtime. The goal is to run the script I will build under mfsbsd and then boot the system in working order as if it had been installed via sysinstall by someone sitting at a console. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ 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 and mfs Great News and another Question
On Tue, Feb 9, 2010 at 4:41 AM, Martin McCormick wrote: > I really hate to give up on anything and I finally found > out my problem with getting sysinstall to use the hard drive > rather than garbaging up mfs every time. The problem is not > something you can set in the partition editor or disklabel > editor. It is found in the very first menu which oddly is > numbered 2 and is the options editor. The option that makes it > all work is one that lets you specify where you want the > distribution to go on the drive. It is always set for you when > using the CDROM unless you were formatting another disk so it is > kind of easy to miss. I missed it for a week and a half. > > Now the question. There are a bunch of functions that > can be set in sysinstall such as the bsdlabel editor, partition > editor and dists to name a few. It would be nice to be able to > set that mount point in install.cfg because I am trying to make > a script that coworkers can run to configure a system quickly > without having to waste a week of their own trying to figure it > all out. IMHO it is easier to to install FreeBSD without using sysinstall at all. See the "FreeBSD Install Without Sysinstall" guide at http://www.daemonforums.org/showthread.php?t=1538 ___ 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 and mfs Great News and another Question
I really hate to give up on anything and I finally found out my problem with getting sysinstall to use the hard drive rather than garbaging up mfs every time. The problem is not something you can set in the partition editor or disklabel editor. It is found in the very first menu which oddly is numbered 2 and is the options editor. The option that makes it all work is one that lets you specify where you want the distribution to go on the drive. It is always set for you when using the CDROM unless you were formatting another disk so it is kind of easy to miss. I missed it for a week and a half. Now the question. There are a bunch of functions that can be set in sysinstall such as the bsdlabel editor, partition editor and dists to name a few. It would be nice to be able to set that mount point in install.cfg because I am trying to make a script that coworkers can run to configure a system quickly without having to waste a week of their own trying to figure it all out. It turns out that one can format the disk, mount /dev/ad0s1a on /mnt and then one must set the root option to /mnt and things work so much better! Occasionally, /var fills up and I haven't figured out why but it appears that ftp gets ahead of the ability to store the files. Whatever it happening, it is now more right than wrong. Again, thanks for all your help. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ 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"
Fw: Re: sysinstall and mfs I'm out of Ideas.
--- On Sat, 2/6/10, Mark wrote: > From: Mark > Subject: Re: sysinstall and mfs I'm out of Ideas. > To: "Martin McCormick" > Date: Saturday, February 6, 2010, 12:17 AM > > > --- On Fri, 2/5/10, Martin McCormick > wrote: > > > From: Martin McCormick > > Subject: Re: sysinstall and mfs I'm out of Ideas. > > To: "Mark" > > Date: Friday, February 5, 2010, 8:21 PM > > Mark writes: > > > I'm sure you have already read this from man > > sysinstall, but it may give > > > a hint to something you may have missed. > > > > > > > > <<<< Note: > > Nothing is actually written to disk by this function, > an > > > > > explicit call to diskPartitionWrite being required for > that > > > > > to happen. >>>> > > > > > > diskPartitionWrite > > > Causes > > any pending MBR changes (typically from the > > > > > diskPartitionEditor function) to be written out. > > > > > > > > Variables: None > > > > > > > > > <<< Note: No file system data is > actually > > written to disk until an > > > > > explicit call to diskLabelCommit is made. > > > > Thank you. The commit is definitely > > never happening. > > When it does happen, several messages appear and there > is a > > time > > lag while the newfs takes place. It should happen > right > > after > > one selects the installation media. Instead, it just > skips > > that > > step and ruins mfs by overwriting some of its > utilities > > with > > binaries that should be going to the hard drive. > > Again, thanks. > > > > Martin McCormick > > > > perhaps adding "sleep 120" to halt the script execution for > 2 minutes to allow the new files system write to complete. > hth > > ___ 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 and mfs I'm out of Ideas.
--- On Fri, 2/5/10, Martin McCormick wrote: > From: Martin McCormick > Subject: sysinstall and mfs I'm out of Ideas. > To: freebsd-questions@freebsd.org > Date: Friday, February 5, 2010, 2:22 PM > After about a week > of trying, I don't think sysinstall > will install FreeBSD when used with mfsbsd. I > launched mfsbsd > from a CDROM and it works fine. I also used dd to feed the > mfsboot.img file to the boot sector on the system's hard > drive > and that also worked fine. mfsbsd doesn't appear to be the > problem. Everything but sysinstall works as one would > expect. > > Sysinstall may either be confused > because the host is in > multi-user mode or it may be trying to protect what it > thinks is > the system's boot drive from damage. It absolutely will > not > write one byte to /dev/ad0 partitions even though it sees > the > drive. the rest of sysinstall appears to be normal except > for > its fear about writing to /dev/ad0sx. > > I will be very happy to be proven wrong, > but I don't > know what else to do to sysinstall to get it to use that > drive. > > It does work from the local console in > single-user mode > from the CDROM. I greatly appreciate all the help and > welcome > any new ideas, but it appears to be back to the drawing > board > for remotely-done upgrades. > > Martin McCormick > ___ > 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" > I'm sure you have already read this from man sysinstall, but it may give a hint to something you may have missed. Note: Nothing is actually written to disk by this function, an explicit call to diskPartitionWrite being required for that to happen. diskPartitionWrite Causes any pending MBR changes (typically from the diskPartitionEditor function) to be written out. Variables: None <<< Note: No file system data is actually written to disk until an explicit call to diskLabelCommit is made. >>> diskLabelCommit Writes out all pending disklabel information and creates and/or mounts any file systems which have requests pending from the diskLabelEditor function. Variables: None ___ 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 and mfs
Jerry McAllister writes: > I don't understand why you are trying to do your own MFS for this. > You need to be booted to the MFS for it to make any difference and > that is what the install image (from the CD) normally does. If you > just create an MFS and copy sysinstall to it, it will make no > difference in its ability to modify the labels on the system disks. > They are already busy and you would have to reboot to unbusy them What I actually did was to download the mfsbsd tool set which lets you create either an iso image you can burn to a CD or another image that you spray on to the MBR of the hard drive via dd. Either way, the system that comes up is not connected in any way to the hard drive. That is what I thought one had when booting from the CDROM. The only difference is that one is in multiuser mode under mfs and single user mode when booting the CDROM. That difference may be the problem. It just occurred to me that one of the messages you see as sysinstall starts up is that it is probing devices. Since many of those devices are part of mfs, this may be how things go wrong. Sysinstall may see a device that essentially breaks its idea of the hard drive and where it is. I have never been so confused about something that seemed so straight-forward. Thanks for your help. Martin McCormick ___ 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 and mfs
On Thu, Feb 04, 2010 at 03:31:33PM -0600, Martin McCormick wrote: > It appears that the same sysinstall executable that > works fine when run from the installation CDROM malfunctions > when run from a mfs platform even though it finds the disk it is > supposed to install on. > > One can format the disk manually and mount the > partitions under mfs, but sysinstall can't seem to do the > installation. This does not make sense, but that is the score > right now. I don't understand why you are trying to do your own MFS for this. You need to be booted to the MFS for it to make any difference and that is what the install image (from the CD) normally does. If you just create an MFS and copy sysinstall to it, it will make no difference in its ability to modify the labels on the system disks. They are already busy and you would have to reboot to unbusy them and then you lose the MFS. You could muck around and go down to Single User and maybe come up running from MFS and free up the disk, but don't know a way to do that. What happens when the boot or fixit is running is that you are booted to a special filesystem that resides in MFS. The system copies over what it needs from the CD (or floppies) and runs from there. Mainly it is a filesystem and it allows nothing else but the MFS and the boot media (CD/Floppy) to be mounted. Then the hard disk is free to diddle with the labels on. If you do an install of something on to the hard disk, then it creates a mount point within that Memory Filesystem and mounts the disk partition to it. I don't know the naming convention that it uses for the mount points, but it could be anything such as iroot, iusr, etc or maybe something based on the partition name such as mda1s1a, mda1s1d, etc.Maybe they make an mroot and then put the rest of the mount points in that mroot directory just like they will be in a running system. So, if there are more than root partitions they would look something like /mroot, /mroot/tmp, /mroot/usr, etc. Guess I should poke around sometime and see what they call them - sometime when I have a lot of extra time. The system uses these to install the software and then when it reboots, these temporary mount points disappear and when the new system comes up, it just uses the mount points written in the /etc/fstab file (or in the /mroot/etc/fstab file before the reboot when still doing the install) This is rambling too much. The point is that MFS is only meaningful in this situation if the system is booted and running from it. It does not mean anything to sysinstall otherwise. There are other uses for MFS such as a handy device for creating these boot images, but that has little bearing on how sysinstall runs. jerry > > Martin McCormick > ___ > 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: sysinstall and the Right Terminal
On Mon, Jan 25, 2010 at 09:25:21AM -0600, Martin McCormick wrote: > Thomas Dickey writes: > > "Terminal" would probably be one of the programs using VTE, > > which differs from "linux". > > This is all very interesting. Thanks to all. What I > normally do is start a command-line shell on a Debian Linux box. > This defaults to a "linux" console. When I ssh somewhere, ssh > passes the exported $TERM value to the remote host so as I > understand it, it will use this value in the environment that it > exports to any application called from that shell. The question > is whether or not all the escape codes it sends to address the > terminal and all the escape sequences it looks for to represent > arrow keys, etc, will still work. It should - the remote machine "should" have the same terminal description. Your local machine however may have initialized the Linux console to expect UTF-8 encoding, and the remote machine may not know about that. Line- drawing wouldn't work properly in that case, but cursor-movement and keys should. > The best results, so far, are with using cons25 as the > TERM value. The Up and Down arrows work right as opposed to going > right straight to X Exit this menu. My first impression was that it could be a disagreement between the two machine whether cursor-application mode is set. That changes the escape sequence sent by the cursor-keys. However, ncurses' descriptions for both say they're using normal (non-application) mode. So that doesn't seem to explain it. It's also possible that the screensize isn't being transmitted (and "stty -a" would show if it's really 25 lines or not). > > I appreciate all the input because in this game, > knowledge is the power to fix it. > > Martin McCormick > ___ > 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" -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgpQLAAPrLnah.pgp Description: PGP signature
Re: sysinstall and the Right Terminal
Thomas Dickey writes: > "Terminal" would probably be one of the programs using VTE, > which differs from "linux". This is all very interesting. Thanks to all. What I normally do is start a command-line shell on a Debian Linux box. This defaults to a "linux" console. When I ssh somewhere, ssh passes the exported $TERM value to the remote host so as I understand it, it will use this value in the environment that it exports to any application called from that shell. The question is whether or not all the escape codes it sends to address the terminal and all the escape sequences it looks for to represent arrow keys, etc, will still work. The best results, so far, are with using cons25 as the TERM value. The Up and Down arrows work right as opposed to going right straight to X Exit this menu. I appreciate all the input because in this game, knowledge is the power to fix it. Martin McCormick ___ 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 and the Right Terminal
On Sat, Jan 23, 2010 at 12:48:32PM -0700, Dale Scott wrote: > > Using Ubuntu 9.10 (Karmic Koala) and GNOME Terminal 2.28.1, $TERM is Xterm. > > $ echo $TERM > Xterm > $ > > The only thing I'd change about the mapping is that I'd rather flash the > screen instead of ringing the bell. > Put: XTerm*visualBell:true in ~/.Xdefaults and that should fix it. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.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 and the Right Terminal
Using Ubuntu 9.10 (Karmic Koala) and GNOME Terminal 2.28.1, $TERM is Xterm. $ echo $TERM Xterm $ The only thing I'd change about the mapping is that I'd rather flash the screen instead of ringing the bell. > -Original Message- > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > questi...@freebsd.org] On Behalf Of Martin McCormick > Sent: January-23-10 7:02 AM > To: freebsd-questions@freebsd.org > Subject: Re: sysinstall and the Right Terminal > ... > Is TERM = "linux" or something else? > ___ 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 and the Right Terminal
On Sat, Jan 23, 2010 at 08:01:41AM -0600, Martin McCormick wrote: > Dale Scott writes: > > I don't have a solution but can report I regularily login to my fbsd 7 > > and 8 boxes from an Ubuntu laptop using ssh in > > Terminal and run sysinstall. I've never encountered this problem though. > > Thank you for responding. > > If you type > > echo $TERM > > or just the command > > env > > Is TERM = "linux" or something else? "Terminal" would probably be one of the programs using VTE, which differs from "linux". -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net pgplbt0hD0XM4.pgp Description: PGP signature
Re: sysinstall and the Right Terminal
Dale Scott writes: > I don't have a solution but can report I regularily login to my fbsd 7 > and 8 boxes from an Ubuntu laptop using ssh in > Terminal and run sysinstall. I've never encountered this problem though. Thank you for responding. If you type echo $TERM or just the command env Is TERM = "linux" or something else? As I write this message, I have cons25l1 as the environment variable for TERM and sysinstall came up with no issues at all. I could make that my default terminal except for the fact that a few of the escape codes for formatting the screen quit working for applications like vi. In vi, for instance, one can join two lines together by typing a J in command mode. That works under a linux or VT100 terminal but it doesn't work when using cons25. It may end up being one of those things I just remember to do when necessary. One interesting thing I notice is that when in "linux" or "VT100" emulation, I always lost the Bell that rings during vi when you hit Escape more than once or try to move the cursor past the end of the text. The bell works in cons25. The formatting issues are more of an issue than the bell so I will need to go back to a more VT100-like terminal. What we may be dealing with is the fact that some programs do their own emulation based on what they think the terminal should be. There is something called "raw" mode and "cooked" mode. The shell and a lot of applications use "cooked" mode and rely on the shell to do the addressing. Other full-screen programs like vi turn off the shell's processing and use their own. This is only bad if it isn't what works with your display device. What is even more interesting is that vi under Linux, itself, has all the bells, so to speak. I am getting in to an area in which I know less than I should so I will stop here. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ 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 and the Right Terminal
Polytropon writes: > What about using $TERM = xterm or cons25 (or cons25l1)? Thank you! I tried cons25 first and it worked very well. Since I am still actually receiving via the linux terminal definition, I was surprised it worked as well as it does. The cons25 must use many of the same escape sequences that vt100 style terminals do. The arrows appeared to work and the screen seemed to be formatted well enough. I left $TERM set to cons25 and tried vi on a file. It started out okay but some of the escape sequences are not compatible as things soon got messy. Even so, it is nice to know that sysinstall can be remotely run without too much strangeness. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ 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 and the Right Terminal
> If one logs in to a FreeBSD system from a Linux > platform, the terminal type is set to linux which is compatible > with a vt100. As soon as I run sysinstall, things go to the dogs > very fast. It is as if there was no terminal emulation in effect I don't have a solution but can report I regularily login to my fbsd 7 and 8 boxes from an Ubuntu laptop using ssh in Terminal and run sysinstall. I've never encountered this problem though. -- Dale Scott Calgary, AB, Canada ___ 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 and the Right Terminal
On Fri, 22 Jan 2010 16:10:15 -0600, Martin McCormick wrote: > If one logs in to a FreeBSD system from a Linux > platform, the terminal type is set to linux which is compatible > with a vt100. What about using $TERM = xterm or cons25 (or cons25l1)? -- 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"
Re: sysinstall colours
On Fri, Oct 16, 2009 at 6:00 PM, Michiel Overtoom wrote: > > On Friday 16 October 2009, Randi Harper wrote: > > > Personally if I spent a lot of time on such a project, I'd be sure to > have > > the "is this going to make it into freebsd base?" conversation first. > > I think there's no doubt about it that 'sysinstall' will feature in the > next > FreeBSD too. It will! Keep up the good work! It's worth it. > Thank you for the kind words. :) > > The sysinstall manual page makes two apocalyptical remarks about itself: > > 1. "This product is currently at the end of its life cycle and will > eventually > be replaced." > > 2. "This utility is a prototype which lasted several years past its > expiration > date and is greatly in need of death." > > These doomsayings are wrong. To date no serious contenders have surfaced > and > up until that time sysinstall does its job, underappreciated perhaps, but > it > does it reasonably well, and adequately. Now that it is back in the focus, > we can look to a bright, evolutionary future for sysinstall. > As much as I want to agree with you, I can't quite do so. There are (to the best of my understanding) solid reasons why no other installer has made it into base. This doesn't necessarily mean that sysinstall is the final answer, though. Eventually, in my opinion, sysinstall needs to be replaced. It tries to do more than it should. For example, one of the things I'd like to see removed is the upgrade option - although I'm expecting quite a bit of backlash on that, so we'll see if that happens. I also don't think it should manage configuring rc.conf beyond network interfaces/hostname. The network services configuration is a mess. I don't think enabling the NFS server via sysinstall even works at this point. That aside, the code for sysinstall isn't really that bad, although it's been more of a history lesson than I initially expected. It was clearly written with the restrictions of older technology in mind. Bringing it completely up to date with current technology (devfs, gpt, zfs, whatever) is going to be such an extensive rewrite that it's true, one might as well write a new installer altogether. Then again, maybe I just like playing devil's advocate. :) -- randi ___ 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 colours
On Friday 16 October 2009, Randi Harper wrote: > Personally if I spent a lot of time on such a project, I'd be sure to have > the "is this going to make it into freebsd base?" conversation first. I think there's no doubt about it that 'sysinstall' will feature in the next FreeBSD too. It will! Keep up the good work! It's worth it. The sysinstall manual page makes two apocalyptical remarks about itself: 1. "This product is currently at the end of its life cycle and will eventually be replaced." 2. "This utility is a prototype which lasted several years past its expiration date and is greatly in need of death." These doomsayings are wrong. To date no serious contenders have surfaced and up until that time sysinstall does its job, underappreciated perhaps, but it does it reasonably well, and adequately. Now that it is back in the focus, we can look to a bright, evolutionary future for sysinstall. alexbes...@math.uni-muenster.de wrote: > personally if i spent a lot of time on such a project i'd be expecting it > to get integrated into the base system. if not i'd get rather upset and > would probably switch to linux or opensolaris. I wouldn't switch operating systems just because something in the installer bugged me. Some enhancements I made to OSS and were rejected by the maintainers also didn't make me abandon that software. Greetings, Michiel Overtoom, Software developer. -- "The ability of the OSS process to collect and harness the collective IQ of thousands of individuals across the Internet is simply amazing." - Vinod Valloppillil http://www.catb.org/~esr/halloween/halloween4.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 colours
On Tue, Oct 13, 2009 at 2:23 PM, Alexander Best < alexbes...@math.uni-muenster.de> wrote: > > just did a quick research and google soc sponsored the finstaller in 2007 > and > the bsdinstaller in 2005. > > personally if i spent a lot of time on such a project i'd be expecting it > to > get integrated into the base system. if not i'd get rather upset and would > probably switch to linux or opensolaris. > > just my 2 cents. > > alex > Personally if I spent a lot of time on such a project, I'd be sure to have the "is this going to make it into freebsd base?" conversation first. -- randi ___ 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 colours
Kevin Kinsey schrieb am 2009-10-11: > Alexander Best wrote: > >>Seriously?!?!?! All the problems with sysinstall, and your idea is > >>to > >>change > >>the color? Are you trying to start a bikeshed? If so, I prefer > >>pink. > >>-- randi > I'm painting the little girl's room next week and might have > some leftover interior latex, if that will do. Oh, but, it's > outside, so prolly not. Sorry. Or, do you want your pink > bikeshed in the garage? ;-) > >current developers don't seem to have any interest in improving > >sysinstall. so > >it's important to get new people involved in freebsd. and the way > >to do that > >is with an attractive looking installer and an easy installation > >process imo. > I don't want to be harsh, but do you know what you're talking about? > Randi, for one, has taken on the zombie known as sysinstall with a > nice big shotgun, and is attempting to keep adding a few features > here/there as needed to keep up with necessities while other > developers (AFAIK) work on other projects, including, at last count, > a couple differnet possibilities for installers. It's apparently > been rather daunting work, and, as a result, the new installer, > whatever its name is/will be, isn't ready for inclusion with 8.0. > However, a day is coming ... > Kevin Kinsey just did a quick research and google soc sponsored the finstaller in 2007 and the bsdinstaller in 2005. personally if i spent a lot of time on such a project i'd be expecting it to get integrated into the base system. if not i'd get rather upset and would probably switch to linux or opensolaris. just my 2 cents. alex ___ 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 colours
Alexander Best wrote: Seriously?!?!?! All the problems with sysinstall, and your idea is to change the color? Are you trying to start a bikeshed? If so, I prefer pink. -- randi I'm painting the little girl's room next week and might have some leftover interior latex, if that will do. Oh, but, it's outside, so prolly not. Sorry. Or, do you want your pink bikeshed in the garage? ;-) current developers don't seem to have any interest in improving sysinstall. so it's important to get new people involved in freebsd. and the way to do that is with an attractive looking installer and an easy installation process imo. I don't want to be harsh, but do you know what you're talking about? Randi, for one, has taken on the zombie known as sysinstall with a nice big shotgun, and is attempting to keep adding a few features here/there as needed to keep up with necessities while other developers (AFAIK) work on other projects, including, at last count, a couple differnet possibilities for installers. It's apparently been rather daunting work, and, as a result, the new installer, whatever its name is/will be, isn't ready for inclusion with 8.0. However, a day is coming ... Kevin Kinsey ___ 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 install.cfg
On Wed, 1 Apr 2009 23:25:16 +0200, Andreas Nilsson wrote: AN> AN> # Now set the parameters for the partition editor on da0. AN> disk=da0 AN> partition=all AN> bootManager=none try bootManager=standard AN> diskPartitionEditor AN> diskPartitionWrite try to remove diskPartitionWrite -- Anton Yuzhaninov ___ 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 cannot find snapshot releases
On Sun, Mar 22, 2009 at 11:38 AM, Jason Nordwick wrote: > I'm a previous FreeBSD user that used to track current and returning after a > few years. If my memory is correct, the definition of -stable, -release, and > -current seems to have changed? (but my memory sucks so excuse me if I'm > wrong). No. > > Can you no longer track -release, but instead -stable is actually more > advanced at times (more bug fixes and backports)? > You can track -RELEASE for security errata. > So I guess I would like to use -current or -stable and occasionally cvsup > the tree. I tried downloading the 200902 current and stable snapshots, and > sysinstall keeps telling me the Main site doesn't have them, so I tried > 200812 current and that doesn't work either. Is there an FTP problem this > morning? > How exactly are you trying to do this? If your answer is freebsd-update, read the manual page for freebsd-update, as it clearly states you cannot use it with -STABLE and -CURRENT. -- Glen Barber ___ 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 partition oddities (6.3/i386 -> 7.x/amd64)
Steve Polyack wrote: I've seen some oddities with the partition and bsdlabel editors in the sysinstall program on the 7.0 and 7.1 releases. The partition editor seems to be reading or parsing the partition table incorrectly. I had a 6.3-RELEASE system with the following layout: /dev/amrd3s1a on / (ufs, local) /dev/amrd3s1g on /opt (ufs, local, soft-updates) /dev/amrd3s1f on /usr (ufs, local, soft-updates) /dev/amrd3s1d on /var (ufs, local, soft-updates) /dev/amrd3s1e on /var/log (ufs, local, soft-updates) Upon booting into the 7.x install media and encountering the FDISK Partition Editor, the partition it's seeing is amrd3*a*s1, as opposed to amrd3s1. Trying to continue with the partition table and bsd labels as is only led to the installer bailing out. As soon as it would attempt to newfs the disk partitions, the installer would error and report that it can't find a device entry in /dev for amrd3*a*s1a. Since preserving the data on the disk was not critical, I was able to continue by deleting the original partition/slice and recreating them. This worked fine. However, I'm still curious as to what the cause of this is. I have seen this before on two other systems while installing 7.x, quite possibly while upgrading from 6.3. When this occurred, I was also moving from i386 to amd64; Is there some kind of offset for partition tables which may change based on architecture? Lastly, here's a screenshot of the partition editor: http://people.collaborativefusion.com/~spolyack/fbsd-install.jpg Unfortunately, I do not have any screenshots of the errors during the newfs step. If this comes up again, I'll be sure to take some. Thanks. This also occurs in VMWare. I'm able to get the exact same behavior by installing a 7.1-RELEASE system (single slice, da0s1), then booting off the install media and start a new installation. It picks up the partition as da0as1 instead of da0s1, making it impossible to use sysinstall while preserving existing partitions. -Steve Polyack ___ 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 Thu, Jan 8, 2009 at 2:55 PM, Freminlins wrote: > 2009/1/8 Jerry McAllister > > > > Beyond that, it is just the pretty pictures > > that are missing. > > sysinstall also works over serial console. No use for pretty pictures > there... Oh My God! If ever you weren't a fan of sysinstall, try YaST over a serial console. http://dannyman.toldme.com/2006/09/06/serial-console-woes/ I still have nightmares. -danny -- http://dannyman.toldme.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Sysinstall
2009/1/8 Jerry McAllister > > Beyond that, it is just the pretty pictures > that are missing. sysinstall also works over serial console. No use for pretty pictures there... > jerry MF. ___ 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 Wed, Jan 07, 2009 at 07:23:20PM -0500, Grant Peel wrote: > Cool to see the thread take this twist, but the original question still > remains: > > How doe one install FreeBSD without the sysinstal utility? You can do it manually, piece by piece. But, otherwise, you don't and you don't want to.Sysinstall works just fine. Mostly it doesn't have the pretty graphics of some fancier systems, but who cares.There are a couple of response sequences that can be confusing - that appear to make you do something more than once unless you skip them the second time you see it and just quit. But you get used to that. Beyond that, it is just the pretty pictures that are missing. jerry > > -Grant > > - Original Message - > From: "Kurt Buff" > To: "Gonzalo Nemmi" > Cc: > Sent: Wednesday, January 07, 2009 6:51 PM > Subject: Re: Sysinstall > > > >On Wed, Jan 7, 2009 at 3:14 PM, Gonzalo Nemmi wrote: > >>On Wednesday 07 January 2009 8:50:39 pm Grant Peel wrote: > >>>Hi all, > >>> > >>>I keep reading in the man pages and elsewhere that 'sysinstall' is > >>>greatly > >>>in need of 'Death'. > >>> > >>>How would one do a fresh install of FBSD without it? > >>> > >>>Is there a replacement in the works? > >>> > >>>-Grant > >> > >>Actually, the more use it, the more I like it .. > >> > >>The only con that I find is that I don't whether it's possible to install > >>Postfix instead of Sendmail by default, thus getting completely rid of > >>Sendmail on my FreeBSD installs. But that probably something that I'm > >>missing. > >> > >>Regards > >>-- > >>Blessings > >>Gonzalo Nemmi > > > >In the curses-based sysinstall of later versions of FBSD (7+, I think > >- haven't done 6 in a while) I do indeed select postfix to install, or > >no MTA at all, then add postfix later. Depends on my mood... > > > >Kurt > >___ > >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" ___ 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 Wed, 7 Jan 2009 19:23:20 -0500, "Grant Peel" wrote: > Cool to see the thread take this twist, but the original question still > remains: > > How doe one install FreeBSD without the sysinstal utility? In principle, you just start a kind of minimal live file system, use its commands (like fdisk, bsdlabel, newfs, then tar etc.) to install the system from the CD or DVD (or the Internet). Neccessary changes to files (like /etc/rc.conf) would have to be done manually (read: you would have to write it by yourself). Not that it wasn't impossible. If I remember correctly, the last time I tried OpenBSD it had a "guided installer" similar to this. No ncurses based dialog driven installer. I don't know how fast the sysinstall utility will disappear, but I would miss it. Personally, a "next, next, next, next, next, next" GUI based installer wouldn't be applealing to me, requiring me to be present during the installation, hah! :-) After a while, you can be really fast with sysinstall, and especially in the early stage of installation its very helpful. I don't use it to install software afterwards. In any case, it would be great to have the choice to still use sysinstall if the new installer is worse. But hey, this is FreeBSD, and up to this point, I haven't seen anything that would be crap from the OS team. (Crap only in ports.) :-) So I would definitely give any new sysinstaller a chance. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Sysinstall
El día Wednesday, January 07, 2009 a las 07:23:20PM -0500, Grant Peel escribió: > Cool to see the thread take this twist, but the original question still > remains: > > How doe one install FreeBSD without the sysinstal utility? > > -Grant Here you go: http://www.unixarea.de/installEeePC.txt Adopt the procedure to your needs. HIH matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion ___ 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 Wednesday 07 January 2009 9:51:11 pm Kurt Buff wrote: > On Wed, Jan 7, 2009 at 3:14 PM, Gonzalo Nemmi wrote: > > On Wednesday 07 January 2009 8:50:39 pm Grant Peel wrote: > >> Hi all, > >> > >> I keep reading in the man pages and elsewhere that 'sysinstall' is > >> greatly in need of 'Death'. > >> > >> How would one do a fresh install of FBSD without it? > >> > >> Is there a replacement in the works? > >> > >> -Grant > > > > Actually, the more use it, the more I like it .. > > > > The only con that I find is that I don't whether it's possible to install > > Postfix instead of Sendmail by default, thus getting completely rid of > > Sendmail on my FreeBSD installs. But that probably something that I'm > > missing. > > > > Regards > > -- > > Blessings > > Gonzalo Nemmi > > In the curses-based sysinstall of later versions of FBSD (7+, I think > - haven't done 6 in a while) I do indeed select postfix to install, or > no MTA at all, then add postfix later. Depends on my mood... > > Kurt Thanks a lot Kurt. Will take that route. Thanks you, really :) Regards -- Blessings Gonzalo Nemmi ___ 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 Wed, Jan 7, 2009 at 7:23 PM, Grant Peel wrote: > Cool to see the thread take this twist, but the original question still > remains: > > How doe one install FreeBSD without the sysinstal utility? > > -Grant > > - Original Message - From: "Kurt Buff" > To: "Gonzalo Nemmi" > Cc: > Sent: Wednesday, January 07, 2009 6:51 PM > Subject: Re: Sysinstall > > > > On Wed, Jan 7, 2009 at 3:14 PM, Gonzalo Nemmi wrote: >> >>> On Wednesday 07 January 2009 8:50:39 pm Grant Peel wrote: >>> >>>> Hi all, >>>> >>>> I keep reading in the man pages and elsewhere that 'sysinstall' is >>>> greatly >>>> in need of 'Death'. >>>> >>>> How would one do a fresh install of FBSD without it? >>>> >>>> Is there a replacement in the works? >>>> >>>> -Grant >>>> >>> >>> Actually, the more use it, the more I like it .. >>> >>> The only con that I find is that I don't whether it's possible to install >>> Postfix instead of Sendmail by default, thus getting completely rid of >>> Sendmail on my FreeBSD installs. But that probably something that I'm >>> missing. >>> >>> Regards >>> -- >>> Blessings >>> Gonzalo Nemmi >>> >> >> In the curses-based sysinstall of later versions of FBSD (7+, I think >> - haven't done 6 in a while) I do indeed select postfix to install, or >> no MTA at all, then add postfix later. Depends on my mood... >> >> Kurt >> ___ >> 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" > you can't unless you do a freebsd from scratch which you can find here http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/index.html there are other ways to do it but I just don't know them. there is finstall in the works ___ 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
Cool to see the thread take this twist, but the original question still remains: How doe one install FreeBSD without the sysinstal utility? -Grant - Original Message - From: "Kurt Buff" To: "Gonzalo Nemmi" Cc: Sent: Wednesday, January 07, 2009 6:51 PM Subject: Re: Sysinstall On Wed, Jan 7, 2009 at 3:14 PM, Gonzalo Nemmi wrote: On Wednesday 07 January 2009 8:50:39 pm Grant Peel wrote: Hi all, I keep reading in the man pages and elsewhere that 'sysinstall' is greatly in need of 'Death'. How would one do a fresh install of FBSD without it? Is there a replacement in the works? -Grant Actually, the more use it, the more I like it .. The only con that I find is that I don't whether it's possible to install Postfix instead of Sendmail by default, thus getting completely rid of Sendmail on my FreeBSD installs. But that probably something that I'm missing. Regards -- Blessings Gonzalo Nemmi In the curses-based sysinstall of later versions of FBSD (7+, I think - haven't done 6 in a while) I do indeed select postfix to install, or no MTA at all, then add postfix later. Depends on my mood... Kurt ___ 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: Sysinstall
On Wed, Jan 7, 2009 at 3:14 PM, Gonzalo Nemmi wrote: > On Wednesday 07 January 2009 8:50:39 pm Grant Peel wrote: >> Hi all, >> >> I keep reading in the man pages and elsewhere that 'sysinstall' is greatly >> in need of 'Death'. >> >> How would one do a fresh install of FBSD without it? >> >> Is there a replacement in the works? >> >> -Grant > > Actually, the more use it, the more I like it .. > > The only con that I find is that I don't whether it's possible to install > Postfix instead of Sendmail by default, thus getting completely rid of > Sendmail on my FreeBSD installs. But that probably something that I'm > missing. > > Regards > -- > Blessings > Gonzalo Nemmi In the curses-based sysinstall of later versions of FBSD (7+, I think - haven't done 6 in a while) I do indeed select postfix to install, or no MTA at all, then add postfix later. Depends on my mood... Kurt ___ 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"
