On 12/31/06, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
On Sunday 31 December 2006 13:12, Richard Fish [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] USB freezes the machine...':
On 12/31/06, Marco Calviani [EMAIL PROTECTED] wrote:
some days ago i've upgraded to udev-103 (stable
gotcha. Thanks for the info.
Shawn
On 1/5/07, Ryan Sims [EMAIL PROTECTED] wrote:
On 1/5/07, Shawn Singh [EMAIL PROTECTED] wrote:
[snip]
[blocks B ] sys-apps/coldplug (is blocking sys-fs/udev-103)
I can't emerge: sys-fs/udev-103 or udev-103 b/c that's not a valid
package
atom
locate that file on my system...
carcharias linux # equery belongs
/etc/udev/rules.d/60-persistent-storage.rules
[ Searching for file(s) /etc/udev/rules.d/60-persistent-storage.rules in *...
]
sys-fs/udev-096-r1 (/etc/udev/rules.d/60-persistent-storage.rules)
HTH,
-Richard
--
gentoo
On Sat, Aug 19, 2006 at 01:59:36PM -0700, Penguin Lover Richard Fish squawked:
Hrm, we can only hope that the API between the kernel and udev
stabilizes in the future. It really should _not_ be necessary to
change kernel versions when upgrading udev or vice-versa.
Now that you mentioned
been taken over by udev. There have been issues on and off of
conflicts between udev and the hotplug package, but nothing current
that I am aware of.
You can't mount itwhy? Is there no device being created?
udevmonitor may help to figure out why...
I remember some discussion about hotplug
On Friday 25 August 2006 22:06, Richard Fish wrote:
Yeah, udev = 089 blocks coldplug, so the init script should have been
removed, assuming you have upgraded to udev = 089.
OK, I'm still on stable: sys-fs/udev-087-r1
carcharias rjf # emerge --info | grep CONFIG_PROTECT
CONFIG_PROTECT=/etc
dmesg
Ben
- Original Message
From: Michael Sullivan msulli1...@gmail.com
To: gentoo-user gentoo-user@lists.gentoo.org
Sent: Mon, November 23, 2009 4:05:17 PM
Subject: [gentoo-user] udev (probably)
I've been working all day rearranging furniture in my apartment. I got
the my computer
I saw a message that said something about some kernel option that was
turned on that shouldn't be, and that udev might not work.
I found it in /var/log/messages. It said:
Nov 23 15:37:07 camille kernel: udev: missing sysfs features; please
update the kernel or disable the kernel's
as udev will not name them that way
Actually, yes - it is a 2003 Dell D600 with a standard ATA/IDE hard drive.
So yes - it would be /dev/hda; and yes, udev has been working fine until
this issue.
For quite some time now IDE drives have been handled below the SCSI subsytem
so you do in fact get
G'day,
I've been running baselayout-2 for several months and it's been working
fine AFAICT. Over the weekend I noticed that my USB thumb drive is no
longer automounting.
This evening I ran /etc/init.d/udev status which reported:
* status: stopped.
Running /etc/init.d/udev start reported
ubiquitous1980 schrieb am 24.04.2010 07:29:
why has moving /etc/udev/rules.d/40-hplip.rules to
/etc/udev/rules.d/71-hplip.rules and
/etc/udev/rules.d/55-hpmud_support.rules to
/etc/udev/rules.d/71-hpmud_support.rules changed the group from scanner
to lp for file: /dev/bus/usb/005/005
on the keyboard are not detected.
When I enable it, everything works but several driver packages (evdev
and mouse, probably others) want me to deactivate it.
[...]
So many softwares that used hal before are or have
migrated to something else, such as udev. Xorg has also chosen to do
this, and so
like to make it automatic by creating an udev rule, so
when I plug in that device the swap space is automatically activated
and the priority is changed.
Create the udev rule in the usual way and add
RUN=/path/to/your/script
You must use a full path when running a program from a udev rule
So, it solves the first problem, identifiying the device, but how can I tell
to udev to use always /dev/sds (for example) for this device? Also I'm
thinking how can I instruct udev to turn off swap when the device is
removed, but this is another story :)
Thanks
L:
2010/7/1 Neil Bothwick n
tor 2010-07-01 klockan 08:49 -0700 skrev Bill Longman:
On 07/01/2010 08:44 AM, SpaceCake wrote:
So, it solves the first problem, identifiying the device, but how can I
tell to udev to use always /dev/sds (for example) for this device?
You need to have the udev rule or the script that it runs
the following
line in dmesg's log:
udev: renaming etho to eth1
There is only the onboard lan chip and no extra ethernet
card is installed in the rig.
Now I have eth1 and no eth0.
Why does this happen? What is the reason for that?
Most likely they have different MACs
On Sat, Feb 19, 2011 at 12:35 PM, Nikos Chantziaras rea...@arcor.de wrote:
On 02/19/2011 10:14 PM, Mark Knecht wrote:
SNIP
Should I be enabling udev globally in make.conf? I'm currently not. I
do have it on xorg-server so I'm not seeing the OP's issue, but I
never wanted to get into making my
Hello,
I just have one question, reciently I read in a forum that HAL might be
deprecated on Gentoo, so, I started using UDEV:
USE= -hal udev
But, then I have this problem, updating xorg-server won't work, every new
version of xorg-server just give me a blank screen, so I thought it might
On Wed, Sep 14 2011, Michael Mol wrote:
On Wed, Sep 14, 2011 at 11:36 AM, Neil Bothwick n...@digimed.co.uk wrote:
On Wed, 14 Sep 2011 10:49:29 -0400, Michael Mol wrote:
Trust me, you would want to run a udev that contained any code
written by me!
No offense man, but I don't know you
On Thu, 15 Sep 2011 17:37:53 +0200, Joost Roeleveld wrote:
There are 3 solutions for this:
1) The easy way out: the whole user-space must be available before udev
2) udev actually includes correct error-handling for this and retries
3) udev splits this into 2 seperate tools
4) udev remains
Some fool wrote:
Following the debates over the summer, about plans to require an
initramfs for udev, I put together a slightly different approach using
the dependency tracking in openrc. It's outlined (in Unsupported Software)
at: http://forums.gentoo.org/viewtopic-p-6866484.html
Just
The 03/01/12, Pandu Poluan wrote:
But I can see a use case for mdev completely replacing udev: servers and
virtual machines.
Servers, especially production ones, have a hardware change only once in
every two blue moons. They don't need all the bells and whistles of udev
On Thu, 5 Jan 2012 11:01:49 +0100, Nicolas Sebrecht wrote:
You might like it or not but udev is a core system tool, nowadays.
Yes, today. It wasn't yesterday and it may not be tomorrow. I like udev,
but I do not like the direction it is taking. I am not alone in this and
there may be a critical
lvm2, kde, and gnome (including
the XFCE subset) require udev. Ouch.
:-) This cannot be the case. Otherwise somebody would have said. Hmm.
What we could do with is a requires xdev, for x in (m u). I've
forgotten what that's called in portage.
There are surely lots of packages marked need udev
.
This post here:
http://lists.busybox.net/pipermail/busybox/2011-September/076662.html
seems to indicate that Xorg communicates with udev (something mdev can't
do, because that would increase the complexity of mdev by several orders of
magnitude).
BUT, in the same message, it is stated that Xorg *can
Hi there!
emerge --update --newuse @world wants to re-install sys-fs/udev-182 due
to changed USE flags (static-libs), but this package just failed to
compile because of file collisions.
* package sys-fs/udev-182 NOT merged
*
* Detected file collision(s):
*
* /usr/share/gtk-doc/html
, required by @world (argument) =sys-fs/udev-
**
Mask =sys-auth/consolekit-0.4.5-r3
% cat /etc/portage/package.mask/udev-181
=sys-fs/udev-181
=sys-auth/consolekit-0.4.5-r3
Thanks. Works fine (emerge in progress). I was too pessimistic and
assumed that anything that wanted me to unmaks
On 05/21/2012 03:27 PM, Michael Hampicke wrote:
I updated udev from 171-r5 to 171-r6 and now i get several udevd
boot message as : udevd[1389]: can not find
'/lib/udev/rules.d/90-network.rules': No such file or directory
udevd[1389]: can not find '/lib/udev/rules.d/95-keymap.rules
Hi,
After upgrading to udev-186 I saw some errors when the service was restarted:
Jul 9 14:54:57 virtual udevd[30356]: unknown key 'RUN{builtin}' in
/lib/udev/rules.d/80-drivers.rules:10
Jul 9 14:54:57 virtual udevd[30356]: invalid rule
'/lib/udev/rules.d/80-drivers.rules:10'
Jul 9 14:54:57
I also had those errors and I successfully rebooted (didn't get the
errors on the next boot).
Good luck,
--Brennan
On Mon, Jul 9, 2012 at 3:38 PM, Paul Hartman
paul.hartman+gen...@gmail.com wrote:
Hi,
After upgrading to udev-186 I saw some errors when the service was restarted:
Jul 9 14:54
On Mon, Sep 10, 2012 at 9:57 PM, Canek Peláez Valdés can...@gmail.com wrote:
On Mon, Sep 10, 2012 at 9:37 PM, Chris Stankevitz
chrisstankev...@gmail.com wrote:
[snip]
# 2012-09-10: appease thunar
xfce-base/thunar -udev
This makes no sense; the udev flag in thunar only asks for
=sys-fs/udev
want pulseaudio or systemd. Now it is forced
on everybody.
When systemd devs took over udev, one was told that of course, one could
use udev without [systemd] in the future.
Now they are talking about making udev systemd only.
obsolutly nonsense. what they remove , is the ability
is a valid reaction.
A
lot of people don't need nor want pulseaudio or systemd. Now it is
forced
on everybody.
When systemd devs took over udev, one was told that of course, one could
use udev without [systemd] in the future.
Now they are talking about making udev
. If it is also based on lies, hate is a
valid reaction. A lot of people don't need nor want pulseaudio or
systemd. Now it is forced on everybody.
When systemd devs took over udev, one was told that of course,
one could use udev without [systemd] in the future.
Now they are talking about
On Mon, Nov 12, 2012 at 09:20:42PM -0600, Dale wrote:
Well, it appears we have someone willing to fork udev. Yeppie !! Me, I'm
looking forward to seeing how this works and giving it a test run when it
gets ready. Since it is a fork, shouldn't be to long, I hope.
I wonder what
On 11/01/13 19:51, Stefan G. Weichinger wrote:
Am 11.01.2013 16:14, schrieb Nikos Chantziaras:
Running this command (all in one line):
emerge -p1 $(for p in $(qfile -Cvq $(find /usr/lib/udev/) | sort -u); do
echo =$p; done)
should re-emerge all packages that still have files there. After
On Fri, Jan 11, 2013 at 4:33 PM, Walter Dnes waltd...@waltdnes.org wrote:
On Fri, Jan 11, 2013 at 10:42:37AM -0600, Canek Pel??ez Vald??s wrote
No, because the problem has never been in udev (nor systemd, for that
matter). It fixes how *Gentoo* packages udev; probably the devs read
Hi, Gentoo!
After synching, I've got a whole lot of programs to emerge, amongst them
being udev-197. :-( I'd rather do this on its own, in peace and quiet,
rather than together with 12 or 13 other programs.
emerge -puND world generates these:
[ebuild U #] sys-fs/udev-197-r4 [171-r9
On Sun, Jan 20, 2013 at 10:22:24PM +, Alan Mackenzie wrote
emerge decided to install sys-fs/udisks-1.0.4-r4 (presumably this had
just become stable), and this had a dependency on
=virtual/udev-197[gudev,hwdb]
. So rather than refusing to merge udisks, it insisted on merging
udev
On Sun, 20 Jan 2013 16:57:59 +
Peter Humphrey pe...@humphrey.ukfsn.org wrote:
On Sunday 20 January 2013 08:51:43 Philip Webb wrote:
I just tried upgrading to udev-197 , which is supposed to be
stable. There were multiple problems I'm now back with udev-171 .
My daily update pulled
»Q« wrote:
Peter Humphrey pe...@humphrey.ukfsn.org wrote:
My daily update pulled in udev-197-r3. The installation went smoothly
but I decided I ought to reboot to check that I could. I couldn't.
Udev couldn't start because my kernel config didn't have
CONFIG_DEVTMPFS=y. So I booted my rescue
on 01/23/2013 04:41 AM »Q« wrote the following:
On Sun, 20 Jan 2013 16:57:59 +
Peter Humphrey pe...@humphrey.ukfsn.org wrote:
On Sunday 20 January 2013 08:51:43 Philip Webb wrote:
I just tried upgrading to udev-197 , which is supposed to be
stable. There were multiple problems I'm now
on 01/23/2013 01:10 PM Thanasis wrote the following:
on 01/23/2013 04:41 AM »Q« wrote the following:
On Sun, 20 Jan 2013 16:57:59 +
Peter Humphrey pe...@humphrey.ukfsn.org wrote:
On Sunday 20 January 2013 08:51:43 Philip Webb wrote:
I just tried upgrading to udev-197 , which is supposed
On Sat, Jan 26, 2013 at 6:15 PM, Florian Philipp li...@binarywings.net wrote:
Hi list!
Quick question: If I deactivate the kmod use flag in udev and keep
sys-apps/module-init-tools, does udev still load modules or is kmod a
required flag for that?
I'm not 100% sure, but I don't think so
Michael Mol writes:
So, I botched the upgrade to udev-191. I thought I'd followed the
steps, but I apparently only covered them for one machine, not both.
[...]
Udev also complained about DEVTMPFS not being enabled in the
kernel.[2] I couldn't get into X, but I could log in via getty
Ok, I sync'd this morning, and now see the warning about udev 171-r10
being masked, so I guess it is time..
I know this was discussed quite a bit a few months ago, but just to
refresh my memory...
My question is, if I am currently running 171-r10 on my server, and I
have a separate lvm
Am 25.03.2013 22:56, schrieb Mike Gilbert:
Try just emerge -v1 systemd. You no longer need sys-fs/udev, and it
should be removed when you upgrade to sys-apps/systemd-r5.
Oh, interesting. I understand. Is there any information somewhere on
this (no ranting! just asking for ... as other users
Am 26.03.2013 15:57, schrieb Mike Gilbert:
apcupsd-3.14.10-r1 still installs its rules into /lib/udev/rules.d
... the path is hard-coded in the ebuild (line 99).
Thanks, I have just committed a fix for that.
Great, my next question would have been if I should file a bug ... not
needed
On 03/27/2013 10:25 AM, Tanstaafl wrote:
Ok...
So, what is this all about?
Does all of this mean that udev is now going *completely* away,
*totally* replaced by systemd?
If so, has there been any kind of formal announcement about this
*anywhere*??
Hold your horses.
The devs will work
On 03/27/2013 10:33 AM, Michael Mol wrote:
On 03/27/2013 10:25 AM, Tanstaafl wrote:
Ok...
So, what is this all about?
Does all of this mean that udev is now going *completely* away,
*totally* replaced by systemd?
If so, has there been any kind of formal announcement about this
*anywhere
On Thu, Apr 04, 2013 at 12:41:26AM -0900, Jackie wrote:
Hello all,I was trying to reinstall gentoo on my PC and when I was
emerging gentoo-sources-3.8.5,sys-fs/udev-200 was required.However,after
installation of gentoo-sources,comlpilation of udev failed and there is no
output of error
I just did got udev updated. Did all the steps in the news:
1. tempfs in kernel
2. nothing in /etc/udev/rules.d
3. removed udev-postmount from runlevel
4) check fstab for the /tmp
And it changed!
This is the pits dude...
N.
On 4/7/13, Michael Hampicke gentoo-u...@hadt.biz wrote:
Am
For those that have an error compiling udev 200:
# emerge -1 XML-Parser
# perl-cleaner --all
There was not mention of this in the news. Nor will the package pull
them in as a
dependency.
N.
On 4/7/13, Nick Khamis sym...@gmail.com wrote:
Is changing it back to eth0 and eth1 like pulling teeth
to call it an ethernet *device*
[snip...]
For more info, research this list going back about 4 months. The whole
topic was discussed at length. Search for udev persistent names. A
word of warning - it wasn't pretty at the time and nothing changed just
becuase those mails are now archived :-)
Let's
On Wed, Jul 31, 2013 at 5:09 AM, Graham Murray gra...@gmurray.org.uk wrote:
Canek Peláez Valdés can...@gmail.com writes:
The wiki is wrong. The script /etc/init.d/udev is part of sys-fs/udev,
which you need to uninstall before installing systemd. Perhaps it's
CONFIG_PROTECT'd, but anyway sys
On Fri, 09 Aug 2013 08:45:47 -0400, Tanstaafl wrote:
No, the virtual is always needed, eudev satisfies it. but you do need
to make sure your USE settings for eudev and virtual/udev match.
Ok... so, as long as I don't have anything for either of them in
package.use, I'm ok
130825 Pavel Volkov suggested:
On Sunday 25 August 2013 20:26:32 meino.cra...@gmx.de asked:
So...which ghost in my system dares to set the symlink /dev/rtc
to point to /dev/rtc0 instead of /dev/rtc1 ???
I bet it's /usr/lib64/udev/rules.d/50-udev-default.rules
I have /usr/udev/rules.d/50
to change it?
My VituralBox complain and will not start with owner: root:dialout
/dev/ttyS0
It's a udev rule. Mine looks like this, tweak yours
$ grep -r uucp /lib/udev/rules.d/
/lib/udev/rules.d/50-udev-default.rules:KERNEL==tty[A-Z]*[0-9]|pppox[0-9]*|ircomm[0-9]*|noz[0-9]*|rfcomm[0-9]*,
GROUP
to previous setting: root:dialout 600
How to change it?
My VituralBox complain and will not start with owner: root:dialout
/dev/ttyS0
It's a udev rule. Mine looks like this, tweak yours
$ grep -r uucp /lib/udev/rules.d/
/lib/udev/rules.d/50-udev-default.rules:KERNEL==tty[A-Z]*[0-9]|pppox[0-9
/udisks
sys-power/upower
gnome-base/gvfs
But now I have a BIG problem, I can not mount USB stick at all as user
(only as root).
Eject doesn't work either.
fast reply off the top of the head of someone who has never used systemd:
Systemd and udev are tightly interwoven. Did you restart udev?
--
Alan
On 10/05/14 09:43, Mick wrote:
On Friday 09 May 2014 23:25:06 Neil Bothwick wrote:
On Fri, 9 May 2014 21:56:45 +0100, Mick wrote:
What is the meaning of this change?
[ebuild U ] sys-fs/udev-212-r1 [208] USE=acl firmware-loader
gudev introspection kmod -doc (-selinux) -static-libs
On Friday 06 Jun 2014 12:18:09 Rich Freeman wrote:
That would be udev. It has been around long before systemd, and you
must have missed the huge flamewar when they renamed it to
systemd-udevd. Maybe we'll see java renamed to
java-by-oracle-with-ask-toolbar next. :)
TBH I wouldn't
Am Sat, 13 Jun 2015 00:06:38 -0400
schrieb Valmor de Almeida val.gen...@gmail.com:
[...]
sys-fs/udev:0
(sys-fs/udev-216:0/0::gentoo, ebuild scheduled for merge) conflicts with
=sys-fs/udev-208-r1:0/0[abi_x86_64(-),gudev(-)] required by
(virtual/libgudev-215-r3:0/0::gentoo, installed
On Thu, Jun 09, 2016 at 08:16:57AM -0500, Dale wrote
> k...@aspodata.se wrote:
> > Dale:
> > ...
> >> Can a system even boot without udev?
> > Yes, use sys-fs/static-dev (unless you have some special boot
> > requirements).
>
> Well, I was talking a
s is the output from emerge:
[...]
> I switched mine back when eudev was new and not even stable yet. It
> was as simple as unmerge udev and emerge eudev. I don't recall even
> doing a reboot, which I rarely do here anyway.
THX for your answer.
That's also what I normally do in such a
s part of that update wants it. You have two choices:
1) Start uninstalling important stuff at random until either the
problem goes away or you break your system badly enough to need a
reinstall.
2) Use --tree to see exactly what is pulling in the blockers, and why,
then deal with that.
> ud
/ systemd or even supporting both) then it will not be
>> useful for me.
>>
> Checkrestart lists what services or programs are using outdated files
> after a upgrade. As a example, you upgrade udev and have not rebooted
> or restarted udev, checkrestart will list that udev is using
Neil Bothwick:
> On Tue, 20 Dec 2016 23:11:08 +0100, lee wrote:
> > >> But you already heard of udev rules? I guess I mentioned them
> > >> already. They are not so hard to write and they only need to be
> > >> written once.
> > > It's too late by
On Tuesday, 22 May 2018 00:13:31 BST Mike Gilbert wrote:
> On Sat, May 19, 2018 at 3:53 AM, Mick <michaelkintz...@gmail.com> wrote:
> > I noticed network related google variables being added in the compilation
> > by emerge as udev was being updated to 238 today:
[snip .
[2019-10-27 18:47] Dale
>
> part text/plain 30K
> Howdy,
Hi,
> I'm trying to do my weekly update. I use eudev but something seems to
> want plain udev and to remove eudev while at it. I have udev masked so
> emerge knows not to install it. This is wha
On 12/19/21 9:48 AM, Dale wrote:
> the...@sys-concept.com wrote:
>> Updating 3-months old system.
>> What should I watch for when it comes to updating from eudev to udev
>>
>> from the news file:
>> "If you DO NOT want the "predictable interface namin
the...@sys-concept.com wrote:
> Updating 3-months old system.
> What should I watch for when it comes to updating from eudev to udev
>
> from the news file:
> "If you DO NOT want the "predictable interface naming" of newer versions
> of udev and instead
that udev is now doing something different.
Has anyone else seen this of late?
I am set up as auto for the udev/devfs choice in /etc/conf.d/rc,
as well as not using a tarball. udev is up and running:
gigastudio ~ # ps aux | grep udev
root 854 0.0 0.0 1468 484
On Thu, 8 Sep 2011 19:34:56 -0400
Canek Peláez Valdés can...@gmail.com wrote:
You don't need every possible thing that udev could ever run to be
avialable on /, just the things that are essential. That is quite a
small list subset of the full list of all possible devices:
All HID
Canek Peláez Valdés can...@gmail.com
wrote:
snip
Fringe programs will not require udev, or it will be optional; but
the moment a fringe program reaches critical mass to become
maistream, the probability of it needing udev (directly or
indirectly) will increase.
I'm willing to bet
here. My response to his (IMO
needlessly aggressive) email was basically this:
Why *shouldn't I* be able to go but a Bluetooth keyboard and mouse if I
wanted to? Those things *work perfectly fine with udev*. And why wouldn't I
want to use the *same* solution for all of my various machines, even
Hi, Alan.
On Sun, Jan 20, 2013 at 11:18:40PM +0200, Alan McKinnon wrote:
On Sun, 20 Jan 2013 20:50:12 +
Alan Mackenzie a...@muc.de wrote:
Hi, Gentoo!
After synching, I've got a whole lot of programs to emerge, amongst
them being udev-197. :-( I'd rather do this on its own
Am Mon, 21 Jan 2013 21:56:00 -0600
schrieb »Q« boxc...@gmx.net:
udev-197-r3 gave me this postinstall warning:
Upstream has removed the persistent-cd rules generator. If you need
persistent names for these devices, place udev rules for them
in /etc/udev/rules.d.
Well, I have had
On 2013-02-15, Stefan G. Weichinger wrote:
Am 28.01.2013 00:00, schrieb Allan Gottlieb:
Thanks for all the suggestions. I did the following, which worked.
1. Built and installed kernel with CONFIG_DEVTMPFS=y
2. Moved udev-postmount back to /etc/init.d (I had moved it to /tmp).
rc
On 02/08/13 11:01, Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work as designed, not a
single valid bug filed about them.
Stop
On 12/08/2013 13:37, Tanstaafl wrote:
On 2013-08-12 6:48 AM, Alan McKinnon alan.mckin...@gmail.com wrote:
On 12/08/2013 12:19, Tanstaafl wrote:
Hmmm... so is it eudev that would need to be updated to 'fix' this? Or
virtual/udev? Or both?
It has to do with how virtuals work.
If you have
On Sat, 7 Dec 2013 09:40:13 +0100
Tom Wijsman tom...@gentoo.org wrote:
On Sat, 7 Dec 2013 07:32:09 +0100
meino.cra...@gmx.de wrote:
[blocks B ] sys-fs/udev (sys-fs/udev is blocking
sys-apps/systemd-208-r2)
Pick one or the other; you can use sys-apps/systemd without running
restart it goes back to previous setting: root:dialout 600
How to change it?
My VituralBox complain and will not start with owner: root:dialout
/dev/ttyS0
It's a udev rule. Mine looks like this, tweak yours
$ grep -r uucp /lib/udev/rules.d/
/lib/udev/rules.d/50-udev-default.rules:KERNEL==tty
y I get the following
> >>> [ebuild R *] sys-fs/zfs-::gentoo USE="rootfs -bash-completion
> >>> -custom-cflags -debug (-kernel-builtin) -static-libs -test-suite"
> >>> PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB
> >>&g
"rootfs -bash-completion
>>> -custom-cflags -debug (-kernel-builtin) -static-libs -test-suite"
>>> PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB
>>> [blocks B ] >=sys-fs/udev-init-scripts-28
>>> (">=sys-fs/udev-init-sc
On Wed, Dec 21, 2016 at 05:19:35PM -0800, Daniel Campbell wrote
> On Wed, Dec 21, 2016 at 07:53:51AM -0500, Rich Freeman wrote:
>
> > How do you think we ended up with eudev?
>
> I assume we ended up with eudev because upstream decided that
> they were going back on their pr
On 02/08/13 08:28, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 06:14, Dale wrote:
Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
Futhermore predictable network interface names work
On 5/22/05, Brett I. Holcomb [EMAIL PROTECTED] wrote:
Okay. That's not it. Here's what I have in /etc/conf.d/rc that pertains
to udev/devfs. I assume you have RC_DEVFSD_STARTUP set to no but what
about the tarball?
# Set to yes if you want to save /dev to a tarball on shutdown
Try the tarball no. It may be using the old devfs tarball.
On Sun, 22 May 2005, Mark Knecht wrote:
On 5/22/05, Brett I. Holcomb [EMAIL PROTECTED] wrote:
Okay. That's not it. Here's what I have in /etc/conf.d/rc that pertains
to udev/devfs. I assume you have RC_DEVFSD_STARTUP set
point of it is also relevant here. My response to his (IMO
needlessly aggressive) email was basically this:
Why *shouldn't I* be able to go but a Bluetooth keyboard and mouse if I
wanted to? Those things *work perfectly fine with udev*. And why wouldn't I
want to use the *same* solution for all
On 02/08/13 09:06, Alon Bar-Lev wrote:
On Fri, Aug 2, 2013 at 6:17 AM, William Kenworthy bi...@iinet.net.au wrote:
On 02/08/13 11:01, Samuli Suominen wrote:
On 02/08/13 05:48, Dale wrote:
Samuli Suominen wrote:
Huh? USE=firmware-loader is optional and enabled by default in
sys-fs/udev
in sys-fs/udev Futhermore predictable network interface names
work as designed, not a single valid bug filed about them.
Stop spreading FUD.
Looking forward to lastrite sys-fs/eudev just like
sys-apps/module-init-tools already was removed as unnecessary
later on.
So your real agenda
s {-test}" ABI_X86="(64) -32 (-x32)"
> 1.705 KiB
> [ebuild N ] dev-libs/libgudev-230::gentoo USE="-debug -introspection
> -static-libs" ABI_X86="(64) -32 (-x32)" 0 KiB
> [blocks B ] sys-fs/udev ("sys-fs/udev" is blocking sys-fs
On Wed, Sep 25 2013, walt wrote:
On 09/25/2013 03:24 PM, gottl...@nyu.edu wrote:
I want to downgrade systemd from 207-r2 to 204 (highest stable).
I currently have virtual/udev-206-r2 installed, which prevents
systemd-204.
OK. So I need to downgrade virtual/udev to 200.
I thought
On Sun, 11 Mar 2012 07:27:05 -0400 (EDT)
Daddy da...@happypenguincomputers.com wrote:
On March 11, 2012 at 5:09 AM Walter Dnes waltd...@waltdnes.org
wrote:
This revision makes 2 changes...
A) The removal of udev is now standard instead of optional.
udev-181 and higher
From: Alan McKinnon [mailto:alan.mckin...@gmail.com]
OK, semantics. Let me re-phrase:
Why is a third party script, running in the context of the udev universe,
indiscriminately allowed to launch daemons at early boot time?
I don't think I agree with Neil in that this is a udev design
On 12/17/05, Ernie Schroder [EMAIL PROTECTED] wrote:
I'm obviously looking in the wrong places, but I can't find documentation on
getting udev to start at boot. Sound and a few other things you don't notice
right away fail to work until I do:
# udevstart
/dev/dsp is created with correct
On a new system I built I had to recreate the /dev/nv* items.
From: Alexander Puchmayr [EMAIL PROTECTED]
Date: 2005/10/12 Wed AM 03:11:08 EDT
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev and nvidia
Am Dienstag, 11. Oktober 2005 13:51 schrieb [EMAIL PROTECTED
hi;
I upgraded to udev-070 recently (and now to udev-070-rc1).
Since then, I can't mount /mnt/cdrom properly.
Before, my /dev directory had a /dev/hdb, as well as /dev/hdb1,
/dev/hdb2 . Now, it only has /dev/hdb1, /dev/hdb2, but /dev/hdb is
no longer there. I still don't understand how
I've been running 2.6.10 for some time. Then I started reading some stuff
that I should update my Dell Inspiron 8200 notebook to UDEV. So I followed
the gentoo wiki page and used kernel 2.6.13. This caused (known) issues with
my nvidia driver and I couldn't get the USB mouse to work (yet the alps
701 - 800 of 8452 matches
Mail list logo
