Upstart - event-based init daemon. Tutorials - Ubuntu's Success Story: the Upstart Startup Manager. Controlling Boot Sequence, What is Event-Based April 8, 2010 By Akkana Peck Boot Camp Part I explained how Linux boots, using the old "SysV init" system of scripts. But some modern Linux distros have been gradually migrating to a newer model, called Upstart. Upstart has been around since 2006, but it's only in the last year or so that it's taken a major role in booting distributions like Ubuntu and Fedora. Debian and OpenSuSE are reportedly joining in soon, while it's available as an optional component on most other distros. No distro uses it as the sole boot method yet: even Fedora 12 and the upcoming Ubuntu 10.04 keep a lot of functionality in SysV scripts. An event-based model The normal SysV boot process is synchronous -- meaning things happen one at a time, one after the other. Upstart, in contrast, is event based.
This event-based system has another advantage: you can theoretically use it even after the system is up and running. New directories Boot sequence Job definition files. Forum Ubuntu-fr.org / Crontab avec VIM et non pas NANO. Apt-Pinning for Beginners. Why apt-pinning? Do you run Debian? Have you ever gotten annoyed at how Debian Stable always seems to be out of date? I will show you a way that you can have apt mix-and-match between Stable, Testing, and Unstable sources. This will allow you to run a mostly-Stable system, but also track the latest and greatest of those packages that you are most keenly interested in. Why do this? Stable is covered by the Security Team. Sources.list The first step is to set up your /etc/apt/sources.list to include your typical Stable, plus the Testing/Unstable sources that you want.
A simple sources.list may look like this: You would probably want to add your mirrors, security.debian.org, and perhaps the appropriate deb-src lines. Preferences The next step is to create/edit your /etc/apt/preferences file. preferences is where the apt-pinning takes place. A simple preferences file may look like this: Note the decending values. My actual preferences file is what you see above. apt-get update That's it! Have fun!
Sender Policy Framework. Sender Policy Framework is defined in IETF publication RFC 7208. Principles of operation[edit] The Simple Mail Transfer Protocol permits any computer to send email claiming to be from any source address. This is exploited by spammers who often use forged email addresses, making it more difficult to trace a message back to its sender, and easy for spammers to hide their identity in order to avoid responsibility. It is also used in phishing techniques, where users can be duped into disclosing private information in response to an email purportedly sent by an organization such as a bank. SPF allows the owner of an Internet domain to specify which computers are authorized to send mail with sender addresses in that domain, using Domain Name System (DNS) records.
Receivers verifying the SPF records may reject messages from unauthorized sources before receiving the body of the message. SPF has potential advantages beyond helping identify unwanted mail. Reasons to implement[edit] HELO tests[edit] Building a mail server on Debian 6.0 - gog's.info.