From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: couple linux(deb) questions
Date: Sun, 1 Apr 2007 15:38:56 -0600 [thread overview]
Message-ID: <002e01c774a6$27815910$6401a8c0@blanchew2fs98i> (raw)
In-Reply-To: <019701c7749b$2494c170$36c09792@mcgee>
Will do, thanks
----- Original Message -----
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, April 01, 2007 2:20 PM
Subject: Re: couple linux(deb) questions
> I hate it when people don't answer the question actually asked but based
on
> this question and the one you asked about finding duplicate files, I'm
going
> to guess you're trying to free up some disk space. Well, looking for
> orphaned libs is probably a waste of time. You'll never free up much space
> that way.
>
> You might be able to do something with the tools for finding orphaned
> packages. That would allow you to remove whole apps rather than just the
> libs they may use. But even that probably won't get you much.
>
> If you're running out of space, you should look in your home directories.
> Use the du command to see where most of it is going. ie:
>
> $ du -sh *
>
> I have a laptop with a 6 Gb drive and it is only 30% full. And I have
> apache, mysql, gcc, perl, and a bunch of other tools installed. I've
always
> just installed anything I wanted. Never had any problems with disk space.
> The only thing is I don't have X installed. But even so, your os just
> doesn't take up that much space. And the libs are only a small part of the
> os. I would forget about looking to free up space by removing libs. You're
> more likely to trash something important than you are to free up
> significant space.
>
>
>
> ----- Original Message -----
> From: "Littlefield, Tyler" <compgeek13@gmail.com>
> To: "Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
> Sent: Saturday, March 31, 2007 12:28 PM
> Subject: couple linux(deb) questions
>
>
> > Hello list,
> > I've got a couple questions.
> > First, is there a way to find out what libs are installed, but aren't
> > being depended on? I know I have extra packages, and don't want to keep
> > them if I don't meed them, e.g libraries mainly.
> > Second, is there a way to get all my manpages installed? I used to be
able
> > to do man cfunction, and I could see something, now I don't get
anything.
> > I believe I'm missing a package, just not sure which.
> > Thanks,
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Littlefield, Tyler
[not found] ` <20070331183134.GB3267@cm.nu>
` Littlefield, Tyler
` Gregory Nowak
` Littlefield, Tyler
` Gregory Nowak
` Littlefield, Tyler
` Adam Myrow
` Littlefield, Tyler
` Erik Heil
` Littlefield, Tyler
` Alex Snow
` Nick Gawronski
` Erik Heil
` John Heim
` Gregory Nowak
` OT: a speakup success story (Re: couple linux(deb) questions) John Heim
` Gregory Nowak
` John Heim
` C.M. Brannon
` Littlefield, Tyler [this message]
` couple linux(deb) questions Doug Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002e01c774a6$27815910$6401a8c0@blanchew2fs98i' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).