On Thu, Feb 15, 2007 at 10:47:37PM -0500, Celejar wrote: > On Wed, 14 Feb 2007 19:02:31 -0600 > Default User <[EMAIL PROTECTED]> wrote: > > [snip] > > > Doing "sudo du -BKB /lib64" does indeed show 2793kB in /libc64. Yikes! > > > > Doing "sudo dpkg -l libc64*" returns: "No packages found matching > > libc64*." Since "sudo dpkg -l" returns a list of several hundred (at > > least) packages, I am guessing that the libc64* qualifier would list > > "64-bit" programs actually available to the system (and not just having > > files present on a hard drive). Or something like that. > > > > I was absolutely stunned to learn that 64-bit code is made available to > > a 32-bit system, even if it's not used. I'm too old for all this > > learning . . . > > Speaking of learning, you shouldn't be running 'du' and 'dpkg -l' with > sudo; they'll run just fine as a normal user.
Won't they have a hard time with directories and files that are not readable by the normal user? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
