Re: [gentoo-user] hp H222 SAS controller
Am 12.07.2013 01:02, schrieb Stefan G. Weichinger: > Am 12.07.2013 00:38, schrieb Paul Hartman: > >> Hmmm, even the data on HP's website says H222 uses LSI SAS2x08 chipset >> and mpt2sas driver. I think maybe those Marvell entries are >> SATA/eSATA ports on your motherboard. > > Yes, you might be right ... > > and I see the IDs in /sys/bus/pci/drivers/ahci > > So the LTO4 is connected *somewhere* else, I don't get any /dev/st0 even > with "st" compiled into the kernel. I checked for PCI(e) devices in the BIOS: the controller does not show up there! hmm ...
Re: [gentoo-user] Linux viruses
On 7/5/2013 11:12 PM, Dale wrote: I since did some googling and it seems I am right and he just thought I was some know nothing guy he could sell some service too. Anyway, has anything changed to make Linux more prone to viruses than it used to be? I read a percentage somewhere that said like 99% of viruses are windoze only. Is there a indisputable source of information on this? Linux is inherently more secure than Windows, but it isn't so much more secure that only 1% of all viruses can attack it. Virus developers don't have a financial incentive to develop Linux viruses (not enough Linux users, most Linux users knowledgeable about computers, and moral reasons). -- Timur Aydin
Re: [gentoo-user] hp H222 SAS controller
Am 12.07.2013 15:52, schrieb Stefan G. Weichinger: > Am 12.07.2013 01:02, schrieb Stefan G. Weichinger: >> Am 12.07.2013 00:38, schrieb Paul Hartman: >> >>> Hmmm, even the data on HP's website says H222 uses LSI SAS2x08 chipset >>> and mpt2sas driver. I think maybe those Marvell entries are >>> SATA/eSATA ports on your motherboard. >> >> Yes, you might be right ... >> >> and I see the IDs in /sys/bus/pci/drivers/ahci >> >> So the LTO4 is connected *somewhere* else, I don't get any /dev/st0 even >> with "st" compiled into the kernel. > > I checked for PCI(e) devices in the BIOS: the controller does not show > up there! > > hmm ... chose another slot, now it works!
Re: [gentoo-user] Linux viruses
Am 12.07.2013 18:36, schrieb Timur Aydin: > On 7/5/2013 11:12 PM, Dale wrote: >> I since did some googling and it seems I am right and he just thought I >> was some know nothing guy he could sell some service too. Anyway, has >> anything changed to make Linux more prone to viruses than it used to >> be? I read a percentage somewhere that said like 99% of viruses are >> windoze only. Is there a indisputable source of information on this? > > Linux is inherently more secure than Windows, but it isn't so much > more secure that only 1% of all viruses can attack it. Virus > developers don't have a financial incentive to develop Linux viruses > (not enough Linux users, most Linux users knowledgeable about > computers, and moral reasons). > moral reasons... you just made my day
Re: [gentoo-user] Linux viruses
On Jul 12, 2013 4:32 PM, "Volker Armin Hemmann" wrote: > > Am 12.07.2013 18:36, schrieb Timur Aydin: > > On 7/5/2013 11:12 PM, Dale wrote: > >> I since did some googling and it seems I am right and he just thought I > >> was some know nothing guy he could sell some service too. Anyway, has > >> anything changed to make Linux more prone to viruses than it used to > >> be? I read a percentage somewhere that said like 99% of viruses are > >> windoze only. Is there a indisputable source of information on this? > > > > Linux is inherently more secure than Windows, but it isn't so much > > more secure that only 1% of all viruses can attack it. Virus > > developers don't have a financial incentive to develop Linux viruses > > (not enough Linux users, most Linux users knowledgeable about > > computers, and moral reasons). > > > moral reasons... you just made my day > Yeah, that made me think back to a reddit AMA with a guy who ran a botnet and everyone kept asking him about morals.
Re: [gentoo-user] pop up windows with text message
On 07/11/13 09:28, Neil Bothwick wrote: On Wed, 10 Jul 2013 20:48:22 -0600, Joseph wrote: Thanks Alan, yes I'm looking into it and your are the second person who suggested to me "inotify" is the tool for the job. I've installed inotify-tools but I think I will need to find more samples to make it to work :-) Try incron, it uses the kernel's inotify functions but does the work for you, and it comes with plenty of examples. Once I copy the file, the system should notify a use that new file exist (a message pop-up). If the use closes the message and will not open the file, after few ours I want to remind the user that the file has not been open yet. incron could launch one script you when the file is created. This would send the notification and create an at job to send another notification after a specified time. Then you could have another icrond task triggered by the file being opened for read, that kills the at job -- Neil Bothwick God is real, unless specifically declared integer. I found "gxmessage" it is very simple and perfect for pop-up message on the other computer. -- Joseph
[gentoo-user] Removing excessive stuff from profile
Hi all, I have recently purchased a cubieboard: http://cubieboard.org/ which is an ARM device with SATA. It is going to become a low power media server. I have followed the instructions on getting Gentoo onto it as outlined here: pluto.blogspot.com.au Monday March 18, 2013 I get a working system up and happening when I do the first boot. I then do the profile selection as listed but there are no server profiles, all basically desktop orientated. I chose 27 as suggested but when I do the emerge --pretend -NuD world I get an emerge that has over 250 items and includes things such as cups, libraries for image viewing etc etc, all stuff fine for a desktop but just additional stuff that my little server won't need. So my question is, what files do I have to fiddle to stop portage from wanting to install all of these additional files? I've looked in the world file and there is basically nothing there so I'm guessing it's in the profile somewhere - but just where? Any thought, greatly appreciated, Andrew
Re: [gentoo-user] strange eix-sync
Stroller [13-07-12 00:51]: > > On 11 July 2013, at 19:58, meino.cra...@gmx.de wrote: > > ... > > beaglebone:/root>Krm -v > > rm: remove regular empty file ‘/tmp/foobar123’? yes > > removed ‘/tmp/foobar123’ > > ... > > > > Everything was done as root. > > I think this is the output of `rm -vi $file` not `rm -v $file` - this > suggests you have at least one alias enabled. > > This is probably a red herring, but I would try everything again ensuring no > aliases or other user shell customisations enabled. > > Stroller. > > How can I pratically proof the availability of xattr on the filesystem of /tmp -- beside checking the kernel config. "From the point of view of rsync" -- so to say? After this update it stops working. In the meanwhile I had reinstalled all old versions with no success 1373166229: Started emerge on: Jul 07, 2013 05:03:48 1373166229: *** emerge --oneshot --keep-going --verbose =sys-fs/dosfstools-3.0.20-r1 =net-misc/rsync-3.0.9-r3 =app-admin/eselect-1.3.6 =net-misc/ntp-4.2.6_p5-r3 =virtual/udev-200 1373166331: >>> emerge (1 of 5) sys-fs/dosfstools-3.0.20-r1 to / 1373166332: === (1 of 5) Cleaning (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166333: === (1 of 5) Compiling/Merging (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166409: === (1 of 5) Merging (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166432: >>> AUTOCLEAN: sys-fs/dosfstools:0 1373166432: === Unmerging... (sys-fs/dosfstools-3.0.20) 1373166447: >>> unmerge success: sys-fs/dosfstools-3.0.20 1373166465: === (1 of 5) Post-Build Cleaning (sys-fs/dosfstools-3.0.20-r1::/usr/portage/sys-fs/dosfstools/dosfstools-3.0.20-r1.ebuild) 1373166465: ::: completed emerge (1 of 5) sys-fs/dosfstools-3.0.20-r1 to / 1373166465: >>> emerge (2 of 5) net-misc/rsync-3.0.9-r3 to / 1373166465: === (2 of 5) Cleaning (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166466: === (2 of 5) Compiling/Merging (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166811: === (2 of 5) Merging (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166828: >>> AUTOCLEAN: net-misc/rsync:0 1373166828: === Unmerging... (net-misc/rsync-3.0.9-r2) 1373166843: >>> unmerge success: net-misc/rsync-3.0.9-r2 1373166861: === (2 of 5) Post-Build Cleaning (net-misc/rsync-3.0.9-r3::/usr/portage/net-misc/rsync/rsync-3.0.9-r3.ebuild) 1373166861: ::: completed emerge (2 of 5) net-misc/rsync-3.0.9-r3 to / 1373166861: >>> emerge (3 of 5) app-admin/eselect-1.3.6 to / 1373166861: === (3 of 5) Cleaning (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166862: === (3 of 5) Compiling/Merging (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166904: === (3 of 5) Merging (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166929: >>> AUTOCLEAN: app-admin/eselect:0 1373166929: === Unmerging... (app-admin/eselect-1.3.5) 1373166944: >>> unmerge success: app-admin/eselect-1.3.5 1373166960: === (3 of 5) Post-Build Cleaning (app-admin/eselect-1.3.6::/usr/portage/app-admin/eselect/eselect-1.3.6.ebuild) 1373166960: ::: completed emerge (3 of 5) app-admin/eselect-1.3.6 to / 1373166961: >>> emerge (4 of 5) net-misc/ntp-4.2.6_p5-r3 to / 1373166961: === (4 of 5) Cleaning (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373166963: === (4 of 5) Compiling/Merging (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167738: === (4 of 5) Merging (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167774: >>> AUTOCLEAN: net-misc/ntp:0 1373167774: === Unmerging... (net-misc/ntp-4.2.6_p5-r2) 1373167792: >>> unmerge success: net-misc/ntp-4.2.6_p5-r2 1373167815: === (4 of 5) Post-Build Cleaning (net-misc/ntp-4.2.6_p5-r3::/usr/portage/net-misc/ntp/ntp-4.2.6_p5-r3.ebuild) 1373167815: ::: completed emerge (4 of 5) net-misc/ntp-4.2.6_p5-r3 to / 1373167816: >>> emerge (5 of 5) virtual/udev-200 to / 1373167816: === (5 of 5) Cleaning (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167816: === (5 of 5) Compiling/Merging (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167841: === (5 of 5) Merging (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167855: >>> AUTOCLEAN: virtual/udev:0 1373167855: === Unmerging... (virtual/udev-197-r3) 1373167870: >>> unmerge success: virtual/udev-197-r3 1373167888: === (5 of 5) Post-Build Cleaning (virtual/udev-200::/usr/portage/virtual/udev/udev-200.ebuild) 1373167888: ::: completed emerge (5 of 5) virtual/udev-200 to / 1373167888: *** Finished. Cleaning up... 1373167905: *** exiting successfully. 1373167914: *** terminating. 1373248019: Started emerge
