10 More Discussions You Might Find Interesting
1. Solaris
hi am trying to get some knowledge on Solaris common trouble shooting problems..
can some one help me in getting most common issues..
and how to solve those issues.
thanks in advance (4 Replies)
Discussion started by: aravindreddy
4 Replies
2. Linux
I recently downloaded a DSL iso file. I loaded the iso in VirtualBox and it worked perfectly, but when I wrote the iso to a CD using k3b and I tried booting it, I got an error. I tried booting from the disk in VirtualBox and got the same error. "FATAL: Could not read from the boot medium! System... (3 Replies)
Discussion started by: Bradj47
3 Replies
3. Solaris
Solaris 10 5/08 on Ultra 40 M2
It boots fine off primary disk but having issues booting off the mirror disk.
I get this error when booting off mirror disk:
Booting 'Solaris 10 ... Mirror disk'
root (hd1,0,a)
Error 22: No such partition
Press any key to continue...
Any... (7 Replies)
Discussion started by: etc
7 Replies
4. Solaris
Hi All,
I have detached a mirror and primary disk from my Solaris box.
On trying to boot from Primary disk, It boots up good.
But from my mirror disk, it is not booting and giving me the login prompt
Instead it goes to maintenance state by issuing a coredump.
Can you explain why... (9 Replies)
Discussion started by: jegaraman
9 Replies
5. Solaris
Hello..
I am Still Learing Solaris ..
when i try to Install Solaris 8 from its CD...i pressed STOP + A and i get a OK prompt screen.
I then typed, "boot cdrom" and i am getting this error message.
" FATAL: system is not bootable, boot command is disabled."
How do we enable the boot... (5 Replies)
Discussion started by: vr76413
5 Replies
6. UNIX for Dummies Questions & Answers
I booted up my SUSE ver 10.1 linux box today. Went to the DOS-type login. Failed to display KDE.
I understand this has something to do with levels. But how do I change the default? I know zero about Vi (and don't need to learn it). How do I get the system to boot to KDE again?
Best... (5 Replies)
Discussion started by: dickbash
5 Replies
7. Linux
I installed RH8 on Thinkpad R51. The install went smooth, but when I tried to boot, it hanged at:
PCI_IDE: unknown IDE controller on Pci bus 00 device f9, VID=8086, ID=24ca
PCI: Device 00:1f.1 not available because of resource collisions.
PCI_IDE: (ide_setup_pci_device:) could not enable... (0 Replies)
Discussion started by: etc
0 Replies
8. UNIX for Dummies Questions & Answers
Hello there guys ,
I have a unix box that i just install on a HP VL400 , installation went all the way no problem.
I get the BOOT: Hit enter and it goes to the point that you can see the all the hardware info.
the problem is that freeses when gets to this point
H oeminit
Note: I put... (1 Reply)
Discussion started by: josramon
1 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
I've managed to get Mandrake 9 installed by disconnecting my 2 windows' drives. When I reconnect them Mandrake wants to take over. I figure it's time for the BootManager, or should I use a Linux specific one like Lilo? Or have I already stuffed up by not running Lilo at time of... (2 Replies)
Discussion started by: onestepto
2 Replies
10. UNIX for Advanced & Expert Users
When i try to boot my solaris 2.6 E220R server, i get this error message
> INIT: cannot create /var/adm/utmp or /var/adm/utmpx
>INIT: failed write of utmpx entry:" "
>INIT: failed write of utmpx entry:" "
INIT Single User Mode
Press Ctrl-d for normal boot process or enter roots password... (10 Replies)
Discussion started by: lealyz
10 Replies
yum-filter-data(1) yum-filter-data(1)
NAME
yum filter data plugin
SYNOPSIS
yum [options] [command] [package ...]
DESCRIPTION
This plugin extends yum with some options, currently just for "update" and "list update" type commands, to allow filters to be placed on
which packages should be used based on the data in those packages. Note that due to some of the data being unknown, and thus could possibly
match, all unknown data is treated as a match.
GENERAL OPTIONS
These are the options added to yum that are available in the "list updates", "info updates", "check-update" and "update" commands. They
are:
--filter-vendors
This option includes packages which have a vendor which matches one of the passed vendor wildcard strings, or is unknown. Note that
vendors can have spaces in their value, so "," is the only way to specify multiple vendors as one option argument.
--filter-rpm-groups
This option includes packages which have a group which matches one of the passed rpm group wildcard strings, or is unknown. Note
that rpm groups can have spaces in their value, so "," is the only way to specify multiple rpm groups as one option argument.
--filter-packagers
This option includes packages which have a packager which matches one of the passed packager wildcard strings, or is unknown. Note
that vendors can have spaces in their value, so "," is the only way to specify multiple packagers as one option argument.
--filter-licenses
This option includes packages which have a license which matches one of the passed license wildcard strings, or is unknown. Note
that licenses can have spaces in their value, so "," is the only way to specify multiple licenses as one option argument.
--filter-arches
This option includes packages which have a arch which matches one of the passed arch wildcard strings, or is unknown.
--filter-committers
This option includes packages which have a committer which matches one of the passed committer wildcard strings, or is unknown. Note
that committers can have spaces in their value, so "," is the only way to specify multiple committers as one option argument. Also,
committer values are so loosely formed that they could contain commas too, it is recommended to not do that but you can work around
it by using "?".
--filter-buildhosts
This option includes packages which have a buildhost which matches one of the passed buildhost wildcard strings, or is unknown.
--filter-urls
This option includes packages which have a url which matches one of the passed url wildcard strings, or is unknown.
--filter-package-sizes
This option includes packages which have a packagesize which is within one of the passed packagesize ranges, or is unknown.
--filter-archive-sizes
This option includes packages which have a archivesize which is within one of the passed archivesize ranges, or is unknown.
--filter-installed-sizes
This option includes packages which have a installedsize which is within one of the passed installedsize ranges, or is unknown.
--filter-groups
This option includes packages which are in a yum group which matches one of the passed yum group id strings, or is unknown. Note
that yum groups can have spaces in their value, so "," is the only way to specify multiple yum groups as one option argument.
EXAMPLES
To list all updates that are 1 MB or less use:
yum --filter-package-sizes=-1m check-update
To apply updates that Dan Walsh has committed use:
yum --filter-committers='Dan Walsh *' update
To list updates for a specific group use:
yum --filter-rpm-groups='App*/Sys*' list updates
To apply updates to a specific set of groups use:
yum --filter-rpm-groups='App*/System,Devel*/Lib*,System Environment/Base' update
To list updates for a set of yum groups use:
yum --filter-groups='PostgreSQL Database,Web Server' list updates
To apply updates to a specific set of yum groups use:
yum --filter-groups='KDE,Core,Printing Support' update
SEE ALSO
yum-list-data (1)
yum (8)
yum.conf (5)
AUTHORS
James Antill <james.antill@redhat.com>.
BUGS
Currently yum can't filter packages in all of the commands, so for instance "yum list 'yum*'" doesn't get the results filtered.
Apart from that there are no bugs, but should you find any, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and
if unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.red-
hat.com for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs.
James Antill 04 February 2008 yum-filter-data(1)
