Re: [gentoo-user] {OT} rdiff-backup: push or pull?
On Thursday, August 18, 2011 06:01:08 PM Grant wrote: You can seperate the backups by giving each system a different account where to store the backups. I'm not sure what you mean. The backups are all stored on the backup server. Each machine to be backed up has a different account on the backup server. This will prevent machine A from accessing the backups of machine B. This way, if one machine is compromised, only this machines backups can be accessed using the access-keys for the backup. And this machines keys can then be revoked without affecting other backups. That's a great idea. I will do that. Should that backup account have any special configuration, or just a standard new user? I would suspect just a standard new user with default permissions. Eg. only write-access to his/her own files. And I'd prevent that user account from being able to get a shell-account. I created the backup users and everything works as long as the backup users have shells on the backup server and are listed in AllowUsers in /etc/ssh/sshd_config on the backup server. Did I do something wrong or should the backup users need shells and to be listed in AllowUsers? I'm not too familiar with rsync backups. A shell might be required, but if you set the command run on the server-side in the authorized_keys it should prevent any other command from being run. Should I set up any extra restrictions for them in sshd_config? I have disabled all password-logins and only allow shared-key logins. Should I set passwords for them? I don't set passwords for these type of users. By default, they can not login with any password that way. Setting a password will leave the possibility open someone might randomly guess the password. -- Joost
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
On Thursday, August 18, 2011 06:51:32 PM Grant wrote: I'm setting up an automated rdiff-backup system and I'm stuck between pushing the backups to the backup server, and pulling the backups to the backup server. If I push, I have to allow read/write access of my backups via SSH keys. If I pull, I have to enable root logins on each system to be backed-up, allow root read access of each system via SSH keys, and I have to deal with openvpn or ssh -R so my laptop can back up from behind foreign routers. The conventional wisdom online seems to indicate pulling is better, but pushing seems like it might be better to me. Do you push or pull? I would push, to be honest. What can be done about the fact that any attacker who can break into a system and wipe it out can also wipe out its backups? That negates one of the reasons for making the backups in the first place. True, except if, after a backup is finished, you move the actual backup to a different location. (Or you backup the backup server) I store all important files on my server and the backups there can not be accessed from the fileserver itself. (That backup is done in pull mode every night.) Should private SSH keys be excluded from the backup? Should anything else be excluded? When a host is compromised, the corresponding entries in the authorized_keys should be removed from all other servers/hosts. This will make those private keys useless. If you protect them with a passphrase, the private keys are not usable in any case. But this will require the backups to be started manually to allow you to enter the passphrase. Or you unlock the passphrase in memory and use ssh-agent for that. -- Joost
Re: [gentoo-user] Running HTTP and DNS on same machine
On Thu 18 August 2011 14:36:26 Michael Mol did opine thusly: On Thu, Aug 18, 2011 at 2:17 PM, Florian Philipp li...@binarywings.net wrote: Am 18.08.2011 03:35, schrieb Michael Mol: On Wed, Aug 17, 2011 at 5:53 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On Wed 17 August 2011 17:23:41 Michael Mol did opine thusly: At a minimum they should be on different interfaces and preferably in chroots. Otherwise all manner of $BAD_STUFF happens. Hm. Interested. echo $BAD_STUFF (or URI) URI: http://cr.yp.to/djbdns/separation.html Ah, gotcha. Yeah, I'm a bit worried about that. Even though I use a FQDN, I'm only authorative within my own network and I don't (yet) expose my DNS records publicly. (It all resolves to RFC1918 addresses...what'd be the point?) On your scale you'd probably get away with it, that's why I made that little note earlier. Throughout this thread I've been replying from the viewpoint of having very large auth servers to maintain, I have to deal with stuff you'd likely never see, simply because you only have one zone. My employers have seen fit to sign up something like 40,000 zones from customers then said Here you Alan, make this work. Aside from security and integrity issues, all sorts of interesting data problems happen on that scale, and they all seem the trace back to inappropriate use of glue. Sooner or later you will find a record you need to look up for purposes other than it being an NS, and you have it already in glue. If you are using that bind instance also as a cache, it will never do a proper look up for that glue record as it is ALREADY authoritative. You will go nuts and turn your brains into scrambled eggs trying to find that one. (exactly the same weird issues can be found in almost any kind of coding problem using data and linked data structures, it's not unique to DNS). Any large DNS provider should (and almost all do) keep the caches and auth servers distinctly separate. Most also split top-level and second-level domains too. -- alan dot mckinnon at gmail dot com
[gentoo-user] (OT) TP-Link TL-MR3420 GPL?
Just bought a TP-Link TL-MR3420 3G/3.75G Wireless N Router (the kind that accepts a 3G or EVDO USB modem), and the first thing that fell on my hand when I opened it... ... is a printed copy of GPL! I wonder what GPLicensed software this access point uses... anyone knows? Rgds, -- -- Pandu E Poluan - IT Optimizer My website: http://pandu.poluan.info/
Re: [gentoo-user] (OT) TP-Link TL-MR3420 GPL?
Am 08/19/11 09:35, schrieb Pandu Poluan: Just bought a TP-Link TL-MR3420 3G/3.75G Wireless N Router (the kind that accepts a 3G or EVDO USB modem), and the first thing that fell on my hand when I opened it... ... is a printed copy of GPL! I wonder what GPLicensed software this access point uses... anyone knows? Rgds, Most routers, nas devices, TVs, toasters run a modified or sometimes not modified version of linux (Debian, Slackware etc.) with stock daemons providing their funktionality. Norman
Re: [gentoo-user] (OT) TP-Link TL-MR3420 GPL?
On Friday, August 19, 2011 02:35:45 PM Pandu Poluan wrote: Just bought a : 3G/3.75G Wireless N Router (the kind that accepts a 3G or EVDO USB modem), and the first thing that fell on my hand when I opened it... ... is a printed copy of GPL! I wonder what GPLicensed software this access point uses... anyone knows? My guess: Linux kernel wth the iptables stack and tools. Maybe also a few other things, like a DHCP-server and a DNS-cache. I've seen this as well and you should either have a list of software used or a way to download the source-code from the manufacturers website: http://www.tp-link.com/en/support/gpl/ -- Joost
Re: [gentoo-user] /dev/sda* missing at boot
On Friday 19 Aug 2011 03:27:23 Mark Knecht wrote: On Thu, Aug 18, 2011 at 11:59 AM, fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Thanks a lot Francisco P.S.: my boot partition is sda2, sda3 is a swap partition, and everything else is in sda4. sda1 is not used (up to now) and this is my grub.conf : title Gentoo Linux 2.6.39-gentoo-r3 root (hd0,1) kernel /boot/kernel-genkernel-x86_64-2.6.39-gentoo-r3 ro root=/dev/ram0 init=/linuxrc real_root=/dev/sda4 vga=0x318 video=uvesafb:1024x768-32 nodevfs udev devfs=nomount quiet CONSOLE=/dev/tty1 initrd /boot/initramfs-genkernel-x86_64-2.6.39-gentoo-r3 Maybe I'm missing the obvious here but have you taken a copy of whatever config file was used/generated by genkernel and used that as a jumping off point for building your own kernel. kernel's a kernel's a kernel. What it is capable of doing is in the .config file. If genkernel doesn't give you a .config file - I've never used genkernel so I don't know what it does - then assuming you have the feature turned on you can get the running config using zcat /proc/config.gz. Save that to a new .config file, put it in the kernel source directory and you should be good to go. You can also use zcat /proc/config.gz on the install CD kernel if yuo boot from that. Save it to a disk and use it as the basis for creating your own config. If you no longer use genkernel it is likely that you do not need an initram. Build chipset and fs modules into the kernel. Other drivers you can choose if you want to build as modules. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What's the status of ht://Dig?
On Thursday 18 August 2011 08:33:06 Matthew Finkel wrote: Browsing through the page, the project looks pretty dead which seems strange considering how many contributors it had. As such, I've never used it but Hyper Estraier[0] may do what you want, as well. There are probably others out there. There's also always the Google option. [0] http://fallabs.com/hyperestraier/ I had a play with this, but there's a snag at the server end - it threw an internal config error when I tried to run the cgi-bin script. While looking into that, I discovered the the web host already has a search engine available to its customers. Well, what do you know! That has to be my next investigation. Thanks for the idea anyway. -- Rgds Peter Linux Counter 5290, 1994-04-23
[gentoo-user] move to xfce and forget kde and gnome
hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? Thank you Laszlo
[gentoo-user] emerge unable to find telepathy-logger[introspection]; why?
I run ~amd64 with the gnome overlay on one of my machines.
I just ran an update world, which failed with
emerge: there are no ebuilds to satisfy
=net-im/telepathy-logger-0.2.4[introspection].
(dependency required by gnome-base/gnome-shell-3.0.2 [installed])
(dependency required by gnome-base/gnome-light-3.0.0 [installed])
(dependency required by @selected [set])
(dependency required by @world [argument])
Not only do there seem to be ebuilds for this on my machine, but the
installed telepathy-logger seems to satisfy the requirements.
oldlap ~ # eix telepathy-logger
[I] net-im/telepathy-logger
Available versions: 0.1.7 (~)0.2.9 0.2.10 {doc +introspection test}
Installed versions: 0.2.10(11:00:55 AM 06/09/2011)(introspection -doc
-test)
What is wrong?
thanks,
allan
[gentoo-user] Re: /dev/sda* missing at boot
On 08/18/2011 10:08 PM, András Csányi wrote: On 18 August 2011 18:59,fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Why have you choose this way? I mean, non-genkernel way. genkernel generates generic (bloated) kernels.
[gentoo-user] Re: move to xfce and forget kde and gnome
On 08/19/2011 03:02 PM, Space Cake wrote: hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? You change your profile. You can see your current profile with: eselect profile list For KDE you would use default/linux/amd64/10.0/desktop/kde and for Gnome default/linux/amd64/10.0/desktop/gnome. For anything else, use default/linux/amd64/10.0/desktop. Then do a: emerge -auDN --with-bdeps=y world emerge -a --depclean If KDE/Gnome stuff still remains after that, use: emerge -pv --depclean package to see what's pulling-in package.
Re: Re: [gentoo-user] /dev/sda* missing at boot
Em 18/08/2011 23:27, Mark Knecht markkne...@gmail.com escreveu: On Thu, Aug 18, 2011 at 11:59 AM, fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Thanks a lot Francisco PS: my boot partition is sda2, sda3 is a swap partition, and everything else is in sda4. sda1 is not used (up to now) and this is my grub.conf : title Gentoo Linux 2.6.39-gentoo-r3 root (hd0,1) kernel /boot/kernel-genkernel-x86_64-2.6.39-gentoo-r3 ro root=/dev/ram0 init=/linuxrc real_root=/dev/sda4 vga=0x318 video=uvesafb:1024x768-32 nodevfs udev devfs=nomount quiet CONSOLE=/dev/tty1 initrd /boot/initramfs-genkernel-x86_64-2.6.39-gentoo-r3 Maybe I'm missing the obvious here but have you taken a copy of whatever config file was used/generated by genkernel and used that as a jumping off point for building your own kernel. kernel's a kernel's a kernel. What it is capable of doing is in the .config file. If genkernel doesn't give you a .config file - I've never used genkernel so I don't know what it does - then assuming you have the feature turned on you can get the running config using zcat /proc/config.gz. Save that to a new .config file, put it in the kernel source directory and you should be good to go. You can also use zcat /proc/config.gz on the install CD kernel if yuo boot from that. Save it to a disk and use it as the basis for creating your own config. HTH, Mark That's what I am doing right now. I am using genkernel to have something to boot on. Then I will try to find a way to optimize another one. Thanks Francisco
Re: Re: [gentoo-user] /dev/sda* missing at boot
Em 19/08/2011 07:09, Mick michaelkintz...@gmail.com escreveu: On Friday 19 Aug 2011 03:27:23 Mark Knecht wrote: On Thu, Aug 18, 2011 at 11:59 AM, fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Thanks a lot Francisco PS: my boot partition is sda2, sda3 is a swap partition, and everything else is in sda4. sda1 is not used (up to now) and this is my grub.conf : title Gentoo Linux 2.6.39-gentoo-r3 root (hd0,1) kernel /boot/kernel-genkernel-x86_64-2.6.39-gentoo-r3 ro root=/dev/ram0 init=/linuxrc real_root=/dev/sda4 vga=0x318 video=uvesafb:1024x768-32 nodevfs udev devfs=nomount quiet CONSOLE=/dev/tty1 initrd /boot/initramfs-genkernel-x86_64-2.6.39-gentoo-r3 Maybe I'm missing the obvious here but have you taken a copy of whatever config file was used/generated by genkernel and used that as a jumping off point for building your own kernel. kernel's a kernel's a kernel. What it is capable of doing is in the .config file. If genkernel doesn't give you a .config file - I've never used genkernel so I don't know what it does - then assuming you have the feature turned on you can get the running config using zcat /proc/config.gz. Save that to a new .config file, put it in the kernel source directory and you should be good to go. You can also use zcat /proc/config.gz on the install CD kernel if yuo boot from that. Save it to a disk and use it as the basis for creating your own config. If you no longer use genkernel it is likely that you do not need an initram. Build chipset and fs modules into the kernel. Other drivers you can choose if you want to build as modules. -- Regards, Mick I the case I don't need a initram, I guess that the grub line for parameter passing to the kernel would be empty. Am I wrong? I was just looking on how to build my own initram. What is it supposed to do anyway? Thanks Francisco
Re: Re: [gentoo-user] /dev/sda* missing at boot
On Fri, Aug 19, 2011 at 9:12 AM, fra...@gmail.com wrote: Em 19/08/2011 07:09, Mick michaelkintz...@gmail.com escreveu: On Friday 19 Aug 2011 03:27:23 Mark Knecht wrote: On Thu, Aug 18, 2011 at 11:59 AM, fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Thanks a lot Francisco P.S.: my boot partition is sda2, sda3 is a swap partition, and everything else is in sda4. sda1 is not used (up to now) and this is my grub.conf : title Gentoo Linux 2.6.39-gentoo-r3 root (hd0,1) kernel /boot/kernel-genkernel-x86_64-2.6.39-gentoo-r3 ro root=/dev/ram0 init=/linuxrc real_root=/dev/sda4 vga=0x318 video=uvesafb:1024x768-32 nodevfs udev devfs=nomount quiet CONSOLE=/dev/tty1 initrd /boot/initramfs-genkernel-x86_64-2.6.39-gentoo-r3 Maybe I'm missing the obvious here but have you taken a copy of whatever config file was used/generated by genkernel and used that as a jumping off point for building your own kernel. kernel's a kernel's a kernel. What it is capable of doing is in the .config file. If genkernel doesn't give you a .config file - I've never used genkernel so I don't know what it does - then assuming you have the feature turned on you can get the running config using zcat /proc/config.gz. Save that to a new .config file, put it in the kernel source directory and you should be good to go. You can also use zcat /proc/config.gz on the install CD kernel if yuo boot from that. Save it to a disk and use it as the basis for creating your own config. If you no longer use genkernel it is likely that you do not need an initram. Build chipset and fs modules into the kernel. Other drivers you can choose if you want to build as modules. I the case I don't need a initram, I guess that the grub line for parameter passing to the kernel would be empty. Am I wrong? I was just looking on how to build my own initram. What is it supposed to do anyway? The initramfs is a container for modules and stuff need to bring up the system before the mounts of / and /boot.If all the drivers are built-in to the kernel (or at least the minimum required drivers are built-in) then the initramfs isn't necessary. Passing parameters to the kernel is a different issue entirely. My grub.conf line is: kernel /vmlinuz-3.0.3-gentoo root=/dev/sda2 pata_it821x.noraid=1 with the pata_it821x driver built-in for the kenel to find a set of older IDE drives on the IT8212 card I have installed. IIRC the initramfs is built with the mkinitrd command. I haven't had to use it so I could be wrong.
Re: [gentoo-user] /dev/sda* missing at boot
On Fri 19 August 2011 13:12:25 fra...@gmail.com did opine thusly: I the case I don't need a initram, I guess that the grub line for parameter passing to the kernel would be empty. Am I wrong? Yes. Using or not using kernel parameters has nothing to do with whether you use an initramfs or not. It's the initrd line in grub you do not need. I was just looking on how to build my own initram. What is it supposed to do anyway? First, it's initramfs (the previous incarnation was initrd). You should use the correct name. An initramfs is a filesystems image stored on disk in a place that grub can find. It contains a kernel, essential drivers and other bits and pieces. When booting, grub finds the image, bangs it into memory and instructs the cpu to start executing at a known point. Why is this useful? For Gentoo it usually isn't (there are times when it is - see below). Binary distros like Ubuntu and Fedora absolutely require this. These distros do not know what hardware you have and what drivers you require, so they supply drivers for everything. But Ubuntu cannot possibly compile into the kernel every possible driver you might need to boot as the list would be huge (every known floppy, CD, USB, every known MFM, IDE, SATA, SCSI, netboot, Fibre and more driver for a start), so what they do instead is probe the hardware at boot time, find out what you have, and load the driver modules you DO need. This is the problem. The kernel wants to load disk drivers so that it can access the disk and continue booting. Where are the drivers? Well, they are on the disk. Oops, circular problem. The difficulty is not finding and loading drivers, it's how do you get the disk driver off the disk before you have the disk driver in memory? (think chicken and egg here). An initramfs solves this nicely. Grub shoved a disk image into memory when it booted. The kernel knows how to access it's memory it doesn't need a driver for that. And now the files containing the needed drivers are on a virtual disk *in memory*. The kernel loads them, and can now access the real physical disks. Lots more complicated stuff then happens, like getting rid of the virtual filesystem from the initramfs and mounting the real filesystem from disk at /, but that's beyond the scope of this mail. Gentoo mostly doesn't need any of this because you do know your hardware and can just compile your disk drivers into the kernel - this is the very thing that Ubuntu cannot do. Some Gentoo users still need an initramfs, such as booting off drives in a RAID configuration. They need the RAID drivers first to read the disks so use an initramfs to fix this little problem exactly as Ubunut fixes their problem. Make sense? -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: move to xfce and forget kde and gnome
On 2011. aug. 19., péntek, 14.54.40 CEST, Nikos Chantziaras wrote: On 08/19/2011 03:02 PM, Space Cake wrote: hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? You change your profile. You can see your current profile with: eselect profile list For KDE you would use default/linux/amd64/10.0/desktop/kde and for Gnome default/linux/amd64/10.0/desktop/gnome. For anything else, use default/linux/amd64/10.0/desktop. Then do a: emerge -auDN --with-bdeps=y world emerge -a --depclean If KDE/Gnome stuff still remains after that, use: emerge -pv --depclean package to see what's pulling-in package. Are you sure that's all? No need to change my global useflags at all? When I change profile and check what would be re-emerged, only a few minor changes exists. What I would like to achieve to get rid of all the fat kde/gnome stuff but of course without re install my whole system. Is there anyone here who already did something similar? Thank you Laszlo
Re: [gentoo-user] Re: move to xfce and forget kde and gnome
Lazlo my use flags for keeping kde and gnome away are -kde -gnome -qt4 I also have eselect profile set 1 You may have to use /etc/portage/package.use to get guis to some packages That may need kde or gnome Jdm Sent from my BlackBerry® smartphone on O2 -Original Message- From: Space Cake spaceca...@gmail.com Date: Fri, 19 Aug 2011 16:07:40 To: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: move to xfce and forget kde and gnome On 2011. aug. 19., péntek, 14.54.40 CEST, Nikos Chantziaras wrote: On 08/19/2011 03:02 PM, Space Cake wrote: hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? You change your profile. You can see your current profile with: eselect profile list For KDE you would use default/linux/amd64/10.0/desktop/kde and for Gnome default/linux/amd64/10.0/desktop/gnome. For anything else, use default/linux/amd64/10.0/desktop. Then do a: emerge -auDN --with-bdeps=y world emerge -a --depclean If KDE/Gnome stuff still remains after that, use: emerge -pv --depclean package to see what's pulling-in package. Are you sure that's all? No need to change my global useflags at all? When I change profile and check what would be re-emerged, only a few minor changes exists. What I would like to achieve to get rid of all the fat kde/gnome stuff but of course without re install my whole system. Is there anyone here who already did something similar? Thank you Laszlo
[gentoo-user] Re: move to xfce and forget kde and gnome
On 08/19/2011 05:07 PM, Space Cake wrote: [...] If KDE/Gnome stuff still remains after that, use: emerge -pv --depcleanpackage to see what's pulling-inpackage. Are you sure that's all? No need to change my global useflags at all? Well, I just said above to use emerge -pv to see what's pulling packages in. That means you have to use your brain and see if USE flags are pulling-in Gnome/KDE deps.
[gentoo-user] Re: move to xfce and forget kde and gnome
On 08/19/2011 05:27 PM, j...@jdm.myzen.co.uk wrote: Lazlo my use flags for keeping kde and gnome away are -kde -gnome -qt4 -qt4 has nothing to do with KDE. If any package has a qt4 USE flag that results in KDE dependencies, then it should be reported as a bug. I'm not aware of any such packages though.
Re: [gentoo-user] move to xfce and forget kde and gnome
2011/8/19 Space Cake spaceca...@gmail.com: hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? I think we agree. Nowadays I use xfce because KDE is hungry and makes my system slower. But there is a few application (amarok - big bloatware but I like the amarok services, umbrello, krusader, kile, etc) which is needed and I always have a full KDE install beside xfce. What is your strategy? You will not use any KDE related application or if something is needed you will install it separately? -- - - -- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- http://facebook.com/andras.csanyi -- Trust in God and keep your gunpowder dry! - Cromwell
Re: Re: [gentoo-user] /dev/sda* missing at boot
Em 19/08/2011 10:48, Alan McKinnon alan.mckin...@gmail.com escreveu: On Fri 19 August 2011 13:12:25 fra...@gmail.com did opine thusly: I the case I don't need a initram, I guess that the grub line for parameter passing to the kernel would be empty. Am I wrong? Yes. Using or not using kernel parameters has nothing to do with whether you use an initramfs or not. It's the initrd line in grub you do not need. I was just looking on how to build my own initram. What is it supposed to do anyway? First, it's initramfs (the previous incarnation was initrd). You should use the correct name. An initramfs is a filesystems image stored on disk in a place that grub can find. It contains a kernel, essential drivers and other bits and pieces. When booting, grub finds the image, bangs it into memory and instructs the cpu to start executing at a known point. Why is this useful? For Gentoo it usually isn't (there are times when it is - see below). Binary distros like Ubuntu and Fedora absolutely require this. These distros do not know what hardware you have and what drivers you require, so they supply drivers for everything. But Ubuntu cannot possibly compile into the kernel every possible driver you might need to boot as the list would be huge (every known floppy, CD, USB, every known MFM, IDE, SATA, SCSI, netboot, Fibre and more driver for a start), so what they do instead is probe the hardware at boot time, find out what you have, and load the driver modules you DO need. This is the problem. The kernel wants to load disk drivers so that it can access the disk and continue booting. Where are the drivers? Well, they are on the disk. Oops, circular problem. The difficulty is not finding and loading drivers, it's how do you get the disk driver off the disk before you have the disk driver in memory? (think chicken and egg here). An initramfs solves this nicely. Grub shoved a disk image into memory when it booted. The kernel knows how to access it's memory it doesn't need a driver for that. And now the files containing the needed drivers are on a virtual disk *in memory*. The kernel loads them, and can now access the real physical disks. Lots more complicated stuff then happens, like getting rid of the virtual filesystem from the initramfs and mounting the real filesystem from disk at /, but that's beyond the scope of this mail. Gentoo mostly doesn't need any of this because you do know your hardware and can just compile your disk drivers into the kernel - this is the very thing that Ubuntu cannot do. Some Gentoo users still need an initramfs, such as booting off drives in a RAID configuration. They need the RAID drivers first to read the disks so use an initramfs to fix this little problem exactly as Ubunut fixes their problem. Make sense? Completely! Thanks a lot. So I guess that my problem is to find an appropriate pair of driver and hard disk operating mode. -- alan dot mckinnon at gmail dot com Thanks again Francisco
Re: [gentoo-user] move to xfce and forget kde and gnome
On 2011. aug. 19., péntek, 16.50.09 CEST, András Csányi wrote: 2011/8/19 Space Cake spaceca...@gmail.com: hi, after playing a lot with desktop environment first I've decided to move from kde to gnome because kde is too shine and eat too much and contains a lot of feature which I don't really need.. gnome is good but still too fat so finally I've found Xfce which is perfect for my needs... :) my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? I think we agree. Nowadays I use xfce because KDE is hungry and makes my system slower. But there is a few application (amarok - big bloatware but I like the amarok services, umbrello, krusader, kile, etc) which is needed and I always have a full KDE install beside xfce. What is your strategy? You will not use any KDE related application or if something is needed you will install it separately? I'll try to avoid as many kde/gnome application as I can :) I don't really like them because I want to have my window in front of me right when click on the icon :). I just started to clean-up my useflags, changed to desktop profile and I'll leave my machine here for the weekend to re-emerge everything is needed for this change. I'm sure some revdep-rebuild and depclean still waiting for me and also I think lot of kde / gnome libs will remain because of the dependencies... Laszlo
Re: [gentoo-user] /dev/sda* missing at boot
On Fri 19 August 2011 15:06:46 fra...@gmail.com did opine thusly: Some Gentoo users still need an initramfs, such as booting off drives in a RAID configuration. They need the RAID drivers first to read the disks so use an initramfs to fix this little problem exactly as Ubunut fixes their problem. Make sense? Completely! Thanks a lot. So I guess that my problem is to find an appropriate pair of driver and hard disk operating mode. That's right. Don't forget the filesystem drivers. For example if you mount an ext3 partition at / and it's on a SATA drive, then you need SATA and ext3 drivers in the kernel (not as modules). -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Re: move to xfce and forget kde and gnome
On Friday 19 August 2011 13:54:40 Nikos Chantziaras wrote: You change your profile. You can see your current profile with: eselect profile list For KDE you would use default/linux/amd64/10.0/desktop/kde and for Gnome default/linux/amd64/10.0/desktop/gnome. Those are recent additions to the profiles. At any rate, I only started using the KDE one this year. If Laszlo has default/linux/amd64/10.0 as his profile already (that's what I used to do), he's going to have to do an awful lot of work with USE flags. A full re-installation may be easier in the end. Any time I do a fresh installation, I back the whole thing up to external disk at significant stages of the operation so that I can start again (if I need to) from much further on. For anything else, use default/linux/amd64/10.0/desktop. Then do a: emerge -auDN --with-bdeps=y world emerge -a --depclean He may find that it doesn't make much of a change, depending on which profile he has set now. -- Rgds Peter Linux Counter 5290, 1994-04-23
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
I created the backup users and everything works as long as the backup users have shells on the backup server and are listed in AllowUsers in /etc/ssh/sshd_config on the backup server. Did I do something wrong or should the backup users need shells and to be listed in AllowUsers? I'm not too familiar with rsync backups. A shell might be required, but if you set the command run on the server-side in the authorized_keys it should prevent any other command from being run. I'm actually talking about rdiff-backup. I'm prompted for a password if the backup user doesn't have a shell. Are you able to rdiff-backup without a shell on the backup server? Should I set up any extra restrictions for them in sshd_config? I have disabled all password-logins and only allow shared-key logins. I want to be prompted for a password with my normal user but I want the backup users to be restricted. I tried 'ChallengeResponseAuthentication no' within a Match block for a backup user but ChallengeResponseAuthentication isn't allowed in a Match block. Are my options to restrict all users or none? - Grant
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
On 08/17/11 13:35, Grant wrote: Is there a way to restrict SSH keys to the rsync command? Yes, via the authorized_keys file. you can add a command directive. this will always force that command to be executed whenever a connection is made using this key. I'm using the command directive with rdiff-backup like command=rdiff-backup --server but I can't figure out the rsync command to specify. Is anyone restricting an SSK key to rsync with the command directive? We're doing the same thing for our backups. Here's that chunk of our documentation, if it's helpful. === rdiff-backup Client === Creating the Remote User First, create a new system user on the backup server. Log in (as root), and run, useradd -d /home/username -m username The ''-d'' parameter sets the home directory, and ''-m'' creates it automatically. The rdiff-backup program uses SSH to synchronize the local and remote filesystems. As a result, non-interactive operation requires a server/client certificate pair. Furthermore, we cannot prevent shell logins for our new user account. Give it a reasonably-complex password. You'll only need to type it twice: passwd username Installing rdiff-backup First things first; install rdiff-backup on the client. In Gentoo, all this requires is the following, emerge rdiff-backup If that works, go ahead and continue. Setting up SSH Authentication For now, we're done on the backup server. Log in to the client server (the one to be backed up) as root. We need to generate an SSH key pair: ssh-keygen Name the file something informative when asked. '''Do not create a password for the key file.''' For example, your private key for backup_server might be named ~/.ssh/backup_server_rsa. Now, copy the public key, e.g. ~/.ssh/backup_server_rsa.pub to the backup server using the user that we created earlier. scp ~/.ssh/public_key_file remote_user@backup_server:~/ And add a section to the local ~/.ssh/config file which corresponds to the backup server. This forces the local machine to authenticate to the backup server using its key rather than a password. pre Host backup_server_hostname Hostname backup_server_hostname IdentityFile ~/.ssh/private_key_file IdentitiesOnly yes /pre Now, ssh into the backup server as your new user. Our goal is to add this key as trusted, allowing anyone with the corresponding key to connect as this user. On the backup server (as our new user), execute, cat public_key_file ~/.ssh/authorized_keys rm public_key_file and add the following to the authorized_keys file manually. Add it at the beginning of the line for the new public key. command=/usr/bin/rdiff-backup --server,no-pty,no-port-forwarding This will restrict the user with this public key to executing only the rdiff-server command.
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
I'm setting up an automated rdiff-backup system and I'm stuck between pushing the backups to the backup server, and pulling the backups to the backup server. If I push, I have to allow read/write access of my backups via SSH keys. If I pull, I have to enable root logins on each system to be backed-up, allow root read access of each system via SSH keys, and I have to deal with openvpn or ssh -R so my laptop can back up from behind foreign routers. The conventional wisdom online seems to indicate pulling is better, but pushing seems like it might be better to me. Do you push or pull? I would push, to be honest. What can be done about the fact that any attacker who can break into a system and wipe it out can also wipe out its backups? That negates one of the reasons for making the backups in the first place. True, except if, after a backup is finished, you move the actual backup to a different location. (Or you backup the backup server) I do back up the backup server to another system via rsync, but if the backups on the backup server are wiped out, rsync will wipe them out on the other system too. I store all important files on my server and the backups there can not be accessed from the fileserver itself. (That backup is done in pull mode every night.) I thought you were in favor of pushing? How do you back up to a system that can't access the backups? Should private SSH keys be excluded from the backup? Should anything else be excluded? When a host is compromised, the corresponding entries in the authorized_keys should be removed from all other servers/hosts. This will make those private keys useless. So it's OK to back up a private key to another system? I just want to make sure I'm not breaking a good admin rule by doing this. - Grant
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
We're doing the same thing for our backups. Here's that chunk of our documentation, if it's helpful. Thanks Michael. You've found that a shell account is required on the backup server in order to push backups to it? Is the purpose of the Host block in .ssh/config to store the hostname of the backup server so it doesn't need to be used directly in the rdiff-backup command? Why create a password for the backup user? Doesn't that open up the possibility of someone logging in as that user, when otherwise the account would only be used for backing up files? - Grant === rdiff-backup Client === Creating the Remote User First, create a new system user on the backup server. Log in (as root), and run, useradd -d /home/username -m username The ''-d'' parameter sets the home directory, and ''-m'' creates it automatically. The rdiff-backup program uses SSH to synchronize the local and remote filesystems. As a result, non-interactive operation requires a server/client certificate pair. Furthermore, we cannot prevent shell logins for our new user account. Give it a reasonably-complex password. You'll only need to type it twice: passwd username Installing rdiff-backup First things first; install rdiff-backup on the client. In Gentoo, all this requires is the following, emerge rdiff-backup If that works, go ahead and continue. Setting up SSH Authentication For now, we're done on the backup server. Log in to the client server (the one to be backed up) as root. We need to generate an SSH key pair: ssh-keygen Name the file something informative when asked. '''Do not create a password for the key file.''' For example, your private key for backup_server might be named ~/.ssh/backup_server_rsa. Now, copy the public key, e.g. ~/.ssh/backup_server_rsa.pub to the backup server using the user that we created earlier. scp ~/.ssh/public_key_file remote_user@backup_server:~/ And add a section to the local ~/.ssh/config file which corresponds to the backup server. This forces the local machine to authenticate to the backup server using its key rather than a password. pre Host backup_server_hostname Hostname backup_server_hostname IdentityFile ~/.ssh/private_key_file IdentitiesOnly yes /pre Now, ssh into the backup server as your new user. Our goal is to add this key as trusted, allowing anyone with the corresponding key to connect as this user. On the backup server (as our new user), execute, cat public_key_file ~/.ssh/authorized_keys rm public_key_file and add the following to the authorized_keys file manually. Add it at the beginning of the line for the new public key. command=/usr/bin/rdiff-backup --server,no-pty,no-port-forwarding This will restrict the user with this public key to executing only the rdiff-server command.
Re: [gentoo-user] vsftpd: how can I chroot both anon and auth users to the same dir?
On 10-Aug-11 20:36, Paul Hartman wrote: So I'd like to change it the way that both anonymous as well as local users are chrooted to base ftp directory /home/ftp but I do not know how to do it. Set user_config_dir to point to someplace such as /etc/vsftpd/users In that directory, create files for each username and within it put: local_root=/home/ftp Actually, instead of creating file for each username I included these options in main config file /etc/vsftpd/vsftpd.conf: chroot_local_user=YES local_root=/home/ftp Now it works as I expected: both anonymous local users are chrooted to /home/ftp and can enter any sub-directory, but local users can upload files to /home/ftp/$USER (homedirs where they have write permission). On 10-Aug-11 20:19, Michael Orlitzky wrote: Are they local users? Change their home directories to /home/ftp. I did not test this, but it might work too. The only drawback is I'd have to edit /etc/passwd always when I add new user. Problem solved, thank you for help... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
On 08/19/11 14:00, Grant wrote: We're doing the same thing for our backups. Here's that chunk of our documentation, if it's helpful. Thanks Michael. You've found that a shell account is required on the backup server in order to push backups to it? Yes, you have to be able to run a command (rdiff-backup --server...) and that requires a shell. I tried to do it without a shell, but couldn't figure out how to do it sensibly. I do `chmod 700` all home directories. Is the purpose of the Host block in .ssh/config to store the hostname of the backup server so it doesn't need to be used directly in the rdiff-backup command? It forces key-based authentication when connecting to the backup server. The default is password-based, which obviously won't work in a cron job. Why create a password for the backup user? Doesn't that open up the possibility of someone logging in as that user, when otherwise the account would only be used for backing up files? It might work without one; in these instructions the machine-to-be-backed-up never connects to the backup server as root, and so you need a way to SCP stuff to the backup server. I usually use a `pwgen 16` password for these accounts and then immediately forget it, so nobody will log in to them for a few billion years at least. Does key-based authentication work with no password? I've never tried. I am emotionally troubled by the existence of local shell accounts, but rationally, I know that no one can ever log in to them.
[gentoo-user] Re: /dev/sda* missing at boot
On Friday 19 August 2011, Nikos Chantziaras wrote: On 08/18/2011 10:08 PM, András Csányi wrote: On 18 August 2011 18:59,fra...@gmail.com wrote: Hi, guys It is a shame, I know, but after several years using Gentoo, it is the first time I try to build a kernel without genkernel. And now I can't boot to that new kernel, it does not find (and really do not have a) /dev/sda* root partition (real-root); during the boot it stops, complaining about that, gives me the option to get a shell, from which I am able to see that there is no /dev/sda* . I have included everything SATA, so it looks like that is not a kernel problem, but a initramfs issue, I guess. What am I missing? Why have you choose this way? I mean, non-genkernel way. genkernel generates generic (bloated) kernels. This is a generalization, not entirely true: genkernel --no-clean --no-mrproper --kerneldir=blabla all With the above command, for example, you can provide your own .config and genkernel will do exactly as you wish. Cheers Francesco -- Linux Version 3.0.0-gentoo, Compiled #3 SMP PREEMPT Fri Aug 5 21:02:22 CEST 2011 Two 1GHz AMD Athlon 64 X2 Processors, 4GB RAM, 4021.84 Bogomips Total aemaeth
Re: [gentoo-user] move to xfce and forget kde and gnome
On Fri, Aug 19, 2011 at 11:50, András Csányi sayusi.a...@gmail.com wrote: 2011/8/19 Space Cake spaceca...@gmail.com: my question is what is the easiest way to get rid of kde/gnome stuff? is this enough to change my useflags to -kde and -gnome? Is there any list what I can safely unmerge in this case? I think we agree. Nowadays I use xfce because KDE is hungry and makes my system slower. But there is a few application (amarok - big bloatware but I like the amarok services, umbrello, krusader, kile, etc) which is needed and I always have a full KDE install beside xfce. What is your strategy? You will not use any KDE related application or if something is needed you will install it separately? Totally agree. I am a XFCE user, but I just love K3B, and it needs kdelibs. I don't like KDE or Gnome, but I can live with compiling some of their libs... -- Daniel da Veiga
Re: [gentoo-user] {OT} rdiff-backup: push or pull?
Is the purpose of the Host block in .ssh/config to store the hostname of the backup server so it doesn't need to be used directly in the rdiff-backup command? It forces key-based authentication when connecting to the backup server. The default is password-based, which obviously won't work in a cron job. I don't use an .ssh/config at all and I'm not prompted for a password if the keys are in place. My sshd_config is pretty much default and my normal user is prompted for a password. Why create a password for the backup user? Doesn't that open up the possibility of someone logging in as that user, when otherwise the account would only be used for backing up files? It might work without one; in these instructions the machine-to-be-backed-up never connects to the backup server as root, and so you need a way to SCP stuff to the backup server. I usually use a `pwgen 16` password for these accounts and then immediately forget it, so nobody will log in to them for a few billion years at least. Does key-based authentication work with no password? I've never tried. It does! :) - Grant
Re: [gentoo-user] /dev/sda* missing at boot
Gregory Woodbury wrote: The initramfs is a container for modules and stuff need to bring up the system before the mounts of / and /boot.If all the drivers are built-in to the kernel (or at least the minimum required drivers are built-in) then the initramfs isn't necessary. Passing parameters to the kernel is a different issue entirely. My grub.conf line is: kernel /vmlinuz-3.0.3-gentoo root=/dev/sda2 pata_it821x.noraid=1 with the pata_it821x driver built-in for the kenel to find a set of older IDE drives on the IT8212 card I have installed. IIRC the initramfs is built with the mkinitrd command. I haven't had to use it so I could be wrong. Update with new info. With udev needing some things in /usr, and /var, you will need a init* if /usr and /var is not on / in the near future. Yea, real neat. Some need it already just depends on what is installed from what I read. Dale :-) ;-)
Re: [gentoo-user] move to xfce and forget kde and gnome
On Fri, Aug 19, 2011 at 05:19:29PM +0200, Space Cake wrote
I'll try to avoid as many kde/gnome application as I can :) I don't
really like them because I want to have my window in front of me right
when click on the icon :). I just started to clean-up my useflags,
changed to desktop profile and I'll leave my machine here for the
weekend to re-emerge everything is needed for this change. I'm sure
some revdep-rebuild and depclean still waiting for me and also I think
lot of kde / gnome libs will remain because of the dependencies...
Here's my autodepclean script. It parses the output of a pretend
depclean and generates, but does not execute, a script called
cleanscript, which has to be run as root. Note the warning to check
cleanscript before running it. Remove the commands to unmerge the
stuff you want to keep. In addition to some gentoo-sources kernels, it
now wants to remove nano, ever since virtual/editor showed up in
Gentoo. I get the warning...
!!! 'app-editors/nano' (virtual/editor) is part of your system profile.
!!! Unmerging it may be damaging to your system.
Here's the script...
#!/bin/bash
# autodepclean script v 0.01 released under GPL v3 by Walter Dnes 2010/08/18
# Generates a file cleanscript to remove unused ebuilds, including
# buildtime-only dependancies.
#
# Warning; this script is still beta. I recommend that you check the output
# in cleanscript before running it. It is agressive about removing unused
# gentoo-sources versions. This includes those that are higher than your
# current kernel. This is technically correct for removing unused ebuilds,
# but it may not be what you want.
#
echo #!/bin/bash cleanscript
echo # cleanscript.000
emerge --pretend --depclean |\
grep -A1 ^ .*/ |\
grep -v ^ \* |\
grep -v ^-- |\
sed :/: {
N
s:\n::
s/selected: /-/
s/^ /emerge --depclean =/
} cleanscript.000
while read
do
echo ${REPLY} cleanscript
if [ ${REPLY:0:6} == emerge ]; then
echo revdep-rebuild cleanscript
fi
done cleanscript.000
chmod 744 cleanscript
--
Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] move to xfce and forget kde and gnome
On Saturday 20 August 2011 00:14:07 Walter Dnes wrote: Here's my autodepclean script. It parses the output of a pretend depclean and generates, but does not execute, a script called cleanscript, which has to be run as root. Note the warning to check cleanscript before running it. Remove the commands to unmerge the stuff you want to keep. In addition to some gentoo-sources kernels, it now wants to remove nano, ever since virtual/editor showed up in Gentoo. I get the warning... !!! 'app-editors/nano' (virtual/editor) is part of your system profile. !!! Unmerging it may be damaging to your system. Here's the script... Interesting - thanks! It found an unused library file (qdbm) here that nothing else had. One suggestion: I'd create cleanscript in /tmp rather than wherever I happened to be at the time. -- Rgds Peter Linux Counter 5290, 1994-04-23
Re: [gentoo-user] move to xfce and forget kde and gnome
Cool! I can see myself using this script routinely.
That said, since one *must* check the resulting script anyway, why not
start the editor directly after chmod? E.g.:
$EDITOR cleanscript
Oh, also don't forget to delete cleanscript.000 ;)
Rgds,
On 2011-08-20, Walter Dnes waltd...@waltdnes.org wrote:
On Fri, Aug 19, 2011 at 05:19:29PM +0200, Space Cake wrote
I'll try to avoid as many kde/gnome application as I can :) I don't
really like them because I want to have my window in front of me right
when click on the icon :). I just started to clean-up my useflags,
changed to desktop profile and I'll leave my machine here for the
weekend to re-emerge everything is needed for this change. I'm sure
some revdep-rebuild and depclean still waiting for me and also I think
lot of kde / gnome libs will remain because of the dependencies...
Here's my autodepclean script. It parses the output of a pretend
depclean and generates, but does not execute, a script called
cleanscript, which has to be run as root. Note the warning to check
cleanscript before running it. Remove the commands to unmerge the
stuff you want to keep. In addition to some gentoo-sources kernels, it
now wants to remove nano, ever since virtual/editor showed up in
Gentoo. I get the warning...
!!! 'app-editors/nano' (virtual/editor) is part of your system profile.
!!! Unmerging it may be damaging to your system.
Here's the script...
#!/bin/bash
# autodepclean script v 0.01 released under GPL v3 by Walter Dnes 2010/08/18
# Generates a file cleanscript to remove unused ebuilds, including
# buildtime-only dependancies.
#
# Warning; this script is still beta. I recommend that you check the output
# in cleanscript before running it. It is agressive about removing unused
# gentoo-sources versions. This includes those that are higher than your
# current kernel. This is technically correct for removing unused ebuilds,
# but it may not be what you want.
#
echo #!/bin/bash cleanscript
echo # cleanscript.000
emerge --pretend --depclean |\
grep -A1 ^ .*/ |\
grep -v ^ \* |\
grep -v ^-- |\
sed :/: {
N
s:\n::
s/selected: /-/
s/^ /emerge --depclean =/
} cleanscript.000
while read
do
echo ${REPLY} cleanscript
if [ ${REPLY:0:6} == emerge ]; then
echo revdep-rebuild cleanscript
fi
done cleanscript.000
chmod 744 cleanscript
--
Walter Dnes waltd...@waltdnes.org
--
--
Pandu E Poluan - IT Optimizer
My website: http://pandu.poluan.info/
Re: [gentoo-user] move to xfce and forget kde and gnome
On Sat, Aug 20, 2011 at 01:34:33AM +0100, Peter Humphrey wrote Interesting - thanks! It found an unused library file (qdbm) here that nothing else had. One suggestion: I'd create cleanscript in /tmp rather than wherever I happened to be at the time. Question... how many people have /tmp on a partition that's mounted noexec? That could be a problem. -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] move to xfce and forget kde and gnome
On Sat, Aug 20, 2011 at 08:17:57AM +0700, Pandu Poluan wrote Oh, also don't forget to delete cleanscript.000 ;) The autodepclean script cleans out the the temporary file with... echo # cleanscript.000 ...Note the which zaps cleanscript.000. I leave it around as a debugging aid. This is GPL. Feel free to append the the line... rm cleanscript.000 ...to your copy of autodepclean if you wish. -- Walter Dnes waltd...@waltdnes.org
Re: [gentoo-user] {OT} USB 3.0 hard drive speed test
On Thu, Aug 18, 2011 at 6:32 PM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Thursday 18 August 2011 23:46:30 Paul Hartman wrote: I saw that one of the pins on the port was bent inward on itself, so it never made contact when I plugged devices into it. And when you tried to straighten it, it broke off, no? That's been my experience. It was bent in such an awkward way that I couldn't get it to move... I'm sure it would have snapped off if I did, though. Luckily, it was a port on the case, not the motherboard, and the front panel was modular -- so the manufacturer (Antec) sent me a new one free of charge.
