Sponsored Content
Operating Systems Linux Slackware Anyone Using Slackware Anymore? Post 302868711 by Neo on Monday 28th of October 2013 03:31:43 PM
Old 10-28-2013
For one thing, I like all the Debian-style install tools like aptitude and apt-get...

Second, I like the huge install base and large community for Ubuntu and the way Ubuntu is well supported.
 

8 More Discussions You Might Find Interesting

1. Slackware

After installing linux cannot boot PC anymore?

After installing linux (slackware) my (experimental) computer can't boot anymore. When I start the pc it says: "There was an error during linux startup" (or something like that, it was written in my language and I'm a bad translator) And after that my computer doesn't do a thing anymore. I... (4 Replies)
Discussion started by: RellioN
4 Replies

2. UNIX for Dummies Questions & Answers

Can't login as SU anymore - SU: NO SHELL

the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message 'su: no shell' so we can't login as superuser. Is there an easy way to rectify this? please use step by step instructions/commands - I... (4 Replies)
Discussion started by: homechoice
4 Replies

3. UNIX for Dummies Questions & Answers

connection doesn't work anymore

Hello, first of all, I want to make myself clear about my language. I'm brazilian, so I ask you all to understand if i commit any mistake with the grammar. Here is the problem. Some days ago I needed to use a "sh" command in the Terminal (I use a Mac OSX 10.5.6) followed by a file... (0 Replies)
Discussion started by: anubisbr
0 Replies

4. UNIX for Dummies Questions & Answers

Can't SSH as root anymore!

I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore. I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies

5. UNIX for Dummies Questions & Answers

Input of char 's' is not possible anymore

Hello, I have a big problem and no idea how to solve it. I was looking up commands in /bin with 'man' as I found 'sh'. In mistake I started the command. Now after that I can not input the character 's' in shell anymore! Even after restarting system the problem is still there. Mysterious... (7 Replies)
Discussion started by: daWonderer
7 Replies

6. Windows & DOS: Issues & Discussions

Can't login to Vista anymore

hello obviously something got messed up and I can't login to my Vista account anymore. the password was automatically disabled hence it was directly booting into vista. then I installed openSSH and created a password for the user. But vista login doesn't recognize this password and now I can't... (6 Replies)
Discussion started by: milhan
6 Replies

7. Solaris

Telnet access is not available anymore

Hi Folks, My telnet access to the server is not available anymore. I have found that when I execute >telnet IP, the login prompt for username/password entry is not displayed. Cursor blinks in a empty line and I dont see the prompt to enter my username. It hungs in this state and not possible... (1 Reply)
Discussion started by: ekorgur
1 Replies

8. What is on Your Mind?

They won't need so many sys admins anymore

Nice eye catching title huh ;) I got laid off along with 55000 others from HP worldwide have been expecting this for some time and now it's finally my turn. Most of the folks I know get laid off at around this age of 40+ so do take note. Ideas that ran thru my head this last few weeks:... (16 Replies)
Discussion started by: sparcguy
16 Replies
DEBCONF-APT-PROGRESS(1) 					      Debconf						   DEBCONF-APT-PROGRESS(1)

NAME
debconf-apt-progress - install packages using debconf to display a progress bar SYNOPSIS
debconf-apt-progress [--] command [args ...] debconf-apt-progress --config debconf-apt-progress --start debconf-apt-progress --from waypoint --to waypoint [--] command [args ...] debconf-apt-progress --stop DESCRIPTION
debconf-apt-progress installs packages using debconf to display a progress bar. The given command should be any command-line apt frontend; specifically, it must send progress information to the file descriptor selected by the "APT::Status-Fd" configuration option, and must keep the file descriptors nominated by the "APT::Keep-Fds" configuration option open when invoking debconf (directly or indirectly), as those file descriptors will be used for the debconf passthrough protocol. The arguments to the command you supply should generally include -y (for apt-get or aptitude) or similar to avoid the apt frontend prompting for input. debconf-apt-progress cannot do this itself because the appropriate argument may differ between apt frontends. The --start, --stop, --from, and --to options may be used to create a progress bar with multiple segments for different stages of installation, provided that the caller is a debconf confmodule. The caller may also interact with the progress bar itself using the debconf protocol if it so desires. debconf locks its config database when it starts up, which makes it unfortunately inconvenient to have one instance of debconf displaying the progress bar and another passing through questions from packages being installed. If you're using a multiple-segment progress bar, you'll need to eval the output of the --config option before starting the debconf frontend to work around this. See "EXAMPLES" in the EXAMPLES section below. OPTIONS
--config Print environment variables necessary to start up a progress bar frontend. --start Start up a progress bar, running from 0 to 100 by default. Use --from and --to to use other endpoints. --from waypoint If used with --start, make the progress bar begin at waypoint rather than 0. Otherwise, install packages with their progress bar beginning at this "waypoint". Must be used with --to. --to waypoint If used with --start, make the progress bar end at waypoint rather than 100. Otherwise, install packages with their progress bar ending at this "waypoint". Must be used with --from. --stop Stop a running progress bar. --no-progress Avoid starting, stopping, or stepping the progress bar. Progress messages from apt, media change events, and debconf questions will still be passed through to debconf. --dlwaypoint percentage Specify what percent of the progress bar to use for downloading packages. The remainder will be used for installing packages. The default is to use 15% for downloading and the remaining 85% for installing. --logfile file Send the normal output from apt to the given file. --logstderr Send the normal output from apt to stderr. If you supply neither --logfile nor --logstderr, the normal output from apt will be discarded. -- Terminate options. Since you will normally need to give at least the -y argument to the command being run, you will usually need to use -- to prevent that being interpreted as an option to debconf-apt-progress itself. EXAMPLES
Install the GNOME desktop and an X window system development environment within a progress bar: debconf-apt-progress -- aptitude -y install gnome x-window-system-dev Install the GNOME, KDE, and XFCE desktops within a single progress bar, allocating 45% of the progress bar for each of GNOME and KDE and the remaining 10% for XFCE: #! /bin/sh set -e case $1 in '') eval "$(debconf-apt-progress --config)" "$0" debconf ;; debconf) . /usr/share/debconf/confmodule debconf-apt-progress --start debconf-apt-progress --from 0 --to 45 -- apt-get -y install gnome debconf-apt-progress --from 45 --to 90 -- apt-get -y install kde debconf-apt-progress --from 90 --to 100 -- apt-get -y install xfce4 debconf-apt-progress --stop ;; esac RETURN CODE
The exit code of the specified command is returned, unless the user hit the cancel button on the progress bar. If the cancel button was hit, a value of 30 is returned. To avoid ambiguity, if the command returned 30, a value of 3 will be returned. AUTHORS
Colin Watson <cjwatson@debian.org> Joey Hess <joeyh@debian.org> 2012-09-10 DEBCONF-APT-PROGRESS(1)
All times are GMT -4. The time now is 04:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy