[Cooker]
SUB cooker
RE: [Cooker] Re: [CHRPM] kernel-2.4.16.3mdk-1-1mdk
> -Original Message- > From: Alexander Skwar [mailto:[EMAIL PROTECTED]] > > So sprach »Cain Brian-BCAIN1« am 2001-12-05 um 10:37:53 -0600 : > > > Isn't this the whole purpose for Cooker? I use cooker on my ... > Did you read Juans mail? He explained that he wants to have multiple Feelin' pretty stupid about now. I think I'll take a more passive stance on the list (or at least read the entire thread before contributing to it). ... > a) Don't cc me! I read the list! Hm. I thought it was convenient when people CCd me, even when I read the list. Consider me informed. > b) Your lines are *WAY* too long! Keep it down to ~72 chars! Sorry about that. Perhaps I should know better than to use Outlook as a mail client (manually wrapping lines sucks). -Brian
RE: [Cooker] Re: [CHRPM] kernel-2.4.16.3mdk-1-1mdk
> -Original Message- > From: Alexander Skwar [mailto:[EMAIL PROTECTED]] > > So sprach »Yves Duret« am 2001-12-05 um 15:00:24 +0100 : > > patches from everywhere without the risk of breaking > cooker. if the new one is > > stable enough, the older goes away and so on... > > Hm, if that's the goal, what about having: > > Name: kernel ... > and for the experimental kernel: > > Name: kernel-test ... > > This would allow the kernel hackers to experiment with a kernel, while ... Isn't this the whole purpose for Cooker? I use cooker on my "production" machine, knowing all along that it shouldn't be considered stable. It seems like you're advocating yet another unstable branch for Mandrake Linux? The only reason I could see that there would be a need for it is if you think that there should be three branches - "stable", "kinda stable", "experimental". The simplest solution for your problem would probably be just to use Mandrake kernel (and otherwise) rpms, and stay away from Cooker rpms. -Brian
RE: [Cooker] Problem with kernel 2.4.8-26mdk and above
Interesting...This looks slightly similar to the problem I observed w/lilo. I would recommend trying a more recent version (from another distro, if necessary). See my thread "[Cooker] Kernel and samba upgrades -- solved, mostly...". > -Original Message- > From: Anders Bruun Olsen [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 28, 2001 12:09 PM > To: [EMAIL PROTECTED] > Subject: Re: [Cooker] Problem with kernel 2.4.8-26mdk and above > > > On Monday 19 November 2001 14:41, you wrote: > > > >> sounds like your kernel is too big try taking some > kernel drivers out > > > >> bye the way which kernel did you install and is it compressed > > > anders> I'm using the standard rpm from cooker to install > it so I can't > > > just remove anders> some drivers, at least not unless I > compile the > > > kernel myself... but anders> shouldn't it just work > "out-of-the-box"?? > > > Yes, I thought that you was compiling Mandrake kernel. That don't > > > happens here, could you re-check with a latest > 2.4.13-8mdk kernel and > > > report back? > > Sure thing, I'll have access to the machine in question again this > > wednesday - I'll check it there.. > > I didn't have access to it this wednesday, but I had access > to it today :) > > I'm afraid the problem persists.. 2.4.13-12mdk still reboots > if I try to boot > up the system with it.. > > > > >> > > At work I have an IBM IntelliStation E Pro. > > > >> > > It's specs are: > > > >> > > Pentium III 933MHz > > > >> > > 128Mb RAM > > > >> > > Via chipset > > > >> > > Adaptec 29160 (7892A according to harddrake) SCSI > controller > > > >> > > Samsung SC-148F CDROM (Atapi) > > > >> > > Intel 82557 Ethernet Pro 100 > > > >> > > GeForce video card > > > >> > > I've upgraded it from 8.0 to 8.1 except for the > kernel, when I try > > > >> > > to it on a 2.4.8-26mdk or 2.4.10-2mdk kernel it just writes > > > >> > > "Loading Linux ..." (the normal stuff) and then > reboots. The same > > > >> > > happens when I try to boot from the 8.1 cds .. ?? > > > >> > > Kernel 2.4.3-20mdk works fine.. > > > >> > I've just tried kernel 2.4.12-5mdk today... same problem as > > > >> > 2.4.10-2mdk .. the machine still reboots after the > "Loading Linux" > > > >> > line.. > > -- > Anders > -BEGIN GEEK CODE BLOCK- > Version: 3.12 > GO d--@ s:+ a-- C++ $UL++ P++ L+++ E- W+ N(+) o K? w !O M-- V > PS+ PE@ Y+ PGP+ t 5 X R+ tv+ b+ DI+++ D+ G e- h !r y? > --END GEEK CODE BLOCK-- >
RE: [Cooker] Kernel and samba upgrades -- solved, mostly...
> -Original Message- > From: Cain Brian-BCAIN1 [mailto:[EMAIL PROTECTED]] > ... > I recently attempted a kernel upgrade (to 2.4.13-8mdk), but > it was unsuccessful. LILO gives me a "EBDA too big" error, ... This problem was fixed by upgrading to a more recent lilo version. Unfortunately, on the upgrade to 2.4.13-11mdk, it happened again. This was then fixed by upgrading to a more recent version of lilo (lilo-22.1-1), though I was forced to use another distro's rpm. I have conferred with lilo's maintainer, and he confirms that there were some inconsistencies in the way lilo worked in 21.x, which should have all been addressed by 22.x. Is there an instability with recent lilo versions, or any other reason not to be on 22.x? (Or am I just being impatient?) > ~~~ > > Also, my most recent samba upgrade (to 2.2.2-?mdk) has been > fraught with peril. I believe that the "network recycle bin" > patch might be the cause of one problem I've noticed -- I ... Thanks, Sylvestre, samba-2.2.2-5mdk works great! (My domain logon issue was misconfiguration...d'oh!). XP seems to have some weird problem deleting directories sometimes. I believe it's trying to delete the files in parallel, and it might be trying to delete the directory before it's empty? In any case, attempting to delete the directory multiple times is the workaround. (Has anyone else noticed this behavior?) -Brian
[Cooker] Kernel and samba upgrades
Hi all, Is this the proper venue for listing bugs (or probable bugs) found in cooker rpms? If not, I'd appreciate a pointer to the right place. I recently attempted a kernel upgrade (to 2.4.13-8mdk), but it was unsuccessful. LILO gives me a "EBDA too big" error, which I've read about a little, but I can't seem to find a unilateral fix. vmlinuz-2.4.13-8mdk is 1073187 bytes long, and since the kernel's precompiled, I haven't any clue how to decrease its size. I'm curious why more people wouldn't run into this kind of limitation -- it must have to do with some obscure hardware I'm using (it is a pretty old BIOS...)? The original rpm install claimed that the postinstall script had an exit code of 1 (detectloader couldn't find the bootloader?), which I had no clue how to address. I've reinstalled the rpm (w/ --force) quite a few times, and it hasn't worked yet (so it wasn't just a fluke, I would imagine), though it no longer complains about the postinstall script failing (see debug below): This is not the first kernel upgrade where I've encountered an "EBDA too big" error. I'd really appreciate it if someone could tell me how to fix this (or confirmed that it is some kind of bug). The one kernel that I can boot from is 2.4.9 (I believe I might have compiled this one on my own), is 1046303 bytes -- not much smaller than 2.4.13-8mdk (but just under 2^20?). ~~~ rpm --upgrade --force -vvh output: D: running preinstall script (if any) kernel #GZDIO: 1901 reads, 15567340 total bytes in 31.395 secs # D: ---427 kernel-2.4.13-8mdk D: removing "kernel" from Name index. D: removing 1221 entries from Basenames index. D: removing "System/Kernel and hardware" from Group index. D: removing 9 entries from Requirename index. D: removing 5 entries from Providename index. D: removing 2 entries from Conflictname index. D: +++428 kernel-2.4.13-8mdk D: adding "kernel" to Name index. D: adding 1221 entries to Basenames index. D: adding "System/Kernel and hardware" to Group index. D: adding 9 entries to Requirename index. D: adding 5 entries to Providename index. D: adding 2 entries to Conflictname index. D: running postinstall scripts (if any) + cd /boot + '[' -x /sbin/installkernel ']' + /sbin/installkernel -a -c 2.4.13-8mdk not adding entry, 2413-8 already exists + depmod -a -F /boot/System.map-2.4.13-8mdk 2.4.13-8mdk D: closed db index /var/lib/rpm/Depends ...(various other rpm db closes) ~~~ [root@guild brian]# file /boot/vmlinuz-2.4.13-8mdk /boot/vmlinuz-2.4.13-8mdk: x86 boot sector ~~~ [root@guild brian]# grep "x86 boot" /usr/share/magic/magic 0x1FE leshort 0xAA55 x86 boot sector ~~~ [root@guild brian]# lilo -v -T EBDA LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof Development beyond version 21 Copyright (C) 1999-2001 John Coffman Released 24-Feb-2001 and compiled at 18:11:44 on Apr 8 2001. Extended BIOS Data Area (EBDA) = 1K Conventional Memory = 639K0x09FC00 The First stage loader boots at: 0x7C00 (07C0:) The Second stage loader runs at: 0x0009D600 (9D60:) The kernel cmdline is passed at: 0x0009FA00 (9000:FA00) ~~~ [root@guild brian]# ls -lF /boot/vmlinuz-2.4.13-8mdk -rw-r--r--1 root root 1073187 Nov 17 13:00 /boot/vmlinuz-2.4.13-8mdk ~~~ [root@guild brian]# lilo -v LILO version 21.7, Copyright (C) 1992-1998 Werner Almesberger Linux Real Mode Interface library Copyright (C) 1998 Josh Vanderhoof Development beyond version 21 Copyright (C) 1999-2001 John Coffman Released 24-Feb-2001 and compiled at 18:11:44 on Apr 8 2001. Reading boot sector from /dev/hda Merging with /boot/boot.b Mapping message file /boot/message-graphic Boot image: /boot/vmlinuz Added linux * Boot image: /boot/vmlinuz Added failsafe Boot image: /boot/vmlinuz-2.4.9 Added linux-2.4.9 Boot other: /dev/fd0, loader /boot/chain.b Pseudo partition start: 0 Added floppy Skipping /boot/vmlinuz-2.4.13-1mdk Boot image: /boot/vmlinuz-2.4.13-8mdk Added 2413-8 /boot/boot.0300 exists - no backup copy made. Writing boot sector. ~~~ Also, my most recent samba upgrade (to 2.2.2-?mdk) has been fraught with peril. I believe that the "network recycle bin" patch might be the cause of one problem I've noticed -- I have trouble deleting files on samba shares (about 95% of the files I attempted to delete, I could not. Windows told me that the file might be in use -- which is a different error message than a sharing violation, I believe). Also, Domain logons don't seem to work either (though I fear that's probably a generic samba bug, probably not limited to the cooker build). I can include my smb.conf and debug level 10 logs, if anyone thinks it'll help. -- Brian Cain
RE: [Cooker] HP OFFICEJET G95 G75 G85 etc
http://www.linuxprinting.org/show_printer.cgi?recnum=421970 -- that's the G95. I believe the G85 was also listed. HP does have an "apparent" commitment to Open Source Software/Linux... http://linux.hp.com/ -- Unfortunately, they aren't as loose w/drivers as they should be. -Brian -Original Message- From: steve ide [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 25, 2001 3:59 PM To: [EMAIL PROTECTED] Subject: [Cooker] HP OFFICEJET G95 G75 G85 etc Hi, Does anybody have any tech info on the above printers HP seems to be reluctant to give info :( they are good printers so why can't we have support from H.P. ??? It would be good to use the scan/fax under linux H.E.L.P Steve
[Cooker] proftpd package issues....
Greetings, I've had a spot of trouble installing a recent proftpd source package. I currently have a binary package installed (though I don't see why I couldn't upgrade to a newer source one). Attempts listed below: ~~~ [root@x /root]# rpm --upgrade -vh proftpd-1.2.4-1mdk.src.rpm proftpd ## [root@x /root]# rpm -qa | grep proftpd proftpd-1.2.2-2mdk [root@x /root]# rpm -ivvh proftpd-1.2.4-1mdk.src.rpm D: counting packages to install D: found 1 packages D: looking for packages to download D: retrieved 0 packages D: New Header signature D: Signature size: 149 D: Signature pad : 3 D: sigsize : 152 D: Header + Archive: 506915 D: expected size : 506915 D: found 1 source and 0 binary packages D: New Header signature D: Signature size: 149 D: Signature pad : 3 D: sigsize : 152 D: Header + Archive: 506915 D: expected size : 506915 D: installing a source package D: sources in: /usr/src/RPM/SOURCES D: spec file in: /usr/src/RPM/SPECS D:file: proftpd-1.2.2-conf.patch.bz2 action: unknown D:file: proftpd-1.2.2-ldap.patch.bz2 action: unknown D:file: proftpd-1.2.4.tar.bz2 action: unknown D:file: proftpd.init action: unknown D:file: proftpd.logrotate action: unknown D:file: proftpd.spec action: unknown D:file: proftpd.xinetd action: unknown proftpd #GZDIO: 63 reads, 508348 total bytes in 0.162 secs # [root@x /root]# rpm -qa | grep proftpd proftpd-1.2.2-2mdk Does this mean there's a problem with the package? I welcome pointers to appropriate documentation, or a more appropriate forum to ask this question if it doesn't belong here. -Brian
