upgrading RH 9 system->Fedora with iso files and apt only
by Didier Casse
I have the yarrow's iso files on my HD in a RH9 system. Let's say I want
to upgrade selected packages using an "apt-get install" pointing to my
iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to
upgrade packages. Can anybody redirect me to the correct
resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use
apt-cdrom. Thanks.
With kind regards,
Didier.
---
PhD student
Singapore Synchrotron Light Source (SSLS)
5 Research Link,
Singapore 117603
Email: slsbdfc at nus dot edu dot sg \or\
didierbe at sps dot nus dot edu dot sg
Website: http://ssls.nus.edu.sg
2 years, 3 months
kernel/accounting question ...
by William W. Austin
(I know that this question might be more reasonable on a kernel list,
but a while back I posted the question twice and got no answers.)
The acct struct is defined in /usr/include/sys/acct.h includes both
ac_io and ac_rw for bytes transferred and blocks read or written,
respectively. Fair and good - works (on paper) similarly to unix,
solaris, hp-ux, etc.
However, in the kernel code [kernel/acct.c], ac_io (char) and ac_rw
(blocks) are always set to 0 by these two lines:
ac.ac_io = encode_comp_t(0 /* current->io_usage */);
ac.ac_rw = encode_comp_t(ac.ac_io / 1024);
For most purposes, this probably wouldn't be an issue, but I also do
extensive performance analysis on several platforms and have written a
fairly compresive accounting package (as a wraparound for psacct or as
a standalone) including both an improved acctcom and a built-in
reporter for it.
Does anyone know wby the kernel zero's out the bytes transferred data?
(Overhead comes to mind.) Not that it makes a huge differnce for my
purposes (I had to write some wraparound code to make a
"best-guestimate" about the data I'm missing), but curiosity is bugging
me now. When I compile my program on other OS's I get useful data for
char and block i/o and I'd like to find out whether there is something
obvious that I'm just totally missing here...).
Thanks
--
william w. austin waustin(a)speakeasy.net
"life is just another phase i'm going through. this time, anyway ..."
14 years, 4 months
acctcom for linux
by William W. Austin
I recently made several updates to a Linux version of of acctcom
(actually another accounting add-on package) which I've been using for
several years, and one of the people testing it asked a question which
I cannot answer. I'm hoping that someone on this list can give me some
info.
I have previously (over a year ago) asked on both this and a couple of
kernel lists (several times there) about this issue, but nobody has
ever answered. So if you have any info about this, I'd really
appreciate it.
As in many (all?) previous Linux kernels, the struct acct (defined in
/usr/include/sys/acct.h) has members ac_io and ac_rw which are
presumably counts of characters transferred and blocks read/written
respectively.
However, in the kernel code, the ac_io is set to 0 and the ac_rw gets
set to (ac_io/512) or some such - it is set to 0 as well (and thus
these are always reported as 0 in process accounting records. not good
if you're trying to measure them...).
Does anybody know why this is done that way? A long time ago (IIRC
late 2.2 and an early 2.4 kernel) I looked into "fixing" this in the
kernel code but was not successful (I finally produced a bootable
kernel, but it was unstable. Then I changed jobs, got swamped at work,
and eventually gave up).
As I said above, I have previously asked about this issue without
success, and I have essentially given up changing or "fixing" it.
But if anyone knows __WHY__ it is this way (I'm hypothesizing that it's
just too much work for too little added value), I'd really appreciate
knowing the reason. Curiosity and the cat and all that ...
Thanks
- Bill
--
william w. austin waustin(a)speakeasy.net
"life is just another phase i'm going through. this time, anyway ..."
14 years, 4 months
file system mount
by Amitakhya Phukan
hi all!
i have a system with fedora 7 and rhel 5 installed. recently, i changed
the f7 to rawhide. now whenever i boot up, it mounts all the file
systems related to rhel5 along with it and displays on the desktop.
dmesg says /dev/sda1 mounted on /media/_1 and so on. I want to disable
this feature. i don't know if this is anything useful ?? i even don't
know if its a feature or a bug... can any one please help me out with
this thing ? i understand hal is doing this (??), but why ? and even
when i unmount it, the same can still be found in /media. right clicking
on those partitions give me the option of mounting/unmounting them. but
i don't want to let them appear in my rawhide systems totally. anyone
else has this experience on rawhide??how do i disable it ??
thanks in advance.
with regards,
amitakhya phukan.
15 years, 8 months
Zimbra packages in Fedora
by Neal Gompa
I had noticed how well that Zimbra has been doing, and I was wondering if it
would be possible for someone to make packages for Zimbra to be included in
Fedora?
16 years
Any way to search all .spec files?
by Orion Poplawski
Is there any was to do a grep/search on all of the Fedora .spec files
for a specific release (or devel)? I'd be fine with checking them all
out if there was a way to just the the spec files for a specific release.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
16 years, 1 month
Orphaning packages
by Paul F. Johnson
Hi,
Just to let you know that other than the mono packages I currently maintain,
I'm going to have to drop the other packages I have down for me.
For ease, if it's a mono or mono-related package (such as mono-develop,
libgdiplus, db4o etc), I'll maintain it. Anything else is dropped. I'll update
the wiki and the owners lists as soon as I can.
Basically, it's the old problem of time....
TTFN
Paul
--
Get your free @ukpost.com account now
http://www.ukpost.com/
16 years, 2 months
Fedora 8 installation crash
by Thomas Swan
I don't think this is just you. When trying to install F8 on an HP laptop
(in text mode)
loader received SIGSEGV! Backtrace:
[0x804a030]
[0x110420]
[0x81a3f42]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
0x8048151]
Installing in graphical mode yields the following error messages:
*** glibc detected *** /sbin/loader: munmap_chunk(): invalid pointer:
0x0850c810
=== Backgrace: ===
[0x81a4083]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
======= Memory map =======
00110000-00111000 r-xp 001110000 00:00 0 [vdso]
08048000-0828e000 r-xp 00000000 00:01 36 /sbin/loader
0828e000-08299000 rw-p 00245000 00:01 36 /sbin/loader
08299000-082d3000 rw-p 08299000 00:00 0
0849b000-08589000 rw-p 0849b000 00:00 0
b7f36000-b7f39000 rw-p b7f36000 00:00 0
bfedb000-bfef0000 rw-p bffea000 00:00 0
loader received a SIGABRT! Backtrace:
[0x804a030]
[0x110420]
[0x81e7f80]
[0x8182a30]
[0x819930b]
[0x81a4003]
[0x805b750]
[0x805c153]
[0x804b207]
[0x8175004]
[0x8048151]
install exited abnormally [1/1]
This exact same problem happens when installing from known good media on
both USB DVD drives and the local dvd drive.
I am using the Fedora-8-i386-DVD.iso. Memtest has been run on this system
and there are no memory errors.
This doesn't seem to be isolated. <
http://www.nabble.com/F8-Installation-Issue---Second-Try-tf4806216.html#a...
>
--
The early bird may get the worm, but the it's the second mouse that gets the
cheese.
16 years, 3 months
Re: KDE logout options with F8
by Kevin Kofler
Christopher Aillon <caillon <at> redhat.com> writes:
> If your first reaction had been to ask for more information instead of
> add complaints, I might have mentioned that the plan is to have this for
> F9 (I think so at least, someone can correct me if I'm wrong?). Not
> sure if that counts as long term...
Even if somebody implements a KDE frontend for the GDM backend, that won't make
KDM go away. There's no way KDM is going away for KDE 4.0 which realistically
will be what F9 will be shipping. (And of course, it's even less likely that
said thing would happen in 3.5. Chances that KDE 4.1 will be anywhere near
ready at F9 release are essentially nil, 4.1 might quite possibly not even make
F10.)
> It is a reasonable request. Can you accept reasonable answers? Notting
> and jkeating have already replied with technical analysis explaining why
> it is not possible.
I have suggested at least 2 technical solutions, none of which needs any
changes to Anaconda:
1. revert the default login manager in Base X to XDM. As much as you
(plural "you") hate that, it's the most logical solution and some other people
in this thread are defending it too.
2. change the fallback logic to pick KDM over GDM. As I said, I think we can
easily put KDM in a subpackage so it doesn't accidentally get installed by a
dependency on kdebase, kde-redhat used to do that in FC6 times.
There's another one, which is even less invasive (and doesn't change the
behavior for the neither-GNOME-nor-KDE case as 1. nor for the
both-GNOME-and-KDE case as 2., but really only affects KDE-but-not-GNOME which
is what needs fixing), but has to be implemented as a specialized Anaconda
hack. Pseudocode:
if (! upgrade && KDE selected && ! GNOME selected)
echo 'DISPLAYMANAGER="KDE"' >/mnt/sysimage/etc/sysconfig/desktop
> Besides, we already know it's not going to happen for F8. And F9 we
> could in theory have a better all around solution....
"better" is subjective. If upstream KDE isn't going to drop KDM or recommend
against it, IMHO that fact shouldn't be ignored.
Kevin Kofler
16 years, 3 months
LTSP 5 on Fedora
by Alexandre Magaz Graça
Hi,
While searching for LTSP 5 for Fedora, I didn't find anything but this
bug report https://bugzilla.redhat.com/show_bug.cgi?id=234048. Also,
I've not found anything regarding LTSP in this list.
So, Is someone working on LTSP 5 support for Fedora? Is there some
repository were pick code from or anything?
Thanks,
Àlex
16 years, 3 months
