Re: FreeBSD Install Problem

[Devin Teske]

Not saying your suggestion won't work but…

The last time I had to flip the SATA mode in a BIOS to Compatibility (sometimes 
labeled "Legacy" or "IDE" mode) was when I was installing FreeBSD-4.11 on an 
Intel S5000PSL/R.

I don't think I've come across a machine that required me to change the SATA 
mode before installing FreeBSD 9.

The OP may have said he tried sysinstall approaches but unless he specifically 
said he tried Druid, it actually implies he was comparing FreeBSD 8 media to 
FreeBSD 9's. This is naturally not a fair fight because both install media are 
using different kernels.

That's why I recommend that you try a sysinstall based installer that's 
actually built from/for 9.0-RELEASE. It will boot with a 9.0 kernel and use 
sysinstall to automatically set up the system.

Trying FreeBSD Druid will put the two installers (sysinstall v bsdinstall) on 
the same ground using the same kernel, so we'll be able to tell if its your 
hardware or the installer.
-- 
Devin


On Sep 7, 2012, at 11:46 PM, Dale Scott wrote:

> Check the SATA drive mode in the BIOS. It may need to be set to
> "Compatibility" (or vice versa).
> 
> -Original Message-
> From: owner-freebsd-questi...@freebsd.org
> [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of dte...@freebsd.org
> Sent: Friday, September 07, 2012 6:20 PM
> To: 'Chris Neudorf'; questi...@freebsd.org
> Subject: RE: FreeBSD Install Problem
> 
> 
> 
>> -Original Message-
>> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- 
>> questi...@freebsd.org] On Behalf Of Chris Neudorf
>> Sent: Friday, September 07, 2012 2:10 PM
>> To: questi...@freebsd.org
>> Subject: FreeBSD Install Problem
>> 
>> Hello,
>> 
>> I have a problem installing FreeBSD 9.0 Releaseon my Lenovo Thinkpad 
>> R61i laptop (4GB RAM, 160GB HDD, 32-bit). It doesn't matter if I tried 
>> installing
> it from
>> the CD or the DVD, I still have the same problem. I even tried 
>> re-downloading
> and
>> re-burning a new CD or DVD, and I'm still unable to install. I even 
>> have
> problems
>> going through the "sysinstall" route.
>> 
> 
> Can you try the following?
> 
> http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b57.iso/
> down
> load
> 
> NOTE: New version posted just a couple days ago (but not announced yet;
> in-progress).
> --
> Devin
> 
> 
>> 
>> In the installation process, I'm able to go far to the partitioning area
> in
> where the
>> problem occurs. I click for "Guided" partitioning and then I receive this
> "Abort"
>> message:
>> 
>> Abort
>> --
>> 
>> An installation step has been aborted. Would you like to restart the
> installation or
>> exit the installer?
>> 
>> 
> 
> 
> ---
>> [ Restart ] [ Exit ]
>> 
>> -
>> 
>> When I click restart I end up with the same result, and I end up in a
> neverending
>> cycle of unable to install.
>> 
>> 
>> (I even have a the same problem installing from GhostBSD.)
>> 
>> 
>> 
>> Is there any remedies to this problem?
>> 
>> 
>> Thank you so much,
>> 
>> --Christopher
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"
> 
> _
> The information contained in this message is proprietary and/or
> confidential. If you are not the intended recipient, please: (i) delete the
> message and all copies; (ii) do not disclose, distribute or use the message
> in any manner; and (iii) notify the sender immediately. In addition, please
> be aware that any message addressed to our domain is subject to archiving
> and review by persons other than the intended recipient. Thank you.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

RE: FreeBSD Install Problem

[Dale Scott]

Check the SATA drive mode in the BIOS. It may need to be set to
"Compatibility" (or vice versa).

-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of dte...@freebsd.org
Sent: Friday, September 07, 2012 6:20 PM
To: 'Chris Neudorf'; questi...@freebsd.org
Subject: RE: FreeBSD Install Problem



> -Original Message-
> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- 
> questi...@freebsd.org] On Behalf Of Chris Neudorf
> Sent: Friday, September 07, 2012 2:10 PM
> To: questi...@freebsd.org
> Subject: FreeBSD Install Problem
> 
> Hello,
> 
> I have a problem installing FreeBSD 9.0 Releaseon my Lenovo Thinkpad 
> R61i laptop (4GB RAM, 160GB HDD, 32-bit). It doesn't matter if I tried 
> installing
it from
> the CD or the DVD, I still have the same problem. I even tried 
> re-downloading
and
> re-burning a new CD or DVD, and I'm still unable to install. I even 
> have
problems
> going through the "sysinstall" route.
> 

Can you try the following?

http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b57.iso/
down
load

NOTE: New version posted just a couple days ago (but not announced yet;
in-progress).
--
Devin


> 
> In the installation process, I'm able to go far to the partitioning area
in
where the
> problem occurs. I click for "Guided" partitioning and then I receive this
"Abort"
> message:
> 
> Abort
> --
> 
> An installation step has been aborted. Would you like to restart the
installation or
> exit the installer?
> 
>


---
> [ Restart ]     [ Exit ]
> 
> -
> 
> When I click restart I end up with the same result, and I end up in a
neverending
> cycle of unable to install.
> 
> 
> (I even have a the same problem installing from GhostBSD.)
> 
> 
> 
> Is there any remedies to this problem?
> 
> 
> Thank you so much,
> 
> --Christopher
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"

_
The information contained in this message is proprietary and/or
confidential. If you are not the intended recipient, please: (i) delete the
message and all copies; (ii) do not disclose, distribute or use the message
in any manner; and (iii) notify the sender immediately. In addition, please
be aware that any message addressed to our domain is subject to archiving
and review by persons other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
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: FreeBSD Install Problem

[dteske]

> -Original Message-
> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
> questi...@freebsd.org] On Behalf Of Chris Neudorf
> Sent: Friday, September 07, 2012 2:10 PM
> To: questi...@freebsd.org
> Subject: FreeBSD Install Problem
> 
> Hello,
> 
> I have a problem installing FreeBSD 9.0 Releaseon my Lenovo Thinkpad R61i
> laptop (4GB RAM, 160GB HDD, 32-bit). It doesn't matter if I tried installing
it from
> the CD or the DVD, I still have the same problem. I even tried re-downloading
and
> re-burning a new CD or DVD, and I'm still unable to install. I even have
problems
> going through the "sysinstall" route.
> 

Can you try the following?

http://sourceforge.net/projects/druidbsd/files/FreeBSD-9.0_Druid-1.0b57.iso/down
load

NOTE: New version posted just a couple days ago (but not announced yet;
in-progress).
-- 
Devin


> 
> In the installation process, I'm able to go far to the partitioning area in
where the
> problem occurs. I click for "Guided" partitioning and then I receive this
"Abort"
> message:
> 
> Abort
> --
> 
> An installation step has been aborted. Would you like to restart the
installation or
> exit the installer?
> 
>

---
> [ Restart ]     [ Exit ]
> 
> -
> 
> When I click restart I end up with the same result, and I end up in a
neverending
> cycle of unable to install.
> 
> 
> (I even have a the same problem installing from GhostBSD.)
> 
> 
> 
> Is there any remedies to this problem?
> 
> 
> Thank you so much,
> 
> --Christopher
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD Install Problem

[lokada...@gmx.de]

On 09/07/12 23:10, Chris Neudorf wrote:

An installation step has been aborted. Would you like to restart the 
installation or exit the installer?

---
[ Restart ] [ Exit ]

-

When I click restart I end up with the same result, and I end up in a 
neverending cycle of unable to install.


(I even have a the same problem installing from GhostBSD.)
Is there any remedies to this problem?

In Bios is legacy support for sata enable?
On some systems this is a problem.
___
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 Install Problem

[Chris Neudorf]

Hello,

I have a problem installing FreeBSD 9.0 Releaseon my Lenovo Thinkpad R61i 
laptop (4GB RAM, 160GB HDD, 32-bit). It doesn't matter if I tried installing it 
from the CD or the DVD, I still have the same problem. I even tried 
re-downloading and re-burning a new CD or DVD, and I'm still unable to install. 
I even have problems going through the "sysinstall" route.


In the installation process, I'm able to go far to the partitioning area in 
where the problem occurs. I click for "Guided" partitioning and then I receive 
this "Abort" message:

Abort
--

An installation step has been aborted. Would you like to restart the 
installation or exit the installer?

---
[ Restart ]     [ Exit ]

-

When I click restart I end up with the same result, and I end up in a 
neverending cycle of unable to install.


(I even have a the same problem installing from GhostBSD.) 



Is there any remedies to this problem? 


Thank you so much,

--Christopher
___
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: pxegrub + FreeBSD install

[Rick Miller]

I was able to figure out how to pass the variables to the FreeBSD
mfsroot.  I did so by modifying the grub.cfg file like the below:

menuentry "freebsd82-x86_64" {
   kfreebsd /boot/kernel/kernel
   kfreebsd_loadenv /boot/device.hints
   kfreebsd_module /boot/mfsroot.gz type=mfs_root
   set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
   set kFreeBSD.boot.nfsroot.server=$pxe_default_server
   set kFreeBSD.boot.netif.hwaddr=$net_pxe_mac
   set kFreeBSD.boot.netif.ip=$net_pxe_ip
   set kFreeBSD.dhcp.host-name=$net_pxe_hostname
}


On Tue, Apr 24, 2012 at 2:10 PM, Rick Miller  wrote:
> Hi All,
>
> I am attempting to build FreeBSD 8.x-RELEASE over the network via PXE.
>  I chain pxegrub to pxelinux and load the FreeBSD kernel and mfsroot
> through pxegrub with the following:
>
> menuentry "freebsd-x86_64" {
>   kfreebsd /boot/kernel/kernel
>   kfreebsd_loadenv /boot/device.hints
>   kfreebsd_module /boot/mfsroot.gz type=mfs_root
>   set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
> }
>
> The mfsroot.gz is from the installation DVD with a couple of scripts
> and an install.cfg which result in a non-interactive install.  I set
> variables necessary to allow sysinstall to retrieve the expected
> files.  The variables (previously) are populated as follows:
>
> server=`kenv -q boot.nfsroot.server`
> mac=`kenv -q boot.netif.hwaddr`
> ip=`kenv -q boot.netif.ip`
> nm=`kenv -q boot.netif.netmask`
> gw=`kenv -q boot.netif.gateway`
> name=`kenv -q dhcp.host-name`
> route=`kenv -q dhcp.routers`
>
>
> The mfsroot.gz does not see these as set when the environment loads
> through pxegrub.  If I load the environment through pxeboot.bs, the
> variables populate ok.  Unfortunately, with pxeboot.bs I experience
> extremely high tftp failure rates when compared to pxegrub.
>
> My question is how should I populate these variables in the mfsroot.gz
> when loading via pxegrub?
>
>
> --
> Take care
> Rick Miller



-- 
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"

pxegrub + FreeBSD install

[Rick Miller]

Hi All,

I am attempting to build FreeBSD 8.x-RELEASE over the network via PXE.
 I chain pxegrub to pxelinux and load the FreeBSD kernel and mfsroot
through pxegrub with the following:

menuentry "freebsd-x86_64" {
   kfreebsd /boot/kernel/kernel
   kfreebsd_loadenv /boot/device.hints
   kfreebsd_module /boot/mfsroot.gz type=mfs_root
   set kFreeBSD.vfs.root.mountfrom=ufs:/dev/md0c
}

The mfsroot.gz is from the installation DVD with a couple of scripts
and an install.cfg which result in a non-interactive install.  I set
variables necessary to allow sysinstall to retrieve the expected
files.  The variables (previously) are populated as follows:

server=`kenv -q boot.nfsroot.server`
mac=`kenv -q boot.netif.hwaddr`
ip=`kenv -q boot.netif.ip`
nm=`kenv -q boot.netif.netmask`
gw=`kenv -q boot.netif.gateway`
name=`kenv -q dhcp.host-name`
route=`kenv -q dhcp.routers`


The mfsroot.gz does not see these as set when the environment loads
through pxegrub.  If I load the environment through pxeboot.bs, the
variables populate ok.  Unfortunately, with pxeboot.bs I experience
extremely high tftp failure rates when compared to pxegrub.

My question is how should I populate these variables in the mfsroot.gz
when loading via pxegrub?


-- 
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: domain required for FreeBSD install and isc dhcp

[Chris Whitehouse]

On 20/04/2012 20:56, Chuck Swiger wrote:

On Apr 20, 2012, at 12:40 PM, Chris Whitehouse wrote:

I've wondered this for ages. When you set up networking as part of
installing FreeBSD one of the pieces of information requested is a
domain name. Also setting up dhcp.conf one of the fields is domain
name. What do you do if you don't have your own domain?


There have been a few domains which are permanently reserved and will
never be assigned elsewhere:

http://www.ietf.org/rfc/rfc2606.txt

You can reasonably claim to be part of your ISP's domain, if you
prefer. .lan might be reasonable, or .local, although the latter
might conflict with Bonjour/Zeroconf.


I've never supplied a domain name when installing FreeBSD and it
doesn't seem to have been a problem. I'm just setting up dhcp for
the first time and I don't know if it matters here.


It's mainly used to setup the default search domain which clients use
to find local unqualified hosts.

Regards,

Thanks Chuck, I went with .lan.

cheers

Chris
___
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: domain required for FreeBSD install and isc dhcp

[Chuck Swiger]

On Apr 20, 2012, at 12:40 PM, Chris Whitehouse wrote:
> I've wondered this for ages. When you set up networking as part of installing 
> FreeBSD one of the pieces of information requested is a domain name. Also 
> setting up dhcp.conf one of the fields is domain name. What do you do if you 
> don't have your own domain?

There have been a few domains which are permanently reserved and will never be 
assigned elsewhere:

  http://www.ietf.org/rfc/rfc2606.txt

You can reasonably claim to be part of your ISP's domain, if you prefer.
.lan might be reasonable, or .local, although the latter might conflict with 
Bonjour/Zeroconf.

> I've never supplied a domain name when installing FreeBSD and it doesn't seem 
> to have been a problem. I'm just setting up dhcp for the first time and I 
> don't know if it matters here.

It's mainly used to setup the default search domain which clients use to find 
local unqualified hosts.

Regards,
-- 
-Chuck

___
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"

domain required for FreeBSD install and isc dhcp

[Chris Whitehouse]

hi,

I've wondered this for ages. When you set up networking as part of 
installing FreeBSD one of the pieces of information requested is a 
domain name. Also setting up dhcp.conf one of the fields is domain name. 
What do you do if you don't have your own domain?


I've never supplied a domain name when installing FreeBSD and it doesn't 
seem to have been a problem. I'm just setting up dhcp for the first time 
and I don't know if it matters here.


thanks

Chris
___
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"

iBook G3 -- FreeBSD Install -- USB Wireless adapter support?

[David A.]

Someone with experience with a similar hardware?

I want to know if is viable to install FreeBSD on an iBook G3 (PowerPC
800MHz 12''), the main focus is to get working the network hardware,
also if there's someone with the same experience and could let me know
which wireless network adapter (USB) could work? Would be really
appreciated.

The iBook is fully functional was bought from eBay for less than $60
the only missing piece is the Airport card, but anyway isn't supported
on FreeBSD (i think
http://www.freebsd.org/releases/8.1R/hardware.html#WLAN ).


Thanks in advance!

 -- David A.
___
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: Not booting after freebsd install

[Bruce Cran]

On Tue, 17 Aug 2010 10:17:14 +0530
Mubeesh ali  wrote:

> thanks bruce. Here the laptop is stuck at bios splash screen. here if
> i cannot get to bios set up.

You'll need to either follow instructions for resetting the CMOS
battery on the laptop (probably involving partial disassembly), or
remove the drive and repartition it in a differentc computer.

-- 
Bruce
___
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: Not booting after freebsd install

[Bruce Cran]

   Dear Sir/Madam,
   Your email was unable reach the intended person that you were sending
   it to.
   For more information on our business please click on the following
   link:
   [1]Click here for our website
   We look forward to your continued business in the future.
   Regards,
   Webmaster

References

   1. http://www.downwind.com.au/avdir/rd.php?id=7564
___
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: Not booting after freebsd install

[Mubeesh ali]

thanks bruce. Here the laptop is stuck at bios splash screen. here if i
cannot get to bios set up.


thanks,

Mubeesh

On Tue, Aug 17, 2010 at 3:05 AM, Bruce Cran  wrote:

> On Mon, 16 Aug 2010 22:30:07 +0100
> Bruce Cran  wrote:
>
> > Specific configurations of partitions (or rather, byte patterns) are
> > known to cause some BIOSes to hang during POST - on mine it was
> > Windows and FreeBSD. If you can, try switching from AHCI to IDE or
> > vice versa. Otherwise you might have to remove the drive and
> > reconfigure it on another system with a less buggy BIOS.
> >
>
> For reference, my problem was due to the AHCI BIOS:
>
> http://communities.intel.com/thread/10768;jsessionid=BE85ABF882B97023AE879865A741FDD6.node7COM
> It was solved by resetting the CMOS so I could get into the setup menu.
>
> --
> Bruce Cran
>



-- 
Best  Regards,

Mubeesh Ali.V.M
___
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: Not booting after freebsd install

[Bruce Cran]

On Mon, 16 Aug 2010 22:30:07 +0100
Bruce Cran  wrote:

> Specific configurations of partitions (or rather, byte patterns) are
> known to cause some BIOSes to hang during POST - on mine it was
> Windows and FreeBSD. If you can, try switching from AHCI to IDE or
> vice versa. Otherwise you might have to remove the drive and
> reconfigure it on another system with a less buggy BIOS.
> 

For reference, my problem was due to the AHCI BIOS:
http://communities.intel.com/thread/10768;jsessionid=BE85ABF882B97023AE879865A741FDD6.node7COM
It was solved by resetting the CMOS so I could get into the setup menu.

-- 
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: Not booting after freebsd install

[Bruce Cran]

On Mon, 16 Aug 2010 23:54:51 +0530
Mubeesh ali  wrote:

> Hi, i have an acer 5745 which had ubuntu running not booting after an
> attempted freebsd install .i understand that i  might have wiped by
> choosing auto partition :-( and had not written mbr so that we could
> manage all from grub .now the laptop is stuck at bios splash screen.it
> refuses to go even to bios setup.
> please advice how i can recover and start over

Specific configurations of partitions (or rather, byte patterns) are
known to cause some BIOSes to hang during POST - on mine it was Windows
and FreeBSD. If you can, try switching from AHCI to IDE or vice versa.
Otherwise you might have to remove the drive and reconfigure it on
another system with a less buggy BIOS.

-- 
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"

Not booting after freebsd install

[Mubeesh ali]

Hi, i have an acer 5745 which had ubuntu running not booting after an
attempted freebsd install .i understand that i  might have wiped by
choosing auto partition :-( and had not written mbr so that we could
manage all from grub .now the laptop is stuck at bios splash screen.it
refuses to go even to bios setup.
please advice how i can recover and start over

Thanks
mubeesh

-- 
Best  Regards,

Mubeesh Ali.V.M
___
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: freebsd-install upgrade, how many install phases required

[Matthew Seaman]

On 23/07/2010 17:19:54, Martin Koch Andersen wrote:
> Hi,
> 
> Will freebsd-install upgrade tell you, if any libraries version numbers got 
> bumped, and thus if installed packages needs rebuilding?
> 
> I followed the handbook and did the 8.0-RELEASE to 8.1-RELEASE upgrade like:
> 
> freebsd-update -r 8.1-RELEASE upgrade
> freebsd-update install
> shutdown -r now
> freebsd-update install

freebsd-update only updates the *base* system.  It doesn't update the
ports tree at all.  For that, you need portsnap, which works very much
like freebsd-update (or else one of a number of alternatives like
csup(1), which work differently.)

Once you've updated the ports tree using portsnap (or whatever) then you
can update your installed ports from it, which is where tools like
portupgrade(1) or portmaster(1) come in.  portupgrade(1) won't find any
work to do unless you have run portsnap first.

> And then:
> 
> portupgrade -af
> freebsd-update install
> shutdown -r now
> 
> But was this last round of rebuilding installed ports etc. really needed? Or 
> would the second "freebsd-update install" have told me if it was? In any 
> case, the last "freebsd-update install" did nothing.

If the OS major version is the same, then the shlib ABI version on all
the shlibs in the base system is still the same.  That's a guarantee by
the FreeBSD project.  Or in other words, binary compatibility between
all 8.x releases (or all 7.x, or whatever).  So, there is no reason to
update ports that is caused by using freebsd-update to do a minor
version upgrade.  No, you didn't need to run 'portupgrade -af' at all.

Running portsnap and then 'portupgrade -a' would however have been a
reasonably good idea since you were in an upgrading mood.  Ports may
well have become out of date due to the normal updating of the ports
tree over the passage of time.  This is largely independent of
development schedules in the base system, so should there can be updates
available to apply at just about any time.

On the other hand, if you do a *major* version upgrade, you simply *do*
need to reinstall every port.  freebsd-update warns you about this
directly, and the necessity of doing so is well documented all over the
place eg. at Colin Percival's blog:
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html

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

freebsd-install upgrade, how many install phases required

[Martin Koch Andersen]

Hi,

Will freebsd-install upgrade tell you, if any libraries version numbers got 
bumped, and thus if installed packages needs rebuilding?

I followed the handbook and did the 8.0-RELEASE to 8.1-RELEASE upgrade like:

freebsd-update -r 8.1-RELEASE upgrade
freebsd-update install
shutdown -r now
freebsd-update install

And then:

portupgrade -af
freebsd-update install
shutdown -r now

But was this last round of rebuilding installed ports etc. really needed? Or 
would the second "freebsd-update install" have told me if it was? In any case, 
the last "freebsd-update install" did nothing.

Have a nice weekend all.

Kind regards,

-- 
Martin Koch Andersen
http://925.dk___
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: FreeBSD install Error

[Georghy]

Georghy a écrit :

Hi folks,
I'm experiencing a problem when I try to install FreeBSD on a Virtual 
Server using KVM,
The first part of the installation was fine but after setting all the 
option (I use a custom installation of FreeBSD)

the installation encounter an error :
"Write failure on transfer! (wrote -1 bytes of 1425408 bytes)"
I tried to use "alt"+"2" but it doesn't show any clue for that error
Do you know how should I fix it ?


Forget it, I have found what's wrong.
But do you know how do i insert a "." when I type "." the screen 
displays ";"

Maybe it is virt-manager related

--
Cordialement, / Greetings,
Georghy FUSCO

___
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 install Error

[Georghy]

Hi folks,
I'm experiencing a problem when I try to install FreeBSD on a Virtual 
Server using KVM,
The first part of the installation was fine but after setting all the 
option (I use a custom installation of FreeBSD)

the installation encounter an error :
"Write failure on transfer! (wrote -1 bytes of 1425408 bytes)"
I tried to use "alt"+"2" but it doesn't show any clue for that error
Do you know how should I fix it ?

--
Cordialement, / Greetings,
Georghy FUSCO

___
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: freebsd install from floppy

[Polytropon]

On Sun, 7 Mar 2010 13:58:07 -0800, Walt Pawley  wrote:
> At 1:28 PM -0500 3/6/10, Chuck Swiger wrote:
> 
> >While I think floppy drives are still useful for BIOS updates and the
> >like, it's not just Apple that isn't selling machines with floppy
> >drives any more.  Go to HP or Dell and try to buy a new machine with a
> >floppy drive-- they don't sell them anymore, either...
> 
> I certainly can't argue that modern machines typically have
> floppy drives ... even if the motherboard supports one.
> 
> So what?

I think he wanted to point out that even if motherboards
today still support floppy disk drives, the computer itself
often does omit one. Instead, a blank cover is used for
the intended slot, or a SD + CF + who knows what reader
comes built-in.

This, of course, doesn't stop you from building one (or
two) into your box. But manufacturers seem to have agreed
that - especially in the home consumer market, which is
their most important playing field - floppies aren't
used anymore.

But soon, the ability to connect a floppy will disappear.
First, the connectors will vanish, followed by the
functionality within the hardware (e. g. BIOS) to
access them.

You find such a situation in notebooks. They don't have
floppy drives for many years now, and the only way to
access floppies with them is to buy (!) an external drive,
usually USB based. (I had such a situation with a customer
who needs floppy support, but had to buy a new notebook.
Imagine his surprise! While home customers already have
accepted that there are no floppies anymore, corporate
customers that work in a specific field still rely on
their presence.)



> Not everyone in the world throws their three year old
> computer in the trash so they can stay "up to date."

Average home consumers do. In fields where it is important
to have access to data and programs for much longer time,
you often don't find PCs, e. g. in the (still alive) mainframe
area, notably IBM's.



> I, for one,
> find it very annoying that new versions of software which once
> worked just fine on equipment I still use every day no longer
> work in their current incarnations.

That's a feeling I had, too, when upgrading my home system
from a perfectly working (until the total crash) 5.4 to 7.0,
from XFree86 to X.org. Lots of things had to be done, and
the observation that if you update things on FreeBSD, they
get better and faster, doesn't seem to be confirmed this
time (except for the OS) - speed down, usability down, overhead
up. But that, what we mostly call "bloat", be it in hardware
or in software, seems to be a needed motor for development,
at least I have been told that. :-)

It's a bit scary that the 300 MHz P2 (FreeBSD 5 and apps)
works much faster than my 2000 MHz P4 (FreeBSD 7 and apps).



> Delving into several such
> cases, I've found comments to the effect that functions are
> removed because no one uses the old stuff (ie. three years
> old) any more.

THere are still situations where you depend on three (or thirteen)
years old stuff, especially in data analytics and forensics.

The common situation, especially with home users, is to
constantly migrate data from one format to another (again,
this may mean file format as well as storage media), to
keep them accessible.

By the way, I have floppies older than twenty (20!) years
that work perfectly - that's much longer as a "modern" DVD
driver works. :-)

This leads me to my conclusion again: The older something
is, the longer it lasts. Mostly.




-- 
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: freebsd install from floppy

[Walt Pawley]

At 1:28 PM -0500 3/6/10, Chuck Swiger wrote:

>While I think floppy drives are still useful for BIOS updates and the
>like, it's not just Apple that isn't selling machines with floppy
>drives any more.  Go to HP or Dell and try to buy a new machine with a
>floppy drive-- they don't sell them anymore, either...

I certainly can't argue that modern machines typically have
floppy drives ... even if the motherboard supports one.

So what?

Not everyone in the world throws their three year old
computer in the trash so they can stay "up to date." I, for one,
find it very annoying that new versions of software which once
worked just fine on equipment I still use every day no longer
work in their current incarnations. Delving into several such
cases, I've found comments to the effect that functions are
removed because no one uses the old stuff (ie. three years
old) any more.
-- 

Walter M. Pawley 
Wump Research & Company
676 River Bend Road, Roseburg, OR 97471
 541-672-8975
___
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: freebsd install from floppy

[Chuck Swiger]

On Mar 6, 2010, at 12:44 PM, James Phillips wrote:
Correction: Apple stopped selling computers with floppy drives about  
10 years ago. The floppy drive is not obsolete because there is  
still no viable replacement that has the same (or better)  
functionality.


While I think floppy drives are still useful for BIOS updates and the  
like, it's not just Apple that isn't selling machines with floppy  
drives any more.  Go to HP or Dell and try to buy a new machine with a  
floppy drive-- they don't sell them anymore, either...


The problem with USB sticks is that they don't have user-accessible  
write-protect tabs. If you plug a USB stick into a compromised  
system, it is "tainted."



Some USB flash drives have write-protect switches:

  http://www.newegg.com/Product/Product.aspx?Item=N82E16820141486

Regards,
--
-Chuck

___
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: freebsd install from floppy

[James Phillips]

> Date: Sat, 06 Mar 2010 09:54:38 +
> From: Matthew Seaman 
> Subject: Re: freebsd install from floppy
> To: per...@pluto.rain.com
> Cc: questi...@freebsd.org,
> plukaw...@gmail.com
> Message-ID: <4b92265e.5030...@infracaninophile.co.uk>
> Content-Type: text/plain; charset=UTF-8
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 06/03/2010 09:26:22, per...@pluto.rain.com
> wrote:
> > I seem to remember something about the floppy images
> being dropped
> > because few current (or even recent) systems have a
> floppy drive at
> > all, much less a bootable one.
> 
> Yeah, but the floppy disk drive was already obsolete 10
> years ago.  It's
> just taken this long for it to fall down dead.  Good
> riddance to it.
> Why would anyone want an unreliable, slow and tiny capacity
> device when
> you can get GiB capacity USB sticks everywhere nowadays?
> 

Correction: Apple stopped selling computers with floppy drives about 10 years 
ago. The floppy drive is not obsolete because there is still no viable 
replacement that has the same (or better) functionality.

The problem with USB sticks is that they don't have user-accessible 
write-protect tabs. If you plug a USB stick into a compromised system, it is 
"tainted."

Secure Digital Cards have a write-protect tab, but "Secure" means "secure 
against copying" (Copy Protection for Recordable Media), making them 
inappropriate for "known good" filesystem images.

I have started using CD-ROM booting to install FreeBSD. The problem with CD-R 
images is that any "tweaks" to the disk image require burning a new disk.

Regards,

James Phillips

Recent Slashdot exchange about exactly this issue:
http://slashdot.org/comments.pl?sid=1565678&cid=31302916




  __
Make your browsing faster, safer, and easier with the new Internet Explorer® 8. 
Optimized for Yahoo! Get it Now for Free! at 
http://downloads.yahoo.com/ca/internetexplorer/

___
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: freebsd install from floppy

[Polytropon]

On Sat, 6 Mar 2010 12:24:30 +0100, Piotr Lukawski  
wrote:
> In many situations, especially for and old or non standard equipment
> floppies are the best or even the only solution.
> [...]
> The decision to make floppies obsolete is very bad, because it is still
> needed by many people.

Sometimes you simply stick with systems that just work,
even if they are 10 years old - and older. So a machine
with no USB support can likely exist. It gets even more
interesting if you need to read and write floppies to
keep computer systems alive for a museum (see 5,25"
floppies). Sometimes, a floppy is completely sufficient
and easy to use, e. g. when transfering some config
files to a system without network and USB; the tar
utility can be used to directly operate on floppies,
which is very useful, and maybe even faster than using
USB (device detection, mounting etc.).

So when booting via CD, USB or network isn't possible,
what are the options?

Okay, with FreeBSD, you can extract the hard disk,
place it into a different computer and then install
the OS there; retransfer the hard disk to the original
computer and everything should work from now on.
(Special hardware may require additional configuration,
but the base system doesn't care on what kind of
hardware it is running, basically.)

The reason to still use such old systems can be very
different, for example "just works" is one of the main
reasons. Others may include accurate and reliable
working, or less power consumption. (One thing that
I could observe over the years: The older hardware
is, the longer it works - mostly.) Another reason
could be the idea of resisting to buy something new
that does the same as the old stuff, an action that
costs money and creates electronic waste.

I still have such a system which I keep for nostalgia
mostly: It introduced me to FreeBSD: A 150MHz P1
with 128 MB SDR-SDRAM, SCSI CD (which I can't boot
from), no USB, but Ethernet (which I also can't
boot from), and it's in a perfect condition, still
usable as a workstation. It does nearly everything
my current workstation (P4, 2GHz) can do, and some
of the things even faster. I'm sure most of you can't
even imagine that. :-)

FreeBSD has always impressed me by providing working (!)
drivers for older stuff that still works, e. g. SCSI
PCI cards, SCSI scanners and PD drives. Most hardware
works out of the box, and for very special cases, there
are modules or kernel options.

And why use FreeBSD? Because it runs faster on the same
hardware with every new release. That's something
other operating systems can't do. Settings where you
update your software, then need to update your hardware,
and then still don't feel that anything is faster at
all, are known.

If floppy images aren't included on the install CD / DVD
or via FTP, then at least there should be a simple means
to generate them, e. g. "make floppies".

I wouldn't like to see floppies disappear for, let's say,
the next 10 years, as much as I dislike floppy media per
se.

By the way, their form factor is superior to CDs and
DVDs in every concern! Give the world a rewritable optical
media the size of a Minidisc and the world is yours.
I don't like the idea that I need a drive with the size
of a full-featured computer to use media that dissolves
chemically and gets unreadable if touched with the finger
on the wrong side. :-)


-- 
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: freebsd install from floppy

[Piotr Lukawski]

In many situations, especially for and old or non standard equipment
floppies are the best or even the only solution.
Actually if I haven't found the solution to use floppy to install FreeBSD, I
would be forced to use another system eg. OpenBSD instead, even if I prefer
FreeBSD.
The decision to make floppies obsolete is very bad, because it is still
needed by many people.

On 6 March 2010 10:54, Matthew Seaman wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 06/03/2010 09:26:22, per...@pluto.rain.com wrote:
> > I seem to remember something about the floppy images being dropped
> > because few current (or even recent) systems have a floppy drive at
> > all, much less a bootable one.
>
> Yeah, but the floppy disk drive was already obsolete 10 years ago.  It's
> just taken this long for it to fall down dead.  Good riddance to it.
> Why would anyone want an unreliable, slow and tiny capacity device when
> you can get GiB capacity USB sticks everywhere nowadays?
>
> Not providing floppy disk installation images doesn't imply dropping
> kernel support for floppy drives.  My ancient system has a floppy, and
> if I blew the dust out of it and could find some media it should work
> just fine with FreeBSD 8.0.
>
> In fact, if you need to support older equipment, free OSes like FreeBSD
> are really your only choice.  Drivers for old devices tend to stick
> around in the source tree for much longer than in any commercial
> offering.  They might suffer from bit-rot due to lack of developer
> access to samples of kit, but if you really need something like that
> fixed you probably could get patches.  In fact, I think the primary
> reason for dropping old device drivers is usually because they don't
> receive any attention during the occasional code refactoring that
> occurs: no one complains, and the device sits around unusable or needing
> special backwards compatibility shims for a while, then gets quietly
> deleted.
>
>
>
>
> - --
> 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/
>
> iEYEARECAAYFAkuSJl4ACgkQ8Mjk52CukIxSWACfSkJ6k09ig0sR5lctO7tooF1k
> NnUAnRrWUeDMssvWDx7rvzMgPWb3fHSw
> =3zRd
> -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: freebsd install from floppy

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 06/03/2010 09:26:22, per...@pluto.rain.com wrote:
> I seem to remember something about the floppy images being dropped
> because few current (or even recent) systems have a floppy drive at
> all, much less a bootable one.

Yeah, but the floppy disk drive was already obsolete 10 years ago.  It's
just taken this long for it to fall down dead.  Good riddance to it.
Why would anyone want an unreliable, slow and tiny capacity device when
you can get GiB capacity USB sticks everywhere nowadays?

Not providing floppy disk installation images doesn't imply dropping
kernel support for floppy drives.  My ancient system has a floppy, and
if I blew the dust out of it and could find some media it should work
just fine with FreeBSD 8.0.

In fact, if you need to support older equipment, free OSes like FreeBSD
are really your only choice.  Drivers for old devices tend to stick
around in the source tree for much longer than in any commercial
offering.  They might suffer from bit-rot due to lack of developer
access to samples of kit, but if you really need something like that
fixed you probably could get patches.  In fact, I think the primary
reason for dropping old device drivers is usually because they don't
receive any attention during the occasional code refactoring that
occurs: no one complains, and the device sits around unusable or needing
special backwards compatibility shims for a while, then gets quietly
deleted.




- -- 
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/

iEYEARECAAYFAkuSJl4ACgkQ8Mjk52CukIxSWACfSkJ6k09ig0sR5lctO7tooF1k
NnUAnRrWUeDMssvWDx7rvzMgPWb3fHSw
=3zRd
-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: freebsd install from floppy

[perryh]

Piotr Lukawski  wrote:
> ... I really cannot understand why nobody can change
> just one parameter and put the file in a proper place in
> ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/

I seem to remember something about the floppy images being dropped
because few current (or even recent) systems have a floppy drive at
all, much less a bootable one.

I sure hope they don't start applying the same reasoning to drivers
for old-ish devices.  Some of us do not rush out and acquire
the latest/greatest whiz-giz every few months just because it's
available.
___
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: freebsd install from floppy

[ill...@gmail.com]

On 5 March 2010 13:51, Piotr Lukawski  wrote:
> On 4 March 2010 05:51, ill...@gmail.com  wrote:
>> On 3 March 2010 07:33, Piotr Lukawski  wrote:
>> > Dears,
>> > I need to install Freebsd 8.0 using floppy and then ftp, but there are
>> > no
>> > floppy images
. . .
>> > Could you please produce install floppy images for Freebsd 8.0? Please
>> > please please. I have no power to do the install of 7, upgrade and fail
>> > again :-(
>>
>> Have you tried installing 8.0-RELEASE from your
>> 7.x floppies?  I have heard rumour that it is possible
>> by just changing the release name under "View/Set
>> Various Installation Options".
>>
> Illoai,
> Thanks a lot! Your solution works - system is up and running now :-)
> However, in such a case I really cannot understand why nobody can change
> just one parameter and put the file in a proper place in
> ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/.
> It can simplify life for many people.
>

I'm glad it worked for you. :)

I'm not aware of why the floppy images are no longer
being generated, however, just repackaging the 7.x
floppies is probably not the best idea:  you can select
a couple of options under 7.x that will likely break an
8.x install (I'm under the impression that "Dangerously
Dedicated" disks do this).

-- 
--
___
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: freebsd install from floppy

[Piotr Lukawski]

Illoai,
Thanks a lot! Your solution works - system is up and running now :-)
However, in such a case I really cannot understand why nobody can change
just one parameter and put the file in a proper place in
ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/
.
It can simplify life for many people.
Thanks again for your help.
Take care,
Piotr

On 4 March 2010 05:51, ill...@gmail.com  wrote:

