Sponsored Content
Full Discussion: Unable to format suse Linux
Operating Systems Linux SuSE Unable to format suse Linux Post 302951923 by MadeInGermany on Tuesday 11th of August 2015 05:28:01 PM
Old 08-11-2015
According to How to Enter Your PC's BIOS | PCWorld it's not always the F2 key; it can be F1 or F3 or Del or Esc.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to boot with XP after installing SUSE

Hi, I'm not sure if this is the right forum to post. I had following setup before installing SUSE Linux: Windows 98 installed on Primary partition Windows XP installed on Extended Partition When I installed SUSE, it shared space from primary partition and shrunk the size of Windows... (4 Replies)
Discussion started by: patras
4 Replies

2. SuSE

Unable to Run a script at startup in suse

Hi I have a script myscript.sh that needs to be run whenever the server boots. The script is actually logging Syslog-ng messages to sql server. I need to lauch it at startup I have copied the script in etc/init.d i have also added the link ln -s /etc/init.d/syslog-ng-mssql-pipe.sh... (5 Replies)
Discussion started by: SystemEng
5 Replies

3. Linux

Unable to login with Domain users in the Suse linux

Hi Team, I have joined the Suse Linux Server in my domain. I am not able update the DNS but I am able to join the domain. net ads testjoin gives me Join ok. even net ads dns register -P results to DNS update failed. wbinfo -u and wbinfo -g also not working. Samba Configuration: ... (1 Reply)
Discussion started by: naree
1 Replies

4. UNIX for Beginners Questions & Answers

Linux SuSE SLES 8 error..unable to issue shutdown command

the only way we can power off is if we actually press power button on server. Running on HP DL-G4. from root, when we issue command it just returns to root prompt. (1 Reply)
Discussion started by: amexboy
1 Replies
locks(5)							   System Tools 							  locks(5)

NAME
locks - libzypp locking file DESCRIPTION
The file /etc/zypp/locks is read by libzypp at startup if zypp.conf allows it. The entries are used for initial locking of packages. Lock- ing a package means not allowing to install or uninstall it. Valid entries are attribute: value Where attributes and their values are described below. Locks are separated by empty lines. ATTRIBUTES
All attributes are lower-case. repo specifies repository restriction. Only alias is accepted. By default all repositories match. type resolvable type restriction The values can be package, patch, pattern, product and srcpackage. By default all types match. case_sensitive if strings are matched case sensitive. The values are true, false, on, off. The default is case insensitive. install_status status of object. Possible states are installed, not-installed and all. If more install statuses are specified then the last one is used. The values are installed for all packages which are installed, non-installed for packages which can be installed or reinstalled and all for both. The default is all. match_type type of string matching in values. Does not affect type and repo which must be specified exactly. The values are exact, substring, regex for regular expressions, glob for matching as on the command line, and word. The default is substring. query_string String to be matched in multiple attributes. Should be restricted by another attribute with empty value ( it is recommended, because without restriction expect some performance problems ). version Restrict the lock only to some versions. It contains two parts: an optional operator and the version. The operator is ==,!=,<,>,<=,>=. If operator is not specified then == is used. The version has the format [epoch:]version[-release]. Example: version: < 0:0.11.4-2 solvable_name name of object (e.g. zypper) solvable_summary summary of object solvable_arch architecture of object (e.g. x86_64, i586) solvable_description description of object solvable_eula license text of objects which request accepting license by user solvable_license license of package (only for package) (e.g. GPL2) solvable_keywords keywords which specify package (only for package) solvable_authors authors of package (only for package) solvable_group package group (only for package) (e.g. Development/Tools/Version Control ) update_reference_type reference for update (e.g. bugzilla,cve) (only for patches) EXAMPLES
Exact Package This is the way YaST UI does it. Lock k3b (e.g. you don't want to update it). -----locks----- type: package solvable_name: k3b match_type: exact case_sensitive: on Package Wildcard This is the way "zypper addlock cross-*-gcc-icecream-backend" does it. -----locks----- type: package solvable_name: cross-*-gcc-icecream-backend match_type: glob case_sensitive: on Versioned Lock Do not install new GCC. This format is used when converting from the openSUSE-10.3 lock format. -----locks----- solvable_name: gcc match_type: glob version: > 4.2 Anything named KDE Locks everything which contains kde in the name. -----locks----- solvable_name: kde Anything mentioning KDE Locks everything which contains kde in the name, summary, or description. -----locks----- query_string: kde solvable_name: solvable_summary: solvable_description: HOMEPAGE
This manual page only covers the most important attributes. The complete list is available at http://en.opensuse.org/Libzypp/Locksfile AUTHORS
Josef Reidinger <jreidinger@suse.cz> Manual page contributions by Martin Vidner <mvidner@suse.cz>. SEE ALSO
zypper(8) libzypp 4.25.0 locks(5)
All times are GMT -4. The time now is 12:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy