On Feb 16, 2012, at 12:32 PM, Peter Lebbing wrote:
On 16/02/12 17:54, Rick Thomas wrote:
I tried it on a couple of Debian Squeeze machines and only saw
shm d
Which makes sense.
Correct, that is also what I see on Squeeze boxes.
What release are you running?
This is on Wheezy (testing
Grepping the debian udev source gives:
udev/udevd.c:
udev/udev-rules.c:
udev/udev-event.c:
/* set sticky bit, so we do not remove the node on module unload */
And in line 426-429 of udev/udev-node.c, version 175-3, function
int udev_node_remove(struct udev_device *dev):
if (stats.st_mode & 01000
On 16/02/12 17:54, Rick Thomas wrote:
>
> I tried it on a couple of Debian Squeeze machines and only saw
> shm d
> Which makes sense.
Correct, that is also what I see on Squeeze boxes.
> What release are you running?
This is on Wheezy (testing). This behaviour is relatively new in testing.
I tried it on a couple of Debian Squeeze machines and only saw
shm d
Which makes sense.
What release are you running?
Rick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://l
ost, what does the sticky bit on character or block device files even
> _mean_? I'm guessing it's meaningless, but I wonder. My Google fu comes up
> empty. It's a big cover up? ;P
POSIX does not specify a behavior for the S_ISVTX bit being set on a
file: http://pubs.opengroup.org/onli
Hello all,
Since some time I get the message
> swapon: [...]: insecure permissions 1660, 0660 suggested.
[1] is related to this. I'm not worried, but there are two things I wonder:
1) Foremost, what does the sticky bit on character or block device files even
_mean_? I'm
Camaleón wrote:
> On Sat, 11 Feb 2012 14:06:40 +0100, Morten Bo Johansen wrote:
>> In the latter case, which package should I report against?
> I'd say "libsane".
I think I'll go for udev. Once the scanner is attached to to a
scsi device file, then the appropriate module should be loaded
and th
ed to a scsi device, but the scsi device files are not being
> created automatically under /dev/ which means that xsane will not see
> it. When I ran:
>
>~/ % sudo modprobe sg
>
> manually, the scsi device files are created as /dev/sg0 etc. and my
> scanner now works ag
ANSI: 4
My Epson scanner is thus recognized. However, the scanner is also being
attached to a scsi device, but the scsi device files are not being
created automatically under /dev/ which means that xsane will not see it.
When I ran:
~/ % sudo modprobe sg
manually, the scsi device files are
On Thu, 2007-02-22 at 09:56 -0500, I wrote:
> Now, though, every time I boot, the /dev/flash link disappears. And
> recently, /dev/sdc1 disappeared too.
On Thu Feb 22 10:07:59 2007, Greg Folkert <[EMAIL PROTECTED]> replied:
> HAL and UDEVD.
>
> They auto create and r
sdc1 with mknod, it functions fine, but it disappears after
> any reboot. There are plenty of other symbolic links that came with the
> system (e.g. cdrom -> hda), and they don't disappear.
>
> What's going on? Are device files checked against some official registry
olic links that came with the
system (e.g. cdrom -> hda), and they don't disappear.
What's going on? Are device files checked against some official registry and
deleted if they're unrecognized?
Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
Hello!
I just wanted to report that I finally found a way to
generate more than 256 device nodes for a major device:
Making a dist-upgrade to Debian Etch ("testing")!
To avoid any bad sideeffects that could postpone my project any
further all installations have been made inside a VMware Server
e
On Fri, Nov 24, 2006 at 06:36:06PM +0100, Stefan Sperling wrote:
> Hello Kevin,
>
> I did diff my Debian kernel configuration with the one from
> Ubuntu. Lots of differences but nothing really in the filesystem
> area 8-(
>
> I found two differences worth checking: Ubuntu has no DEVFS
> support c
Hello Kevin,
I did diff my Debian kernel configuration with the one from
Ubuntu. Lots of differences but nothing really in the filesystem
area 8-(
I found two differences worth checking: Ubuntu has no DEVFS
support compiled/activated. And there was a raw files parameter
set to 255. Neither throw
lder" ones.
>
>The problem is this:
>
> I want to create more than 4000 device files
>for a project. I am aware that this is an
>uncommon scenario. But it is a customer request.
>
>Generating the device files works well for the
>first 255 ones.
Hello!
0. I discovered a strange phenomenon with a Debian
Sarge installation. I am able to replicate it
on several machines. It occurs on freshly
installed machines as well as on "older" ones.
The problem is this:
I want to create more than 4000 device files
for a
Ken Bloom <[EMAIL PROTECTED]> writes:
> The patch to create these devices in udev is included in debian's non-free
> source. Perhaps you were missing the appropriate udev rules to actually
> create the device files.
>
> Put the following in a file (whose name ends
On Thu, 15 Apr 2004 20:10:21 +0200, Jan Pfeifer wrote:
> hi,
>
> I had problems trying to use the (non-free) nvidia kernel module
> generated from nvidia-kernel-source and I found out that the device
> files /dev/nvidia[ctl|0|1] were not created by any of the nvidia*
> pack
hi,
I had problems trying to use the (non-free) nvidia kernel module
generated from nvidia-kernel-source and I found out that the device
files /dev/nvidia[ctl|0|1] were not created by any of the nvidia*
packages, and are also not created by the MAKEDEV script nor by the
udev package.
I'
s using the device file ht0, but the device
doesn't exist. What am I missing? What is the proceedure for creating
the device files for this tape drive?
Thanks in advance,
Jon.
--
Mailed using Netscape Communicator 4.6 running on Debian Linux 2.1begin:vcard
n:Dallara;Jon
tel;fax:408.970.
On Fri, Jul 02, 1999 at 10:44:04PM -0500, ktb wrote:
> Have you tried looking in your /dev directory?
>
> John Cuson wrote:
> >
> > can anyone point me to where i might find a device file index of some sort?
If you have the kernel source, try /usr/src/linux/Documentation/devices.txt
Have you tried looking in your /dev directory?
kent
John Cuson wrote:
>
> hi-
>
> can anyone point me to where i might find a device file index of some sort?
>
> John Cuson
> [EMAIL PROTECTED],[EMAIL PROTECTED]
>
> "Those are my principles, and if you don't like them... well, I have
> others
hi-
can anyone point me to where i might find a device file index of some sort?
John Cuson
[EMAIL PROTECTED],[EMAIL PROTECTED]
"Those are my principles, and if you don't like them... well, I have
others."
-- Groucho Marx
24 matches
Mail list logo
