03-07-2007
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have been facing a telnet problem with our SunOS 5.7 box. Initially we were facing porblems in login both from the console as well as through telnet. The machine was hard-booted after which login from console is possible, but telnet connection is not.
The error that is displayed is... (1 Reply)
Discussion started by: manoj_gopal
1 Replies
2. UNIX for Dummies Questions & Answers
Sorry I think someone already pointed out this but I couldn't find it.
Please tell me what is the difference between SunOS Version and Solaris Version.
What is the purpose of maintaining these two things ?
Thanks (2 Replies)
Discussion started by: champion
2 Replies
3. UNIX for Dummies Questions & Answers
Whats the difference between Solaris Relase and SunOS Release?? (1 Reply)
Discussion started by: eloquent99
1 Replies
4. UNIX for Dummies Questions & Answers
Ok I have searched the archives but I don't seem to have a satisfactory answer for my questions.
1, What are the differences between the two in terms of kernel (I'm used to /stand for all)
2, What hardware do they run on?
3, Are they both platforms?
A frustrated HP fan. (3 Replies)
Discussion started by: mattd
3 Replies
5. Solaris
Manufacturer Links
Home Page: Oracle | Hardware and Software, Engineered to Work Together
Documentation: Oracle Documentation
Support: Oracle Configuration Support Manager
Oracle Solaris open source projects: Java.net Maintenance outage
FreeWare
Introduction
http://www.opencsw.org/
... (0 Replies)
Discussion started by: Perderabo
0 Replies
6. UNIX for Advanced & Expert Users
I have compiled binary file using "cc" on SunOS 5.8 and the same binary file i have copied to SunOS 5.9 and it is giving me core dump error.I want to know whether migration of compiled code from lower version to higer version created this problem. how can i solve this problem.I am pasting the core... (1 Reply)
Discussion started by: Arvind Maurya
1 Replies
7. Solaris
Hey all,
I've got my hands on 10 SunOS 5.6 SPARCStation 20 machines and I'm looking to get them up and running. They're all in various states of disrepair but I've got them all to a state where the hardware is working and the machine will at least attempt to boot.
I've only used Solaris as a... (1 Reply)
Discussion started by: kevpatts
1 Replies
8. Solaris
Hi,
I am bulding a path to open files like this \path\values\file.xxx This path is opened in an IE browser window and opens the file/document I am trying to see. I mean it opens a pdf document or it promps you to "save" or "open" the specific file (if it's a .xml, .doc, .html).
I was using... (1 Reply)
Discussion started by: hcibl_javok
1 Replies
9. Solaris
Hi,
I called Sun and they said they no longer sell SunOS 5.6. I desperately need a CD-ROM of the install CD to perform maintenance work on a server.
Does anyone know where to get one or know someone who can make me a copy? (2 Replies)
Discussion started by: mojoman
2 Replies
10. Post Here to Contact Site Administrators and Moderators
7 out of 8 links in one of the two Solaris Sticky threads are dead:
https://www.unix.com/solaris/17943-sunos-solaris-links.html
Could a moderator update them or unlock the thread to allow contributors to provide up to date replacement links ? (3 Replies)
Discussion started by: jlliagre
3 Replies
LEARN ABOUT CENTOS
xcb_randr_get_screen_resources_crtcs_end
xcb_randr_get_screen_resources(3) XCB Requests xcb_randr_get_screen_resources(3)
NAME
xcb_randr_get_screen_resources -
SYNOPSIS
#include <xcb/randr.h>
Request function
xcb_randr_get_screen_resources_cookie_t xcb_randr_get_screen_resources(xcb_connection_t *conn, xcb_window_t window);
Reply datastructure
typedef struct xcb_randr_get_screen_resources_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
xcb_timestamp_t timestamp;
xcb_timestamp_t config_timestamp;
uint16_t num_crtcs;
uint16_t num_outputs;
uint16_t num_modes;
uint16_t names_len;
uint8_t pad1[8];
} xcb_randr_get_screen_resources_reply_t;
Reply function
xcb_randr_get_screen_resources_reply_t *xcb_randr_get_screen_resources_reply(xcb_connection_t *conn,
xcb_randr_get_screen_resources_cookie_t cookie, xcb_generic_error_t **e);
Reply accessors
xcb_randr_crtc_t *xcb_randr_get_screen_resources_crtcs(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_crtcs_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_crtcs_end(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_output_t *xcb_randr_get_screen_resources_outputs(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_outputs_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_outputs_end(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_mode_info_t *xcb_randr_get_screen_resources_modes(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_modes_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_mode_info_iterator_t xcb_randr_get_screen_resources_modes_iterator(const xcb_randr_get_screen_resources_reply_t *reply);
uint8_t *xcb_randr_get_screen_resources_names(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_names_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_names_end(const xcb_randr_get_screen_resources_reply_t *reply);
REQUEST ARGUMENTS
conn The XCB connection to X11.
window TODO: NOT YET DOCUMENTED.
REPLY FIELDS
response_type
The type of this reply, in this case XCB_RANDR_GET_SCREEN_RESOURCES. This field is also present in the xcb_generic_reply_t and
can be used to tell replies apart from each other.
sequence The sequence number of the last request processed by the X11 server.
length The length of the reply, in words (a word is 4 bytes).
timestamp TODO: NOT YET DOCUMENTED.
config_timestamp
TODO: NOT YET DOCUMENTED.
num_crtcs TODO: NOT YET DOCUMENTED.
num_outputs
TODO: NOT YET DOCUMENTED.
num_modes TODO: NOT YET DOCUMENTED.
names_len TODO: NOT YET DOCUMENTED.
DESCRIPTION
RETURN VALUE
Returns an xcb_randr_get_screen_resources_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_screen_re-
sources_reply.
If you want to handle errors in the event loop instead, use xcb_randr_get_screen_resources_unchecked. See xcb-requests(3) for details.
ERRORS
This request does never generate any errors.
SEE ALSO
AUTHOR
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
XCB
2014-06-10 xcb_randr_get_screen_resources(3)