Re: Corrupt data - RAID sata_sil 3114 chip
On Fri, 2 Jan 2009 22:30:07 +0100 Bernd Schubert b...@q-leap.de wrote: Hello Bengt, sil3114 is known to cause data corruption with some disks. News to me. There are a few people with lots of SI and other devices jammed into the same mainboard who had problems but that doesn't appear to be an SI problem as far as I can tell. There are some incompatibilities between certain silicon image chips and Nvidia chipsets needing BIOS workarounds according to the errata docs. Alan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [Re: Can't boot 2.4.17 or 2.5.1 kernel] problem solved ?!
more seriously, thanks to all the people making the ac kernel-variants. Just one more -silly?- question: it seems -for me at least- that some of the ac patches should be integrated in the kernel, why aren't they ? (I repeat that ANY 2.4.17 variant I compiled won't even boot ! I'm not talking about kernel panic here) Most of them are. In your case I really dont know what is in the older -ac that makes it boot on your box 8(
Re: new legacy Yamaha PCI module in 2.2.16 kernel won't link??
undefined reference is found with the error message below. The ymf_sb.c modules compiles fine and is loaded in the sound.a library. So why won't it link? drivers/sound/sound.a(sound_core.o): In function `soundcore_init': sound_core.o(.text+0x3e5): undefined reference to `init_ymf7xxsb_module' make: *** [vmlinux] Error 1 Oops. Thats a bug. Build it modular I'll squash that in .17
Re: 2.2.10-14 i686 SMP: IDE RAID-5 array hangs on mount
1. If you are lucky and have working RAID based on stock 2.2.x (for example RAID 0 :-) you should be able to upgrade to 2.2.14 without big hassle. So upgrade to RAID 0.90 in mainstream kernel posponed to 2.4 ... Thanks, I will do that as soon as possible. 2. RAID 0.90 need some changes in some important kernel structures and such changes will affect even users without RAID. RedHat 6.1 includes RAID patches anyway so I'm not sure if 2. still can be considered seriously. Cool, then maybe they'll be in 2.2.15? Too many people whined. If you use raid use the 0.90 patches. Unfortunately a pile of people don't want raid 0.90 in the standard kernel, which is silly. Alan
Re: 2.2.10-14 i686 SMP: IDE RAID-5 array hangs on mount
Ask Cox, not me :-) Since Cox is RedHat's employee it looks VERY weird to me that RedHat's kernel and official Cox's kernel are two such different beasts. 2.2.15 and the Red Hat kernel are two different things. They I suspect always will be. The things vendors want make it work now and the main tree needs make it work right are never going to totally overlap They should wait for Ingo to release RAID 0.90 patch for 2.2.15 I think :-) At least knfsd (not know about RAID) was sheduled for inclusion in 2.2.15 but now when 2.2.15 is quick bug-fix release (AGAIN!) it looks like KNFSD and RAID will be postponed once again :-/ I think all the important NFS stuff is already in 2.2.14. Alan
Re: module aliases
Periodically I get the following messages in my logfiles: modprobe: can't locate module sound-slot-1 modprobe: can't locate module sound-service-1-0 How can I tell for certain which modules I need to add an alias for, or if I should alias them off entirely? I'm running kernel version 2.2.11, sound-slot-%d is /dev/dsp%d and /dev/audio%d so if you have one sound card alias sound-slot-1 off Alan
Re: Desktop normalization
I hereby volunteer to be virtual Jon Postel and maintain such an archive, should it be considered useful. You need to grow the beard, otherwise yes I think this is a veyr good idea. It'll also encourage library vendors and people like the perl and python projects to provide reference naming schemes etc
Re: Desktop normalizationy
All that is needed other than that is a standard way to interface to add this to rootmenu/toolbar that can be used to update _all_ window manager data from fvwm to enlightenment as well as kde/gnome. That's what I mean. *All* of them. What users (I think) would love to see is to have particular layout of their menus, settings, etc. transferred as seamlessly as possible to another wm when they decide to give it a try. Well Gnome/KDE almost share format which is a good start. I need to document it and submit it I suppose
Re: Desktop normalization
An API to access either Gnome or KDE desktop strikes me as beyond the scope of the LSB. 1. How about *generic desktop API*. 2. If there is any reason for LSB, it is desktop. KDE is outside of any LSB work. Remember the main reason for the LSB is at least notionally commercial software. Secondly the LSB exists to standardise neccessary interfaces. For commercial X11 apps right now that means Motif/Xaw/Xlib. All that is needed other than that is a standard way to interface to add this to rootmenu/toolbar that can be used to update _all_ window manager data from fvwm to enlightenment as well as kde/gnome. It may become neccessary to spec gtk over time (given netscapes commitment to gtk)
Re: Future of Linux
Badlandz wrote: Alan Cox wrote: I think it is unwize at this point to make LSB conserned with X11R6 standards. Of course it should/could comply with what X11R6, but I libX11.so.* is Xlib is X11, as are the X packages. Other stuff like themed widget sets sit on X11 (ie another library that you can specify when it settles down) or replace X11 (in which case its another spec) Therefore I think LSB should focus on more basic issues like making FHS compliant, sysV vs BSD init standards, and libs. ISV's ship X11 apps, ISV's need to know X11 will just work. Compilers are also an issue I feel strongly about. I think gcc and egcs are awsome, but no match (yet) for commercial compilers. Funny, I think the reverse, so btw do Sega, 3com, cisco to name a few people ;) therefore if: Linux/hardware allowed Serial number on hardware, accessable in OS then: ISV's would LOVE to port to linux because there would be no piracy, and they would have a better/secure sales expectation. But for two things. 1. We already do support serial info on hardware that has it (eg sun) 2. Anyone with an hour can 'fix' their serial number on a sun to be what they like under Linux. The fact sun accidentally published their algorithm doesnt help too ;) So its tricky to spec. More productive vendors incorporate handy addons that poll the vendors site weekly when installed and mail the admin any upgrade info. In the meantime of course advertising who has which copy ;) Alan
Re: The Future of Linux: 'real' Locale support from X libs or no?
Glibc is good, but what about wide char, unicode etc.. etc.. etc.. ad biggum. Glibc does wide char, ncurses seems to imply it does (I've not checked yet). toward. Is there any interest in what we have thus far at Xi? Well I know the currnt KDE doesnt handle 16bit Glyphs, Im not sure about the Gtk toolkit on that. (hint to some: code pages work only for vts) Depends on your Xterminal and fonts ;) The kernel itself uses UTF8 for file names so you can reasonably keep a Klingon ext2fs if you wish.
Re: Future of Linux
steps in bridging linux compatibility. What, if any, is the consensus on the FHS 2.0... do the distributions that are part of the lsb agree to use it? It was discussed at and shortly after the LI meeting when Bruce presented the whole cunning plan. FHS 2.0 is a big help but it might need some tightening. Dan Quinlan is conveniently in both the LSB and FHS projects Second, I want to address libc. Will glibc be present on all upcoming linux distributions? I believe that moving to glibc is an important step in securing a posix conformant linux. Judging from the latest release of debian, however, I wonder if there is any progress on moving away from libc5... libc5 is dead, even its maintainers have proclaimed this. I've not seen any major pressure to spec libc5 at all, even if some vendors choose for now to ship libc5 based systems with glibc available. upcoming UDI drivers? Personally, I feel the UDI is one of the BIGGEST steps linux has taken to avoid being shut out of the latest hardware by Microsoft. The UDI will, most likely, end the FUD tactic of claiming that linux only works with OLD hardware. UDI is irrelevant. The existing UDI semantics cannot express the Linux resource management or driver layering. Its also out of the lsb standard area completely (indeed conceptually you could probably hack freebsd around and produce a LSB compliant freebsd) since we care about services at the glibc level. Alan
Re: Future of Linux
What else will the lsb cover? Or has there been a decision about that yet? The only other stuff covered at the meeting was X11. The good work XFree does is a big help there as their binary interfaces and the X specification API's are both stable. Motif has been raised as a question, as has OpenGL/MESA. ESR also raised the question of standardising things like Python. The suggestion for that was that the python people ought to define any such standard and then the lsb issue is purely one of namespace ie lsb-python-... shall be Python meeting he following criteria, with the following options etc. This is so that every app doesnt install their own version of python just in case. That could be extended to all interpreters and some libraries probably and a farmed out approach would IMHO be good. As to testing and stuff, all I've been watching is HJ Lu's patches and failure reports for the 2.1.12x kernel
Re: looking for a X-based Tcl/Tk FTP browser
I'm looking for an attractive X-based Tcl/Tk FTP browser that I could modify to use smbclient instead of ftp. Attractive and Tk. Strange pairing. TkDesk is probably the nearest. However you might be better of playing with midnight commander as this has both multiple output ends (gnome-gtk,tk,openlook,slang...) and virtualised file system layers (ftp, tar etc). So you can teach it smbfs files and it'll do the rest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0.34
I just upgraded a Debian 1.3 (bo) machine to 2.0.34, and when I do ifconfig eth0 203.14.18.1 netmask 203.14.18.128 broadcast 203.14.18.127 That isnt a valid netmask I think you mean 255.255.255.128 ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: what is the best pop3d?
The URL is ftp://ftp.cac.washington.edu/mail/imap.tar.Z Also in the /mail directory is a discussion of pop vs imap. It works fine, make sure you have the current one though, the older one asked the right way gives out root shells -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: How can I submit packages to be included in the distribution?
In article [EMAIL PROTECTED], Christoph Lameter [EMAIL PROTECTED] wrote: I know. Perhaps you can just publish the patches and have debian.rules do an automatic ftp from the gated site? The patches contain actual lines of gated code. So the advice on that appears to be be careful. However you shouldn't need any patches for the very latest gated Alan -- .-- UKUU free UUCP Project Swansea | Alan Cox, [EMAIL PROTECTED] +44 1792 422028 (Cabletel) | Custom Linux Software Projects. Sonix 33.6K 24x7 | Linux Consultancy. Linux Networking.
Re: Sicherheitsluecke bei rlogin auf Linux [LSF Update#11: Vulnerability of rlogin] (fwd)
In article [EMAIL PROTECTED], Stephen Masterman [EMAIL PROTECTED] wrote: Debian/GNU Linux systems may be vulnerable if NetKit-B-0.6 is installed. Until the official fix-kit is available for Debian/GNU Linux, system administrators of Debian systems are advised to follow guidelines under Other Linux Distributions section. Anyone have any more comments about this? There is no package called NetKit that I know of, I'm just curious if the developers have anything to say? The debian box I checked had all the netkit bugs in it, every last little one except for one - the telnetd environment bug. I've no idea what Debian has chosen to rename netkit as in its internal packaging system, but at minimum you want to replace o rlogin (TERM bug - present in all commercial systems I've tried so ask vendors for a fix too) o talkd (DNS spoofing flash bug, also spoof scribble) Note: the rlogin bug requires an account to exploit o rdist IF you are running it setuid (buffer overrun as seems traditional in older 4.x BSD derived code) Alan -- .-- UKUU free UUCP Project Swansea | Alan Cox, [EMAIL PROTECTED] +44 1792 422028 (Cabletel) | Custom Linux Software Projects. Sonix 33.6K 24x7 | Linux Consultancy. Linux Networking.
Re: Still Linux doesn't see my Ethercard
In article [EMAIL PROTECTED], Pedro I. Sanchez [EMAIL PROTECTED] wrote: to have Linux to recongnize my Ethernet card without success. I have a NIC with an AMD-PCNet chip. According to the Ethernet-HOWTO the right driver to use is lance. I managed to recompile the kernel to include this driver but still the driver doesn't see my card. Which PCnet chip variant do you know. 1.2.13 doesnt know all the current variants of this chip. I have no idea what to do next. The ethercard is ok (runs under windows) but I am missing something under linux. Any suggestions? The AMD PC-Net shouldnt be a problem because everything is on the chip so a vendor can't really do much to make it non standard. There have been some with hardware problems but clearly yours is ok as it runs under windows. Alan -- .-- UKUU free UUCP Project Swansea | Alan Cox, [EMAIL PROTECTED] +44 1792 422028 (Cabletel) | Custom Linux Software Projects. Sonix 28.8K [33.6 soon] 24x7 | Linux Consultancy.
