Installation questions

xviddivxoggmp3 · 07-18-2004, 01:28 AM

I was reading the freebsd installation guide, and see that it states to take down system information that is logged in my os (hardware, drivers, etc.) how would i do this? I'm using slackware on the box in question.

frob23 · 07-18-2004, 03:52 AM

Okay,

print a copy of the output from "dmesg"

it might be wise to print a copy of files you have changed in /etc ... like rc.conf and rc.local

If you are going to dual boot then most of this information can be gained by mounting the linux disk and poking around etc.

I think that instruction is more applicable to windows because it makes it much harder to find the information if you don't boot into the system. As everything works in Linux I expect you will not have any problems with FreeBSD

xviddivxoggmp3 · 07-18-2004, 07:55 PM

what do you mean by this

Quote:

it might be wise to print a copy of files you have changed in /etc ... like rc.conf and rc.local

do you mean my .bashrc file?

frob23 · 07-18-2004, 09:08 PM

Have you made any changes to /etc... like hard coding your ip address? or having a hosts file so you can talk to other computers on your network by name?

Most global settings will be in there. If you haven't made any... you probably will be safe not looking at it -- but you may find some things are automatically setup for you.

The dmesg command will list out all your hardware as Linux sees it. That is useful to see if BSD found everything.

xviddivxoggmp3 · 07-18-2004, 09:39 PM

i know it missed a couple things when i loaded linux, but they are very inconsiquential (i.e. radio tuner, video capture card, etc.)
my pc isn't powerful enough for half of the gadget i got for it.
time to upgrade.
thanks for the details.
i was advised on the forum that i would need to know the cylinders and things like that.
if i'm not dual booting the directions say this is not needed.
what is correct?

frob23 · 07-18-2004, 09:45 PM

If you have linux on the drive, you should not need to know the cylinders and all that.

But if you want to be safe, and who doesn't, do "fdisk /dev/hda" and it should spit that information out for you... then just write it down.