Closed
Bug 600282
Opened 14 years ago
Closed 14 years ago
Re-install Mac OSX 10.6 on momo-xserve-01
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gozer, Assigned: phong)
References
Details
We are re-purposing our XServe, and I need it to be running Mac OSX 10.6 (it's 10.5 right now). Unfortunately, that's not something I can do remotely, so I'd like to ask someone from MoCO IT to just install vanilla Mac OSX 10.6 on it and let set an administrator password on it and let me know what it is. Networking should be DHCP, but just in case: Hostname: momo-xserve-01.sj.mozillamessaging.com IP: 10.200.80.100 Netmask: 255.255.255.0 Gateway: 10.200.80.1 DNS: 10.200.74.10, 10.200.74.11 There is a LOM module on it and it shouldn't need changing either. It's at 10.200.80.101 and 10.200.80.102 (same network) There is nothing to backup or archive on that thing, and it's currently idle. So it can be re-installed at wish. Thanks!
Comment 1•14 years ago
|
||
When do you need it by?
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > When do you need it by? Soon, but it's not dramatic. This week would be great, next week okay too.
Updated•14 years ago
|
Assignee: server-ops → phong
Assignee | ||
Comment 3•14 years ago
|
||
Is there anything we need to back up on this server before I blow it away?
Comment 4•14 years ago
|
||
Phong: I've reconfirmed with gozer that there is nothing of value on momo-xserve-01. Please feel free to proceed with the reinstall. Thanks.
Assignee | ||
Comment 5•14 years ago
|
||
Is this a PPC or Intel server? 10.6 will only support on Intel.
Comment 6•14 years ago
|
||
It's an Intel server
Assignee | ||
Comment 7•14 years ago
|
||
I will update this the next time I am at the data center.
Flags: colo-trip+
Assignee | ||
Comment 8•14 years ago
|
||
updated to clean 10.6 install.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•