Re: [gentoo-user] Re: Switching from eudev to udev, disaster.

2021-12-01 Thread Grant Taylor

On 12/1/21 10:02 AM, Grant Edwards wrote:
IIRC, there are situations where using udev rules to rename them 
"ethN" based on MAC addresses will fail because that can conflict 
with the low-level kernel names. Or something like that.


I don't think I ever ran into a problem re-using the original kernel 
eth# names /as/ /long/ /as/ the target name wasn't currently in use. 
Sometimes I needed to vacate the target name before I could re-use it.




--
Grant. . . .
unix || die



[gentoo-user] Re: Switching from eudev to udev, disaster.

2021-12-01 Thread Grant Edwards
On 2021-11-30, Grant Taylor  wrote:

> I guess I never really gave the renaming much thought because I
> almost always complied drivers into the kernel, which meant that
> they had a consistent ~> predictable enumeration and naming order.

I think that's generally true on most motherboards for PCI
devices. Possibly not so much for USB.

--
Grant







[gentoo-user] Re: Switching from eudev to udev, disaster.

2021-12-01 Thread Grant Edwards
On 2021-11-30, Grant Taylor  wrote:

> Besides, it's a LOT easier to /just/ `tcpdump -nni eth0` when logging 
> into a machine than it is to have to figure out the interface name first.

Yep. I always add udev rules to rename the boards net0, net1, etc.
based don the MAC addresses.

> That being said, I was okay with what CentOS 6.x did, where the new name 
> was matched against the MAC address.  I had eth0 based on MAC for 
> outside and eth1 based on MAC for inside on a number of systems.

IIRC, there are situations where using udev rules to rename them
"ethN" based on MAC addresses will fail because that can conflict with
the low-level kernel names. Or something like that.

--
Grant (the other one)





[gentoo-user] Re: Switching from eudev to udev, disaster.

2021-11-29 Thread Grant Edwards
On 2021-11-30, tastytea  wrote:
> On 2021-11-29 22:47-0600 Dale  wrote:
>
>> Now if I can figure out how to reset the list of /dev/sd* names that
>> are lurking about and inconsistent, that would be like striking gold.
>>  Every time I hook up my external drive, it gets a different sd*
>> name.  It does the same on the SD cards from my trail cameras too but
>> I can auto mount those. 
>
> I don't think it is possible to get consistent sd* names for removable
> media.

You can write udev rules that trigger on the manufacturer, model, and
serial numbers. You can then assign consistent symlinks or even mount
them in predictable locations in the udev rules. I don't remember if
you can change the actual sd* names themselves, but there's no real
need to do so.

> But you could use volume labels with `tune2fs -L` or `tune.exfat
> -L` or `fatlabel` and then mount them via /dev/disk/by-label/*.