12-15-2009
I doubt OpenSolaris as a pdc is something commonly deployed. If configuring samba as a pdc under freeBSD is a nightmare, the same statement will likely apply to OpenSolaris.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Can Linux be a PDC for Windows 2000 or Windows XP clients? If so how do I set this is. By the way im using Red Hat 7.3. (1 Reply)
Discussion started by: DonSJ67
1 Replies
2. UNIX for Dummies Questions & Answers
this is the seventh problem i'm having with samba.
for some reason, i cannot logon to the domain.
i've created user accounts... and i was able to establish a connection between
the samba server (my PDC) and my workstations by logging in as "root."
however now when i try to logon it gives... (5 Replies)
Discussion started by: xyyz
5 Replies
3. UNIX for Dummies Questions & Answers
Hi there,
Hope this forum is adapted to my question. I have :
+ 1 Debian server with Samba set to authenticate users in the domain HOME (workgroup = HOME / domain logons = yes).
+ 3 Windows XP Laptops configured to belong to the domain HOME. So on startup, I'm invited to enter a login password... (2 Replies)
Discussion started by: chebarbudo
2 Replies
4. Shell Programming and Scripting
Hi,
I currently use the ntpdate and date command to sync the internal clock source of my Solaris systems to the primary domain controller.
admin@myserver # ntpdate -d -u 192.168.???.???
14 Jan 17:42:02 ntpdate: ntpdate 3-5.93e+sun 03/06/05 23:16:45 (1.4)
transmit(192.168.???.???)... (2 Replies)
Discussion started by: jamba1
2 Replies
5. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I have a barebones XP Pro SP2 with no firewall.
CentOS 5.xx running a Samba 3.xx Domain (PDC)
The XP machine... (2 Replies)
Discussion started by: pogipants
2 Replies
6. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
7. Red Hat
Hi all
I am facing a problem.
I have configured SAMBA PDC on RHEL 6. Everything is going very smooth. Users are being logged in properly & their network drives (i-e; z: drives) are being shown. But either i login to Windows XP or Windows 7, user's profile does not get loaded. I get an error... (0 Replies)
Discussion started by: Yawar_Aziz
0 Replies
pdc(1M) pdc(1M)
NAME
pdc - processor-dependent code (firmware)
DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com-
pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard-
ware as described below.
To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot
Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model.
When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini-
tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con-
sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths.
If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character
on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support
autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium.
If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A
simple menu is then displayed where the user can:
o Boot a specific device, using the abbreviated path identifier, or the full mnemonic.
o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not
check the contents).
o Enter the boot administration level.
o Exit the menu and return to autobooting
o Get help on choices
If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the
Boot Path to use. Any required path components that are not supplied default to zero.
The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via
SEE ALSO
boot(1M), isl(1M).
PA-RISC Systems Only pdc(1M)