11-22-2012
yes you need the mac if you like to install a server via jumpstart... getting the mac depends on how you are connected to the remote server. to use jumpstart you need access to the servers console/obp. from there you'll find the mac address easily.
show-nets will give you the physical path to your networkdevices. use cd to navigate to the device and view all information about that device with .properties
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have been asked to research Jumpstart and don't know where to begin! Any ideas would be much appreciated! Thanks! :-) (1 Reply)
Discussion started by: avana100
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Which sites have general information on JumpStart for Solaris 8?
I would like to know more about boot server, installation server, and configuration server.... and all other good things about JumpStart....Thanks..:p
Doo... (2 Replies)
Discussion started by: dookeobih
2 Replies
3. UNIX for Advanced & Expert Users
HI.
i was wondering if you can jumpstart using the solaris intel platform? please help thanks (3 Replies)
Discussion started by: souldier
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
where can i find documention on how to create a jumpstart system?
dori (2 Replies)
Discussion started by: dorilevy
2 Replies
5. Solaris
Hello all,
I configured a jumpstart server ( the server is in the same subnet as the client) and gave boot net - install in the client.
The client boots up shows the banner and then displays error:
cant read disk label
cant open disk label package
and then goes to OK prompt.
What... (1 Reply)
Discussion started by: Pratik Gharti
1 Replies
6. Solaris
Hi Peeps,
Created a jumpstart server for an unattened install and it works, but got 2 bugs in the config which I would like to work out:
when you boot net install
It still asks you to select a language and locale, after you do this it kicks of an unattended install.
So my question is,... (5 Replies)
Discussion started by: callmebob
5 Replies
7. Solaris
Hello All,
Do I really need to add the install server name in the /etc/hosts file? Why do we need to add? If I don't add it is not working. Isn't it only arp/rarp works here? I thought it works in mac address level. thanks in advance. (3 Replies)
Discussion started by: mokkan
3 Replies
8. Solaris
Keep getting this message after system identification portion.
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services:Assertion failed: *count <= max, file ns_dns_misc.c, line 189
Abort - core dumped... (0 Replies)
Discussion started by: soupbone38
0 Replies
9. Solaris
Hi everyone,
We have a T5240 and noticed we were having issues booting the system using our jumpstart server (it seems as though we don't have the correct drivers for the nxge NIC)
We thought we needed to update our jumpstart server image 9/10 Solaris SPARC image.
Now I'm still learning... (4 Replies)
Discussion started by: Keepcase
4 Replies
10. Solaris
I want to have a bootable DVD that will perform a jumpstart install of Solaris 10 x86 I've mainly used JumpStart DVD (with Solaris flash archive) for x86 platform as a reference, and I used the sysidcfg, profile, rules, etc. from a working jumpstart server. For the life of me, though, I cannot... (1 Reply)
Discussion started by: jnojr
1 Replies
LEARN ABOUT FREEBSD
mac_is_present
MAC_IS_PRESENT(3) BSD Library Functions Manual MAC_IS_PRESENT(3)
NAME
mac_is_present -- report whether the running system has MAC support
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/mac.h>
int
mac_is_present(const char *policyname);
DESCRIPTION
The mac_is_present() function determines whether the currently-running kernel supports MAC for a given policy or not. If policyname is
non-NULL, the presence of the named policy (e.g. ``biba'', ``mls'', ``te'') is checked, otherwise the presence of any MAC policies at all is
checked.
RETURN VALUES
If the system supports the given MAC policy, the value 1 is returned. If the specified MAC policy is not supported, the value 0 is returned.
If an error occurs, the value -1 is returned.
ERRORS
[EINVAL] The value of policyname is not valid.
[ENOMEM] Insufficient memory was available to allocate internal storage.
SEE ALSO
mac(3), mac_free(3), mac_get(3), mac_prepare(3), mac_set(3), mac_text(3), mac(4), mac(9)
HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project.
BSD
July 7, 2006 BSD