Sponsored Content
The Lounge What is on Your Mind? How to switch from SVR4/BSD internals to Linux internals? Post 302814011 by figaro on Tuesday 28th of May 2013 02:34:15 PM
Old 05-28-2013
Why is your employer not in favor of putting you on a relevant Linux course? Can you make the case to him/her that you would like to develop yourself into other areas, while still staying on for the legacy tasks, thereby making you more valuable for the firm?
Is there any point in asking to make a lateral move within the firm?
The other option I can think of is participating in an open source project with enough critical mass to also get noticed by future employers. It would also be a way to get in touch with like-minded developers who might give you advice on where else to look.
 

9 More Discussions You Might Find Interesting

1. New to Unix. Which books should I read?

UniX internals Material

Hi! I have 1.5 years experience in unix environment and shell scripting. Now, I started learning UNIX internals and network programming. Can you please help in finding the same material on the net Thanks Srinivas. (7 Replies)
Discussion started by: srinivaskathika
7 Replies

2. Filesystems, Disks and Memory

on unix internals

will anybody tell me how can i access all the fields of process table .if there is any structure and a system call please specify . (1 Reply)
Discussion started by: vish_shan
1 Replies

3. HP-UX

HP-UX Internals Book

. (2 Replies)
Discussion started by: Driver
2 Replies

4. Programming

UNIX Internals, Help required...

I know UNIX user level commands, shell scripts. But i have no idea about kernel level programming and networking. I know the terms semaphore,IPC,socket programming. But i don't know in details what are these. I need to know the following. 1. Unix kernel level programming. 2. Unix Internals. 3.... (4 Replies)
Discussion started by: digdarshan
4 Replies

5. Linux

Kernel internals for ARM

Hi, Does anybody have a good pointer on Linux kernel internals for ARM architecture? I can locate plenty for x86 but since ARM is RISC I think there would be subtle changes. So if somebody has a knowledge of good document on Linux Kernel internals for ARM or even a comparative study of kernel on... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

6. Programming

Need more info on internals of c compilers

Hello Gurus, i am ok with the concepts of c language but i would like to know more about the internals of c with respect to the compilers what happens when we say gcc filename.c the a.out will get created(what actaully compiler does to the code inaddition to generating object code) ... (5 Replies)
Discussion started by: MrUser
5 Replies

7. Programming

Internals of the printf function?

hey all, im a new programmer. i was wondering how you would go about writing the printf function yourself? it is my understanding that when you call printf you are calling an already written function and just providing an argument? if this is the case, is it possible to write that function... (8 Replies)
Discussion started by: Christian.B
8 Replies

8. UNIX for Dummies Questions & Answers

Linux Internals Interview Questions

Can anyone list the interview questions on Linux Internals? Any link for the same will also be helpful. In a job requirement of say C, linux internals what is expected about linux internals? (0 Replies)
Discussion started by: rupeshkp728
0 Replies

9. UNIX for Advanced & Expert Users

GDB Breakpoint Internals

When we put a breakpoint using gcc then what all things happen internally and how the gdb using break is able to pause the execution of process( instead of killing it ) and later on resume the process execution? (0 Replies)
Discussion started by: rupeshkp728
0 Replies
POSIX_FADVISE(2)					     Linux Programmer's Manual						  POSIX_FADVISE(2)

NAME
posix_fadvise - predeclare an access pattern for file data SYNOPSIS
#define _XOPEN_SOURCE 600 #include <fcntl.h> int posix_fadvise(int fd, off_t offset, off_t len, int advice); DESCRIPTION
Programs can use posix_fadvise() to announce an intention to access file data in a specific pattern in the future, thus allowing the kernel to perform appropriate optimizations. The advice applies to a (not necessarily existent) region starting at offset and extending for len bytes (or until the end of the file if len is 0) within the file referred to by fd. The advice is not binding; it merely constitutes an expectation on behalf of the application. Permissible values for advice include: POSIX_FADV_NORMAL Indicates that the application has no advice to give about its access pattern for the specified data. If no advice is given for an open file, this is the default assumption. POSIX_FADV_SEQUENTIAL The application expects to access the specified data sequentially (with lower offsets read before higher ones). POSIX_FADV_RANDOM The specified data will be accessed in random order. POSIX_FADV_NOREUSE The specified data will be accessed only once. POSIX_FADV_WILLNEED The specified data will be accessed in the near future. POSIX_FADV_DONTNEED The specified data will not be accessed in the near future. RETURN VALUE
On success, zero is returned. On error, an error number is returned. ERRORS
EBADF The fd argument was not a valid file descriptor. EINVAL An invalid value was specified for advice. ESPIPE The specified file descriptor refers to a pipe or FIFO. (Linux actually returns EINVAL in this case.) VERSIONS
posix_fadvise() appeared in kernel 2.5.60. Glibc support has been provided since version 2.2. CONFORMING TO
POSIX.1-2001. Note that the type of the len argument was changed from size_t to off_t in POSIX.1-2003 TC1. NOTES
Under Linux, POSIX_FADV_NORMAL sets the readahead window to the default size for the backing device; POSIX_FADV_SEQUENTIAL doubles this size, and POSIX_FADV_RANDOM disables file readahead entirely. These changes affect the entire file, not just the specified region (but other open file handles to the same file are unaffected). POSIX_FADV_WILLNEED initiates a nonblocking read of the specified region into the page cache. The amount of data read may be decreased by the kernel depending on virtual memory load. (A few megabytes will usually be fully satisfied, and more is rarely useful.) In kernels before 2.6.18, POSIX_FADV_NOREUSE had the same semantics as POSIX_FADV_WILLNEED. This was probably a bug; since kernel 2.6.18, this flag is a no-op. POSIX_FADV_DONTNEED attempts to free cached pages associated with the specified region. This is useful, for example, while streaming large files. A program may periodically request the kernel to free cached data that has already been used, so that more useful cached pages are not discarded instead. Pages that have not yet been written out will be unaffected, so if the application wishes to guarantee that pages will be released, it should call fsync(2) or fdatasync(2) first. BUGS
In kernels before 2.6.6, if len was specified as 0, then this was interpreted literally as "zero bytes", rather than as meaning "all bytes through to the end of the file". SEE ALSO
readahead(2), sync_file_range(2), posix_fallocate(3), posix_madvise(3), feature_test_macros(7) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2010-06-14 POSIX_FADVISE(2)
All times are GMT -4. The time now is 06:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy