Re: [gentoo-user] Potential Supid question re Grep
On Thu, Jul 07, 2005 at 07:18:26PM +0100, Michael Thompson wrote: > I am trying to extract information in my logs for a abuse department and am > using the code: > > Code: > > zcat /var/log/messages.*?.gz | grep 212.56.68.108 >> /home/mike/abuse1 > > The logs are standard: messages.??.gz > > However, when I examine the output, it starts on the 1st may, however the > logs > contain details from the 25th Febuary. What am I doing wrong? This isn't the cause of your problem (which has probably been solved by some of the other posts), but don't forget that grep matches regexps, not strings, and "." in a regexp matches any single character. Therefore your code will match "212a56b68c108" (for example), as well as the ip you probably intended to match. To make sure you only match the ip, you'll need to escape the .s and surround the regexp by quotes: grep '212\.56\.68\.108' I'm probably telling you things you already know ;-) And it probably won't matter much anyway, but I thought I'd mention it in case it helps someone. Toby -- Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kde-3.4.0/3.4.1 mess
On Sat, Jul 09, 2005 at 02:41:11PM -0700, Robert Persson wrote: > A couple of weeks ago I added all the kde-3.4.1 packages to package.keywords > and then ran emerge -u world and everything updated and ran fine. > > Today I tried to emerge -u world and I got > > [blocks B ] =kde-base/kdeartwork-icewm-themes-3.4* (is blocking > kde-base/kdeartwork-3.4.1) > ... blah blah blah ... > [blocks B ] =kde-base/renamedlg-images-3.4* (is blocking > kde-base/kdeaddons-3.4.1) > > for about 150 kde packages altogether. > > equery tells me that I have version 3.4.1 of each individual kde package > installed, but that I have version 3.4.0 of kde itself and that I don't have > kdeartwork, kdeaddons, kdebase etc. installed. > > How did I get in this mess and how (without recompiling all of kde) do I get > out of it? I had a similar problem with upgrading when 3.4 was unmasked. The problem is moving from the old monolithic ebuilds to the new split ones. I believe it's because you are trying to install both split and unsplit ebuilds that provide some of the same programs. My solution to sort out the mess was to unmerge all the monolithic kde ebuilds, and then emerge the stuff I wanted (kdebase-startkde is the split ebuild that provides the basic stuff like the window manager, though even that isn't necessary if you only want to run some kde apps and not the full kaboodle). It sounds like you might already have the new split ebuilds installed, so you might just need to remove the monolithic ones from your world file, or possibly unmerge them if they're still around. Of course, that assumes you want to use the split ebuilds. If you haven't read it already, the How-To at http://gentoo-wiki.com/HOWTO_Update_KDE_3.3_to_KDE_3.4 is helpful. A bit of research with the online package database to work out which ebuilds are the split ones, which the monolithic ones, and which ones you actually want should sort you out. Toby Cubitt -- Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
[gentoo-user] Autoloading scsi scanner kernel modules
I have an old HP scanner that works fine with one of the drivers included in the kernel. I compiled the driver as a module since I don't use the scanner all that often. However, this means the scanner doesn't work unless it's switched on before booting. Up till now, I've just su-ed to root, and removed and reinserted the appropriate module using modprobe. (I'm not sure if I could have just echoed the right thing to /proc/scsi/scsi, but modprobe certainly does the job). This is an ugly hack though, since anyone who wants to use the scanner either has to have the root password or has to reboot. So I tried getting it to insert the modules and scsi device as needed, by adding the following lines to /etc/modules.conf: pre-install sg modprobe sym53c416 alias char-major-21 sg post-install sg echo "scsi add-single-device 0 0 2 0" > /proc/scsi/scsi This didn't achieve much until I added a /dev/scanner symlink to the appropriate device under /dev/scsi/ (I'm still using devfs). With the symlink in place, it almost works. If I manually unload the scanner modules (actually, unloading the sg module is sufficient), then switch on the scanner and try scanning from a normal user account, the modules are inserted automatically and everything works. Unfortunately, this only works if I first unload the modules. For some inexplicable reason, the scanner driver and the sg modules are loaded at boot, even though they're *not* listed in /etc/modules.autoload.d/. And I guess with the modules already loaded, the sg module doesn't get loaded again when /dev/scanner is accessed, so the pre-install and post-install commands never get executed. Am I making a mess here, is there a better way to do what I want, or am I missing something simple? The SANE web site got me this far, but I can't find anything on the web, forums or lists to get me the last step. (For starters, I'd like to know why the scanner modules are loaded at boot. Is there any way to find out what's causing them to be loaded?) Thanks for any help, Toby Cubitt -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Wireless Network adapetors?
On Sat, Apr 23, 2005 at 06:05:56PM +1000, Devraj Mukherjee wrote: > I am looking to switch to wireless networking and am unsure of which > cards are well supported under Linux? I am looking for PCI styled cards > and preferably ones that can do 54Mbps. > > Any experiences, suggestions? I recently successfully set up my gentoo box as a wireless access point using a D-link DWL-G520, which is based on the Atheros chipset so is supported by the madwifi driver (in portage). It does 54Mbps, and setting it up was hassle-free for me. Atheros-based cards are probably your safest bet nowadays, since newer Prism-based cards aren't supported by the linux Prism driver. After the Prism driver, the madwifi driver is probably the most mature, at least from what I've read. The only thing I haven't got working with it yet is WPA encryption. Apparently it is possible, just not well documented at the moment. WEP is working fine though. (If anyone has any tips on how to get WPA working, I'd love to hear them!) HTH, Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Wireless Network adapetors?
On Mon, Apr 25, 2005 at 04:20:51PM +0100, Ognjen Bezanov wrote: > Toby Cubitt wrote: > > >I recently successfully set up my gentoo box as a wireless access point using > >a D-link DWL-G520, which is based on the Atheros chipset so is supported by > >the madwifi driver (in portage). It does 54Mbps, and setting it up was > >hassle-free for me. > > > Wait a min, I thought that Prism-based cards are the only ones which are > capable of working as Access points, how did you manage this? I guess luckily no one told me that! As far as I understand it, the only thing you need in order to use a card as an access point is to be able to set it to "master" mode. The madwifi and Prism drivers both support this. I've no idea how new support for master mode is in the madwifi driver, so maybe what you said was true until recently. But it definitely works now. > >The only thing I haven't got working with it yet is WPA encryption. > >Apparently > >it is possible, just not well documented at the moment. WEP is working fine > >though. (If anyone has any tips on how to get WPA working, I'd love to hear > >them!) > > > Sorry cannot help, but am interested in this, because its getting harder > for me to find new cards with the older prism chipsets to use as access > points. Yup. That's exactly why I ended up buying an Atheros based card. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 12:12:25PM +0200, Mick wrote: > Hi All, > > I just compiled kernel-2.6.16-gentoo-r3 and it now causes an iptables > error when the machine boots. Any ideas how I can fix it? The kernel iptables implementation changed somewhat between 2.6.15 and 2.6.16. In particular, "make oldconfig" won't set things up correctly. You'll need to run "make menuconfig", and check the iptables section. Note that you *will* need to compile in Xtables support as well as iptables (Networking -> Networking Options -> Network Packet Filtering -> Core Netfilter Configuration -> Netfilter Xtables support). If you use genkernel, I can't help you, since I don't. > Here is some supporting information. > > Boot error looks like this: > = > # /etc/init.d/iptables restart > * Loading iptables state and starting firewall ... > iptables-restore v1.3.4: iptables-restore: unable to initializetable 'nat' This is because your new kernel doesn't have NAT compiled in. It probably doesn't have any iptables support at all at the moment. HTH, Toby Cubitt -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 01:15:29PM +0200, Alexander Skwar wrote: > Toby Cubitt wrote: > > > >The kernel iptables implementation changed somewhat between 2.6.15 and > >2.6.16. In particular, "make oldconfig" won't set things up > >correctly. > > What do you mean with that? I set up my 2.6.16 kernels with make oldconfig, > using the 2.6.15 configs. > > What's broken now? I'm curious, as I didn't notice any breakage - which > might just mean, that I haven't looked closely enough. Because of that, > I'd like to know what to look out for. Nothing will break as such. But some things you might expect to be compiled in won't be, like iptables. This is always a risk when using "make oldconfig", and it's why the docs advise you to avoid using it between major kernel version bumps (2.4 to 2.6). In practice, I find it useful even in that case, so long as you then "make menuconfig" to check through the options, and add missing ones. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 02:34:49PM +0200, Mick wrote: > On 01/05/06, Rumen Yotov <[EMAIL PROTECTED]> wrote: > >Graham Murray wrote: > >> Mick <[EMAIL PROTECTED]> writes: > >>> > >>> I just compiled kernel-2.6.16-gentoo-r3 and it now causes an iptables > >>> error when the machine boots. Any ideas how I can fix it? > >> > >> Kernel 2.6.16 made some major changes to the netfilter code. > > Also, is my (basic-but-functional) fw script now obsolete? Does it > need to be changed - how would you make it compatible with the new > netfilter nomenclature? I don't think much changed in the iptables command, so your script should still work fine once you compile the right options into the kernel. Mine certainly did. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 03:16:36PM +0200, Mick wrote: > On 01/05/06, Toby Cubitt <[EMAIL PROTECTED]> wrote: > >On Mon, May 01, 2006 at 02:34:49PM +0200, Mick wrote: > > >> Also, is my (basic-but-functional) fw script now obsolete? Does it > >> need to be changed - how would you make it compatible with the new > >> netfilter nomenclature? > > > >I don't think much changed in the iptables command, so your script > >should still work fine once you compile the right options into the > >kernel. Mine certainly did. > > Thanks Toby, but I can't find which option I have missed out. That's > why I posted the link to my kernel config, in case someone can spot > it. Ah. Didn't realise from your mail that the script didn't work. Without the error messages it produces, it's mighty difficult to tell... But it's almost certainly a kernel-config issue, since until recently I used the same script (derived from Daniel Robbins' IBM developer works article, right?). Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 04:21:42PM +0200, Mick wrote: > On 01/05/06, Toby Cubitt <[EMAIL PROTECTED]> wrote: > >On Mon, May 01, 2006 at 03:16:36PM +0200, Mick wrote: > > > >Ah. Didn't realise from your mail that the script didn't work. Without > >the error messages it produces, it's mighty difficult to tell... > > > >But it's almost certainly a kernel-config issue, since until recently > >I used the same script (derived from Daniel Robbins' IBM developer > >works article, right?). > > That's right. The script is basically the DR script minus NATing. > The error message that I see at boot up is as originally posted, here > it is again: Okay, I've finally caught up with you ;-) I was confused because the error below is from the gentoo iptables init script, not from your script. > == > # /etc/init.d/iptables restart > * Loading iptables state and starting firewall ... > iptables-restore v1.3.4: iptables-restore: unable to initializetable 'nat' > > Error occurred at line: 8 > Try `iptables-restore -h' or 'iptables-restore --help' for more > information.[ !! ] > == It looks like it's trying to define NAT rules, even though you don't use NAT. Maybe the old rules saved by gentoo's iptables init script included some NAT rules? Does running "/etc/init.d/iptables stop", then running your script, then running "/etc/init.d/iptables save", then "/etc/init.d/iptables start" help at all? Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 05:55:08PM +0200, Mick wrote: > On 01/05/06, Toby Cubitt <[EMAIL PROTECTED]> wrote: [snip] > >Does running "/etc/init.d/iptables stop", then running your script, > >then running "/etc/init.d/iptables save", then > >"/etc/init.d/iptables start" help at all? > > Let's see: > > # /etc/init.d/iptables stop > * ERROR: "iptables" has not yet been started. > # ./fw_script.sh start > Starting firewall... > # /etc/init.d/iptables save > * Saving iptables state ... > # /etc/init.d/iptables start > * Loading iptables state and starting firewall ... > > > No problem. Rebooting thereafter comes up *without* the error. So > the error is caused by the state in which the iptables are saved using > the ./fw_script stop command. Something's amiss with the script then, > given the latest kernel chages. Bingo! Your fw_script.sh contains (line 72): iptables -t nat -F POSTROUTING which fails because you haven't compiled NAT into your kernel. Comment it out and hopefully your script will work. You probably know this already, but once you've set up your rules (using your script), and gentoo's init script has saved them, there's no need to run your script again. The rules will be reloaded from the saved file by the init script whenever it's restarted. However, the init script also saves the rules when it's stopped, e.g. on reboot, overwriting previously saved rules. It's easy while setting things up to accidentally save the wrong rule set. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Change in kernel netfilter config causes an error
On Mon, May 01, 2006 at 09:10:29PM +0200, Mick wrote: > On 01/05/06, Toby Cubitt <[EMAIL PROTECTED]> wrote: > > >Bingo! Your fw_script.sh contains (line 72): > > > >iptables -t nat -F POSTROUTING > > > >which fails because you haven't compiled NAT into your kernel. Comment > >it out and hopefully your script will work. > > Thanks again Toby. I thought that amidst the many modules I had > compiled NAT (or whatever name it may now have) in the kernel. It > seems that I hadn't. tut, tut! I saw you hadn't compiled NAT in your kernel config posting, and almost posted that as to problem, but then I figured you didn't *want* to compile it in so it wasn't a good solution. > OK, I've recompiled the kernel and added nat to it. Now it works as it > should. Do you want NAT? It sounded like you didn't want to use it anyway. Why not just comment out that line in the script and leave NAT out of the kernel? > Thank you All for your responses. :-) Anyway, glad it works now. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: modprobe looks in wrong dir
On Mon, May 01, 2006 at 10:15:36PM +0200, Francesco Talamona wrote: > On Monday 01 May 2006 22:05, maxim wexler wrote: > > make menuconfig, then make && make modules_install > > You missed a step: > make && make modules && make modules_install Actually, he didn't. The 2.6 series kernels don't require the "make modules" step. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] [OT] use shfs
On Fri, May 12, 2006 at 06:57:11PM +0200, Marco Calviani wrote: > Hi list, > i have a question regarding shfs. I'm use to connect a remote > computer (let's call it C) from a linux machine (A) via ssh passing > through a *nix gateway (B). I would like to be able to transfer data > from C to A as easy as possible. Since B works only as a gateway i'm > not able to save anything into it. Is there a way to use shfs (or > similar) in order to reach this objective? I can't test the shfs part - I tried shfs out a while back, liked it, but got rid of it since I never really seemed to use it. But the ssh part is easy: just use port forwarding (assuming you have ssh access to B; if not, you're out of luck). Using your example, you'll need to do something like: ssh -L8022:C:22 B Port 8022 on your local machine A is now a tunnel to port 22 (the ssh port) on C. You should be able to mount directories from C on A, by pointing shfs at port 8022 on A. Something like: shfsmount -P 8022 A:/remotedir /mnt/mountpoint This all assumes your user name is the same on all machines. If not, just specify the appropriate user name before the host names. E.g. shfsmount -P 8022 [EMAIL PROTECTED]:/remotedir /mnt/mountpoint where "user" is your user name on machine C, *not* A, because you're in fact tunnelling to C with this command. HTH, Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Launching X.org through ssh
On Thu, May 25, 2006 at 08:09:38PM +0200, Rafael Fern?ndez L?pez wrote:
> Hi,
>
> I'm connecting from a computer (remote computer) to a server (sshd, it is
> running apache2 too, but it doesn't matter right now), and I can connect
> through ssh to it, and run every command all right, but launching X.org.
>
> If I try a "startx" command, it will start X.org in the local computer,
> and I'd like to run it into the remote computer, as you would do with RDP
> for example.
That won't work. When you run an X program ("client") on the remote
box, it connects to your local X server so you see the remotely
running client on your local display. But the X server itself is, as
the name suggests, a server for X, not a client.
You should look into VNC (there are a number of versions in portage),
or maybe freeNX. In my experience, freeNX gives better performance,
but VNC is easier to set up, especially if you connect via ssh (as you
should). FreeNX is usually used to forward single applications, not
whole desktops, but recent versions can also forward whole
desktops. (It can even connect to VNC sessions.)
HTH,
Toby
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: [EMAIL PROTECTED]
web: www.dr-qubit.org
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc-4.1.1
On Thu, Jun 08, 2006 at 07:00:22AM -0700, Bob Young wrote: > > > > From: Hans-Werner Hilse [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 08, 2006 6:32 AM > > To: gentoo-user@lists.gentoo.org > > Subject: Re: [gentoo-user] gcc-4.1.1 > > > > Try to understand what you are replying to. GCC's internal build logic > > does the staging. That's got nothing to do with what your system calls > > when you issue "gcc", and only at that point the slotting of GCC > > versions comes into play. > > > Show me some documentation for this "staging" you refer to. He did! In the INSTALL/build.html file in the gcc sources. > When you "emerge gcc" it is built with the current compiler, if the > current compiler is gcc 3.4.6, and you emerge gcc 4.1.1, that means > that while gcc 4.1.1 is being emerged it is built with gcc > 3.4.6. gcc 4.1.1 can't be built with 4.1.1 because it hasn't been > emerged yet, and as far as the system knows it doesn't actually > exist yet. Yes. The *first* time that gcc 4.1.1 is built. But then the gcc build process builds it a *second* time, using the gcc 4.1.1 it's just built. And for good measure, it goes on to build it a *third* time with the second version it produced. This is all done by the gcc build process (it's in the Makefile), which is what emerge runs. > Can you clearly and concisely explain to me how something that is in > the process of being emerged can be used to emerge itself? Doesn't > make sense. You're obviously right that you have to *compile* a new gcc at least twice. But this is done automatically by the gcc build process, so there's no need to build (or emerge) gcc twice. This has nothing to do with gentoo. Downloading the gcc sources manually and running ./configure, make, make install (or whatever the exact gcc build process is) would work too: you'd only need to do it once. Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Xorg-x11 problems
On Fri, Aug 04, 2006 at 12:43:26AM +0300, Mantas Povilaitis wrote: > On 8/3/06, Pete Pardoe <[EMAIL PROTECTED]> wrote: > > > ><=x11-base/xorg-x11-6.9 (is blocking > > > >I have tried emerge --clean x11-base/xorg-x11-6.9 and emerge --prune > >x11-base/xorg-x11-6.9 and they both tell me that the package is not there. > > it is written <= before package name, so 6.8 counts too (6.8<6.9) Your problem is that the modular xorg is now in the stable tree, so portage is trying to upgrade to the modular xorg when you do an emerge world (if you look further down the list of packages that emerge world is trying to install, you should see xorg-x11-7.0). The dependencies pulled in by modular xorg have to be installed before xorg-x11 itself can be upgraded, but they are blocked by your currently installed, non-modular xorg-x11-6.8. There are two solutions: unmerge the non-modular xorg-x11-6.8, and then merge the modular xorg-x11-7.0 (following the migration guide on www.gentoo.org). But you seem to have already tried this. The second solution is mask modular xorg by adding the line >x11-base/xorg-x11-6.8 to /etc/portage/package.mask (including the ">", obviously). Then portage won't try to upgrade xorg, it won't pull in all those dependencies that block on your version of xorg, and portage should stop complaining. HTH, Toby -- PhD Student Quantum Information Theory group Max Planck Institute for Quantum Optics Garching, Germany email: [EMAIL PROTECTED] web: www.dr-qubit.org -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Greylisting idea
On Mon, Aug 28, 2006 at 05:38:37PM -0700, Richard Fish wrote:
> On 8/28/06, Grant <[EMAIL PROTECTED]> wrote:
> >Greylisting seems to be the most effective way of eliminating unwanted
> >email. The problem is that it also has the potential to eliminate a
> >legitimate email. Couldn't a feature be added to greylisting software
> >that dispatches an email to the sender of any email that is
> >temporarily rejected and doesn't retry within a certain amount of
> >time? The email could say something like, "Your message of {date} was
> >rejected as possible spam. Please call us at {phone_number}."
>
> att.biz accounts do something like this. It isn't a phone call, but
> "go to $website and enter $code to unblock your mail to $recepient."
TMDA (in portage) could be set up to do something like this, I
believe.
Toby
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: [EMAIL PROTECTED]
web: www.dr-qubit.org
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Are these packages safe to unmerge?
On Sat, Sep 09, 2006 at 02:26:03PM +, Peter wrote:
> On Sat, 09 Sep 2006 12:41:14 +0100, Mick wrote:
>
> > Hi All,
> >
> > Just ran depclean and the following candicates are shown:
> > ===
> > Calculating dependencies... done!
[snip]
> With the exception of tcsh, probably no. Run equery d {package} and see if
> anything depends on them. The ones you show are pretty standard. You might
> be able to dump the framebuffer, but check.
If depclean has listed the packages, I'm fairly sure that means
portage couldn't find anything in "system" or "world" that depends on
it (or anything that depends on something that depends on it,
etc.). So querying for dependencies is, by definition, going to return
nothing.
That doesn't necessarily mean the packages can safely be removed (I
once borked my system badly by making that assumption). Look at the
package descriptions or google them to try to find out what exactly
they do before you decide it's safe to remove them. Usually, even if
the package *is* required, all that happens is some program will no
longer run and you'll need to re-emerge the package. You can then add
it to world so that it's not picked up by depclean in the future. In
the worst case, you find you've remove something essential and the
system no longer even boots. (That's what happened to me, with libcap
if I remember right.)
That was with older versions of portage. I don't know if newer ones
are safer.
HTH,
Toby
--
PhD Student
Quantum Information Theory group
Max Planck Institute for Quantum Optics
Garching, Germany
email: [EMAIL PROTECTED]
web: www.dr-qubit.org
--
gentoo-user@gentoo.org mailing list
