Debian - - List of sections in . Do not install them on a normal system! Debug packages. Packages providing debugging information for executables and shared libraries. Development. Development utilities, compilers, development environments, libraries, etc. Documentation. FAQs, HOWTOs and other documents trying to explain everything related to Debian, and software needed to browse documentation (man, info, etc). Editors. Software to edit files. Programming environments.
Education. Software for learning and teaching. Electronics. Electronics utilities. Embedded software. Software suitable for use in embedded applications. Fonts. Font packages. Games. Programs to spend a nice time with after all this setting up. GNOMEThe GNOME desktop environment, a powerful, easy to use set of integrated applications. GNU REverything about GNU R, a statistical computation and graphics system. GNUstep. The GNUstep environment. Graphics. Editors, viewers, converters.. Everything to become an artist. Ham Radio. Software for ham radio. To: [email protected]; Subject: startup programs; From:Haskell. Everything about Haskell. Web Servers. Web servers and their modules. Interpreters. All kind of interpreters for interpreted languages. Macro processors. Introspection. Machine readable introspection data for use by development tools. Java. Everything about Java. KDEThe K Desktop Environment, a powerful, easy to use set of integrated applications. This is broken since years, I’ve checked in Fedora, Ubuntu, Debian and Arch Linux. Manage the startup applications in Gnome 3 How to Add a Program to the Ubuntu Startup List (After Login). Running a Program at Linux Startup. When the Ubuntu and Debian GNU/Linux operating systems are. The key handler is not neccesary to use these programs. Kernels. Operating System Kernels and related modules. Library development. Libraries necessary for developers to write programs that use them. Libraries. Libraries to make other programs work. They provide special features to developers. Lisp. Everything about Lisp. Language packs. Localization support for big software packages. Mail. Programs to route, read, and compose E- mail messages. Mathematics. Math software. Meta packages. Packages that mainly provide dependencies on other packages. Miscellaneous. Miscellaneous utilities that didn't fit well anywhere else. Network. Daemons and clients to connect your system to the world. Newsgroups. Software to access Usenet, to set up news servers, etc. OCaml. Everything about OCaml, an ML language implementation. Old Libraries. Old versions of libraries, kept for backward compatibility with old applications. Other OS's and file systems. Software to run programs compiled for other operating systems, and to use their filesystems. Perl. Everything about Perl, an interpreted scripting language. PHPEverything about PHP. Python. Everything about Python, an interpreted, interactive object oriented language. Ruby. Everything about Ruby, an interpreted object oriented language. Science. Basic tools for scientific work. Shells. Command shells. Friendly user interfaces for beginners. Sound. Utilities to deal with sound: mixers, players, recorders, CD players, etc. Tasks. Packages that are used by 'tasksel', a simple interface for users who want to configure their system to perform a specific task. Te. XThe famous typesetting software and related programs. Text Processing. Utilities to format and print text documents. Utilities. Utilities for file/disk manipulation, backup and archive tools, system monitoring, input systems, etc. Version Control Systems. Version control systems and related utilities. Video. Video viewers, editors, recording, streaming. Virtual packages. Virtual packages. Web Software. Web servers, browsers, proxies, download tools etc. X Window System software. X servers, libraries, fonts, window managers, terminal emulators and many related applications. Xfce. Xfce, a fast and lightweight Desktop Environment. Zope/Plone Framework. Zope Application Server and Plone Content Managment System. All packages(compact compressed textlist). Manage System Startup and Boot Processes on Linux with Upstart ? Then you need to familiarize yourself with Upstart and take control of your startup and boot processes on Linux. From there, init takes the task of starting up system processes. Turns out, there are several flavors of init, and it depends on which Linux distribution you're using and how modern the release is. Let's take a look at some of the backstory. Unfortunately, that's not been the case and may not be the case for some time. Some Linux distros, most notably Slackware, used the BSD- style init. Slackware (and its derivatives) is the lone holdout for this style these days, and it includes a System V init compatibility workaround so that applications that expect to support System V init scripts can install them normally. Distros using Sys. V init would have several directories under /etc such as rc. Essentially this is the grouping of services that are run by init. For example, runlevel 0 is . On Fedora/Red Hat systems, runlevel 3 is a full set of services to run a multiuser system (networking, etc.), and runlevel 5 includes multiuser services and X1. You'll notice I didn't mention 2 or 4, because those runlevels are rarely used and runlevel 4 isn't even defined by default. Note that you would usually want to just use reboot instead to reboot, but telinit 6 would also work. Each link has a name like KNNsshd or SNNcups, where the NN determines the order in which services are killed (K) or started (S). This became tricky with laptops and mobile systems, because the state of a computer might determine the order in which services should be started. See the rationale for Upstart by Scott James Remnant for more detail . For now, Upstart is the sort- of standard for several distros. Upstart is used by Ubuntu, current Fedora releases, and open. SUSE 1. 1. 3 includes it as an optional package. But the Fedora folks are working on a replacement for Upstart called systemd, which is a . So at some point, you'll need to know Upstart or systemd, or both if you are managing systems using Upstart and systemd. That's a whole different kettle of fish, and depends on the desktop that you're using. For example, if you're running a recent Linux distro with GNOME, you'll look at System - > Preferences - > Startup Applications. This allows you to work with Upstart's init daemon. Naturally, you're going to need to use sudo to run initctl or be logged in as root. You'll see something like this. The first field is the name of the job . The second field is the . To start a job, run initctl start job. You can also request status of jobs with initctl status job. Finally you can restart or reload jobs with the restart and reload commands. What's the difference between restarting and reloading? Restarting does what it says on the tin . The reload command sends the SIGHUP signal to the job, which can be used to tell a daemon to re- read its configuration. They will have a few lines that describe which runlevels to start/stop on like so. The package is bum, and it will let you manage jobs and configure services by runlevel. It's simple to use, and shouldn't require a lot of guidance. For those jobs you'll want to use the service command. For example, iptables will spit out its entire set of policies that are running at the moment. The servicename is the name of the configuration script under /etc/init. For example, to start and stop the open. SSH daemon, you'll use service sshd start or service sshd stop. You'd use something like chkconfig - -level 3. One quick and dirty way is to use /etc/rc. The script should be run during any startup or change of runlevel. Another way is to modify the scripts under /etc/init. Sys. V compatibility) or /etc/init (native Upstart scripts) or write your own for a new service. Writing an init script, whether for Upstart or for Sys. V, is a bit outside the scope of this tutorial. If you are doing system administration, or planning to, you should already be familiar with the init system that your distros are using. If not, now's a good time to learn. If you're a desktop Linux user, you probably won't be managing services very often, but it's a good to know the basics that we've covered here in case you need to do any troubleshooting or just want to fine- tune your system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |