Sponsored Content
Top Forums UNIX for Dummies Questions & Answers how to make programs available to all users Post 302529118 by lramsb4u on Wednesday 8th of June 2011 02:38:51 PM
Old 06-08-2011
how to make programs available to all users

Hi all,

where (path) usually the programs are installed in linux.
How to make installed programs available to all users of the system ?
Thanks in advance!
 

10 More Discussions You Might Find Interesting

1. Solaris

How to make a script executable by all users?

I have a script in my home direcroty which upon execution gives the essential system information like memory,cpu etc and is currently owned by root:root. Now I want to see that every non root user will run this file and grab the reqired system info. I know this is some thing associated with chown... (2 Replies)
Discussion started by: chrs0302
2 Replies

2. Shell Programming and Scripting

make script deleting mp3 with warnig to users

hi i need to make a script that will check the directories of the users on mp3 or mp4 files. if so they must be automaticly deleted and they have to get a warning message instead. this should be running every day at 1 pm and should be done within the cron file. could someone help me with... (2 Replies)
Discussion started by: stefan
2 Replies

3. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

4. UNIX for Dummies Questions & Answers

Are programs like sys_open( ) ,sys_read( ) et al examples of system level programs ?

Are the programs written on schedulers ,thread library , process management, memory management, et al called systems programs ? How are they different from the programs that implement functions like open() , printf() , scanf() , read() .. they have a prefix sys_open, sys_close, sys_read etc , right... (1 Reply)
Discussion started by: vishwamitra
1 Replies

5. Solaris

To restrict the users not to change the passwords for NIS users

Hi All, How to restrict the NIS users not to change their passwords in for NIS users?? and my NIS user is unable to login to at client location what could be the problem for this ? Any body can help me. Thanks in advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies

6. Shell Programming and Scripting

Create multiple users with individual passwords to users

hi, i am new to shell scripts i write a shell script to create multiple users but i need to give passwords to that users while creating users, command to write this script (1 Reply)
Discussion started by: DONFOX
1 Replies

7. UNIX and Linux Applications

How to make ldappasswd use {SHA} instead of {SSHA} for users passwords in openldap?

Is it possible to use {SHA} with ldappasswd? I didn't find responsible option in manual page and doc (1 Reply)
Discussion started by: urello
1 Replies

8. UNIX for Dummies Questions & Answers

Command - filename as arguments - make executable to all users.

Edit: Sorry. Mistakenly posted - please delete (3 Replies)
Discussion started by: Reddax
3 Replies

9. OS X (Apple)

Alternatives to GNU Make for users of newer OS X

As you may already know, Apple has integrated all the GNU developer tools into their own graphical development environment so you can no longer use them from the command line. This means that open source software that is distributed as source is inaccessible to users of newer versions of Mac OS X,... (4 Replies)
Discussion started by: Ultrix
4 Replies

10. UNIX for Dummies Questions & Answers

Difference between inbuilt suid programs and user defined root suid programs under bash shell?

Hey guys, Suppose i run passwd via bash shell. It is a suid program, which temporarily runs as root(owner) and modifies the user entries. However, when i write a C file and give 4755 permission and root ownership to the 'a.out' file , it doesn't run as root in bash shell. I verified this by... (2 Replies)
Discussion started by: syncmaster
2 Replies
DPKG-REPACK(1)						      General Commands Manual						    DPKG-REPACK(1)

NAME
dpkg-repack - put an unpacked .deb file back together SYNOPSIS
dpkg-repack [--root=dir] [--arch=architecture] [--generate] packagename [packagename ...] DESCRIPTION
dpkg-repack creates a .deb file out of a Debian package that has already been installed on your system. If any changes have been made to the package while it was unpacked (ie, conffiles files in /etc modified), the new package will inherit the changes. (There are exceptions to this, including changes to configuration files that are not conffiles, including those managed by ucf.) This utility can make it easy to copy packages from one computer to another, or to recreate packages that are installed on your system, but no longer available elsewhere. Note: dpkg-repack will place the created package in the current directory. OPTIONS
--root=dir Take package from filesystem rooted on <dir>. This is useful if, for example, you have another computer nfs mounted on /mnt, then you can use --root=/mnt to reassemble packages from that computer. --arch=architecture Make the package be for a different architecture. dpkg-repack cannot tell if an installed package is architecture all or is spe- cific to the system's architecture, so by default it uses dpkg --print-architecture to determine the build architecture. If you know the package is architecture all, you can use this option to force dpkg-repack to use the right architecture. --generate Generate a temporary directory suitable for building a package from, but do not actually create the package. This is useful if you want to move files around in the package before building it. The package can be built from this temporary directory by running "dpkg --build", passing it the generated directory. packagename The name of the package to attempt to repack. Multiple packages can be listed. BUGS
This program accesses the dpkg database directly in places, querying for data that cannot be gotten via dpkg. There is a tricky situation that can occur if you dpkg-repack a package that has modified conffiles. The modified conffiles are packed up. Now if you install the package, dpkg does not realize that the conffiles in it are modified. So if you later upgrade to a new version of the package, dpkg will believe that the old (repacked) package has older conffiles than the new version, and will silently replace the conffiles with those in the package you are upgrading to. While dpkg-repack can be run under fakeroot and will work most of the time, fakeroot -u must be used if any of the files to be repacked are owned by non-root users. Otherwise the package will have them owned by root. dpkg-repack will warn if you run it under fakeroot without the -u flag. AUTHOR
Joey Hess <joeyh@debian.org> DEBIAN
Debian Utilities DPKG-REPACK(1)
All times are GMT -4. The time now is 09:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy