Re: [gentoo-user] ignore previous msg (Hotplugging not working)
On 31 Aug 2010, at 01:31, Allan Gottlieb wrote: Jake Moe writes: On 31/08/10 06:57, Allan Gottlieb wrote: I plugged into the desktop and looked on the laptop. Sorry for the noise, allan Whups, only looked at the previous thread, didn't see this. Probably best if you reply to the thread with stuff like this, so we can keep track of it. I thought of that. The problem is that there is quite a delay between my sending the msg and seeing it appear in the newsgroup. I wanted to tell people right away to prevent wasted effort. Perhaps I should have "replied" to my local copy (gnus GCC), but then the references would not be right in the newsgroup. Replying to the copy in your sent items should cause the reply to show properly in thread. The recipients' mail client should thread based the Message-Id: and References: headers. I paused before clicking send on this message, thinking that the Message-Id: might be added by your mail server, however looking in my sent items I find it to be added by the client (or by my client, at least) and a grep finds this header to be preserved when the message arrived to the list. Stroller.
Re: [gentoo-user] help with Persistent hard disk device names with udev
Hi, after following your tips the code gets like the following one:
SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda"
SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb"
SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc"
SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda%n"
KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda%n"
KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n"
KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc%n"
KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9VP0SBVN", NAME="sdc%n"
That's not working, when i plug more devices they get named without
taking care of the rules above. Do someone know why? thanks. i would
like to be able to name devies using its serial number. Thanks in
advanced
2010/8/30 Pau Peris :
> Thx a lot!
>
> 2010/8/30 J. Roeleveld :
>> On Monday 30 August 2010 15:00:28 Pau Peris wrote:
>>> Hi, i would like to give persistent device names to the system hard
>>> drives (just renaming its original device name to the one i want using
>>> its serial number as identifier). I've created the following rules
>>> which are not currently working. I'm trying to use device serial
>>> numbers to properly set its device name. One of the main reasons for
>>> doing that is i have a RAID composed by 3 disk (let's say sda sdc sdd)
>>> and when i plug another 4 disks sda becomes sde, sdc becomes sdg and
>>> so on while new drives take old device names, that's why i would like
>>> to make it sure device names remains always the same.
>>> Here are the rules
>>> Código:
>>>
>>> SUBSYSTEM=="block", ATTR{serial}="VNVB05G2RKTRZH", NAME="hda"
>>> SUBSYSTEM=="block", ATTR{serial}="9QK0T4WM", NAME="sda"
>>> SUBSYSTEM=="block", ATTR{serial}="3QD0X58D", NAME="sdb"
>>> SUBSYSTEM=="block", ATTR{serial}="9QK0RS9G", NAME="sdc"
>>> SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
>>>
>>> KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}="VNVB05G2RKTRZH",
>>> NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}="9QK0T4WM",
>>> NAME="sda%n" KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}="3QD0X58D",
>>> NAME="sdb%n" KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}="9QK0RS9G",
>>> NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN",
>>> NAME="sdc%n"
>>>
>>> Should this work? Do some one know how can i get it to work? thanks in
>>> advanced
>>
>> Hi,
>>
>> You need to use double "=" for all the fields you want to match.
>> In other words, for sda, you need to use:
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
>> instead of:
>>> SUBSYSTEM=="block", ATTR{serial}="9QK0T4WM", NAME="sda"
>>
>> Otherwise it doesn't match it correctly or will try to change the serial for
>> the all the block-devices it finds.
>>
>> (I found this out when trying to rename my network-interfaces)
>>
>> --
>> Joost
>>
>>
>
Re: [gentoo-user] help with Persistent hard disk device names with udev
Pau Peris writes:
> Hi, after following your tips the code gets like the following one:
>
> SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda"
> SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb"
> SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc"
> SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
>
> KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH",
> NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block",
> ATTR{serial}=="9QK0T4WM", NAME="sda%n" KERNEL=="sd*",
> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n"
> KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G",
> NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block",
> ATTR{serial}=="9VP0SBVN", NAME="sdc%n" That's not working, when i plug
> more devices they get named without taking care of the rules above. Do
> someone know why? thanks. i would like to be able to name devies using
> its serial number. Thanks in advanced
Could it be that the sd* notation is somewhere hardwired in UDEV? I'd try
to give the devices different names, like NAME="myhda", and so on.
Just guessing,
Wonko
Re: [gentoo-user] help with Persistent hard disk device names with udev
Alex Schuster wrote:
Pau Peris writes:
Hi, after following your tips the code gets like the following one:
SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda"
SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb"
SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc"
SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH",
NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block",
ATTR{serial}=="9QK0T4WM", NAME="sda%n" KERNEL=="sd*",
SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n"
KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G",
NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block",
ATTR{serial}=="9VP0SBVN", NAME="sdc%n" That's not working, when i plug
more devices they get named without taking care of the rules above. Do
someone know why? thanks. i would like to be able to name devies using
its serial number. Thanks in advanced
Could it be that the sd* notation is somewhere hardwired in UDEV? I'd try
to give the devices different names, like NAME="myhda", and so on.
Just guessing,
Wonko
This is a shot in the dark but just in case. What did you name the
rules file? Is it possible that it is reading your file then reading
another file udev generated and the last one it reads is the one that
sets the names? I would look to see if there is another file in the
rules.d directory that sets the naming and then see what udev reads last.
Again, shot in the dark and this may not apply.
Dale
:-) :-)
[gentoo-user] Proper way of updating mysql from 5.0.90-r2 to 5.1.50?
Hi, what is the proper way of updating mysql? I did it as with any other package, following this sequence: emerge --ask --update --deep --newuse world [ebuild N] net-misc/curl-7.20.0-r2 USE="idn ipv6 ssl -ares -gnutls -kerberos -ldap -libssh2 -nss -test" [ebuild N] dev-util/cmake-2.8.1-r2 USE="ncurses -emacs -qt4 -vim-syntax" [ebuild U ] dev-db/mysql-5.1.50 [5.0.90-r2] USE="-pbxt% -xtradb%" [ebuild U ] virtual/mysql-5.1 [5.0] emerge --depclean revdep-rebuild /etc/init.d/mysqld stop /etc/init.d/mysqld start But this is apparently not the proper way, because after restarting the server, apache does not show my web-page reporting there is no such a database. I checked it with phpmyadmin, and really, there is absolutely no database in mysql! I quickly restored backup version which I have done just before trying mysql-update, so my web-site is up and running. Now I would like to update mysql the right way, I but do not know how to do it... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] Proper way of updating mysql from 5.0.90-r2 to 5.1.50?
On Tuesday 31 August 2010 18:32:04 Jarry wrote: > Hi, > what is the proper way of updating mysql? I did it as with > any other package, following this sequence: > > emerge --ask --update --deep --newuse world > [ebuild N] net-misc/curl-7.20.0-r2 USE="idn ipv6 ssl -ares -gnutls > -kerberos -ldap -libssh2 -nss -test" > [ebuild N] dev-util/cmake-2.8.1-r2 USE="ncurses -emacs -qt4 > -vim-syntax" > [ebuild U ] dev-db/mysql-5.1.50 [5.0.90-r2] USE="-pbxt% -xtradb%" > [ebuild U ] virtual/mysql-5.1 [5.0] > emerge --depclean > revdep-rebuild > /etc/init.d/mysqld stop > /etc/init.d/mysqld start > > But this is apparently not the proper way, because after > restarting the server, apache does not show my web-page > reporting there is no such a database. I checked it with > phpmyadmin, and really, there is absolutely no database > in mysql! > > I quickly restored backup version which I have done just > before trying mysql-update, so my web-site is up and running. > Now I would like to update mysql the right way, I but do not > know how to do it... Hi Jarry, Some years ago I ran into some similar problem, I can't recall exactly what. Lost in folklore (wiki?) were some instructions to first stop mysql before you update it and I have been following them since. I stop apach & mysql, run the update, dispatch-conf and then restart them both. Haven't had problems since. There may be a better way for doing this - in which case others who know better will hopefully chime in. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] ignore previous msg (Hotplugging not working)
Stroller writes: > On 31 Aug 2010, at 01:31, Allan Gottlieb wrote: > >> Perhaps I should have "replied" to my local copy (gnus GCC), but then >> the references would not be right in the newsgroup. > > Replying to the copy in your sent items should cause the reply to show > properly in thread. > > The recipients' mail client should thread based the Message-Id: and > References: headers. > > I paused before clicking send on this message, thinking that the > Message-Id: might be added by your mail server, however looking in my > sent items I find it to be added by the client (or by my client, at > least) and a grep finds this header to be preserved when the message > arrived to the list. I hadn't realized this. Just to be sure, I will send in a few minutes a reply to my local copy (Gnus GCC) of the first msg. You are probable right as I should have realized that gnus will, as usual, do the right thing. allan
[gentoo-user] Re: "hotplugging" usb devices no longer working
Allan Gottlieb writes: > I have a sansa MP3 player and a Flip Video. Each plugs in as a usb > device and presents as a fat file system. This is a test. Please ignore (see prev msg for explanation). allan
Re: [gentoo-user] help with Persistent hard disk device names with udev
Hi, thanks a lot for the answers. The name of the rules file is
00_whatever.rules, as far as i know there's also an option which
prevents to modifye the setted rules. Well, if no one knows how to do
i will try to find a different solution.
2010/8/31 Dale :
> Alex Schuster wrote:
>>
>> Pau Peris writes:
>>
>>
>>>
>>> Hi, after following your tips the code gets like the following one:
>>>
>>> SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH", NAME="hda"
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0T4WM", NAME="sda"
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb"
>>> SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G", NAME="sdc"
>>> SUBSYSTEM=="block", ATTR{serial}="9VP0SBVN", NAME="sdc"
>>>
>>> KERNEL=="hd*", SUBSYSTEM=="block", ATTR{serial}=="VNVB05G2RKTRZH",
>>> NAME="hda%n" KERNEL=="sd*", SUBSYSTEM=="block",
>>> ATTR{serial}=="9QK0T4WM", NAME="sda%n" KERNEL=="sd*",
>>> SUBSYSTEM=="block", ATTR{serial}=="3QD0X58D", NAME="sdb%n"
>>> KERNEL=="sd*", SUBSYSTEM=="block", ATTR{serial}=="9QK0RS9G",
>>> NAME="sdc%n" KERNEL=="sd*", SUBSYSTEM=="block",
>>> ATTR{serial}=="9VP0SBVN", NAME="sdc%n" That's not working, when i plug
>>> more devices they get named without taking care of the rules above. Do
>>> someone know why? thanks. i would like to be able to name devies using
>>> its serial number. Thanks in advanced
>>>
>>
>> Could it be that the sd* notation is somewhere hardwired in UDEV? I'd try
>> to give the devices different names, like NAME="myhda", and so on.
>>
>> Just guessing,
>>
>> Wonko
>>
>>
>
> This is a shot in the dark but just in case. What did you name the rules
> file? Is it possible that it is reading your file then reading another file
> udev generated and the last one it reads is the one that sets the names? I
> would look to see if there is another file in the rules.d directory that
> sets the naming and then see what udev reads last.
>
> Again, shot in the dark and this may not apply.
>
> Dale
>
> :-) :-)
>
>
Re: [gentoo-user] Re: Old IDE drives and the "newer" PATA kernel drivers
Nikos Chantziaras wrote: On 08/27/2010 12:49 PM, Dale wrote: Is there a way to boot a Gentoo/Knoppix CD and make it use the PATA drivers? That way I can boot it and see exactly how it will name them and what drive is what without actually changing anything at all. Is there a boot option "noide" or some other switch I can use? You do the labeling *before* you switch to the new kernel. Once you get it working correctly with your current kernel, then you can upgrade to the new ATA drivers and it will just work (which is the whole point of this exercise.) OK. Finally got updated to a new kernel. I had some trouble with my sensors but after a bit of googling I found a workaround. It appears that the kernel folks are trying to fix one thing and broke something else. lol Progress. Anyway, this did sort of work out to be weird and not what I expected at all. I expected the drives to be laid out in this way: sda first drive with old ide sdb second drive with old ide sdc third drive with old ide sdd forth drive with a SATA controller Well, it actually sees the drive connected to the SATA controller first then the other drives follow along after that in order. Naturally when I first tried to boot I was pointing to sda6 for my root partition. Well, it was actually on sdb6. It did list the drives just before the error and the blinking lights on the keyboard. No scroll back either. :-( I saw just enough to be able to figure out what drives were what. Is there some way to get it to change this or am I stuck? My concern is that I plan to add another drive to the SATA card soon and that will move everything up another notch. I would really like the IDE drives to be seen first since I rarely change them. Still thinking about getting grub to see labels. That would help too. Actually, that would be a good fix too. Thanks. Dale :-) :-)
Re: [gentoo-user] Re: "hotplugging" usb devices no longer working
Had this problem too. Not sure if this suits your case. Have you tried using UUID in place of /dev/sdx? Use blkid to get the UUID for the device and replace /dev/sdx in fstab. On 8/31/10, Allan Gottlieb wrote: > Allan Gottlieb writes: > >> I have a sansa MP3 player and a Flip Video. Each plugs in as a usb >> device and presents as a fat file system. > > This is a test. Please ignore (see prev msg for explanation). > allan > >
[gentoo-user] Thunderbird and IMAP folders
I decided to give thunderbird (and its integrated calendar, lightning) a try after having some troubles with kontact corrupting and deleting events on a webdav calendar. I initially tried thunderbird 3.0.4 (which I think didn't actually have the calendar integrated--not really significant), and had trouble getting TB to display the contents of my email folders on an IMAP server. Most folders showed up empty. I have about 180 folders with about 14,000 messages total--the correct folders were shown, just nothing shown in them. After a bit of googling, I found a reference to a bug resembling my problem that supposedly was fixed in 3.1.2. I tried that version without change to the problem, and today 3.1.2-r1 with the same result. My IMAP server is net-mail/courier-imap 4.5.0 on the same host as my workstation. I have no trouble reading folders and their contents with kontact 4.4.5/kmail 1.13.5 I've tried more googling and searching at the mozilla.org site for clues. Anyone have any experience with this problem--and perhaps a solution? TIA, -- Jim signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: Old IDE drives and the "newer" PATA kernel drivers
On 09/01/2010 03:38 AM, Dale wrote: Nikos Chantziaras wrote: On 08/27/2010 12:49 PM, Dale wrote: Is there a way to boot a Gentoo/Knoppix CD and make it use the PATA drivers? That way I can boot it and see exactly how it will name them and what drive is what without actually changing anything at all. Is there a boot option "noide" or some other switch I can use? You do the labeling *before* you switch to the new kernel. Once you get it working correctly with your current kernel, then you can upgrade to the new ATA drivers and it will just work (which is the whole point of this exercise.) OK. Finally got updated to a new kernel. [...] Anyway, this did sort of work out to be weird and not what I expected at all. I expected the drives to be laid out in this way: sda first drive with old ide sdb second drive with old ide sdc third drive with old ide sdd forth drive with a SATA controller Well, it actually sees the drive connected to the SATA controller first then the other drives follow along after that in order. I mentioned this in a reply :P Usually SATA drives go first. (Emphasis on "usually.") Naturally when I first tried to boot I was pointing to sda6 for my root partition. Well, it was actually on sdb6. It did list the drives just before the error and the blinking lights on the keyboard. No scroll back either. :-( I saw just enough to be able to figure out what drives were what. Is there some way to get it to change this or am I stuck? My concern is that I plan to add another drive to the SATA card soon and that will move everything up another notch. I would really like the IDE drives to be seen first since I rarely change them. What exactly is the problem you have? You can't boot? You can simply hit "Esc" in grub and go to text-only mode, and then "e" to edit the current grub boot entry. There you can boot from somewhere else.