> On 3 March 2010 07:33, Piotr Lukawski  wrote:
> > Dears,
> > I need to install Freebsd 8.0 using floppy and then ftp, but there are no
> > floppy images in
> > ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/<
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/
> >mentioned
> > in
> >
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html
> > I tried so install Freebsd 7 using availiable floppy (successful) and
> update
> > it to 8.0 (after 3 days finally error and now now whole /usr directory so
> I
> > am stacked).
> > Could you please produce install floppy images for Freebsd 8.0? Please
> > please please. I have no power to do the install of 7, upgrade and fail
> > again :-(
> > Thanks in adavance.
> > Piotr
>
> Have you tried installing 8.0-RELEASE from your
> 7.x floppies?  I have heard rumour that it is possible
> by just changing the release name under "View/Set
> Various Installation Options".
>
> --
> --
>
___
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: freebsd install from floppy

[herbert langhans]

On Wed, Mar 03, 2010 at 01:33:52PM +0100, Piotr Lukawski wrote:
> Dears,
> I need to install Freebsd 8.0 using floppy and then ftp, but there are no
> floppy images in
>
+ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned
> in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html
> I tried so install Freebsd 7 using availiable floppy (successful) and update
> it to 8.0 (after 3 days finally error and now now whole /usr directory so I
> am stacked).
> Could you please produce install floppy images for Freebsd 8.0? Please
> please please. I have no power to do the install of 7, upgrade and fail
> again :-(
> Thanks in adavance.
> Piotr
> ___

Yes, I definitly vote for the release of floppy images too! In my case its the 
SCSI-CD drives what do not allow me to boot from a CD.

It might be old fashioned, but its very easy just to boot the floppy and then 
install all over ftp! I guess there are still a couple of systems (old
+laptops, servers) which require it.

Thanks
herb langhans


-- 
sprachtraining langhans
herbert langhans, warschau
http://www.langhans.com.pl
herbert dot raimund at gmx dot net
+0048 603 341 441

___
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: freebsd install from floppy

[ill...@gmail.com]

On 3 March 2010 07:33, Piotr Lukawski  wrote:
> Dears,
> I need to install Freebsd 8.0 using floppy and then ftp, but there are no
> floppy images in
> ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned
> in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html
> I tried so install Freebsd 7 using availiable floppy (successful) and update
> it to 8.0 (after 3 days finally error and now now whole /usr directory so I
> am stacked).
> Could you please produce install floppy images for Freebsd 8.0? Please
> please please. I have no power to do the install of 7, upgrade and fail
> again :-(
> Thanks in adavance.
> Piotr

Have you tried installing 8.0-RELEASE from your
7.x floppies?  I have heard rumour that it is possible
by just changing the release name under "View/Set
Various Installation Options".

-- 
--
___
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 install from floppy

[Piotr Lukawski]

Dears,
I need to install Freebsd 8.0 using floppy and then ftp, but there are no
floppy images in
ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned
in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html
I tried so install Freebsd 7 using availiable floppy (successful) and update
it to 8.0 (after 3 days finally error and now now whole /usr directory so I
am stacked).
Could you please produce install floppy images for Freebsd 8.0? Please
please please. I have no power to do the install of 7, upgrade and fail
again :-(
Thanks in adavance.
Piotr
___
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"

unateended FreeBSD install + zfs + gpt

[kickbsd kickbsd]

Hi!

I've modified mfsBSD scripts http://people.freebsd.org/~mm/mfsbsd/
to make unattended installer for FreeBSD 8.0-RC1 on GPT ZFS root. I've 
successfully installed 3 different servers
with that set of scrips. Modified scrips can be downloaded from 
http://unixdom.com/kickbsd/
Modified files are interfaces and interfaces.conf (that script now tries to 
auto detect first NIC which plugged) + new zinstall script + zfs aware loader.
Let me know if someone already have wrote more serious unattended zfs 
compatible installer/scripts.
___
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: bsd.rd for FreeBSD install

[Tim Judd]

On Wed, Mar 4, 2009 at 1:13 AM,  wrote:

> > If the machines have floppies, there are downloadable floppy
> > images.
>
> Is anyone aware of a simple method to construct a bootable
> zip-drive image from the floppy images and/or bootonly.iso?





problem is to create the zip disk bootable.  Never tried this, would be
COMPLETELY BIOS dependant, and I know of no sure-fire way to make it work.

But the process would be the same.  Install a bootloader on the zip disk,
either install a bsd system, or copy the bootonly directories and files to
the zip disk...  then the zip would act as a bootonly cd...

I've been shipped, by Iomega, a 750MB zip drive in wrong exchange by Iomega
of a 2TB USB drive.  I'm a little torqued.

--TJ
___
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: bsd.rd for FreeBSD install

[perryh]

> If the machines have floppies, there are downloadable floppy
> images.

Is anyone aware of a simple method to construct a bootable
zip-drive image from the floppy images and/or bootonly.iso?
___
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: bsd.rd for FreeBSD install

[Tim Judd]

On Mon, Mar 2, 2009 at 10:36 AM, new_guy  wrote:

>
> Hi,
>
> We normally use OpenBSD, but would like to try FreeBSD on a test system.
> Usually, when updating from one OpenBSD release to another, we do so by
> downloading the latest bsd.rd and booting from that to complete the
> install.
> Our machines have no optical drives. Does FreeBSD have a similar method to
> installation?
>
> Thanks!
> --
> View this message in context:
> http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22292723.html
> Sent from the freebsd-questions mailing list archive at Nabble.com.
>

Being relatively familiar with both, let me input my advice.

first of all, Open and Free use different DOS-partition partition IDs,
OpenBSD being A6, and FreeBSD being A5.  This would be the first road block
to overcome.

Second, there isn't a produced single file to boot FreeBSD in a ramdisk
image from the FreeBSD folks.  There is one out there called mfsbsd that
does that.  Creating a ramdisk based kernel would work, and you'd need to
shove what's in the bootonly CD into that kernel image.

I doubt you'll be able to produce a kernel for FreeBSD on OpenBSD.  Haven't
tried it, but I bet the pmake syntax for FreeBSD will give OpenBSD problems.

Running a PXE/NFS/DHCP boot server would be the first thing I'd go into to
do a completely CD/DVD-less system.  But you have to start from
somewhere...  You have to boot FreeBSD from external medium so you can
prepare a hard drive.

Is it a problem to float a USB CD/DVD drive around to install?  would a
bootserver help you in your efforts?

There's just so many ways to approach this, your initial post isn't helping
me to lean one way or another.

Can you provide your factors why your systems are CD/DVD-less?  Do these
systems boot from PXE/network?


when you answer these questions, something might come into mind that would
benefit you most...  but the different partition IDs is going to become a
hurlde without a external boot medium.

Let me know,

--TJ
___
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: bsd.rd for FreeBSD install

[Mel]

On Monday 02 March 2009 08:36:39 new_guy wrote:

> We normally use OpenBSD, but would like to try FreeBSD on a test system.
> Usually, when updating from one OpenBSD release to another, we do so by
> downloading the latest bsd.rd and booting from that to complete the
> install. Our machines have no optical drives. Does FreeBSD have a similar
> method to installation?

You can use nanobsd (toolt/tools/nanobsd) on a flash card and possibly through 
PXE, but I'd never tried that. You'd still have to circumvent the bootstrap 
of making that image, unless someone on the list wants to share his nanobsd 
image.
If the machines have floppies, there are downloadable floppy images.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
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: bsd.rd for FreeBSD install

[Ricardo Jesus]

Jerry McAllister wrote:

On Mon, Mar 02, 2009 at 10:02:25AM -0800, new_guy wrote:


You misunderstand. I want to install FreeBSD from a ramdisk image (bsd.rd).


That is called  md  (memory disk) in FreeBSD land.   


Is that possible? It's basically a small kernel that boots the machine,
formats the hard drive, setups root and installs the operating system over
ftp. 


That is what sysinstall is, plus the boot.   It is a program that
builds the filesystems, sets up the system and loads everything on
the disk.The big problem is how to boot and bring it up without
any external media.   I think some people have done it from network
and second Hard drive boots as well as floppy and CD boots.   


jerry


--
View this message in context: 
http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22293310.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
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"

One approach could be using an existing install like described here: 
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/article.html


Or even going the nanoBSD way: 
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/nanobsd/article.html


But this defeats the OP's originial intent, e.g., ramdisk
___
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: bsd.rd for FreeBSD install

[Jerry McAllister]

On Mon, Mar 02, 2009 at 10:02:25AM -0800, new_guy wrote:

> 
> You misunderstand. I want to install FreeBSD from a ramdisk image (bsd.rd).

That is called  md  (memory disk) in FreeBSD land.   

> Is that possible? It's basically a small kernel that boots the machine,
> formats the hard drive, setups root and installs the operating system over
> ftp. 

That is what sysinstall is, plus the boot.   It is a program that
builds the filesystems, sets up the system and loads everything on
the disk.The big problem is how to boot and bring it up without
any external media.   I think some people have done it from network
and second Hard drive boots as well as floppy and CD boots.   

jerry

> 
> -- 
> View this message in context: 
> http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22293310.html
> Sent from the freebsd-questions mailing list archive at Nabble.com.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
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: bsd.rd for FreeBSD install'

[Jerry McAllister]

On Mon, Mar 02, 2009 at 06:19:57PM +, Ricardo Jesus wrote:

> new_guy wrote:
> >You misunderstand. I want to install FreeBSD from a ramdisk image (bsd.rd).
> >Is that possible? It's basically a small kernel that boots the machine,
> >formats the hard drive, setups root and installs the operating system over
> >ftp. 
> >
> If that's what you want I definitely misunderstood. Maybe someone of the 
> list can give a hand and help you out.

Wel, that is what a fixit image is - a boot to a ramdisk image.
They call it md  (memory disk)  in FreeBSD land.  Check man pages
and some more stuff online at various sources.

The only problem is that I don't know if the fixit includes sysinstall.
You could try it. I would guess that the install image is build in 
memory too and runs from there rather than from the CD.  So, it should 
be possible with some tinkering - if you have enough memory to run a
sysinstall completely from memory.   You would then pretty much need 
to do an install over the net - which you would probably do anyway.

So, your big problem, if that works, is figuring out how to create that 
image booted in to the memory disk without some external media to
start it with.

jerry   
   
> ___
> 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: bsd.rd for FreeBSD install

[Ricardo Jesus]

new_guy wrote:

You misunderstand. I want to install FreeBSD from a ramdisk image (bsd.rd).
Is that possible? It's basically a small kernel that boots the machine,
formats the hard drive, setups root and installs the operating system over
ftp. 

If that's what you want I definitely misunderstood. Maybe someone of the 
list can give a hand and help you out.

___
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: bsd.rd for FreeBSD install

[Jerry McAllister]

On Mon, Mar 02, 2009 at 09:36:39AM -0800, new_guy wrote:

> 
> Hi,
> 
> We normally use OpenBSD, but would like to try FreeBSD on a test system.
> Usually, when updating from one OpenBSD release to another, we do so by
> downloading the latest bsd.rd and booting from that to complete the install.
> Our machines have no optical drives. Does FreeBSD have a similar method to
> installation? 

Hmmm.   Having a CD drive makes it so easy.   It might be worthwhile
to run out and get an external one you can plug in.

Installs can also be done from a pair of floppies if you have
a floppy drive.   The floppy just has the boot and sysinstall 
stuff.   Everything else downloads over the net or can be loaded
on some other media such as tape or external disk and installed
from there.

You can create almost any kind of media if you can make it bootable
and put stuff on it and boot from it and bring up sysinstall.  But,
I do not think you can put that on the slice you want to install to
and then do a complete install there.

Now, if you have FreeBSD running, you can upgrade it in place.  Update
and csup are all useful tools to learn for that.  But, an initial 
install wants to be on some media other than where it will be installed.
That is mostly because you build your disk filesystem as part of the
installation.


jerry

> 
> Thanks!
> -- 
> View this message in context: 
> http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22292723.html
> Sent from the freebsd-questions mailing list archive at Nabble.com.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
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: bsd.rd for FreeBSD install

[new_guy]

You misunderstand. I want to install FreeBSD from a ramdisk image (bsd.rd).
Is that possible? It's basically a small kernel that boots the machine,
formats the hard drive, setups root and installs the operating system over
ftp. 

-- 
View this message in context: 
http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22293310.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: bsd.rd for FreeBSD install

[Ricardo Jesus]

new_guy wrote:

Hi,

We normally use OpenBSD, but would like to try FreeBSD on a test system.
Usually, when updating from one OpenBSD release to another, we do so by
downloading the latest bsd.rd and booting from that to complete the install.
Our machines have no optical drives. Does FreeBSD have a similar method to
installation? 


Thanks!


As far as I know OpenBSD advises on binary upgrades so I'd say you're 
probably looking for freebsd-update as it provides binary updates. This 
utility is great for binary updates to both kernel and world.


Do take a look at FreeBSD's Handbook.

To update third party applications e.g. ports read this: 
http://www.freebsd.org/doc/en/books/handbook/ports.html


If you want to compile a custom kernel: 
http://www.freebsd.org/doc/en/books/handbook/kernelconfig.html


Update and upgrade methods are described here: 
http://www.freebsd.org/doc/en/books/handbook/updating-upgrading.html


Have fun,
Ricardo Jesus.
___
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"

bsd.rd for FreeBSD install

[new_guy]

Hi,

We normally use OpenBSD, but would like to try FreeBSD on a test system.
Usually, when updating from one OpenBSD release to another, we do so by
downloading the latest bsd.rd and booting from that to complete the install.
Our machines have no optical drives. Does FreeBSD have a similar method to
installation? 

Thanks!
-- 
View this message in context: 
http://www.nabble.com/bsd.rd-for-FreeBSD-install-tp22292723p22292723.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Copying a FreeBSD install to a smaller disk

[Jerry McAllister]

On Thu, Sep 11, 2008 at 05:19:55PM -0700, Chris Weiss wrote:

> How would I go about copying an existing FreeBSD installation to a smaller 
> disk?
> 
> I've got a 3rd FreeBSD install I can boot from and store temporary
> files on, all the disks are in the same hardware, so there's no
> reconfiguration other than the boot device name and interface (IE
> -SATA ad4 will become IDE ad0). The disk is partitioned using the
> "default" sysinstall values and the contents of the larger disk will
> fit on the smaller disk, although I need to increase the size of the /
> and /var slices on the target to hold everything (/usr is fairly
> empty, so it'll easily fit on the smaller disk).
> 
> For now, we'll say ad0 = new smaller disk, ad4 = boot BSD disk, and
> ad6 = the BSD install I want to clone.
> 
> The path I've been going down is to manually partition and slice ad0
> create ad4/mnt/source and ad4/mnt/target and mount /var, /tmp, etc
> from ad0 and ad6 and manually copy the files. But I'm stuck on how to
> handle /, since it'll have dev and proc and such.
> 
> Any thoughts on how to do this, or on a completely different approach?
> I'm not aware of any 3rd party tools that'll deal with shrinking
> FreeBSD partitions.
> 
> Thanks in advance for any help you folks can give!

Seems like you are generally on the right track, though some of your 
mounting seems backwards to me.

First, as you have indicated, manually slice, partition and newfs
the new disk (ad0) to match what you want to have on it.  If you
are making an identical, just smaller, disk to ad4, then do a df 
and see what slices and partitions are being used on ad4.   Probably
it is one slice, divided into several partitions.   

While you are at it, look at each of the filesystem sizes and make 
sure you will have room on the new, smaller disk.   You want at least
the current used size + 10%.   Really you want more to actually
operate.   

Presuming you want a single bootable slice (ad0s1) which is then 
divided in to partitions for:
 a: /
 b: swap
 d: /tmp
 e: /usr
 f: /var
 g: /home

Do:
  fdisk -BI ad0
Creates a single bootable slice with default MBR (good enough).
  bsdlabel -w -B da0s1
Writes an initial label and boot block on the slice
  bsdlabel -e da0s1
Puts you in edit (vi by default) with the current condition of
the partition label showing.  If it is new, it will only show
a 'c' partition covering the whole available size of the slice.
  Edit this page by duplicating that 'c' line for each real partition
  you want to have and changing fstype from 'unused' to '4.2BSD' on
  the a, d, e, f, g partitions and 'swap' on the b partition.

In the end you will have something that looks about like:

# /dev/ad0s3:
8 partitions:
#   size   offset   fstype  [fsize bsize bps/cpg]
 a:   5242880   4.2BSD2048 16384 32776
 b:  2572288* swap
 c: 783168750   unused   0 0# "raw" part, don't edit
 d:  1048576*   4.2BSD2048 16384 8
 e:  4194304*   4.2BSD2048 16384 28552
 f:  6291456*   4.2BSD2048 16384 28552
 g:**   4.2BSD2048 16384 28552

You need only specify the sizes.  You can put '*' for the offset
and the bsdlabel utility figures it out correctly.
Also, you can put '*' for both size and offset on the last
partition and it will use all the remaining available space.
Don't do anything with the actual 'c' partition.

Remember that sizes here are in 512 Byte blocks/sectors.
The sizes I have here are for a disk I happen to have handy at
the moment to look at.
  a: 256 MBMount as;  /
  b:   1,256 MB   swap
  d: 512 MB  "   "/tmp
  e:   2,048 MB  "   "/usr
  f:   3,072 MB  "   "/var
  g:  31,096 MB  "   "/home

Then do a regular newfs on each real file system a, d, e, f, g
  newfs /dev/ad0s1a
  newfs /dev/ad0s1d
etc  for e, f, g

Once you have the new disk created, I would do the rest all in
single user mode.

Boot to single useri, then

  fsck -p
  mount -u /
  mount -a
  swapon -a

Create temporary mount points for the new filesystems (ignore /tmp
unless you actually have something there to maintain - unlikely)
  mkdir /newroot
  mkdir /newusr
  mkdir /newvar
  mkdir /newhome

Use dump/restore to copy the file systems

  cd /newroot
  dump -0af - / | restore -rf -
  cd /newusr
  dump -0af - /usr | restore -rf -
  cd /newvar
  dump -0af - /var | restore -rf -
  cd /newhome
  dump -0af - /home | restore -rf -

These can take a while, especially the /home dump/restore if
it is large.  

Once you are finished with this you need to fix up 
the /etc/fstab file on /newroot.
After this, when you reboot, as long as

Re: Copying a FreeBSD install to a smaller disk

[Giorgos Keramidas]

On Fri, 12 Sep 2008 04:55:36 +0300, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> [8] The final step was to chroot [...]
> [9] Finally, I checked the new `/etc/fstab' [...]

Heh!  Adding `one last "final" step' didn't really work very well in
this case.  I should have read the long message another time before
hitting `send'.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Copying a FreeBSD install to a smaller disk

[Giorgos Keramidas]

On Thu, 11 Sep 2008 17:19:55 -0700, "Chris Weiss" <[EMAIL PROTECTED]> wrote:
> How would I go about copying an existing FreeBSD installation to a smaller 
> disk?
>
> I've got a 3rd FreeBSD install I can boot from and store temporary
> files on, all the disks are in the same hardware, so there's no
> reconfiguration other than the boot device name and interface (IE
> -SATA ad4 will become IDE ad0). The disk is partitioned using the
> "default" sysinstall values and the contents of the larger disk will
> fit on the smaller disk, although I need to increase the size of the /
> and /var slices on the target to hold everything (/usr is fairly
> empty, so it'll easily fit on the smaller disk).
>
> For now, we'll say ad0 = new smaller disk, ad4 = boot BSD disk, and
> ad6 = the BSD install I want to clone.
>
> The path I've been going down is to manually partition and slice ad0
> create ad4/mnt/source and ad4/mnt/target and mount /var, /tmp, etc
> from ad0 and ad6 and manually copy the files. But I'm stuck on how to
> handle /, since it'll have dev and proc and such.

Hi Chris,

If all you want is to make ad0 bootable, you don't need the *contents*
of the /dev and /proc file systems.  They are dynamically generated by
the kernel when you mount these file systems and access them.

If the used disk space in ad6 (the clone source drive) is less than the
size of the clone target, it should be possible to copy the source files
using any of:

* tar
* dump & restore
* cpio

Some care must be taken to avoid copying special file systems, like /dev
and /proc that you mentioned.  If you use something like a Live CD-ROM
to boot, instead of booting from the 'source' disk, this should be easy,
because the special /dev and /proc file systems will be mounted only for
the *boot* device (the CD-ROM in this case), so the hard disk partitions
will merely include empty directories as `potential mount-points' for
the /dev, /proc and other special places.

FWIW, the steps I followed when I cloned my old laptop installation to a
new hard disk are the ones shown below.  I didn't want to open the
laptop, because that would violate its guarantee terms.  So I kept the
'target' disk as ad0 and used a USB-attached enclosure for 2.5" hard
disks to attach the original 'source' disk (taken out of my old, dead
laptop).

[1] Boot from CD-ROM using a FreeSBIE installation(*).

(*) Many thanks to the FreeSBIE folks, for making such an easy to
use Live CD-ROM.  I have found it very useful far too many times to
mention all of them in an email post!

[2] Create an /mnt/source and /mnt/target directory.

# mkdir -p /mnt/source
# mkdir -p /mnt/target

[3] Mount the source root partition, and then use the existing mount
points under that source tree to mount the target partitions:

# mount -o ro /dev/da0s1a /mnt/source
# mount -o ro /dev/da0s1e /mnt/source/home

Note that, for extra safety, I mounted the source partitions as
read-only.  This way I would at least get a warning if I botched the
copying process, and avoid messing my original 'source' data.

[4] Partition and mount the target disk (the internal ad0 disk of the
laptop).  This is where booting from a Live CD-ROM helped a lot,
because I didn't have to do anything special to 'resize' or 'keep'
parts of the disk unpartitioned.  I could use the *full* disk for
the new installation.

# fdisk -BI /dev/ad0
# bsdlabel -w -B /dev/ad0s1
# bsdlabel -e /dev/ad0s1

When I had configured the new ad0s1a and ad0s1e partitions, I saved
the label and exited bsdlabel's editor.

[5] Format the target partitions:

# newfs -L MYROOT /dev/ad0s1a
# newfs -L MYHOME -U /dev/ad0s1e

The -L labels are entirely optional, and, as you can see, I only
enabled softupdates on the new /home partition.

[6] Mount the target partitions under `/mnt/target'.  The mounts were
read-write this time:

# mount /dev/ad0s1a /mnt/target
# mkdir /mnt/target/home
# mount /dev/ad0s1e /mnt/target/home

Note that the second command is not optional.  The new root file
system was brand new, so it appears completely empty after being
mounted.

[7] Copy everything using BSD tar(1):

# tar -C /mnt/source -cf - . | tar -C /mnt/target xvf -

[8] The final step was to chroot into the new 'target' system, and
fix-up any special directory permissions, by using the mtree(8)
specifications from `/etc/mtree'.  This restores any special flags
like `noschg' or the permissions required for proper daemon
operation in `/var/run' and so on.

To avoid side-effects from the runtime environment of the shell I
wa

Copying a FreeBSD install to a smaller disk

[Chris Weiss]

How would I go about copying an existing FreeBSD installation to a smaller disk?

I've got a 3rd FreeBSD install I can boot from and store temporary
files on, all the disks are in the same hardware, so there's no
reconfiguration other than the boot device name and interface (IE
-SATA ad4 will become IDE ad0). The disk is partitioned using the
"default" sysinstall values and the contents of the larger disk will
fit on the smaller disk, although I need to increase the size of the /
and /var slices on the target to hold everything (/usr is fairly
empty, so it'll easily fit on the smaller disk).

For now, we'll say ad0 = new smaller disk, ad4 = boot BSD disk, and
ad6 = the BSD install I want to clone.

The path I've been going down is to manually partition and slice ad0
create ad4/mnt/source and ad4/mnt/target and mount /var, /tmp, etc
from ad0 and ad6 and manually copy the files. But I'm stuck on how to
handle /, since it'll have dev and proc and such.

Any thoughts on how to do this, or on a completely different approach?
I'm not aware of any 3rd party tools that'll deal with shrinking
FreeBSD partitions.

Thanks in advance for any help you folks can give!

-- 
-Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: doing a minimal FreeBSD install

[Joe in MPLS]

Daniel Bye wrote:


On Tue, Oct 02, 2007 at 01:59:55PM -0700, Rogelio Bastardo wrote:
 


I'm looking to install only the bare essentials to FreeBSD and then
install each program piece-by-piece afterwards.

To do this, do I just need the first FreeBSD 6 ISO?  Or can I get away
with just the boot CD ISO and then install each port one-by-one?

(Basically, I just wanna build a Nagios server, and that requires
very, very little)
  



A bit more work perhaps than you're willing or able to commit, but you
might be interested in MiniBSD - a set of scripts that enable you to 
pare down a base FreeBSD system to something very small indeed.


http://www.minibsd.org

It needs some practice to get it right, but the results are quite
useful when you get it right!

Dan

 

I'm running a couple of mini-ITX sized mini-bsd machines now. They're 
dedicated to SSL proxy duties. They boot and run fom 32MB compact flash 
cards. / is mounted read only, /var & /tmp are ramdisks. Runs great on 
VMware too.


...jgm
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: doing a minimal FreeBSD install

[Rogelio Bastardo]

> A bit more work perhaps than you're willing or able to commit, but you
> might be interested in MiniBSD - a set of scripts that enable you to
> pare down a base FreeBSD system to something very small indeed.

Thank you, I will definitely check that out.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: doing a minimal FreeBSD install

[Daniel Bye]

On Tue, Oct 02, 2007 at 01:59:55PM -0700, Rogelio Bastardo wrote:
> I'm looking to install only the bare essentials to FreeBSD and then
> install each program piece-by-piece afterwards.
> 
> To do this, do I just need the first FreeBSD 6 ISO?  Or can I get away
> with just the boot CD ISO and then install each port one-by-one?
> 
> (Basically, I just wanna build a Nagios server, and that requires
> very, very little)

A bit more work perhaps than you're willing or able to commit, but you
might be interested in MiniBSD - a set of scripts that enable you to 
pare down a base FreeBSD system to something very small indeed.

http://www.minibsd.org

It needs some practice to get it right, but the results are quite
useful when you get it right!

Dan

-- 
Daniel Bye
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \


pgpmEA3YOb9Gg.pgp
Description: PGP signature

Re: doing a minimal FreeBSD install

[Tore Lund]

Rogelio Bastardo wrote:
> I'm looking to install only the bare essentials to FreeBSD and then
> install each program piece-by-piece afterwards.
> 
> To do this, do I just need the first FreeBSD 6 ISO?  Or can I get away
> with just the boot CD ISO and then install each port one-by-one?

The boot-only CD will be fine for any sort of installation, as long as
you have a good Internet connection.
-- 
Tore

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: doing a minimal FreeBSD install

[Bahman M.]

On 2007-10-02 Rogelio Bastardo wrote:
> I'm looking to install only the bare essentials to FreeBSD and then
> install each program piece-by-piece afterwards.
> 
> To do this, do I just need the first FreeBSD 6 ISO?  Or can I get away
> with just the boot CD ISO and then install each port one-by-one?
> 
> (Basically, I just wanna build a Nagios server, and that requires
> very, very little)

AFAIK, you will need at least the first ISO.  That's what I exactly did
with my home machine: did a minimal 6.2 installation, 'portsnap fetch',
'portsnap extract' and then ports installation.

HTH

Bahman
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

doing a minimal FreeBSD install

[Rogelio Bastardo]

I'm looking to install only the bare essentials to FreeBSD and then
install each program piece-by-piece afterwards.

To do this, do I just need the first FreeBSD 6 ISO?  Or can I get away
with just the boot CD ISO and then install each port one-by-one?

(Basically, I just wanna build a Nagios server, and that requires
very, very little)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Net-snmp dying with an "ld-elf" error at start on brand new FreeBSD install

[Ivan Voras]

Philip B wrote:


  Starting snmpd.
  /libexec/ld-elf.so.1: /usr/local/sbin/snmpd: Undefined symbol
"PL_markstack_ptr"



I've Googled on "PL_markstack_ptr snmpd" and got back only 5 hits,
none which seem to explain this problem at runtime.

I don't know even where to begin to dig.


It's usually symptomatic of having "stale" or otherwise incompatible 
libraries dynamically linked to new programs. One example can be trying 
to run binaries built on 7.x on a 6.x system.


I'd recommend rebuilding your application (snmpd) *and* all dependencies 
it has, e.g. "portupgrade -R snmpd".




signature.asc
Description: OpenPGP digital signature

Net-snmp dying with an "ld-elf" error at start on brand new FreeBSD install

[Philip B]

I've just set up my 1st FreeBSD box to use as a home router/firewall,
replacing my recently departed Linksys all-in-one.

I installed the latest FeeBSD release, version 6.2-RELEASE.

I installed the Net-Snmp port, with the goal of eventually using it
with RRDTool to graph & monitor activity on the box.

After configuring my snmpd.conf file, and enabling Snmp in rc.conf, I
try to start the snmp daemon with

  /usr/local/etc/rc.d/snmpd start

Unfortunately, it doesn't launch and reports an error in my shell.

  Starting snmpd.
  /libexec/ld-elf.so.1: /usr/local/sbin/snmpd: Undefined symbol
"PL_markstack_ptr"

I've tailed /var/log/messages, but there's nothing reported.

I've Googled on "PL_markstack_ptr snmpd" and got back only 5 hits,
none which seem to explain this problem at runtime.

I don't know even where to begin to dig.

Any wise old folks in here lend a hand?

Phil
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Chad Perrin]

On Sun, Jun 03, 2007 at 09:35:36PM -0400, Jerry McAllister wrote:
> On Sun, Jun 03, 2007 at 01:17:00PM -0600, Chad Perrin wrote:
> 
> > Someone I know tried installing Slackware on a Thinkpad R52 to create a
> > triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
> > present on the system).  The Slackware install didn't get very far (the
> > installer is less than helpful -- wouldn't recognize a swap partition at
> > all), but apparently it got far enough to break the FreeBSD install.
> > 
> > Any tips, hints, and suggestions about how exactly to go about fixing
> > the FreeBSD install (without overwriting the home partition and losing
> > the installed system configuration to minimize time lost getting things
> > back to "normal") would be appreciated.  Thanks in advance.
> 
> Well, you don't say very much about just what you did and where,
> so it leaves only wild guesses.   But one guess is that your other 
> install wiped out the MBR on the disk.
> 
> To fix that, you can boot up the install CD and select  running
> the fixit.   From the fixit use fdisk to install the FreeBSD MBR
> or I think it also has boot0config.   Then try rebooting.  If that
> doesn't help, then we'll have to have some more detailed inf0 --
> like the slices and their layout, what order you installed things
> and maybe some other stuff.

After talking more with the person who owns the laptop and doing some
more investigation, I've come to the conclusion that the actual source
of the problem was QtParted.  The system was booted with a Slackware
installer and an attempt was made to create a swap partition using fdisk
from there, but the Slackware installer didn't recognize it (yes, after
rebooting).  It was attempted again by booting from a Knoppix CD, using
QtParted.  Once that was done the Slackware installer was booted again,
and still did not recognize the existence of a Linux swap partition.

After that, booting into FreeBSD was attempted, and it hung after
selecting F3 (the option for FreeBSD), thus bringing us to the point
where a problem was noticed.

We used QtParted to check out the partition setup, after re-identifying
the FreeBSD slice as such using fdisk from a Knoppix root shell.  It
appears that QtParted automatically classifies the FreeBSD partition
(or "slice" if you prefer -- QtParted calls it a partition) as a Linux
swap partition, and thus thinks there are *two* Linux swap partitions on
the drive.  I think that writing a new partition table to disk after
telling it to add a new swap partition for Slackware caused it to also
change the identification of the FreeBSD partition to a swap partition.

Having already changed its label to identify it as a FreeBSD partition,
I guess the next step is to make it bootable -- not using QtParted, of
course.  I'm frankly stunned that it supports NTFS but not UFS.  Am I
the only one that thinks that's just not right, somehow?

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
Rudy Giuliani: "You have free speech so I can be heard."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Jerry McAllister]

On Sun, Jun 03, 2007 at 02:56:08PM -0600, Chad Perrin wrote:

> On Sun, Jun 03, 2007 at 11:19:39PM +0300, Manolis Kiagias wrote:
> > You can use the grub bootloader to load freebsd (assuming that nothing
> > is damaged in the freebsd slice itself, and I believe it is intact in
> > your case)
> > It's been some time since I've done this myself (I am no longer dual
> > booting FreeBSD on this machine), but I'll try to be as accurate as
> > possible.
> > Start your system, when it gets to the grub loader press "c" to get to
> > the grub command line.
> > Do you know what your freebsd slice is? Even if you don't, you can get
> > this info from fdisk -l from debian. Or you could try searching in the
> > command line.
> > Type something like:
> > 
> > root (hd0,2,a)
> 
> GRUB doesn't recognize the partition type for some reason.  There's
> pretty clearly something wrong with the partition, I think.

Do you mean partition or slice?

The slice needs to be marked as bootable.  You can check this 
from the fixit boot using fdisk - 'fdisk ad0'  or  'fdisk da0'
presuming this is disk 0 and depending on IDE or SCSI.   
Then, if that looks OK, use bsdlabel on that slice (something 
like  'bsdlabel ad0s3' or 'bsdlabel da0s3' depending on IDE or SCSI and
presuming FreeBSD is on slice 3) from the fixit to see what you can 
learn from it.   Just doing bsdlabel with no other command flag will
print out information.

jerry

> 
> -- 
> CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
> McCloctnick the Lucid: "The first rule of magic is simple. Don't waste your
> time waving your hands and hopping when a rock or a club will do."
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install

[Jerry McAllister]

On Sun, Jun 03, 2007 at 01:17:00PM -0600, Chad Perrin wrote:

> Someone I know tried installing Slackware on a Thinkpad R52 to create a
> triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
> present on the system).  The Slackware install didn't get very far (the
> installer is less than helpful -- wouldn't recognize a swap partition at
> all), but apparently it got far enough to break the FreeBSD install.
> 
> Any tips, hints, and suggestions about how exactly to go about fixing
> the FreeBSD install (without overwriting the home partition and losing
> the installed system configuration to minimize time lost getting things
> back to "normal") would be appreciated.  Thanks in advance.

Well, you don't say very much about just what you did and where,
so it leaves only wild guesses.   But one guess is that your other 
install wiped out the MBR on the disk.

To fix that, you can boot up the install CD and select  running
the fixit.   From the fixit use fdisk to install the FreeBSD MBR
or I think it also has boot0config.   Then try rebooting.  If that
doesn't help, then we'll have to have some more detailed inf0 --
like the slices and their layout, what order you installed things
and maybe some other stuff.

jerry

> 
> -- 
> CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
> MacUser, Nov. 1990: "There comes a time in the history of any project when
> it becomes necessary to shoot the engineers and begin production."
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Garrett Cooper]

Manolis Kiagias wrote:

Chad Perrin wrote:
  

On Sun, Jun 03, 2007 at 11:19:39PM +0300, Manolis Kiagias wrote:
  


You can use the grub bootloader to load freebsd (assuming that nothing
is damaged in the freebsd slice itself, and I believe it is intact in
your case)
It's been some time since I've done this myself (I am no longer dual
booting FreeBSD on this machine), but I'll try to be as accurate as
possible.
Start your system, when it gets to the grub loader press "c" to get to
the grub command line.
Do you know what your freebsd slice is? Even if you don't, you can get
this info from fdisk -l from debian. Or you could try searching in the
command line.
Type something like:

root (hd0,2,a)

  

GRUB doesn't recognize the partition type for some reason.  There's
pretty clearly something wrong with the partition, I think.

  


Is it possible that somehow the partition type was changed?
Try as root an fdisk -l from your debian installation.
Your freebsd should show up as partition type a5 (BSD/386)
Otherwise you could use fdisk to fix this.

And for that you need a fixit floppy / LiveCD :).
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Manolis Kiagias]

Chad Perrin wrote:
> On Sun, Jun 03, 2007 at 11:19:39PM +0300, Manolis Kiagias wrote:
>   
>> You can use the grub bootloader to load freebsd (assuming that nothing
>> is damaged in the freebsd slice itself, and I believe it is intact in
>> your case)
>> It's been some time since I've done this myself (I am no longer dual
>> booting FreeBSD on this machine), but I'll try to be as accurate as
>> possible.
>> Start your system, when it gets to the grub loader press "c" to get to
>> the grub command line.
>> Do you know what your freebsd slice is? Even if you don't, you can get
>> this info from fdisk -l from debian. Or you could try searching in the
>> command line.
>> Type something like:
>>
>> root (hd0,2,a)
>> 
>
> GRUB doesn't recognize the partition type for some reason.  There's
> pretty clearly something wrong with the partition, I think.
>
>   
Is it possible that somehow the partition type was changed?
Try as root an fdisk -l from your debian installation.
Your freebsd should show up as partition type a5 (BSD/386)
Otherwise you could use fdisk to fix this.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Chad Perrin]

On Sun, Jun 03, 2007 at 11:19:39PM +0300, Manolis Kiagias wrote:
> You can use the grub bootloader to load freebsd (assuming that nothing
> is damaged in the freebsd slice itself, and I believe it is intact in
> your case)
> It's been some time since I've done this myself (I am no longer dual
> booting FreeBSD on this machine), but I'll try to be as accurate as
> possible.
> Start your system, when it gets to the grub loader press "c" to get to
> the grub command line.
> Do you know what your freebsd slice is? Even if you don't, you can get
> this info from fdisk -l from debian. Or you could try searching in the
> command line.
> Type something like:
> 
> root (hd0,2,a)

GRUB doesn't recognize the partition type for some reason.  There's
pretty clearly something wrong with the partition, I think.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
McCloctnick the Lucid: "The first rule of magic is simple. Don't waste your
time waving your hands and hopping when a rock or a club will do."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Manolis Kiagias]

Chad Perrin wrote:
> On Sun, Jun 03, 2007 at 02:34:28PM -0500, Kevin Kinsey wrote:
>   
>> Chad Perrin wrote:
>> 
>>> Someone I know tried installing Slackware on a Thinkpad R52 to create a
>>> triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
>>> present on the system).  The Slackware install didn't get very far (the
>>> installer is less than helpful -- wouldn't recognize a swap partition at
>>> all), but apparently it got far enough to break the FreeBSD install.
>>>
>>> Any tips, hints, and suggestions about how exactly to go about fixing
>>> the FreeBSD install (without overwriting the home partition and losing
>>> the installed system configuration to minimize time lost getting things
>>> back to "normal") would be appreciated.  Thanks in advance.
>>>   
>> What exactly is broken in the FBSD installation?  Just won't
>> find enough bootstrap stuff to boot?
>> 
>
> Shortly after the aborted Slackware install, the FreeBSD bootloader
> still loaded, but chosing the FreeBSD option would just cause it to hang
> rather than booting up the OS.  Since then, Debian has been installed in
> the free space on the drive, with GRUB installed as the new bootloader,
> and it doesn't list the FreeBSD option as existing at all.
>
>
> 
You can use the grub bootloader to load freebsd (assuming that nothing
is damaged in the freebsd slice itself, and I believe it is intact in
your case)
It's been some time since I've done this myself (I am no longer dual
booting FreeBSD on this machine), but I'll try to be as accurate as
possible.
Start your system, when it gets to the grub loader press "c" to get to
the grub command line.
Do you know what your freebsd slice is? Even if you don't, you can get
this info from fdisk -l from debian. Or you could try searching in the
command line.
Type something like:

root (hd0,2,a)

that is assuming your freebsd slice is hda3 (or sda3) - grub numbering
starts from 0
If you are not sure about the number try others like root (hd0,3,a) and
so on. You will know when you hit the correct partition, since it will say:
Filesystem type is UFS, partition type ... (something similar)
Then type
kernel /boot/loader
and then type
boot
If you get into freebsd successfully, you can then add all the above
instructions in the grub configuration file (normally in
/boot/grub/menu.lst in your linux system)
Hope this helps.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install

[Kevin Kinsey]

Chad Perrin wrote:

On Sun, Jun 03, 2007 at 02:34:28PM -0500, Kevin Kinsey wrote:

Chad Perrin wrote:

Someone I know tried installing Slackware on a Thinkpad R52 to create a
triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
present on the system).  The Slackware install didn't get very far (the
installer is less than helpful -- wouldn't recognize a swap partition at
all), but apparently it got far enough to break the FreeBSD install.




What exactly is broken in the FBSD installation?  Just won't
find enough bootstrap stuff to boot?


Shortly after the aborted Slackware install, the FreeBSD bootloader
still loaded, but chosing the FreeBSD option would just cause it to hang
rather than booting up the OS.  Since then, Debian has been installed in
the free space on the drive, with GRUB installed as the new bootloader,
and it doesn't list the FreeBSD option as existing at all.



"Dual Boot Problems", March 1st, Sam Jones, Jerry McAllister,
Beech Rintoul
"Changing Boot Loader", March 3rd, Tom Marchand, "Vince", 
	Thomas Sparrevohn, Kevin Kinsey

"Skipping F1 FreeBSD prompt on boot", May 12-15th, David
Landgren, Matthew Seaman, Sam Lawrence, Pieter de Goeje


I doubt the "Changing Boot Loader" thread would be much help, and I
don't think "Skipping F1 FreeBSD prompt on boot" sound relevant either.
I'll give them all a look, though.  Thanks for the suggestions.


Well, I didn't read 'em either, but grep found refs to "boot0cfg"
in these threads, which is what Garrett also pointed you toward.

I'm pretty sure that will get you going again.  That said, I
recently used GAG to solve a related issue, as well, and it's now
the permanent resident on one FBSD server I have

KDK
--
Learned men are the cisterns of knowledge, not the fountainheads.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install

[Chad Perrin]

On Sun, Jun 03, 2007 at 02:34:28PM -0500, Kevin Kinsey wrote:
> Chad Perrin wrote:
> >Someone I know tried installing Slackware on a Thinkpad R52 to create a
> >triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
> >present on the system).  The Slackware install didn't get very far (the
> >installer is less than helpful -- wouldn't recognize a swap partition at
> >all), but apparently it got far enough to break the FreeBSD install.
> >
> >Any tips, hints, and suggestions about how exactly to go about fixing
> >the FreeBSD install (without overwriting the home partition and losing
> >the installed system configuration to minimize time lost getting things
> >back to "normal") would be appreciated.  Thanks in advance.
> 
> What exactly is broken in the FBSD installation?  Just won't
> find enough bootstrap stuff to boot?

Shortly after the aborted Slackware install, the FreeBSD bootloader
still loaded, but chosing the FreeBSD option would just cause it to hang
rather than booting up the OS.  Since then, Debian has been installed in
the free space on the drive, with GRUB installed as the new bootloader,
and it doesn't list the FreeBSD option as existing at all.


> 
> Some fairly recent threads on this list that might help:
> 
> "Dual Boot Problems", March 1st, Sam Jones, Jerry McAllister,
>   Beech Rintoul
> "Changing Boot Loader", March 3rd, Tom Marchand, "Vince", 
>   Thomas Sparrevohn, Kevin Kinsey
> "Skipping F1 FreeBSD prompt on boot", May 12-15th, David
>   Landgren, Matthew Seaman, Sam Lawrence, Pieter de Goeje

I doubt the "Changing Boot Loader" thread would be much help, and I
don't think "Skipping F1 FreeBSD prompt on boot" sound relevant either.
I'll give them all a look, though.  Thanks for the suggestions.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
McCloctnick the Lucid: "The first rule of magic is simple. Don't waste your
time waving your hands and hopping when a rock or a club will do."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repair a FreeBSD install

[Chad Perrin]

On Sun, Jun 03, 2007 at 12:34:06PM -0700, Garrett Cooper wrote:
> Chad Perrin wrote:
> >Someone I know tried installing Slackware on a Thinkpad R52 to create a
> >triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
> >present on the system).  The Slackware install didn't get very far (the
> >installer is less than helpful -- wouldn't recognize a swap partition at
> >all), but apparently it got far enough to break the FreeBSD install.
> >
> >Any tips, hints, and suggestions about how exactly to go about fixing
> >the FreeBSD install (without overwriting the home partition and losing
> >the installed system configuration to minimize time lost getting things
> >back to "normal") would be appreciated.  Thanks in advance.
> Go to gag.sf.net, get and install the bootloader, boot up FreeBSD, login 
> as root, run boot0cfg -B /dev/{drive_node} and reboot. Fixed (as long as 
> the user didn't seriously hose the system).

Thanks.  We'll give it a whirl.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
Dr. Ron Paul: "Liberty has meaning only if we still believe in it when
terrible things happen and a false government security blanket beckons."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install (s/repear/repair/ -- wow, I can't spell)

[Chad Perrin]

Sorry about the typo in the title of this thread.  I don't know how that
happened.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
Larry Wall: "A script is what you give the actors.  A program is what you
give the audience."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install

[Kevin Kinsey]

Chad Perrin wrote:

Someone I know tried installing Slackware on a Thinkpad R52 to create a
triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
present on the system).  The Slackware install didn't get very far (the
installer is less than helpful -- wouldn't recognize a swap partition at
all), but apparently it got far enough to break the FreeBSD install.

Any tips, hints, and suggestions about how exactly to go about fixing
the FreeBSD install (without overwriting the home partition and losing
the installed system configuration to minimize time lost getting things
back to "normal") would be appreciated.  Thanks in advance.


What exactly is broken in the FBSD installation?  Just won't
find enough bootstrap stuff to boot?

Some fairly recent threads on this list that might help:

"Dual Boot Problems", March 1st, Sam Jones, Jerry McAllister,
Beech Rintoul
"Changing Boot Loader", March 3rd, Tom Marchand, "Vince", 
	Thomas Sparrevohn, Kevin Kinsey

"Skipping F1 FreeBSD prompt on boot", May 12-15th, David
Landgren, Matthew Seaman, Sam Lawrence, Pieter de Goeje

HTH,

Kevin Kinsey
--
When there is an old maid in the house, a watch dog is unnecessary.
-- Balzac
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: repear a FreeBSD install

[Garrett Cooper]

Chad Perrin wrote:

Someone I know tried installing Slackware on a Thinkpad R52 to create a
triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
present on the system).  The Slackware install didn't get very far (the
installer is less than helpful -- wouldn't recognize a swap partition at
all), but apparently it got far enough to break the FreeBSD install.

Any tips, hints, and suggestions about how exactly to go about fixing
the FreeBSD install (without overwriting the home partition and losing
the installed system configuration to minimize time lost getting things
back to "normal") would be appreciated.  Thanks in advance.
Go to gag.sf.net, get and install the bootloader, boot up FreeBSD, login 
as root, run boot0cfg -B /dev/{drive_node} and reboot. Fixed (as long as 
the user didn't seriously hose the system).

-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

repear a FreeBSD install

[Chad Perrin]

Someone I know tried installing Slackware on a Thinkpad R52 to create a
triple-boot system (MS Windows and FreeBSD 6.2 as the other two, already
present on the system).  The Slackware install didn't get very far (the
installer is less than helpful -- wouldn't recognize a swap partition at
all), but apparently it got far enough to break the FreeBSD install.

Any tips, hints, and suggestions about how exactly to go about fixing
the FreeBSD install (without overwriting the home partition and losing
the installed system configuration to minimize time lost getting things
back to "normal") would be appreciated.  Thanks in advance.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
MacUser, Nov. 1990: "There comes a time in the history of any project when
it becomes necessary to shoot the engineers and begin production."
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[Mark Tinguely]

>  John Baldwin <[EMAIL PROTECTED]> says:
>
>  APIC IDs are not programmable (well, they are on I/O APICs, but not local=20
>  APICs).  However, I am working on patches to support all valid APIC IDs for=
>  =20
>  both mptable and MADT.  Bumping up NLAPICS as a temporary workaround should=
>  =20
>  suffice for now.
>
>  =2D-=20
>  John Baldwin

IMO, the quick solution also requires that MAX_APICID in
[amd64/amd64 | i386/i386]/local_apic.c needs to be changed
because lapic_create() checks if the passed apic_id > MAX_APICID.

Also in [amd64/amd64 | i386/i386]/mp_machdep.c checks in cpu_add()
if the passed apic_id >= MAXCPU. There are a couple other checks
in mp_machdep.c before converting to use the cpu_apic_ids[] array.

I was curious, and wrote up a patch file with the potential minor changes
for -current at http://www.casselton.com/~tinguely/acpicid.patch .
I saw one more change needed to use on FreeBSD 6.2-RELEASE.

--Mark Tinguely
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[John Baldwin]

On Monday 23 April 2007 02:51:19 pm Mark Tinguely wrote:
> 
> >  John Baldwin <[EMAIL PROTECTED]> says:
> >
> >  APIC IDs are not programmable (well, they are on I/O APICs, but not 
local=20
> >  APICs).  However, I am working on patches to support all valid APIC IDs 
for=
> >  =20
> >  both mptable and MADT.  Bumping up NLAPICS as a temporary workaround 
should=
> >  =20
> >  suffice for now.
> >
> >  =2D-=20
> >  John Baldwin
> 
> IMO, the quick solution also requires that MAX_APICID in
> [amd64/amd64 | i386/i386]/local_apic.c needs to be changed
> because lapic_create() checks if the passed apic_id > MAX_APICID.
> 
> Also in [amd64/amd64 | i386/i386]/mp_machdep.c checks in cpu_add()
> if the passed apic_id >= MAXCPU. There are a couple other checks
> in mp_machdep.c before converting to use the cpu_apic_ids[] array.
> 
> I was curious, and wrote up a patch file with the potential minor changes
> for -current at http://www.casselton.com/~tinguely/acpicid.patch .
> I saw one more change needed to use on FreeBSD 6.2-RELEASE.

What I have so far is somewhat similar, but goes ahead and allows the full 
range of APIC IDs while trying to still honor MAXCPU correctly.  I haven't 
ported it to i386 yet, nor compiled it yet, much less booted it. :)  I hope 
to at least get it booted on amd64 today.

-- 
John Baldwin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[John Baldwin]

On Thursday 19 April 2007 03:11:32 pm Dag-Erling Smørgrav wrote:
> Mark Tinguely <[EMAIL PROTECTED]> writes:
> > I suggested that in email too, but looking closer, I think the MAXCPU
> > needs to be increased because the cpu number uses the apic_id. Or could
> > that be changed with a logical CPU to APIC ID lookup?
> >
> > Isn't the APIC IDs programmable? not that I am suggesting that, I
> > can think of headaches of all the places (like interrupt tables)
> > where it needs to be changed, not to mention the worry that the
> > lower APIC IDs were assigned to IOAPICs.
> 
> I don't know, you'd have to ask jhb@ about the details.

APIC IDs are not programmable (well, they are on I/O APICs, but not local 
APICs).  However, I am working on patches to support all valid APIC IDs for 
both mptable and MADT.  Bumping up NLAPICS as a temporary workaround should 
suffice for now.

-- 
John Baldwin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: IBM / FreeBSD Install problem

[Murray Taylor]

Thanks all,

We will look into the code editting and see what we can get
however we are on an very short time frame so may not be able to 
slot it in before a maintenance slot where we need to be able to drop in
the box 'seamlessly' .

But I have noted the proposed fix provided on these lists into the red
book!

mjt
 

> -Original Message-
> From: Mark Tinguely [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 20 April 2007 3:37 AM
> To: [EMAIL PROTECTED]; Murray Taylor
> Cc: [EMAIL PROTECTED]; freebsd-questions@freebsd.org
> Subject: Re: IBM / FreeBSD Install problem
> 
> >
> >  If you can either install without ACPI, or remove two of the CPUs
> >  during installation, this should be fairly easy to fix: change the
> >  definition of NLAPICS in 
> /usr/src/sys/{amd64,i386}/acpica/madt.c and
> >  rebuild your kernel, then boot with ACPI enabled and report back to
> >  us.
> >
> >  DES
> >  --=20
> >  Dag-Erling Sm=F8rgrav - [EMAIL PROTECTED]
> 
> I suggested that in email too, but looking closer, I think the MAXCPU
> needs to be increased because the cpu number uses the 
> apic_id. Or could
> that be changed with a logical CPU to APIC ID lookup?
> 
> Isn't the APIC IDs programmable? not that I am suggesting that, I
> can think of headaches of all the places (like interrupt tables)
> where it needs to be changed, not to mention the worry that the
> lower APIC IDs were assigned to IOAPICs.
> 
> --Mark Tinguely
> 
---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: IBM / FreeBSD Install problem

[Murray Taylor]

Thanks Jerry,

We have determined that our problem is related to the
god-awful mess known as ACPI.

With a single processor installed, it all boots fine, including
finding PCI busses 1 and 2  and the raid on the aac driver is
peachy!

With 2 or more processors installed, and ACPI enabled, it panics
with a madt error about id 38 is greater than the allowed max

And with ACPI disabled, it boots, but doesnt find PCI busses 1 and 2,
which is unfortunate as the RAID controller sits in PCI bus 1 
and the bge inet interface seems to be on PCI bus 2  

So at present we are on the FC6 path, which is obviously much
softer on the vagaries of ACPI and is ignoring the crap data returns.

mjt


> -Original Message-
> From: Jerry McAllister [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 20 April 2007 12:40 AM
> To: Murray Taylor
> Cc: FreeBSD Mailing List; [EMAIL PROTECTED]
> Subject: Re: IBM / FreeBSD Install problem
> 
> On Thu, Apr 19, 2007 at 10:14:13AM +1000, Murray Taylor wrote:
> 
> > Server: IBM X3850 (88633SM)
> > CPU X 4: 40K2522
> > HDD X 6: 40K1051
> > IBM ServeRAID 8i: 39R8729
> > 
> > We are attempting to install FreeBSD 6.2-RELEASE onto this 
> machine and
> > are running into a problem getting the operating system to 
> recognise the
> > RAID controller. As a result not finding any disks when it comes to
> > installing the O/S.
> > 
> > We have attempted various modifications to the boot 
> process, including
> > the loading of an "aac" module, which according to the BSD website,
> > should provide support for this type of controller.
> 
> I have only installed on a couple of raids and so don't know about
> them all or even this one.   So, this might not apply to your 
> situation.
> But, I found that I had to study DMESG very carefully to find 
> out what 
> device to use for them.   The system seemed to put out a lot 
> of messages 
> that looked like other device names but in the end there was just one 
> little line that pointed to the correct one.The most 
> recent one was 
> a Dell Perc 3i or something like that and I had to run the fixit and 
> study the boot messages to figure it out.I don't have that one 
> available to look at what it turned out to be, but it was more simple 
> than I first thought from all the stuff it wrote out.  After mucking
> with fixit a bit, then sysinstall seemed to figure it out OK.  I don't
> remember actually changing anything - just fishing around a while.
> I may have run fdisk under fixit to look at things and maybe delete
> some slices.
> 
> So, rather than trying to change things right off, I would suggest
> looking carefully at stuff and trying to determine what it is already
> doing.
> 
> Anyway, good luck,
> 
> jerry
> 
> > 
> > When we attempt to boot to OS to install after making these above
> > modifications, the boot loader advises that this module 
> already appears
> > to be loaded, which contradicts what I believe. In any respect, it
> > doesn't work either way (with or without the module 
> manually loaded).
> > 
> > One side note (which i don't think is contributing) is that when I
> > attempt to start the boot loader with ACPI enabled, it 
> freezes with the
> > message "cpu id 38 too high". However if I boot the boot loader with
> > ACPI disabled, this message dissapears. It _may_ be a 
> possibility that a
> > bi-product of disabling the ACPI is causing the RAID 
> controller to have
> > issues. This appears to be an issue because of the X4 CPU count ??
> > 
> > That's a quick summary of the problem we have, and the 
> path(s) we have
> > been down to date to attempt to fix it. Any help you can 
> provide would
> > be very much appreciated. We are at the position now where we are
> > prepared to pay for consulting services to get it going.
> > 
> > Dave Faulkner / Murray Taylor
> > 
> > Bytecraft Systems
> > 
> > 
> > --
> > 
> > "Any intelligent fool can make things bigger and more complex... It
> > takes a
> > touch of genius - and a lot of courage to move in the opposite
> > direction."
> > --Albert Einstein 
> > ---
> > The information transmitted in this e-mail is for the exclusive
> > use of the intended addressee and may contain confidential
> > and/or privileged material. Any review, re-transmission,
> > dissemination or other use of it, or the taking of any action
> > in reliance upon this in

Re: IBM / FreeBSD Install problem

[Dag-Erling Smørgrav]

Mark Tinguely <[EMAIL PROTECTED]> writes:
> I suggested that in email too, but looking closer, I think the MAXCPU
> needs to be increased because the cpu number uses the apic_id. Or could
> that be changed with a logical CPU to APIC ID lookup?
>
> Isn't the APIC IDs programmable? not that I am suggesting that, I
> can think of headaches of all the places (like interrupt tables)
> where it needs to be changed, not to mention the worry that the
> lower APIC IDs were assigned to IOAPICs.

I don't know, you'd have to ask jhb@ about the details.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[Mark Tinguely]

>
>  If you can either install without ACPI, or remove two of the CPUs
>  during installation, this should be fairly easy to fix: change the
>  definition of NLAPICS in /usr/src/sys/{amd64,i386}/acpica/madt.c and
>  rebuild your kernel, then boot with ACPI enabled and report back to
>  us.
>
>  DES
>  --=20
>  Dag-Erling Sm=F8rgrav - [EMAIL PROTECTED]

I suggested that in email too, but looking closer, I think the MAXCPU
needs to be increased because the cpu number uses the apic_id. Or could
that be changed with a logical CPU to APIC ID lookup?

Isn't the APIC IDs programmable? not that I am suggesting that, I
can think of headaches of all the places (like interrupt tables)
where it needs to be changed, not to mention the worry that the
lower APIC IDs were assigned to IOAPICs.

--Mark Tinguely
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[Dag-Erling Smørgrav]

"Murray Taylor" <[EMAIL PROTECTED]> writes:
> We are attempting to install FreeBSD 6.2-RELEASE onto this machine and
> are running into a problem getting the operating system to recognise the
> RAID controller. As a result not finding any disks when it comes to
> installing the O/S.
>
> We have attempted various modifications to the boot process, including
> the loading of an "aac" module, which according to the BSD website,
> should provide support for this type of controller.

Excuse me for asking a stupid question, but did you define an array
before attempting to install FreeBSD?  The aac driver won't attach
individual disks, it will only attached defined arrays.

> When we attempt to boot to OS to install after making these above
> modifications, the boot loader advises that this module already appears
> to be loaded, which contradicts what I believe. In any respect, it
> doesn't work either way (with or without the module manually loaded).

The loader is correct, aac is included in GENERIC.

> One side note (which i don't think is contributing) is that when I
> attempt to start the boot loader with ACPI enabled, it freezes with the
> message "cpu id 38 too high". However if I boot the boot loader with
> ACPI disabled, this message dissapears. It _may_ be a possibility that a
> bi-product of disabling the ACPI is causing the RAID controller to have
> issues. This appears to be an issue because of the X4 CPU count ??

It appears the server uses non-consecutive CPU numbers, and we use a
static array with 32 slots, indexed by CPU number, to hold information
about the CPUs (or rather the local APICs they contain).

If you can either install without ACPI, or remove two of the CPUs
during installation, this should be fairly easy to fix: change the
definition of NLAPICS in /usr/src/sys/{amd64,i386}/acpica/madt.c and
rebuild your kernel, then boot with ACPI enabled and report back to
us.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[Jerry McAllister]

On Thu, Apr 19, 2007 at 10:14:13AM +1000, Murray Taylor wrote:

> Server: IBM X3850 (88633SM)
> CPU X 4: 40K2522
> HDD X 6: 40K1051
> IBM ServeRAID 8i: 39R8729
> 
> We are attempting to install FreeBSD 6.2-RELEASE onto this machine and
> are running into a problem getting the operating system to recognise the
> RAID controller. As a result not finding any disks when it comes to
> installing the O/S.
> 
> We have attempted various modifications to the boot process, including
> the loading of an "aac" module, which according to the BSD website,
> should provide support for this type of controller.

I have only installed on a couple of raids and so don't know about
them all or even this one.   So, this might not apply to your situation.
But, I found that I had to study DMESG very carefully to find out what 
device to use for them.   The system seemed to put out a lot of messages 
that looked like other device names but in the end there was just one 
little line that pointed to the correct one.The most recent one was 
a Dell Perc 3i or something like that and I had to run the fixit and 
study the boot messages to figure it out.I don't have that one 
available to look at what it turned out to be, but it was more simple 
than I first thought from all the stuff it wrote out.  After mucking
with fixit a bit, then sysinstall seemed to figure it out OK.  I don't
remember actually changing anything - just fishing around a while.
I may have run fdisk under fixit to look at things and maybe delete
some slices.

So, rather than trying to change things right off, I would suggest
looking carefully at stuff and trying to determine what it is already
doing.

Anyway, good luck,

jerry

> 
> When we attempt to boot to OS to install after making these above
> modifications, the boot loader advises that this module already appears
> to be loaded, which contradicts what I believe. In any respect, it
> doesn't work either way (with or without the module manually loaded).
> 
> One side note (which i don't think is contributing) is that when I
> attempt to start the boot loader with ACPI enabled, it freezes with the
> message "cpu id 38 too high". However if I boot the boot loader with
> ACPI disabled, this message dissapears. It _may_ be a possibility that a
> bi-product of disabling the ACPI is causing the RAID controller to have
> issues. This appears to be an issue because of the X4 CPU count ??
> 
> That's a quick summary of the problem we have, and the path(s) we have
> been down to date to attempt to fix it. Any help you can provide would
> be very much appreciated. We are at the position now where we are
> prepared to pay for consulting services to get it going.
> 
> Dave Faulkner / Murray Taylor
> 
> Bytecraft Systems
> 
> 
> --
> 
> "Any intelligent fool can make things bigger and more complex... It
> takes a
> touch of genius - and a lot of courage to move in the opposite
> direction."
> --Albert Einstein 
> ---
> The information transmitted in this e-mail is for the exclusive
> use of the intended addressee and may contain confidential
> and/or privileged material. Any review, re-transmission,
> dissemination or other use of it, or the taking of any action
> in reliance upon this information by persons and/or entities
> other than the intended recipient is prohibited. If you
> received this in error, please inform the sender and/or
> addressee immediately and delete the material. 
> 
> E-mails may not be secure, may contain computer viruses and
> may be corrupted in transmission. Please carefully check this
> e-mail (and any attachment) accordingly. No warranties are
> given and no liability is accepted for any loss or damage
> caused by such matters.
> ---
> 
> ### This e-mail message has been scanned for Viruses by Bytecraft ###
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD - Install Update - Seems to be ACPI

[David Robillard]

In our initial posts, we stated that we seemed to be having issues
getting the machine to boot with the 4 processors, so to bypass this we
disabled ACPI on boot. This allowed us to get past the CPU error and
continue to boot. However down the track we noticed things like the
ethernet adapater not getting picked up, and the big problem - none of
the disks getting recognised.

We have since tried a few things, one of which was removing all but one
of the CPU's. If we do this, and boot with ACPI enabled, all is totally
fine. All disks are found, and I receive no CPU panic error.

So it appears to me that by disabling ACPI in an attempt to bypass the
QUAD CPU problem, we are causing another issue behind the scenes.

The root of the problem now appears to be, that if we have anything over
1 CPU, directly after the kernel is loaded (when booting from the CD),
we receive the error message "panic: madt_probe_cpus_handler: CPU ID 38
Too High". The moment a second CPU to the machineit bombs out.



Have you tried to present this issue to some specific FreeBSD mailing lists?
I believe some of these might be more suited to help you.

These lists come to mind:

FreeBSD Bugs
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs

FreeBSD ACPI
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi

FreeBSD Hardware
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware

Good luck !

David
--
David Robillard
UNIX systems administrator & Oracle DBA
CISSP, RHCE & Sun Certified Security Administrator
Montreal: +1 514 966 0122
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FW: IBM / FreeBSD - Install Update - Seems to be ACPI

[Derek Ragona]

At 11:32 PM 4/18/2007, Murray Taylor wrote:


In our initial posts, we stated that we seemed to be having issues
getting the machine to boot with the 4 processors, so to bypass this we
disabled ACPI on boot. This allowed us to get past the CPU error and
continue to boot. However down the track we noticed things like the
ethernet adapater not getting picked up, and the big problem - none of
the disks getting recognised.

We have since tried a few things, one of which was removing all but one
of the CPU's. If we do this, and boot with ACPI enabled, all is totally
fine. All disks are found, and I receive no CPU panic error.

So it appears to me that by disabling ACPI in an attempt to bypass the
QUAD CPU problem, we are causing another issue behind the scenes.

The root of the problem now appears to be, that if we have anything over
1 CPU, directly after the kernel is loaded (when booting from the CD),
we receive the error message "panic: madt_probe_cpus_handler: CPU ID 38
Too High". The moment a second CPU to the machineit bombs out.


Have you tried booting a custom kernel with SMP enabled from the hard 
drives?  You might try that and install another CPU and see how the system 
reacts.


Are these CPU's hyperthreaded too?  Or just single core CPU's?  I have had 
problems installing with some systems if hyperthreading was enabled.  Post 
installation with a custom SMP enabled kernel built I could turn 
hyperthreading on or off and the system booted and ran fine.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FW: IBM / FreeBSD - Install Update - Seems to be ACPI

[Murray Taylor]

In our initial posts, we stated that we seemed to be having issues
getting the machine to boot with the 4 processors, so to bypass this we
disabled ACPI on boot. This allowed us to get past the CPU error and
continue to boot. However down the track we noticed things like the
ethernet adapater not getting picked up, and the big problem - none of
the disks getting recognised.

We have since tried a few things, one of which was removing all but one
of the CPU's. If we do this, and boot with ACPI enabled, all is totally
fine. All disks are found, and I receive no CPU panic error.

So it appears to me that by disabling ACPI in an attempt to bypass the
QUAD CPU problem, we are causing another issue behind the scenes.

The root of the problem now appears to be, that if we have anything over
1 CPU, directly after the kernel is loaded (when booting from the CD),
we receive the error message "panic: madt_probe_cpus_handler: CPU ID 38
Too High". The moment a second CPU to the machineit bombs out.

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FW: IBM / FreeBSD Install problem - more part 2

[Murray Taylor]

 BTW we have also successfully booted the 
'offending box' with FC4 and it all came up ok.
This should rule out hardware issues I hope.

Is there a way to force a (re)scan of the other PCI
busses ??

Or is there a hint.??? line I can add?

mjt

-Original Message-
From: Murray Taylor 
Sent: Thursday, 19 April 2007 11:26 AM
To: FreeBSD Mailing List; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: IBM / FreeBSD Install problem - more

OK -- at present I cannot get a 6.2 install disk
to get anywhere further.

Trying FreeSBIE 2.0.1  (aka 6.2) I can get a boot
with 

set hint.acpi.0.disabled=1
set acpi_load=NO
boot -v

However it doesnt find the bge card nor has it found
an fxp card we have tried, so I cant get to dmesg output 
off the machine

What i have seen is that the ServeRAID 8i controller 
say it is on PCI bus 1:2:0

Nowhere in the boot log is pcib1 or any mention of
the physical pci bus 1

Just to test I booted an IBM pizza box x305 with the FreeSBIE disk
in the same fashion, and up comes its bge i/f, the boot -v logs 
show 

pcib0 , pcib1 , pcib2

along with their associated physical busses.

Any help  greatly welcomed

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FW: IBM / FreeBSD Install problem - more

[Murray Taylor]

OK -- at present I cannot get a 6.2 install disk
to get anywhere further.

Trying FreeSBIE 2.0.1  (aka 6.2) I can get a boot
with 

set hint.acpi.0.disabled=1
set acpi_load=NO
boot -v

However it doesnt find the bge card nor has it found
an fxp card we have tried, so I cant get to dmesg output 
off the machine

What i have seen is that the ServeRAID 8i controller 
say it is on PCI bus 1:2:0

Nowhere in the boot log is pcib1 or any mention of
the physical pci bus 1

Just to test I booted an IBM pizza box x305 with the FreeSBIE disk
in the same fashion, and up comes its bge i/f, the boot -v logs 
show 

pcib0 , pcib1 , pcib2

along with their associated physical busses.

Any help  greatly welcomed

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: IBM / FreeBSD Install problem

[Murray Taylor]

From: Derek Ragona [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 18 April 2007 11:34 PM
To: Murray Taylor; FreeBSD Mailing List
Cc: [EMAIL PROTECTED]
Subject: Re: IBM / FreeBSD Install problem


At 07:07 AM 4/18/2007, Murray Taylor wrote:


Server: IBM X3850 (88633SM)
CPU X 4: 40K2522
HDD X 6: 40K1051
IBM ServeRAID 8i: 39R8729

We are attempting to install FreeBSD 6.2-RELEASE onto
this machine and
are running into a problem getting the operating system
to recognise the
RAID controller. As a result not finding any disks when
it comes to
installing the O/S.

We have attempted various modifications to the boot
process, including
the loading of an "aac" module, which according to the
BSD website,
should provide support for this type of controller.

When we attempt to boot to OS to install after making
these above
modifications, the boot loader advises that this module
already appears
to be loaded, which contradicts what I believe. In any
respect, it
doesn't work either way (with or without the module
manually loaded).

One side note (which i don't think is contributing) is
that when I
attempt to start the boot loader with ACPI enabled, it
freezes with the
message "cpu id 38 too high". However if I boot the boot
loader with
ACPI disabled, this message dissapears. It _may_ be a
possibility that a
bi-product of disabling the ACPI is causing the RAID
controller to have
issues. This appears to be an issue because of the X4
CPU count ??

That's a quick summary of the problem we have, and the
path(s) we have
been down to date to attempt to fix it. Any help you can
provide would
be very much appreciated. We are at the position now
where we are
prepared to pay for consulting services to get it going.

Dave Faulkner / Murray Taylor

Bytecraft Systems



Are you creating an Array before you try the installation?

What does the console show for the recognized hardware, and not
recognized hardware?
  You can boot from CD and run dmesg to get this information.

-Derek

 
The array is already created...
 
The hardware for the RAID array _and_ the bge interface are not found.

Murray Taylor

Special Projects Engineer
Bytecraft Systems

P: +61 3 8710 2555
F: +61 3 8710 2599
D: +61 3 9238 4275
E: [EMAIL PROTECTED] 


--

"Any intelligent fool can make things bigger and more complex... It
takes a
touch of genius - and a lot of courage to move in the opposite
direction."
--Albert Einstein 


 
---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FW: IBM / FreeBSD Install problem - more part 2

[Murray Taylor]

 BTW we have also successfully booted the 
'offending box' with FC4 and it all came up ok.
This should rule out hardware issues I hope.

Is there a way to force a (re)scan of the other PCI
busses ??

Or is there a hint.??? line I can add?

mjt

-Original Message-
From: Murray Taylor 
Sent: Thursday, 19 April 2007 11:26 AM
To: FreeBSD Mailing List; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: IBM / FreeBSD Install problem - more

OK -- at present I cannot get a 6.2 install disk
to get anywhere further.

Trying FreeSBIE 2.0.1  (aka 6.2) I can get a boot
with 

set hint.acpi.0.disabled=1
set acpi_load=NO
boot -v

However it doesnt find the bge card nor has it found
an fxp card we have tried, so I cant get to dmesg output 
off the machine

What i have seen is that the ServeRAID 8i controller 
say it is on PCI bus 1:2:0

Nowhere in the boot log is pcib1 or any mention of
the physical pci bus 1

Just to test I booted an IBM pizza box x305 with the FreeSBIE disk
in the same fashion, and up comes its bge i/f, the boot -v logs 
show 

pcib0 , pcib1 , pcib2

along with their associated physical busses.

Any help  greatly welcomed

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IBM / FreeBSD Install problem - more

[Murray Taylor]

OK -- at present I cannot get a 6.2 install disk
to get anywhere further.

Trying FreeSBIE 2.0.1  (aka 6.2) I can get a boot
with 

set hint.acpi.0.disabled=1
set acpi_load=NO
boot -v

However it doesnt find the bge card nor has it found
an fxp card we have tried, so I cant get to dmesg output 
off the machine

What i have seen is that the ServeRAID 8i controller 
say it is on PCI bus 1:2:0

Nowhere in the boot log is pcib1 or any mention of
the physical pci bus 1

Just to test I booted an IBM pizza box x305 with the FreeSBIE disk
in the same fashion, and up comes its bge i/f, the boot -v logs 
show 

pcib0 , pcib1 , pcib2

along with their associated physical busses.

Any help  greatly welcomed

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IBM / FreeBSD Install problem

[Murray Taylor]

Server: IBM X3850 (88633SM)
CPU X 4: 40K2522
HDD X 6: 40K1051
IBM ServeRAID 8i: 39R8729

We are attempting to install FreeBSD 6.2-RELEASE onto this machine and
are running into a problem getting the operating system to recognise the
RAID controller. As a result not finding any disks when it comes to
installing the O/S.

We have attempted various modifications to the boot process, including
the loading of an "aac" module, which according to the BSD website,
should provide support for this type of controller.

When we attempt to boot to OS to install after making these above
modifications, the boot loader advises that this module already appears
to be loaded, which contradicts what I believe. In any respect, it
doesn't work either way (with or without the module manually loaded).

One side note (which i don't think is contributing) is that when I
attempt to start the boot loader with ACPI enabled, it freezes with the
message "cpu id 38 too high". However if I boot the boot loader with
ACPI disabled, this message dissapears. It _may_ be a possibility that a
bi-product of disabling the ACPI is causing the RAID controller to have
issues. This appears to be an issue because of the X4 CPU count ??

That's a quick summary of the problem we have, and the path(s) we have
been down to date to attempt to fix it. Any help you can provide would
be very much appreciated. We are at the position now where we are
prepared to pay for consulting services to get it going.

Dave Faulkner / Murray Taylor

Bytecraft Systems


--

"Any intelligent fool can make things bigger and more complex... It
takes a
touch of genius - and a lot of courage to move in the opposite
direction."
--Albert Einstein 
---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IBM / FreeBSD Install problem

[Derek Ragona]

At 07:07 AM 4/18/2007, Murray Taylor wrote:

Server: IBM X3850 (88633SM)
CPU X 4: 40K2522
HDD X 6: 40K1051
IBM ServeRAID 8i: 39R8729

We are attempting to install FreeBSD 6.2-RELEASE onto this machine and
are running into a problem getting the operating system to recognise the
RAID controller. As a result not finding any disks when it comes to
installing the O/S.

We have attempted various modifications to the boot process, including
the loading of an "aac" module, which according to the BSD website,
should provide support for this type of controller.

When we attempt to boot to OS to install after making these above
modifications, the boot loader advises that this module already appears
to be loaded, which contradicts what I believe. In any respect, it
doesn't work either way (with or without the module manually loaded).

One side note (which i don't think is contributing) is that when I
attempt to start the boot loader with ACPI enabled, it freezes with the
message "cpu id 38 too high". However if I boot the boot loader with
ACPI disabled, this message dissapears. It _may_ be a possibility that a
bi-product of disabling the ACPI is causing the RAID controller to have
issues. This appears to be an issue because of the X4 CPU count ??

That's a quick summary of the problem we have, and the path(s) we have
been down to date to attempt to fix it. Any help you can provide would
be very much appreciated. We are at the position now where we are
prepared to pay for consulting services to get it going.

Dave Faulkner / Murray Taylor

Bytecraft Systems


Are you creating an Array before you try the installation?

What does the console show for the recognized hardware, and not recognized 
hardware?  You can boot from CD and run dmesg to get this information.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IBM / FreeBSD Install problem

[Murray Taylor]

Server: IBM X3850 (88633SM)
CPU X 4: 40K2522
HDD X 6: 40K1051
IBM ServeRAID 8i: 39R8729

We are attempting to install FreeBSD 6.2-RELEASE onto this machine and
are running into a problem getting the operating system to recognise the
RAID controller. As a result not finding any disks when it comes to
installing the O/S.

We have attempted various modifications to the boot process, including
the loading of an "aac" module, which according to the BSD website,
should provide support for this type of controller.

When we attempt to boot to OS to install after making these above
modifications, the boot loader advises that this module already appears
to be loaded, which contradicts what I believe. In any respect, it
doesn't work either way (with or without the module manually loaded).

One side note (which i don't think is contributing) is that when I
attempt to start the boot loader with ACPI enabled, it freezes with the
message "cpu id 38 too high". However if I boot the boot loader with
ACPI disabled, this message dissapears. It _may_ be a possibility that a
bi-product of disabling the ACPI is causing the RAID controller to have
issues. This appears to be an issue because of the X4 CPU count ??

That's a quick summary of the problem we have, and the path(s) we have
been down to date to attempt to fix it. Any help you can provide would
be very much appreciated. We are at the position now where we are
prepared to pay for consulting services to get it going.

Dave Faulkner / Murray Taylor

Bytecraft Systems


--

"Any intelligent fool can make things bigger and more complex... It
takes a
touch of genius - and a lot of courage to move in the opposite
direction."
--Albert Einstein 

---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

### This e-mail message has been scanned for Viruses by Bytecraft ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: unattended FreeBSD install

[Brian A. Seklecki]

The trick about make release(7) is that it installs your native /usr/obj
into /usr/release_chroot or wherever and begins a fresh make buildworld
in it's chroot and doesn't honor or systems' make.conf(5).

Good for integrating source patches
Bad for pruning out subsystems / profiling.

~BAS

On Mon, 2007-03-19 at 15:53 -0400, Dave wrote:
> Hello,
> I've read a howto on creating your own FreeBSD isos located at:
> 
> http://romana.now.ie/writing/customfreebsdiso.html
> 
> and i'd like to combine this with an unattended file install.cfg i believe 
> it is. My goal is to go to a box, boot it from CD, then walk away, come 
> back, and the OS including patches is insalled and ready to go with custom 
> packages already installed. If anyone has any working configs, so far my 
> atempts to create an unattend file, have not been successful, i'd appreciate 
> them.
> Thanks.
> Dave.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-- 
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.




IMPORTANT: This message contains confidential information and is intended only 
for the individual named. If the reader of this message is not an intended 
recipient (or the individual responsible for the delivery of this message to an 
intended recipient), please be advised that any re-use, dissemination, 
distribution or copying of this message is prohibited.  Please notify the 
sender immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

unattended FreeBSD install

[Dave]

Hello,
I've read a howto on creating your own FreeBSD isos located at:

http://romana.now.ie/writing/customfreebsdiso.html

and i'd like to combine this with an unattended file install.cfg i believe 
it is. My goal is to go to a box, boot it from CD, then walk away, come 
back, and the OS including patches is insalled and ready to go with custom 
packages already installed. If anyone has any working configs, so far my 
atempts to create an unattend file, have not been successful, i'd appreciate 
them.

Thanks.
Dave.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to mount an already freebsd paritioned external usb drive onto a new freebsd install

[perryh]

> I was running FreebBSD 5.x until a few days ago at home on a little
> shuttle cube server with a celeron processor when my hard drive
> appeared to develop multiple problems and finally died.  I had a
> western digital external usb hard drive attached to the server that
> I used for daily backups ... The WD usb drive has a freebsd partition
> on it already.  I want to mount this drive so I can start to move
> backed up data to the new box ...

Depending on how you plan to extract the data, you may not need
to mount it at all.  dump(8) will open and read the special file
(/dev/whatever) directly.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to mount an already freebsd paritioned external usb drive onto a new freebsd install

[Andrew Pantyukhin]

On 12/31/06, Steve <[EMAIL PROTECTED]> wrote:

Hi,

I was running FreebBSD 5.x until a few days ago at home on a little shuttle
cube server with a celeron processor when my hard drive appeared to develop
multiple problems and finally died.  I had a western digital external usb
hard drive attached to the server that I used for daily backups.  So I got
a new hard drive and installeed FreeBSD 6.1 on it.  I have plugged in the
WD external usb drive and ran:

dmesg
camcontrol devlist

And the WD usb drive seems to recognized by the system and all is
well.  The WD usb drive has a freebsd partition on it already.  I want to
mount this drive so I can start to move backed up data to the new box, but
reading through the handbook and doing a google search, I'm still not clear
exactly how to do it.  I don't remember how I had setup the old box to
mount the drive as I had done it almost two years ago.

If someone can tell me what to do or point me in the right direction it
would be appreciated.  I really don't want to mess this up.


Assuming the drive you want to mount is /dev/da0, you
should first determine what slices and partitions it
has. It's very easy, just "ls /dev/da0*" for that. Let's
pretend you see something like this:

/dev/da0
/dev/da0s1
/dev/da0s1a
/dev/da0s1b
/dev/da0s1c
/dev/da0s1d
/dev/da0s1e

It might be a lot simpler or a lot more complicated. This
exact result means you have one slice (s1) and several
partitions (a-e). "b" is a swap partition, "c" represents
the whole slice, you only have to mount "a", "d" and "e".

mkdir -p /mnt/a /mnt/d /mnt/e
mount /dev/da0s1a /mnt/a
mount /dev/da0s1d /mnt/d
mount /dev/da0s1e /mnt/e

Use "mount -r" instead of just "mount" to make them read-
only (for safety).

Good luck!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

how to mount an already freebsd paritioned external usb drive onto a new freebsd install

[Steve]

Hi,

I was running FreebBSD 5.x until a few days ago at home on a little shuttle 
cube server with a celeron processor when my hard drive appeared to develop 
multiple problems and finally died.  I had a western digital external usb 
hard drive attached to the server that I used for daily backups.  So I got 
a new hard drive and installeed FreeBSD 6.1 on it.  I have plugged in the 
WD external usb drive and ran:


dmesg
camcontrol devlist

And the WD usb drive seems to recognized by the system and all is 
well.  The WD usb drive has a freebsd partition on it already.  I want to 
mount this drive so I can start to move backed up data to the new box, but 
reading through the handbook and doing a google search, I'm still not clear 
exactly how to do it.  I don't remember how I had setup the old box to 
mount the drive as I had done it almost two years ago.


If someone can tell me what to do or point me in the right direction it 
would be appreciated.  I really don't want to mess this up.




Steve Bopple
www.digitalbluesky.net 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

freebsd install on poweredge 2900

[Stas Khromoy]

hey folks

trying to install freebsd 6.1 on dell's poweredge 2900
6 hard drives on *perc 5/i integrated controller
( the drives are 146gb SAS).

i've set up raid 1 for the first 2 drives
and raid 10 for the remaining 4 .
everything is showing up tip-top in the controller configuration
one virtual drive is 146gb the other one is 280gb

when i finally get to partioning  menu during the FreeBSD install
i see two volumes, problem is both of them are showing up as 146GB.







___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Install

[Jerry McAllister]

On Tue, Sep 26, 2006 at 02:28:47PM -0400, Edward and Nancy Powers wrote:

> 
>   I am new to UNIX, and would like to download FreeBSD to familiarize
>   myself with UNIX commands and the UNIX environment.   I would like
>   something fairly easy to install and maintain.  I do not want to
>   replace Windows, but would like to switch between Windows and FreeBSD.
> 
>   Is it possible to do this with FreeBSD?

Note, you will probably also see posts of people's favorite thing
to push in response to your question as well as possibly some people
trying to tell you not to bother with FreeBSD is you are happy
with MS-Win even though you specifically say you want to learn\
about UNIX.   

Take it all with a grain or tub of salt and try out any of the
suggestions you want, but don't think they are canonical information.
They are just peoples whims and preferences and are no more or less
valid than yours after you have experimented a little.

Have fun,

jerry

> 
> 
>   Ed Powers
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"