Visit Our UNIX and Linux User Community

Contact Us Post Here to Contact Site Administrators and Moderators Thread closed when learner has tried Post 302308636 by Neo on Sunday 19th of April 2009 10:19:21 PM
Old 04-19-2009
Posting homework is a direct violation of the terms of services (rules) of these forums.
 
Test Your Knowledge in Computers #661
Difficulty: Easy
DOS uses the File Access Table (FAT) filesystem.
True or False?

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

please help (closed homework thread)

I have these questions for my unix class that I can't figure out because I missed a couple of days. They are for a quiz we took last week so by answering the questions you are not bettering my grade or doing my homework. I just want to understand was the answers. My teacher is really bad at... (1 Reply)
Discussion started by: djeung
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Thread was closed without a valid reason

Dear Administrators, I think Mr. Vino is one of your Moderators here because he closes this thread: https://www.unix.com/showthread.php?p=302086230#post302086230 without a valid reason. Rule 7 states no headhunters or recruiters, but career advice is not prohibited here i think, because it... (2 Replies)
Discussion started by: patras
2 Replies

3. Post Here to Contact Site Administrators and Moderators

my thread got closed

I had a thread open and now it says it's closed. I had a question still on the forum and about 15mins after I posted my most recent question on it the thread said "closed". Why did this happen? I didn't violate any forum rules. Is there a limit on how many postings you can have in a single thread?... (1 Reply)
Discussion started by: hpicracing
1 Replies

4. UNIX for Dummies Questions & Answers

This forum is closed for new thread ... post here.

This forum is closed for new threads. Please post in this forum: UNIX for Beginners Questions & Answers (0 Replies)
Discussion started by: Neo
0 Replies
MEMSET_S(3)						   BSD Library Functions Manual 					       MEMSET_S(3)

NAME
memset_s -- copy a value to all bytes of a memory buffer LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#define __STDC_WANT_LIB_EXT1__ 1 #include <string.h> errno_t memset_s(void *s, rsize_t smax, int c, rsize_t n); DESCRIPTION
The memset_s() function copies the value c (converted to an unsigned char) into each of the first n bytes of the memory buffer whose starting address is given by s. It is a runtime-consrtaints violation if s is a null pointer, or if either of smax or n is larger than RSIZE_MAX, or if smax is smaller than n. If there is a runtime-constraints violation, and if s is not a null pointer, and if smax is not larger than RSIZE_MAX, then, before reporting the runtime-constraints violation, memset_s() copies smax bytes to the destination. In contrast to the memset(3) function, calls to memset_s() will never be ``optimised away'' by a compiler. This property is required by the following sentences in section K.3.7.4.1 of ISO/IEC 9899:2011 (``ISO C11''): Unlike memset(), any call to the memset_s() function shall be evaluated strictly according to the rules of the abstract machine as described in (5.1.2.3). That is, any call to the memset_s() function shall assume that the memory indicated by s and n may be accessi- ble in the future and thus must contain the values indicated by c. RETURN VALUES
The memset_s() function returns zero for success, or a non-zero error code if there was a runtime-constraints violation. ERRORS
memset_s() returns the following error codes. It does not store the error code in the global errno variable: [EINVAL] The s argument was a null pointer. [E2BIG] One or both of smax or n was larger than RSIZE_MAX. [EOVERFLOW] n was larger than smax. SEE ALSO
memset(3). STANDARDS
The memset_s() function conforms to ISO/IEC 9899:2011 (``ISO C11''), except that the set_constraint_handler_s() interface is not supported. BSD
February 21, 2012 BSD

Featured Tech Videos

All times are GMT -4. The time now is 06:26 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy