FC2t3: error installing Sun j2re rpm on kickstart %post
by Pedro Morais
Hi!
First of all this is not a "jvm does not work" problem; it works just fine,
after I manage to install it.
I've been checking my kickstarts against FC2 test 3; other than small changes,
the only problem is that installing the j2re rpm on %post gives the following
error:
---------------------------------------------------------------
Retrieving http://kickstart/redhat/fc2/extra/java/j2re.rpm
Preparing... ##################################################
j2re ##################################################
error: unpacking of archive failed on file
/usr/java/j2re1.4.2_02/CHANGES;40967cf3: cpio: lsetfilecon failed -
Inappropriate ioctl for device
---------------------------------------------------------------
j2re.rpm is a symlink on the webserver to j2re 1.4.2_02.
However, if I just give the rpm -Uvh command after the install is complete,
using exactly the same http url, everything works fine (besides the
file_contexts warnings).
The CHANGES file mentioned on the error message is the first file on the RPM.
Other RPMs are installed ok, so this is not a generic rpm-in-%post issue.
On the rpm package changelog I found this:
---------------------------------------------------------------
* Qua Mar 10 2004 Jeff Johnson <jbj(a)jbj.org> 4.3-0.20
- add sparcv8 and enable elf32/elf64 Zon sparc64 (#117302).
- fix: --querybynumber looped.
- fix: ENOTSUP filter from lsetfilecon borkage.
...
Sex Mar 05 2004 Jeff Johnson <jbj(a)redhat.com> 4.3-0.18
- selinux: ignore ENOTSUP return from lsetfilecon.
---------------------------------------------------------------
Could it be that that the 'rpm' binary in post is different (older) than the
one that ends up installed?
And maybe this could be related to this bug?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=120552
All SELinux-related stuff was left at the default values.
Worth putting in bugzilla?
Pedro Morais
20 years, 1 month
dmesg error
by bcohen1@binghamton.edu
Hey,
I've been having problems with core 2 once I yum updated to the newest
version. I had the "selinux problem" that someone posted and I fixed it by
setting my selinux config file to "disabled". By the way, what is selinux?
Now my new problem is:
when I run "dmesg" this is what pops up:
re initial load_policy on unknown context system_u:object_r:sysstat_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_log_sysstat_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_log_sysstat_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_log_sysstat_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tcpd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tftpd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tftpd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tftpdir_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tmpreaper_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:tmpreaper_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:traceroute_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:traceroute_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:traceroute_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:traceroute_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:transproxy_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:transproxy_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:udev_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:udev_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:udev_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:udev_helper_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:udev_helper_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:uml_switch_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:uml_switch_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:user_uml_rw_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:updfstab_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:etc_uptimed_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:uptimed_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:uptimed_spool_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:usbmodules_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:usbmodules_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:useradd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:useradd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:useradd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:groupadd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:groupadd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:groupadd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:groupadd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:groupadd_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:userhelper_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:userhelper_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:usernetctl_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:utempter_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_sys_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_sys_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_file_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_file_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_file_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_file_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:vmware_user_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:watchdog_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:watchdog_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:watchdog_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:watchdog_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xauth_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:user_home_xauth_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:user_home_xauth_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_tmp_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_rw_etc_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xsession_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_lib_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_lib_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_var_run_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xfs_tmp_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xfs_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:agp_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:dri_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_lib_xkb_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_lib_xkb_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:var_lib_xkb_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:bin_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_xserver_tmp_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xdm_xserver_tmp_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:xserver_misc_device_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:ypbind_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:ypserv_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:ypserv_conf_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:zebra_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:zebra_exec_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:zebra_log_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:zebra_conf_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_dir_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:httpd_staff_content_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_gpg_secret_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_irc_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_mozilla_rw_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_mozilla_rw_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_mozilla_rw_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_screen_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_screensaver_rw_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_ssh_t
security_context_to_sid: called before initial load_policy on unknown
context root:object_r:staff_home_xauth_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:default_context_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:amanda_recover_dir_t
security_context_to_sid: called before initial load_policy on unknown
context system_u:object_r:staff_home_spamassassin_t
Any suggestions?
Other little things are going wrong also (like my system clock won't
change when I change the time)
Thanks,
Linux newb
20 years, 1 month
Re: libusb and scanners - scanner module removed in 2.6 kernel
by W. Michael Petullo
--- Jim Cornette <redhat-jc(a)insight.rr.com> wrote:
> I was trying to use bugzilla and it did not work correctly. Anyway, the
> version of SANE-Backends is 1.0.13 and there was a lead that a hotplug
> wrapper might be needed to fix the scanner problem using the 2.6 kernel
> and scanners.
> By checking out the SANE webpage, I found the below information. This is
> a recent change. Is this USB hotplugging fix what is needed?
> Currently, I run a chown user /proc/bus/usb/001/004 in my /etc/rc.local
> file to get my scanner working on boot. I leave it plugged into the same
> usb port.
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121893.
--
Mike
20 years, 1 month
Adding fc2trc to Grub menu
by Steven P. Ulrick
Hello, Everyone :)
I did all I reasonbly could to answer this on my own, and I found no
applicable information.
Here's the scenario: I have four devices hooked up to the two ide busses
on my motherboard. They could be described something like this:
primary master: Western Digital 120 gig HD
primary slave: CD-ROM, indeterminate origin
Secondary Master: Maxtor 120 gig HD
Secondary Slave: Maxtor 40 gig HD
I have grub installed on the master boot record, but I installed FC2TR3
on the Secondary Slave, and chose to install GRUB on that disc, so my
main systems GRUB configuration would not get wiped out. What I would
like to do is either burn a CD that would boot right to my Fedora Core 2
test release 3 installation, like a boot floppy used to when we could
make those. Or, I would like to add my Secondary Slave (I'm ASSUMING it
is "hd3", since my grub.conf says that the location of my kernels is
(hd0,0)) to my GRUB boot menu.
The following is my grub.conf, with one kernel from my Fedora Core 1
installation, and my attempt at booting FC2TR3 being the only entries
I'm going to burden you with :):
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2188.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ rhgb
initrd /initrd-2.4.22-1.2188.nptl.img
title Fedora Core 2tr3 (2.6.5-1.327)
root (hd2,1)
kernel /vmlinuz-2.6.5-1.327 ro root=LABEL=/ rhgb
initrd /initrd-2.6.5-1.327.img
Here, I hope, is the /boot directory that I got the 2tr3 information
from:
grub/
lost+found/
boot.b
chain.b
config-2.6.5-1.327
initrd-2.6.5-1.327.img
memtest86+-1.11
os2_d.b
System.map-2.6.5-1.327
vmlinuz-2.6.5-1.327
I have (hd2,1) in my "root" line in grub.conf, but that is just the last
guess I made at trying to get this to work on my own. I tried (hd3,0)
and (hd3,1), and nothing worked.
If this has been answered elsewhere, please feel free to just give me a
link to where it's been answered, and I'll be glad to take it from
there. Of course, if I can't figure it out then, THEN I'll come back to
the experts (you, of course :))
Have a Great Day :)
Steven P. Ulrick
20 years, 1 month
RE: header/RPM mismatch
by Fulko.Hew@sita.aero
>> Whats wrong, is that for some reason (that I do not
>> understand) this morning I had the various apps reporting the
>> following various needs:
>>
>> package rhn up2date yum
>> -------------------------------------------------
>> perl-XML-Twig need it need it need it
>> perl-Net-DNS need it need it
>> gaim need it
>> rpmdb-fedora need it
>>
>> I'd have to think that if they were all using the same info,
>> they'd be reporting the same thing. Wouldn't they?
>> The fact that three different apps are reporting three
>> different 'apparent' states of my system is disconcerting.
>> Thats why I don't know who to believe.
>> And yes, I know that rpm -q tells what I've got But this
>> discussion thread revolves around:
>> 'which of these packages _really_ need updating'?
>> (Not a yum/up2date/apt-get/etc flame war.)
>
>This really looks to me like yum is looking at more repositories than
>up2date is.
Unfortunately, they are both configured the same way...
and that is as delivered on the CD and updates.
>I don't really understand why you have rhn listed as a client
>here, as that is what up2date is.
I use 'rhn' to refer to the 'rhn-applet' on the task bars.
Because it is a different application than 'up2date'.
20 years, 1 month
linux-unbootable-cdrom
by jonas2@optimum2.mii.lt
Dear Colleagues,
I am responding to:
"Fedora Core 2 test3 Available!
Notable changes in this release include:
- The 'CD1 won't boot' issue appears to be resolved. Any reports of
continued failure are certainly appreciated."
This is very good news for those using linux-bootable CDROM.
Attached tables show that most of Intel main boards are not
linux compatible and many Intel BIOS drivers consider the linux boot
CDROM
just as
a CDROM.
My Intel Desktop Board D845BG featuring Intel Express Installer
belongs to
this category
and so many of my students PC.
Before kernel 2.6 that was no problem because
boot-floppies were doing the job.
A solution now seems to develop a sort of two-floppy
boot system.
That will help people without linux-bootable CDROM's
or similar devices.
It would be usefull for others, too,
because floppy-boot is very simple and
convenient.
Best regards
Jonas Mockus
20 years, 1 month
Problems with installation on PackardBell EasyNote M3 (AMD64 3000+, 512MB, LCD 15, 4" 1280 x 800 pixels, ATI Radeon Mobility 9000 Pro)
by Alessandro Torrisi
Hi! I've seen problems in mailing list with eMachines. I see that CPU, GPU
Vendor and Screen types are the same !!!
I've got problems during:
* Graphical installation
* X starts but output is sent to the second output
* After text installation
* X starts but output is sent to the second output
* Must use VESA driver and not ATI one
How can I configure X ? Can I use a resolution of 1280 x 800 with this
notebook ?
Is there any hint for graphical configuration ? Can I follow explanations
for eMachines ?
Thanks in advance, Alessandro Torrisi.
20 years, 1 month
Installing additional packages using apt-get
by Paul F. Johnson
Hi,
I'm trying to install Audacity using apt-get under FC2T3 and I am
getting the following errors
apt-get install audacity
E: Umet dependencies. Try 'apt-get -f install' with no packages (or
specify a solution)
Reading Package Lists...
Building Dependency Tree...
audacity is already the newest version.
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libgnomeprint#1.116.0-9: PreDepends: XFree86 but it is not going to be
installed
libquicktime: Depends: libdv.so.2
mjpegtools: Depends: libdv.so.2
subtitleripper: Depends: libpbm.so.9
Depends: libppm.so.9
tetex-texmf-doc: Depends: tetex-texmf but it is not installable
transcode: Depends: libMagick-5.5.6-Q16.so.0
Depends: libdv.so.2
xine-mozilla-plugin: Depends: libxine1 (>= 1) but it is not
installable
Is it safe for me to run apt-get -f install without screwing things up
on my machine? I run yum update roughly every day and don't want to
break anything.
TTFN
Paul
--
"There are four stages to any war
First they ignore you, then they laugh at you
Then they fight you, then YOU win."
Ghandi
20 years, 1 month