Sponsored Content
Operating Systems Linux SuSE Upgrading from Suse Linux 10.1(x86-64) Post 302991083 by Corona688 on Monday 6th of February 2017 01:15:20 PM
Old 02-06-2017
Without knowing anything about the software, it's tough to guess how to migrate it. That it's SuSE doesn't really tell me anything. But trial and error really isn't an option on an unsupported commercial product unless your backups are very, very good.

I'd suggest not doing anything without a complete, disk-clone deep backup -- so if you mess up, you can restore it to a known working state. (Or swap in the old hard drive.)
 

4 More Discussions You Might Find Interesting

1. SuSE

Suse LINUX

What is the equivalent of sun explorer in suse linux? Thanks (1 Reply)
Discussion started by: hassan2
1 Replies

2. Ubuntu

linux ultimate edition upgrading!!

How can I upgrade my ultimate edition from 9.0 to 11.4 without re-installation? (1 Reply)
Discussion started by: Msoviet
1 Replies

3. Solaris

Upgrading java on solaris 10 x86 32 bit

I have java installed on my solaris 10 as /usr/jdk/jdk1.5.0 , but i need to install Weblogic for that i need -- JDK Sun Java 2 JDK 6.0 Update 05 with the Java HotSpot™ Client and Server VMs (32-bit) and all later service packs of 6.0 How can i upgrade my java for this. (3 Replies)
Discussion started by: jain_sharad143
3 Replies

4. UNIX for Dummies Questions & Answers

terminator shell not working after upgrading ubuntu linux

Terminator is a program that allows users to set up flexible arrangements of GNOME terminals. It has stopped working for me after upgrading to ubuntu 11.10. it does not give prompt to type anything. Just stuck with /bin/bash in the title. I removed and installed again, same... (2 Replies)
Discussion started by: analyst
2 Replies
LN(1)								   User Commands							     LN(1)

NAME
ln - make links between files SYNOPSIS
ln [OPTION]... [-T] TARGET LINK_NAME (1st form) ln [OPTION]... TARGET (2nd form) ln [OPTION]... TARGET... DIRECTORY (3rd form) ln [OPTION]... -t DIRECTORY TARGET... (4th form) DESCRIPTION
In the 1st form, create a link to TARGET with the name LINK_NAME. In the 2nd form, create a link to TARGET in the current directory. In the 3rd and 4th forms, create links to each TARGET in DIRECTORY. Create hard links by default, symbolic links with --symbolic. When cre- ating hard links, each TARGET must exist. Symbolic links can hold arbitrary text; if later resolved, a relative link is interpreted in relation to its parent directory. Mandatory arguments to long options are mandatory for short options too. --backup[=CONTROL] make a backup of each existing destination file -b like --backup but does not accept an argument -d, -F, --directory allow the superuser to attempt to hard link directories (note: will probably fail due to system restrictions, even for the supe- ruser) -f, --force remove existing destination files -i, --interactive prompt whether to remove destinations -L, --logical make hard links to symbolic link references -n, --no-dereference treat destination that is a symlink to a directory as if it were a normal file -P, --physical make hard links directly to symbolic links -s, --symbolic make symbolic links instead of hard links -S, --suffix=SUFFIX override the usual backup suffix -t, --target-directory=DIRECTORY specify the DIRECTORY in which to create the links -T, --no-target-directory treat LINK_NAME as a normal file -v, --verbose print name of each linked file --help display this help and exit --version output version information and exit The backup suffix is `~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control method may be selected via the --backup option or through the VERSION_CONTROL environment variable. Here are the values: Using -s ignores -L and -P. Otherwise, the last option specified controls behavior when the source is a symbolic link, defaulting to -P. none, off never make backups (even if --backup is given) numbered, t make numbered backups existing, nil numbered if numbered backups exist, simple otherwise simple, never always make simple backups AUTHOR
Written by Mike Parker and David MacKenzie. REPORTING BUGS
Report ln bugs to bug-coreutils@gnu.org GNU coreutils home page: <http://www.gnu.org/software/coreutils/> General help using GNU software: <http://www.gnu.org/gethelp/> Report ln translation bugs to <http://translationproject.org/team/> COPYRIGHT
Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
link(2), symlink(2) The full documentation for ln is maintained as a Texinfo manual. If the info and ln programs are properly installed at your site, the com- mand info coreutils 'ln invocation' should give you access to the complete manual. GNU coreutils 8.5 February 2011 LN(1)
All times are GMT -4. The time now is 04:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy