The most recommended programming books of all-time.

Linux kernel release 3.x <http://kernel.org/> These are the release notes for Linux version 3. Read them carefully, as they tell you what this is all about, explain how to install the kernel, and what to do if something goes wrong. WHAT IS LINUX? Linux is a clone of the operating system Unix, written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. It aims towards POSIX and Single UNIX Specification compliance. It has all the features you would expect in a modern fully-fledged Unix, including true multitasking, virtual memory, shared libraries, demand loading, shared copy-on-write executables, proper memory management, and multistack networking including IPv4 and IPv6. It is distributed under the GNU General Public License - see the accompanying COPYING file for more details. ON WHAT HARDWARE DOES IT RUN? Although originally developed first for 32-bit x86-based PCs (386 or higher), today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell, IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS, Xtensa, Tilera TILE, AVR32 and Renesas M32R architectures. Linux is easily portable to most general-purpose 32- or 64-bit architectures as long as they have a paged memory management unit (PMMU) and a port of the GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has also been ported to a number of architectures without a PMMU, although functionality is then obviously somewhat limited. Linux has also been ported to itself. You can now run the kernel as a userspace application - this is called UserMode Linux (UML). DOCUMENTATION: - There is a lot of documentation available both in electronic form on the Internet and in books, both Linux-specific and pertaining to general UNIX questions. I'd recommend looking into the documentation subdirectories on any Linux FTP site for the LDP (Linux Documentation Project) books. This README is not meant to be documentation on the system: there are much better sources available. - There are various README files in the Documentation/ subdirectory: these typically contain kernel-specific installation notes for some drivers for example. See Documentation/00-INDEX for a list of what is contained in each file. Please read the Changes file, as it contains information about the problems, which may result by upgrading your kernel. - The Documentation/DocBook/ subdirectory contains several guides for kernel developers and users. These guides can be rendered in a number of formats: PostScript (.ps), PDF, HTML, & man-pages, among others. After installation, "make psdocs", "make pdfdocs", "make htmldocs", or "make mandocs" will render the documentation in the requested format. INSTALLING the kernel source: - If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it: gzip -cd linux-3.X.tar.gz | tar xvf - or bzip2 -dc linux-3.X.tar.bz2 | tar xvf - Replace "X" with the version number of the latest kernel. Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be. - You can also upgrade between 3.x releases by patching. Patches are distributed in the traditional gzip and the newer bzip2 format. To install by patching, get all the newer patch files, enter the top level directory of the kernel source (linux-3.X) and execute: gzip -cd ../patch-3.x.gz | patch -p1 or bzip2 -dc ../patch-3.x.bz2 | patch -p1 Replace "x" for all versions bigger than the version "X" of your current source tree, _in_order_, and you should be ok. You may want to remove the backup files (some-file-name~ or some-file-name.orig), and make sure that there are no failed patches (some-file-name# or some-file-name.rej). If there are, either you or I have made a mistake. Unlike patches for the 3.x kernels, patches for the 3.x.y kernels (also known as the -stable kernels) are not incremental but instead apply directly to the base 3.x kernel. For example, if your base kernel is 3.0 and you want to apply the 3.0.3 patch, you must not first apply the 3.0.1 and 3.0.2 patches. Similarly, if you are running kernel version 3.0.2 and want to jump to 3.0.3, you must first reverse the 3.0.2 patch (that is, patch -R) _before_ applying the 3.0.3 patch. You can read more on this in Documentation/applying-patches.txt Alternatively, the script patch-kernel can be used to automate this process. It determines the current kernel version and applies any patches found. linux/scripts/patch-kernel linux The first argument in the command above is the location of the kernel source. Patches are applied from the current directory, but an alternative directory can be specified as the second argument. - Make sure you have no stale .o files and dependencies lying around: cd linux make mrproper You should now have the sources correctly installed. SOFTWARE REQUIREMENTS Compiling and running the 3.x kernels requires up-to-date versions of various software packages. Consult Documentation/Changes for the minimum version numbers required and how to get updates for these packages. Beware that using excessively old versions of these packages can cause indirect errors that are very difficult to track down, so don't assume that you can just update packages when obvious problems arise during build or operation. BUILD directory for the kernel: When compiling the kernel, all output files will per default be stored together with the kernel source code. Using the option "make O=output/dir" allow you to specify an alternate place for the output files (including .config). Example: kernel source code: /usr/src/linux-3.X build directory: /home/name/build/kernel To configure and build the kernel, use: cd /usr/src/linux-3.X make O=/home/name/build/kernel menuconfig make O=/home/name/build/kernel sudo make O=/home/name/build/kernel modules_install install Please note: If the 'O=output/dir' option is used, then it must be used for all invocations of make. CONFIGURING the kernel: Do not skip this step even if you are only upgrading one minor version. New configuration options are added in each release, and odd problems will turn up if the configuration files are not set up as expected. If you want to carry your existing configuration to a new version with minimal work, use "make oldconfig", which will only ask you for the answers to new questions. - Alternative configuration commands are: "make config" Plain text interface. "make menuconfig" Text based color menus, radiolists & dialogs. "make nconfig" Enhanced text based color menus. "make xconfig" X windows (Qt) based configuration tool. "make gconfig" X windows (Gtk) based configuration tool. "make oldconfig" Default all questions based on the contents of your existing ./.config file and asking about new config symbols. "make silentoldconfig" Like above, but avoids cluttering the screen with questions already answered. Additionally updates the dependencies. "make olddefconfig" Like above, but sets new symbols to their default values without prompting. "make defconfig" Create a ./.config file by using the default symbol values from either arch/$ARCH/defconfig or arch/$ARCH/configs/${PLATFORM}_defconfig, depending on the architecture. "make ${PLATFORM}_defconfig" Create a ./.config file by using the default symbol values from arch/$ARCH/configs/${PLATFORM}_defconfig. Use "make help" to get a list of all available platforms of your architecture. "make allyesconfig" Create a ./.config file by setting symbol values to 'y' as much as possible. "make allmodconfig" Create a ./.config file by setting symbol values to 'm' as much as possible. "make allnoconfig" Create a ./.config file by setting symbol values to 'n' as much as possible. "make randconfig" Create a ./.config file by setting symbol values to random values. "make localmodconfig" Create a config based on current config and loaded modules (lsmod). Disables any module option that is not needed for the loaded modules. To create a localmodconfig for another machine, store the lsmod of that machine into a file and pass it in as a LSMOD parameter. target$ lsmod > /tmp/mylsmod target$ scp /tmp/mylsmod host:/tmp host$ make LSMOD=/tmp/mylsmod localmodconfig The above also works when cross compiling. "make localyesconfig" Similar to localmodconfig, except it will convert all module options to built in (=y) options. You can find more information on using the Linux kernel config tools in Documentation/kbuild/kconfig.txt. - NOTES on "make config": - Having unnecessary drivers will make the kernel bigger, and can under some circumstances lead to problems: probing for a nonexistent controller card may confuse your other controllers - Compiling the kernel with "Processor type" set higher than 386 will result in a kernel that does NOT work on a 386. The kernel will detect this on bootup, and give up. - A kernel with math-emulation compiled in will still use the coprocessor if one is present: the math emulation will just never get used in that case. The kernel will be slightly larger, but will work on different machines regardless of whether they have a math coprocessor or not. - The "kernel hacking" configuration details usually result in a bigger or slower kernel (or both), and can even make the kernel less stable by configuring some routines to actively try to break bad code to find kernel problems (kmalloc()). Thus you should probably answer 'n' to the questions for "development", "experimental", or "debugging" features. COMPILING the kernel: - Make sure you have at least gcc 3.2 available. For more information, refer to Documentation/Changes. Please note that you can still run a.out user programs with this kernel. - Do a "make" to create a compressed kernel image. It is also possible to do "make install" if you have lilo installed to suit the kernel makefiles, but you may want to check your particular lilo setup first. To do the actual install, you have to be root, but none of the normal build should require that. Don't take the name of root in vain. - If you configured any of the parts of the kernel as `modules', you will also have to do "make modules_install". - Verbose kernel compile/build output: Normally, the kernel build system runs in a fairly quiet mode (but not totally silent). However, sometimes you or other kernel developers need to see compile, link, or other commands exactly as they are executed. For this, use "verbose" build mode. This is done by inserting "V=1" in the "make" command. E.g.: make V=1 all To have the build system also tell the reason for the rebuild of each target, use "V=2". The default is "V=0". - Keep a backup kernel handy in case something goes wrong. This is especially true for the development releases, since each new release contains new code which has not been debugged. Make sure you keep a backup of the modules corresponding to that kernel, as well. If you are installing a new kernel with the same version number as your working kernel, make a backup of your modules directory before you do a "make modules_install". Alternatively, before compiling, use the kernel config option "LOCALVERSION" to append a unique suffix to the regular kernel version. LOCALVERSION can be set in the "General Setup" menu. - In order to boot your new kernel, you'll need to copy the kernel image (e.g. .../linux/arch/i386/boot/bzImage after compilation) to the place where your regular bootable kernel is found. - Booting a kernel directly from a floppy without the assistance of a bootloader such as LILO, is no longer supported. If you boot Linux from the hard drive, chances are you use LILO, which uses the kernel image as specified in the file /etc/lilo.conf. The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or /boot/bzImage. To use the new kernel, save a copy of the old image and copy the new image over the old one. Then, you MUST RERUN LILO to update the loading map!! If you don't, you won't be able to boot the new kernel image. Reinstalling LILO is usually a matter of running /sbin/lilo. You may wish to edit /etc/lilo.conf to specify an entry for your old kernel image (say, /vmlinux.old) in case the new one does not work. See the LILO docs for more information. After reinstalling LILO, you should be all set. Shutdown the system, reboot, and enjoy! If you ever need to change the default root device, video mode, ramdisk size, etc. in the kernel image, use the 'rdev' program (or alternatively the LILO boot options when appropriate). No need to recompile the kernel to change these parameters. - Reboot with the new kernel and enjoy. IF SOMETHING GOES WRONG: - If you have problems that seem to be due to kernel bugs, please check the file MAINTAINERS to see if there is a particular person associated with the part of the kernel that you are having trouble with. If there isn't anyone listed there, then the second best thing is to mail them to me (torvalds@linux-foundation.org), and possibly to any other relevant mailing-list or to the newsgroup. - In all bug-reports, *please* tell what kernel you are talking about, how to duplicate the problem, and what your setup is (use your common sense). If the problem is new, tell me so, and if the problem is old, please try to tell me when you first noticed it. - If the bug results in a message like unable to handle kernel paging request at address C0000010 Oops: 0002 EIP: 0010:XXXXXXXX eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx ds: xxxx es: xxxx fs: xxxx gs: xxxx Pid: xx, process nr: xx xx xx xx xx xx xx xx xx xx xx or similar kernel debugging information on your screen or in your system log, please duplicate it *exactly*. The dump may look incomprehensible to you, but it does contain information that may help debugging the problem. The text above the dump is also important: it tells something about why the kernel dumped code (in the above example, it's due to a bad kernel pointer). More information on making sense of the dump is in Documentation/oops-tracing.txt - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump as is, otherwise you will have to use the "ksymoops" program to make sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred). This utility can be downloaded from ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/ . Alternatively, you can do the dump lookup by hand: - In debugging dumps like the above, it helps enormously if you can look up what the EIP value means. The hex value as such doesn't help me or anybody else very much: it will depend on your particular kernel setup. What you should do is take the hex value from the EIP line (ignore the "0010:"), and look it up in the kernel namelist to see which kernel function contains the offending address. To find out the kernel function name, you'll need to find the system binary associated with the kernel that exhibited the symptom. This is the file 'linux/vmlinux'. To extract the namelist and match it against the EIP from the kernel crash, do: nm vmlinux | sort | less This will give you a list of kernel addresses sorted in ascending order, from which it is simple to find the function that contains the offending address. Note that the address given by the kernel debugging messages will not necessarily match exactly with the function addresses (in fact, that is very unlikely), so you can't just 'grep' the list: the list will, however, give you the starting point of each kernel function, so by looking for the function that has a starting address lower than the one you are searching for but is followed by a function with a higher address you will find the one you want. In fact, it may be a good idea to include a bit of "context" in your problem report, giving a few lines around the interesting one. If you for some reason cannot do the above (you have a pre-compiled kernel image or similar), telling me as much about your setup as possible will help. Please read the REPORTING-BUGS document for details. - Alternatively, you can use gdb on a running kernel. (read-only; i.e. you cannot change values or set break points.) To do this, first compile the kernel with -g; edit arch/i386/Makefile appropriately, then do a "make clean". You'll also need to enable CONFIG_PROC_FS (via "make config"). After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". You can now use all the usual gdb commands. The command to look up the point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes with the EIP value.) gdb'ing a non-running kernel currently fails because gdb (wrongly) disregards the starting offset for which the kernel is compiled.

Up-and-coming:: bibliomaniacs.js ( so far planning to use CloudFlare as CDN for selectize.js,turn.js, idiomatic.js, nd jsPDF with a Yeoman generator I'm sure to make reading books online easier and enable you to make notes on a sidebar; analytics are taken in this process and the results will appear of Parse, Ink. as to general population worldwide by country, area, etc. as to what is being read the most. This is a javacript framework that you can download as a program from github (COMING SOON) and it will have an icon representing the tooling as you read anything online. All you'd have to do is click on the icon for the tooling to enable and open and the source of text you are reading will go into pdf format with a sidebar and a save button as well as a bookmark this page option, so you can go back to look up words or to refer to the information or to share it later with someone else, or....:<Online library with links to free e-literature (short stories, novels, novellas, and poems) of Classics and many, many great new to present-day authors and true to present-past-few eras authors who have written some of the greatest works ever. Now all-in-one site, research and time has enabled the making of this site for anyone to use to read for free any of the literature of their choosing anytime; that is, on an ever-growing list of awesome books to read(any e-mail suggestions for add-ins are highly recommended--you can start now: e-mail me at amcii777@me.com. Amcii Cullum @mc112014, LLC. There are more features available related and extra, however: a blog you can post with issues or essays about books you've read and would like to critique or how your day went or how you feel, you get the point. It is there for you as a signed up user to do what you please with it. The blog could be a doorway where you propose an interesting issue that perhaps begins a conversational bit for our forum where people can talk about reading, writing, favorite music, this era today and how it is difference from the baby boomers children, religious issues, anything theme-related to talk about and hopefully learn from. This is a learning library to have fun with and use with no library card required and no late fees ;)! It is crucial for the site to grow, so I will continue to look for great literature as it is recommended (though please e-mail me on any topics that are of interest to you concerning this site; i.e. add-on links to free literature on the web, things you'd like to see added or removed from the site and why, topic that you'd like me to bring forth in the forum rather than you having to do it, though you may want to participate later, anything at all. Since Heartbleed and NSA et al maintaining an appearance whereby we feel there is no security in our input on the web, I want this to be a liberal arts explosion of ideas coming forth with taboo-topics and a feeling of freedom to talk(1st amendment right, right?!) I am very excited at the potential for what can be done with an online library where the books are always on the shelf for everyone even at the same time. There is a personal profile you can fill out once you register and sign in as a user agent. I am wondering if I should include check boxes next to authors works with -read, -want-to-read,-currently reading,-highly recommend, -do not recommend to others, with a block to type in reason why, a -like block with rating of 1-5 for you to input and it will be saved to your account profile. There will also be a template for you to keep notes on: words you want to look up from the text you're reading, comments you have on literary devices or metaphors used that you liked and why, extrapolation of obscured realities; that is, your take on what the book is trying to say really, and so on. You could even keep a list of books you recommend others to read on the front HOME Page which will be posted for all to see and maybe later after some analytics of what people are reading most etc. I can put lit that's trending now up on the site. There are planned weekly updates to be made to the site for as long as I can do so requiring that I find new literature to post. MY stack so far is planning to run node.js, twitter bootstrap 3.1.1, html5, css and less.js for styling, glyphicons, perhaps meteor.js, history.js, mocha, reveal.js, ember.js, jQuery, list.js, and kraken.js

This post isn't a conclusive listing of what's required for HIPAA compliance and is designed to point you in the best direction. You should assign a Privacy Officer to examine each rule in its entirety. HIPAA compliance 2018 rule "requires appropriate administrative, physical and technical safeguards to ensure the confidentiality, integrity, and security of electronic protected health information" The majorities of us believe that our medical and different wellness data is individual and should be secured. We also believe we should know who has this information and worry about how safe it is. The Privacy Rule, a Federal law, provides you with rights around your quality of life data and models principles and limits on who can look at and obtain your Health information. As long as we ensure reasonable safeguards, 2018 changes to HIPAA compliance Privacy Rule and Security Rule allow appropriate electronically communication and handling of health care 'Protected Health Information'. All personal medical information, including name, address, Social Security number, and all medical information about an "individual" come under PHI. HIPAA 2018 Changes In this HIPAA session we will be discussing HIPAA 2018 Changes taking place in Washington with the Health and Human Services when it comes to the enforcement of the HIPAA regulations already on the books as well as some step-by-step discussions on the audit method and some current functions regarding HIPAA cases (both in courtrooms and from live audits). Attend this Session As a healthcare organization, you must still make sure that a few checks and steps are taken to ensure that HIPAA compliance 2018 changes are followed within the organization: Administrative Safeguards: Always have a documented physical security policies and procedures. Helps guide existing and new security personnel Have designated HIPAA compliance officers whenever and wherever possible Injunction instructions should be documented and followed against workforce members who fail to comply with the security policy Continuous security upgrading and reminders in the form of seminars, test and webinars conducted internally Appling procedures to documents information system activities, such as audit records, access reports and security-incident checking reports Ensure regular reviews of the audit trails, logs and system activity of the employees with access to ePHI Planning and timed reviewing of procedural contingency policy on accessing backups of ePHI, establishing continuous processing of critical business process for protection of ePHI Special business partners compliance contracts with partners who will have access to ePHI. Choose partners that have similar agreements with any of their partners to which they are also extending access HIPAA - Texting & Emailing in 2018 With the introduction of smartphones, emails have become the even more accessible form of communication. In conjunction with email comes the issue of security and them being intercepted and read by unintended persons. Precautions and steps are to be taken at every step of the way. So for a Healthcare concern or a business associate, it's a key to maximize patient communication tools while protecting itself and the organization from government penalties and patient lawsuits. Attend this Session Physical Safeguards: Identifying and assigning personnel for developing and implementing security policies and procedures Disaster recovery plan and emergency plan, which is away from the normal operation facility. This ensures that the organization has a data backup plan established to create, maintain retrievable and restore exact copies of ePHI Employee workstation access and security - ensure proper password control, applications accessed and installed, and the physical attributes and the surroundings of the workstation that can access ePHI Following proper procedures for proper disposal of old/used hardware, proper reuse of the same All old hardware disposed should have data backed up from those disposed hardware Any paper trail of ePHI data is only accessible to selected employee and are always secured properly Implementing strong Bring-Your-Own-Device [BYOD] HIPAA Compliance policies in the organization where ePHI data is accessible and technology tools are integral to control the access to data outside the organization HIPAA Privacy Officer: Module 1 HIPAA Privacy Officer Training will uncover all HIPAA and HITECH expectations in protecting patient and member's right to privacy and the confidentiality of Protected Health Information (PHI) as you engage in treatment, payment, and healthcare operations (TPO) services. Attend this Session Technical Safeguards: Steps for creating changing and securing password management should be documented and implemented regularly Security measures to ensure integrity of the ePHI data that electronically transmitted - making sure they are not improperly modified without detection until discarded Securing digital ePHI data by encrypting them, at all/most times, by whenever means deemed appropriate Securing access control points by ensuring critical thought process is put into password protection, rules for accessing data, automatic log off from systems Audit controls implementing hardware, software and procedural restriction and procedures to record activities on information system that have healthcare data Under new HIPAA 2018 Compliance rule ensure proper steps to be taken by the organization when a patient has not agreed to receive ePHI in unencrypted email or unencrypted text message Ensure ePHI data that are at rest i.e. data that is kept in databases, servers, flash drives either by password protection or access to physical hardware is restricted and data is all/most time's encryption For all online forms that use or request or accept ePHI ensure the use of security measures, such as SSL and advanced password protections like 2FA In 2018 HIPAA Compliance Privacy rule make sure that anti-virus softwares are run and systematically updated on machines that have access to ePHI Current recommendation of using NIST-recommended AES 256-bit encryption standard for data transmissions through electronic devices HIPAA Privacy Officer: Module 2 HIPAA Privacy Officer Training will cover all ongoing activities of a Privacy Program related to the development, implementation, maintenance of, and adherence to the organization's policies and procedures covering the privacy of, and access to, patient health information in compliance with federal and state laws and the healthcare organization's information privacy practices. Attend this Session Critical steps for the success in passing HIPAA Compliance checklists for 2018 Reviewing all the above steps and procedures periodically Documenting procedures and changes done to anything related to ePHI Under HIPAA 2018 Compliance rule ensure your employees are up to date at all times with regards to the procedures Ensuring the end user know about your organization handling of ePHI Determine the likelihood of threat occurrence with ratings such as high, medium and low or numerical represent probability of threat......https://www.complyarena.com/articledetails/Critical-2018-HIPAA-Compliance-Updates-Trump-Administration

Implement a library management program using linked list. The program stores the following information of a book: 1. Name 2. Author 3. Status (available/borrowed) 4. Popularity (calculated based on the number of times a book is borrowed) Whenever new books arrive, those are arranged alphabetically. The librarian can perform the following activities: 1. View list of all (both available or borrowed) books 2. View list of available books 3. Add new book 4. Delete a book if it is lost 5. Check the availability of a particular book 6. Changing the status of a book when a user borrows/returns it 7. Find the most popular book and recommend it to users

This program will recommend the most similar books based on your previous Books read.