Sponsored Content
Operating Systems AIX New to AIX need help Installing/Upgrading Samba on AIX 7.1? Post 302888752 by bakunin on Monday 17th of February 2014 06:55:32 AM
Old 02-17-2014
Quote:
Originally Posted by c3rb3rus
However, I did find it using "lslpp -L | grep "samba" returns..

pware53.samba.rte

So I think at some point installed using installp??
Yes, it looks like this. Issue "lslpp" with the "-h" (history) switch to get a date when it was installed (just in case you are interested).

Quote:
Originally Posted by c3rb3rus
So my goal is to first uninstall the existing samba package (smbd, nmbd, winbindd) and installing the latest 3.6.22 from perlz.org.

My issue is, I have no idea how to install the package (noob to aix/unix) and i'd like to do this as clean as possible.
(btw: i suggest you do a "man smit", because this - using SMIT - is usually the easiest and fastest way for a non-AIX admin to get things done in AIX)

The easiest way is to do a "smitty remove" from the commandline. This brings up SMIT (system management interface tool) with the "removal of software" screen already preselected. All the fields marked with a "+" can be expanded with "PF4" (on some terminals "ESC"+"4" instead). Do this and a list of isntalled packages comes up from which you can select. Select more than one using "PF7" (ESC+7), then press ENTER to return to this screen. Yes/No fields can be selected using the TAB key. Finally press ENTER to do it.

TIP: set the "preview only"-field to "yes" to just simulate removal. All the check will be done normally and give errors in case something would go wrong. Once feeling safe change "preview" to "no" and proceed.

The Perzl software is very fine-grained and hence contains many dependencies. Read Michael Perzls solution to this. The real problem behind this is that IBM still uses an very very old (v3) rpm binary. rpm-v4 would be able to deal with software repositories.

Finally: install the *src* packages only if you plan on compiling new packages. Otherwise take the binary packages and install these. Compilation/configuration/etc. is already done and you do not have to bother with these.

I hope this helps.

bakunin

Last edited by bakunin; 02-17-2014 at 08:00 AM..
 

10 More Discussions You Might Find Interesting

1. AIX

Upgrading AIX Unix

Hi all, I've got a question about an OS upgrade. I'm planning to do a upgrade from AIX UNIX 4.3.2 to 4.3.3 in a few weeks. I haven't got that much information. Could someone give me some general tips or hints, things I should think of before? Things I should know, or general errors. I know... (9 Replies)
Discussion started by: Erik Rooijmans
9 Replies

2. AIX

Installing Samba on AIX 5.3

Hello, I need assistance installing Samba on AIX 5.3 TL06. Smitty Install produces the following error message: Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. geninstall -I "a -cgNQqwXY -J" -Z -d... (5 Replies)
Discussion started by: tgray71
5 Replies

3. AIX

Using SAMBA in AIX 5.3

Please help, I'm wicked... :confused: I'm trying to get Samba to work on an IBM pseries machine (AIX 5.3) to provide access to the server for a user to retrieve reports from her WinXP desktop. I've made the proper entires in the smb.conf file and tried runing the smbpasswd command to add the user... (4 Replies)
Discussion started by: trandall
4 Replies

4. AIX

Upgrading AIX 5.2 to AIX 6.1 - GCC compatibility

Hi All, We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment... how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies

5. AIX

Upgrading AIX from 5.3 to 6.1

Hi, I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup. Please suggest Regards, Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

7. AIX

Upgrading from aix 5.3 to ?

Hey guys, since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap. Any experience on upgrading directly to 7.1, with sap/db2/oracle? could do fresh installs and import my sap/db vgs, but this would be a lot of work cheers Funksen (4 Replies)
Discussion started by: funksen
4 Replies

8. AIX

Regarding Upgrading RAM in AIX 6.1

Hi Folks, Currently we are having the below configuration in one of our AIX 6.1 server. RAM:- 8 GB Paging space :- 19 GB CPU processor:- 1 CPU type: 64 bit But we would like to upgrade the configuration to below to improve the system performance and resolve some memory issues. ... (11 Replies)
Discussion started by: sumanmca2006
11 Replies

9. AIX

Upgrading to AIX 7 vs migrating

Hi all, I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies

10. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
APT(8)									APT								    APT(8)

NAME
apt - command-line interface SYNOPSIS
apt [-h] [-o=config_string] [-c=config_file] [-t=target_release] [-a=architecture] {list | search | show | update | install pkg [{=pkg_version_number | /target_release}]... | remove pkg... | upgrade | full-upgrade | edit-sources | {-v | --version} | {-h | --help}} DESCRIPTION
apt provides a high-level commandline interface for the package management system. It is intended as an end user interface and enables some options better suited for interactive usage by default compared to more specialized APT tools like apt-get(8) and apt-cache(8). Much like apt itself, its manpage is intended as an end user interface and as such only mentions the most used commands and options partly to not duplicate information in multiple places and partly to avoid overwhelming readers with a cornucopia of options and details. update (apt-get(8)) update is used to download package information from all configured sources. Other commands operate on this data to e.g. perform package upgrades or search in and display details about all packages available for installation. upgrade (apt-get(8)) upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for a package requires the remove of an installed package the upgrade for this package isn't performed. full-upgrade (apt-get(8)) full-upgrade performs the function of upgrade but will remove currently installed packages if this is needed to upgrade the system as a whole. install, remove, purge (apt-get(8)) Performs the requested action on one or more packages specified via regex(7), glob(7) or exact match. The requested action can be overridden for specific packages by append a plus (+) to the package name to install this package or a minus (-) to remove it. A specific version of a package can be selected for installation by following the package name with an equals (=) and the version of the package to select. Alternatively the version from a specific release can be selected by following the package name with a forward slash (/) and codename (stretch, buster, sid ...) or suite name (stable, testing, unstable). This will also select versions from this release for dependencies of this package if needed to satisfy the request. Removing a package removes all packaged data, but leaves usually small (modified) user configuration files behind, in case the remove was an accident. Just issuing an installation request for the accidentally removed package will restore its function as before in that case. On the other hand you can get rid of these leftovers by calling purge even on already removed packages. Note that this does not affect any data or configuration stored in your home directory. autoremove (apt-get(8)) autoremove is used to remove packages that were automatically installed to satisfy dependencies for other packages and are now no longer needed as dependencies changed or the package(s) needing them were removed in the meantime. You should check that the list does not include applications you have grown to like even though they were once installed just as a dependency of another package. You can mark such a package as manually installed by using apt-mark(8). Packages which you have installed explicitly via install are also never proposed for automatic removal. search (apt-cache(8)) search can be used to search for the given regex(7) term(s) in the list of available packages and display matches. This can e.g. be useful if you are looking for packages having a specific feature. If you are looking for a package including a specific file try apt- file(1). show (apt-cache(8)) Show information about the given package(s) including its dependencies, installation and download size, sources the package is available from, the description of the packages content and much more. It can e.g. be helpful to look at this information before allowing apt(8) to remove a package or while searching for new packages to install. list (work-in-progress) list is somewhat similar to dpkg-query --list in that it can display a list of packages satisfying certain criteria. It supports glob(7) patterns for matching package names as well as options to list installed (--installed), upgradeable (--upgradeable) or all available (--all-versions) versions. edit-sources (work-in-progress) edit-sources lets you edit your sources.list(5) files in your preferred texteditor while also providing basic sanity checks. SCRIPT USAGE AND DIFFERENCES FROM OTHER APT TOOLS
The apt(8) commandline is designed as an end-user tool and it may change behavior between versions. While it tries not to break backward compatibility this is not guaranteed either if a change seems beneficial for interactive use. All features of apt(8) are available in dedicated APT tools like apt-get(8) and apt-cache(8) as well. apt(8) just changes the default value of some options (see apt.conf(5) and specifically the Binary scope). So you should prefer using these commands (potentially with some additional options enabled) in your scripts as they keep backward compatibility as much as possible. SEE ALSO
apt-get(8), apt-cache(8), sources.list(5), apt.conf(5), apt-config(8), The APT User's guide in /usr/share/doc/apt-doc/, apt_preferences(5), the APT Howto. DIAGNOSTICS
apt returns zero on normal operation, decimal 100 on error. BUGS
APT bug page[1]. If you wish to report a bug in APT, please see /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command. AUTHOR
APT team NOTES
1. APT bug page http://bugs.debian.org/src:apt APT 1.6.3ubuntu0.1 20 October 2015 APT(8)
All times are GMT -4. The time now is 10:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy