Moving HDD with FreeBSD installed between machines with different hardware.

From: Dan MacMillan (flowers_at_users.sourceforge.net)
Date: 06/29/04

  • Next message: Vulpes Velox: "Re: cue images" 
    Date: Tue, 29 Jun 2004 13:28:21 -0600
To: freebsd-questions@freebsd.org

    Hello,

    I have a machine with FreeBSD installed on it that is serving DNS, CVS, NTP
    and a few other things for our organization. I plan to add a mail gateway
    using Postfix, ClamAV, amavisd-new and SpamAssassin as well to protect the
    tender underbelly of our MS Exchange server. However the machine is running
    5.1-RELEASE. It shouldn't be. :)

    I would like to rebuild the machine completely to exercise the knowledge I
    have gained re: FreeBSD but I can't afford for it to be down for the length
    of time it would take and I don't have a standby machine available. So what
    I'm thinking is that I could take a spare hard drive home and pop it in one
    of my own machines, install FreeBSD on that, and then bring it back to work
    and swap the hard drive out with the one in the production machine.

    What kind of problems am I letting myself in for if I go ahead with this?
    The hardware in the two machines in question is quite dissimilar. For
    example, one's an Athlon 266 with 64MB of RAM, one's a Pentium[-something]
    300 with 400 MB.

    Here are the things that occurred to me:

    One of them has an 'rl0' NIC, the other 'dc0'. So I'd have to change the
    ifconfig_ line in /etc/rc.conf. But would this also imply changes elsewhere
    that would have to be made?

    Actually, that's all I've thought of so far. Are there any gotchas I should
    be considering? 

    --
Danny MacMillan
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Vulpes Velox: "Re: cue images"

    Relevant Pages

    • Re: [9fans] 9vx
      ... Plan 9 up on a new machine. ... That code hasn't been changed much since drawterm, ... Life is so boring when your OS doesn't break compatibility with ... FreeBSD and OS X; ah I got the solution: ...
      (comp.os.plan9)
    • Re: cpuctl(formely devcpu) patch test request
      ... Do you plan to MFC this? ... In fact, I plan to MFC that to all supported FreeBSD versions, ... ENOSYS if mallocfails and ENXIO instead of ENOSYS if MSR functionality is ...
      (freebsd-current)
    • Re: cpuctl(formely devcpu) patch test request
      ... Rui Paulo mentioned: ... Do you plan to MFC this? ... In fact, I plan to MFC that to all supported FreeBSD versions, ...
      (freebsd-current)
    • Re: upgrading xorg?
      ... nobody is forcing you to use FreeBSD. ... devise a strategy / plan for how to implement this upgrade in the most efficient way for your environment ... and my time is spent designing/testing/building ...
      (comp.unix.bsd.freebsd.misc)
    • Re: My planned work on networking stack
      ... K>> B> That's the plan, I believe, anyway... ... K>> B> taught about how to add TCP-MD5 keys to both FreeBSD and OpenBSD SADBs. ... K>> Is there any plans about integration of BGP routing daemon (Zebra or Quagga) ...
      (freebsd-current)