Re: kernel-{image,headers} package bloat
On Sun, Apr 22, 2001 at 12:13:57PM +1000, Herbert Xu wrote: > You're ignoring our main disagreement. Which is whether most people should > use precompiled kernel images or recompile them. > > If you took my position, which is that with initrd, there should be almost > no reason to compile a custom kernel image, then the conclusion is clear. Unless you care about performace. Which is the main reason to use different packages for each CPU type. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: kernel-{image,headers} package bloat
On Sun, Apr 22, 2001 at 12:09:12AM -0500, David Starner wrote: > On Sat, Apr 21, 2001 at 09:28:02PM -0500, Rahul Jain wrote: > > Unless you care about performace. Which is the main reason to use different > > packages for each CPU type. > > I compile my own kernels, and have for a long time. But it's a pain > to go through all the poorly-documented options and takes quite a > while to select those options and actually build a kernel. And then > there's the times I have to go back and recompile because I left out > my mouse drivers, or ide-scsi, or vfat. It's entirely rational to > want to pick up the 10% improvement from hitting the right button in > dselect and not worry about the 20% from recompiling the kernel. use the distro kernels' config as a starting point. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Digg Exchange!
Hi, My name is Rahul Jain, I Have recently created a site www.footzyrolls.com, i need ur reviews, ur feedback, about this site. Also I am requesting for dig exchange, if you have please send me your dig url, I will dig them, it will be beneficial for both of us, send me your dig url, will sure to dig them.. please digg it! http://digg.com/arts_culture/Footzyrolls_The_Rollable_Shoe_rollable_shoe Thank you.
Re: Packages not making it into testing
On Wed, Apr 25, 2001 at 10:33:46AM +0200, Petr Cech wrote: > > + xcdroast uploaded 152 days ago, out of date by 142 days! > > gtk/setgid problems, see 92230 etc > > that's new change in gtk 1.2.9 to disallow suid applications, which I find > silly Why does xcdroast need to be setgid? I think it's terrible to have any user able to burn or screw up a burn... why can't they use sudo or su? -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Packages not making it into testing
On Wed, Apr 25, 2001 at 11:57:50PM +1000, Hamish Moffatt wrote: > Doesn't the user have to belong to the relevant group anyway? > We already control access to things like floppy drives, sound > cards etc through groups, so cd burning is another good example. -rwxr-sr-x1 root cdrom 498300 Nov 23 04:37 /usr/bin/xcdrgtk* The user does not need to be in group cdrom to use it. This _gives_ any user access to the raw device. > Why not su/sudo? Well, that would let the user access files they > can't normally read. Eg burn other users' home directories on > to a CD. Also, X authority stuff is messy to transfer between > users. I don't see how sgid cdrom will help here. Just make it non-sgid, and if they're a member of group cdrom, they can burn a cd, period. X authority is easy, just su, don't su -. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Referring what kernel-images to build to the technical committee?
On Thu, Apr 26, 2001 at 04:59:13PM +0200, Russell Coker wrote: > If programs won't run at all (as in the case of MMX and 3DNow!) > then we should compile different kernels. If they just don't run as fast > then we can let the users compile their own kernels. I don't understand why MMX or 3dnow apps can't be used if the kernel isn't compiled to support them. Only the K7 configuration adds 3dnow support, but 3dnow in mpg123 works (or at least seems to) on my k6-3 with k6 chosen for the cpu type in the kernel config. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Problem with installing Postgres throught APT
On Thu, Apr 26, 2001 at 02:03:00PM +0100, Oliver Elphick wrote: > It hasn't stopped its being installed on my system or on a number of others. > I found the conflict was necessary to force the removal of libpgsql2, but > it does indeed provide libpgsql2 to other packages that depend on that. > > I feel there must be some other problem with your system. I had a horrible time upgrading and I ended up removing some packages with --force-depend, and then apt-get dist-upgrading. Would adding a replaces: to some packages help? I know that the pgsql-pl and ecpg packages were merged, so at least it will help there. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Storage (8*IDE HDs) any experiences?
On Thu, Apr 26, 2001 at 01:39:01PM -0500, Dimitri Maziuk wrote: > Hi all > > I notice there are these new-fangled motherboards with 2*ATA-100 and > 2*ATA-33 ports. With 75GB disks, that baby should give us 600GB of raw > disk space (8 drives) at around $2K US. Sounds attractive, considering > that el-cheapo RAID boxes of similar capacity are around $10K. > > Anyone runs [Debian] Linux on an 8-drive box like that? Is that > supported at all? Any gotchas I should know about? The mobo I'm looking > at is ABIT BH6-II. Be warned of the issues with having two hard drives per IDE channel. I know that there were reports of massive corruption when using DMA with specific models of WDC and Maxtor drives on the same channel in DMA mode. You'll also face some pretty serious performance slowdowns when accessing both drives at the same time, since most IDE drives cannot do disconnect/reconnect like SCSI drives can. The best way would be to have one IRQ used for each IDE drive, which is pretty tough to do on an x86 system. Hopefully your BIOS can allow this sort of setup, since IRQ sharing still causes a bit of a performance hit. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Storage (8*IDE HDs) any experiences?
On Thu, Apr 26, 2001 at 09:33:19PM -0700, Brandon High wrote: > On Thu, Apr 26, 2001 at 09:42:16PM -0400, [EMAIL PROTECTED] wrote: > > IDE causes a bit of a performance hit, I don't think we're talking high > > speed file access here though... cheap is the objective. > > You'd be suprised at the performance hit. I had 2 drives/channel and > suffered from really bad performance with the on-board Ultra66 controller. I > installed a PCI controller (Promise Ultra 66) and put every drive on its own > channel. Things are much happier now and about 3x faster. The best part is > that the card only costs about $25. Yep, but the problem there is figuring out how to get each channel on a unique IRQ. With some BIOSes, it's just not possible. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Storage (8*IDE HDs) any experiences?
On Fri, Apr 27, 2001 at 12:48:52PM +0200, Russell Coker wrote: > See http://www.coker.com.au/~russell/hardware/46g.png for some quick > benchmark results showing the differences between a single IDE drive, two > drives on separate channels, and two drives on the same channel. > > Apart from one drive being exceedingly slow at the start (for reasons I have > not yet determined) it seems that two drives on the same channel isn't much > slower than two drives on separate channels. > > Having two drives on separate channels is slower than a single drive can run > on it's own, I think that this is a limitation of CPU and bus performance > (which will be the main factor when you have 8 drives in an array). Are you sure they two channels are not sharing an IRQ? -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Are build-dependancies mandatory?
On Sun, Apr 29, 2001 at 01:30:44AM -0600, Bdale Garbee wrote: > I'd be tempted to agree with you, except... > > I've spent quite a bit of time recently dealing with packages that include an > explicit build dependency on "libstdc++2.10-dev". This is not necessary since > it is a dependency for an item in build-essential, and is in fact called out > explicitly in the build-essential documentation. It breaks the ability to > build the package with gcc-3.0. That will matter to everyone eventually, and > matters to hppa and ia64 right now. maybe there should be meta-packages for packages that have embedded version numbers like that. Or maybe the build-dep on libstdc++2.10-dev indicates that the package relies on some g++ brokenness ;) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Gnome bug 94684Subject: Re: Gnome bug 94684
On Sun, Apr 29, 2001 at 03:39:42PM +0800, zhaoway wrote: > > Bureaucracy is integral to an organization such as Debian. > > I beg to disagree. :) Maybe we need a subcommitte to determine the validity of that statement ;) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: debbugs can now send bug mails to someone different than the maintainer
On Mon, Apr 30, 2001 at 09:06:01PM -0400, Matt Zimmerman wrote: > The client side of fetchmail will (by default) feed each message into your > local MTA for delivery, but you'll have to figure a way to get the mail into > it > from the remote mailbox without IMAP or POP services (which I don't think > master provides). I think someone was working on ETRN recently, which is also > supported by fetchmail... hrm... having fetchmail ssh in and grab the mail directly from the spool would be kind of cool... :) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: SGI's xfs
On Thu, May 03, 2001 at 11:03:09AM -0500, Nathan Scott wrote: > > In addition to Ed's kernel debs and the XFS userspace - ie. > xfsprogs, xfsdump, attr packages - you'll also want a recent > mount package (supports mount by-UUID and mount-by-label for > XFS, documents the XFS mount options, no need to use "-t xfs" > with mount, etc); and also the latest quota package which > supports XFS's notion of journaled quota - which Michael has > just uploaded to unstable in the last few days. And, as another note, the ACLs in XFS need support from the SGI acl package, which I don't believe has been put into unstable by Nathan yet. However, the source from SGI is debianized, so building debs should be quite simple. -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: SGI's xfs
On Thu, May 03, 2001 at 09:28:14AM +0200, Radovan Garabik wrote: > On May 2, 11:22am, Ed Boraas wrote: > > Subject: Re: SGI's xfs > > > Previously Matthias Berse wrote: > > > > Are there any plans in supporting the usage of SGI's xfs filesystem in > > > > debian? Are there kernel patches available and/or userspace tools > > > > being packaged? > > > > > > The userspace tools have been in unstable for a while already actually. > > > > And the kernel patches are in incoming. > > > > and how do you solve the requirement to use gcc version 2.91.66 > for compiling? the gcc 2.95 in unstable works great. it's gcc 2.96 that's the real problematic compiler. (of course) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: Bug#95430 acknowledged by developer (Re: Bug#95430: ash: word-splitting changes break shell scripts)
On Thu, May 03, 2001 at 02:30:28PM -0500, Raja R Harinath wrote:
>
> Maybe you want
>
> sh -c 'echo "x-${IFS}-x"'
>
> Both Solaris 2.6 /bin/sh and Linux bash seem to have IFS set.
>
> $ /bin/sh -c 'echo "x-${IFS}-x"'
> x-
> -x
>
Identical behavior with zsh from unstable here.
--
-> -/- - Rahul Jain - -\- <-
-> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <-
-> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <-
|--||--||-|--|-|-|-|
Version 11.423.999.220020101.23.50110101.042
(c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: debian.org
On Sun, May 06, 2001 at 11:42:28AM +0200, [EMAIL PROTECTED] wrote: > > Hello, > > I hope you can help me. > > May I ask if your company/organization put MS Word files on your CD's? > > > > We are the sole distributors of icWord, which is the Microsoft?? word viewer > for the Mac. Our SW allows Mac users to view, copy and print Word documents > without having to purchase or use Microsoft Word. > > icWord?? viewer is also designed for CD distribution purposes. > > > > Do you think you could find interest in such a viewer? > > If you have any questions please feel free to contact me. > > Your opinion will be appreciated. > How interesting. I wonder what drugs posessed them to think we'd be interested in this... :) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: RaiserFS PPC status
On Mon, May 07, 2001 at 12:03:43AM +0200, Just a friendly Jedi Knight wrote: > You mean XFS from Linus kernel tree? there are some patches on > penguinppc.org This is not in Linus's kernel tree. Are you using SGI's 1.0 release? In any case, that should not affect the compilation of the tools much. > Anyway i have trouble compiling mkfs.xfs I tried: > gcc version 2.95.4 20010319 (Debian prerelease) > gcc version 3.0 20010402 (Debian prerelease) and xfsprogs 1.2.4 Debian > source package as well as source taken from penguinppc.org. I always get > this: you should stick to gcc 2.95 for compiling the kernel, and probably the userspace tools, too. > gcc -O1 -g -DNDEBUG -funsigned-char -Wall -I../include '-DVERSION="1.2.4"' > -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DXFS_BIG_FILES=1 > -DXFS_BIG_FILESYSTEMS=1 -o xfs_db -L../libxfs addr.o agf.o agfl.o agi.o > attr.o attrshort.o bit.o block.o bmap.o bmapbt.o bmroot.o bnobt.o check.o > cntbt.o command.o convert.o data.o dbread.o debug.o dir.o dir2.o dir2sf.o > dirshort.o dquot.o echo.o faddr.o field.o flist.o fprint.o frag.o freesp.o > hash.o help.o init.o inobt.o inode.o input.o io.o malloc.o mount.o output.o > print.o quit.o sb.o uuid.o sig.o strvec.o type.o write.o main.o -lxfs > /usr/lib/libuuid.a > ../libxfs/libxfs.a(xfs_inode.o): In function `libxfs_xlate_dinode_core': > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:563: undefined > reference to `__fswab64' > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:563: relocation > truncated to fit: R_PPC_REL24 __fswab64 > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:563: undefined > reference to `__fswab64' > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:563: relocation > truncated to fit: R_PPC_REL24 __fswab64 > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:564: undefined > reference to `__fswab64' > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:564: relocation > truncated to fit: R_PPC_REL24 __fswab64 > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:564: undefined > reference to `__fswab64' > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_inode.c:564: relocation > truncated to fit: R_PPC_REL24 __fswab64 > ../libxfs/libxfs.a(xfs_mount.o): In function `libxfs_xlate_sb': > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_mount.c:205: undefined > reference to `__fswab64' > /opt/src/robert/XFS/xfsprogs-1.2.4/libxfs/xfs_mount.c:205: relocation > truncated to fit: R_PPC_REL24 __fswab64 > collect2: ld returned 1 exit status > make[2]: *** [xfs_db] Error 1 > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/opt/src/robert/XFS/xfsprogs-1.2.4' > make: *** [built] Error 2 grepping my xfsprogs tree, I get: ./include/libxfs.h:extern __inline__ __const__ __u64 __fswab64 (__u64 x); maybe your GCC isn't inlining the function? note that this declaration has "/* ick */" on the line above it. But I think the relocation truncated to fit: R_PPC_REL24 __fswab64 messages are important. I'll leave it to someone more knowledgable about GCC and ELF to comment on that. > These are the only errors I get... This must be some bug in gcc on powerpc as > it compiles cleanly on i386 (and from looking on ftp.debian.org on other > platforms also). I don't even have idea how to bite this... I'm only on x86 here, so all I can say is "yeah" :) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: RaiserFS PPC status
On Mon, May 07, 2001 at 12:00:34PM +0200, Just a friendly Jedi Knight wrote: > On Sun, May 06, 2001 at 09:58:02PM -0500, Rahul Jain wrote: > > On Mon, May 07, 2001 at 12:03:43AM +0200, Just a friendly Jedi Knight wrote: ... > > you should stick to gcc 2.95 for compiling the kernel, and probably the > > userspace tools, too. > Most probably you are right.. I used gcc-3.0 because i heard that it > compiles reiserfs code (big endian) correctly. So far i have no problems > with kernel built with gcc-3.0 I don't really know of anyone who's using a gcc-3.0-compiled XFS kernel. You might want to check on the mailing list as to how well it does with XFS. ... > If it's not clear it's libxfs.a (which is in the same source tree) that > causes problems.. There is no error while compiling sources of libxfs > itself. Only when ld tries to link with that (freshly built) library > > > > > maybe your GCC isn't inlining the function? > most probably this is the case.. I thought it's matter of optimization but i > get the same even if i turn off optimization (-O0) You need MORE optimization to enable inlining. Inlining reduces debuggability and increases executable size for the benefit of not having to set up a whole new stack frame and possibly being able to optimize the function in the special context of where it's called from. Maybe -O2 will fix it? > > note that this declaration has "/* ick */" on the line above it. But I think > > the relocation truncated to fit: R_PPC_REL24 __fswab64 messages are > > important. > > From what i gather it just can't find code for __fswab64 "function". I have no idea how an extern inline function should be compiled, so I can't really say what gcc should be doing here... -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
Re: [users] Re: Where's lame
On Mon, May 07, 2001 at 10:29:17PM +0200, Joost Kooij wrote: > On Mon, May 07, 2001 at 03:22:33PM -0400, MaD dUCK wrote: > > package tree. i would like to adopt the lame mp3 encoder as a debian > > package and was wondering if there are any objections? is there > > already a maintainer? can this packet be debianized? > > Alas, you hit on a faq. > > Please look at: > http://www.debian.org/devel/wnpp/unable-to-package > > > The most recent iteration of the lame discussion can be found at: > http://bugs.debian.org/90091 > > Maybe looking on the web for "unofficial apt sources" will help you > find some .debs (or should I say ".debz"? ;-) the offical lame sources (latest beta) include a debian/ directory, so building a deb is as easy as debian/rules binary (after you get the build-deps :) -- -> -/- - Rahul Jain - -\- <- -> -\- http://linux.rice.edu/~rahul -=- mailto:[EMAIL PROTECTED] -/- <- -> -/- "I never could get the hang of Thursdays." - HHGTTG by DNA -\- <- |--||--||-|--|-|-|-| Version 11.423.999.220020101.23.50110101.042 (c)1996-2000, All rights reserved. Disclaimer available upon request.
