Does anyone know how I can get around the following error?
VFS: Can't find ext3 filesystem on dev hda1
cramfs: wrong magic
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernal panic: Attempted to kill init!
When I ran LILO I got the warning below but
Leonard Chatagnier <[EMAIL PROTECTED]> writes:
Please someone: Do I have to use udev with 2.6.15
kernels? If not, how to get devfsd to work? Lilo
had
the mount devfs command for linux image in the
config
file.
devfs is no longer supported in the later 2.6 series. I'm not sure
Leonard Chatagnier <[EMAIL PROTECTED]> writes:
>> Please someone: Do I have to use udev with 2.6.15
>> kernels? If not, how to get devfsd to work? Lilo
>> had
>> the mount devfs command for linux image in the
>> config
>> file.
devfs is no longer suppor
Forwarded from smpt account as web mail sending was
never posted.
--- Leonard Chatagnier <[EMAIL PROTECTED]> wrote:
> Date: Sun, 15 Jan 2006 07:46:22 -0800 (PST)
> From: Leonard Chatagnier <[EMAIL PROTECTED]>
> Subject: DEVFS Or UDEV On 2.6.15-1-686 Kernel
> To: debian-u
No response after being posted for three days. Hoping it was just
overlooked. Would appreciate any guidance whatsoever. This was posted
to Linuxant.com support with reply only that devfs and/or modprobe
configuration was causing the problem, not the modem driver. Have read
all related
Missing devfs file in /dev prevents hcfpci~1.deb from installing without
error. Using dpkg -i hcfpci~1.deb
to install driver. Reinstalling devfsd didn't help-/dev/devfs is still
missing and dpkg -i hcf*~1.deb still gives
the same error. Appreciate any help resolving this problem. P
I'm running sid on an Intel box. I have been running devfs for about 5 years.
My motherboard is a KT133 with a Southbridge PCI controller and a Promise
PDC20265 controller. I have the following drive config:
Southbridge controller:
hda: Maxtor 6Y120L0, ATA DISK drive
hdb: Maxtor 6Y160P0
dev plugs in to the standard hotplug program and responds to hotplug
events by creating or destroying device nodes in /dev, based on policies
that you define.
> devfs
Devfs is a kernel module that implements a filesystem. Modules register
with devfs to tell it what devices nodes they need, an
that may or may not be on my computer?
>
> hotplug
Hotplug detects the hardware in your system and inserts the
appropriate kernel modules.
> udev
This is what looks at what drivers are currently loaded and creates
the appropriate devices for them.
> devfs
devfs is udev's older, reta
t;
There is also a udev presentation given at OLS 2003 available at:
<http://www.kroah.com/linux/talks/ols_2003_udev_talk/>
Q: How is udev related to devfs?
A: udev works entirely in userspace, using /sbin/hotplug calls that the
kernel makes whenever a device is added or removed
Sean O'Dubhghaill wrote:
[snip]
- Does hotplug inform udev when a new device connects to the computer?
Not sure, but new devices plugged in will cause new dev entries to be made. I
think hotplug will just load the relevant modules and udev will sort out
devices on its own
Package: udev
Descrip
[snip]
>
> - Does hotplug inform udev when a new device connects to the computer?
Not sure, but new devices plugged in will cause new dev entries to be made. I
think hotplug will just load the relevant modules and udev will sort out
devices on its own
> - Does udev make use of devfs?
Hey guys,
I'm running Sarge with 2.6.8 kernel. I've got the "udev" package installed.
Can anyone help clarify the relationship between any of the following
things that may or may not be on my computer?
hotplug
udev
devfs
hotplug
automount
autofs
HAL
sysfs
procfs
I know that&#
Hi All!
Thanks for clearing it up!
I've kicked Devfs out of my kernel and everything is working as it
should!
Eduard
On Thu, 2004-09-23 at 22:28, Paul Johnson wrote:
> <#secure method=pgp mode=sign>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Eduard Bosma
<#secure method=pgp mode=sign>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eduard Bosma <[EMAIL PROTECTED]> writes:
> Do I have to EXclude this option? Does that mean that DevFS is obsolete?
Devfs is obsolete, yes. udev is the replacement.
-BEGIN PGP SIGNATURE-
Versio
> Do I have to EXclude this option? Does that mean that DevFS is
obsolete?
Yes, exclude it. That is, if it's checked, uncheck it.
Yes, devfs is generally considered to be obsolete; the new favorite is
udev. See http://kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ,
and if you
Andrew,
Do I have to EXclude this option? Does that mean that DevFS is obsolete?
Eduard
On Thu, 2004-09-23 at 14:19, Andrew Schulman wrote:
> > Which options do I have to exclude in my .kernel config to prevent the
> > compiling of devFs?
>
> In 'make menuconfig&#
> Which options do I have to exclude in my .kernel config to prevent the
> compiling of devFs?
In 'make menuconfig', File systems -> Pseudo filesystems -> /dev file
system support (OBSOLETE).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
Hi All!
I'm having a problem with my NVIDIA drivers and DEVFS. When I install
the drivers they compile fine and X-windows is working like a charm. But
as soon as I shutdown my laptop en reboot, I have to reinstall my
drivers. This is a known issue, and I can resolve it by adding the
req
and if I use a real mount to /mnt
then the device pops up as an icon on the desktop. With symlinks to
/var/autofs then this doesn't happen (I guess Gnome is watching mtab
or similar). However - I rarely use graphical disk browsers - so this
is not a real problem.
So - from devfs with
On Thu, Sep 16, 2004 at 09:05:56AM +0200, Chris wrote:
>
> Dave - you said you were using autofs to mount some of your devices?
> You haven't got an example config file you could send?
>
Recall my /etc/udev/rules.d/local.rules:
BUS="usb", SYSFS{product}="JUMPDRIVE", NAME="%k", symlink="jumpdrive
;%k",
SYMLINK="MobileDisk"
This is because when you plug it in the sda1 (or sd?1) device is
created too - so - this can keep it's kernel name and get a symlink.
>> I also have another card reader (Unomas). That has empty vendor
>> and model strings (note -
don't have any multi-function devices, so I'm afraid I can't be of much
help here.
> I also have another card reader (Unomas). That has empty vendor and
> model strings (note - this example from while I still had devfs style
> naming). How to match this one with SYSFS{???} ?
&g
BUS="usb", SYSFS{product}="JUMPDRIVE", NAME="%k", symlink="jumpdrive"
Some progress :-)
1) remove all devfs/compat links from rules.d and replace with a udev
link in rules (so - from devfs style naming to udev style naming)
:-)
2) Create the foll
On Tue, Sep 07, 2004 at 01:30:23PM +0200, Chris Searle wrote:
>
> The other question is rights - how to set up user/groups on /dev and
> how to get devices to turn up at the same place so that they can be
> added to /etc/fstab with "user" option so I don't have to keep
> switching to root to moun
Debian sid.
I was running a 2.4 kernel with devfs/devfsd - I've now got
2.6.7-1-686 kernel with udev installed. devfsd is removed.
The setup is working quite well - but a couple of things I don't
understand.
I have a couple of multifunction card readers - the one I'm currently
On Fri, Jul 09, 2004 at 05:33:21PM -0700, Richard Weil wrote:
| What's the rational for building 2.6 series kernels with devfs? Devfs
| is deprecated.
Backwards compatibility, I imagine. Some people started using devfs
with the 2.4 kernels and their system would break without it. Having
What's the rational for building 2.6 series kernels with devfs? Devfs
is deprecated. Simply ignoring it would seem fine, but ... a bug report
was filed against initrd-tools because it won't work with root raid on
a system on which you're not using devfs. I was glad to see this bug
On Sun, Apr 18, 2004 at 06:48:06PM -0600, D. Frye wrote:
>
> After installing sarge on a laptop, I get the error that not all
> packages were
> setup correctly.
>
> Looking at it closer, the error is that the kernel is configured with
> devfs,
> but devfs is not mount
After installing sarge on a laptop, I get the error that not all
packages were
setup correctly.
Looking at it closer, the error is that the kernel is configured with
devfs,
but devfs is not mounted anywhere. As a result, noflushd cannot work. There
is a reference to the noflushd README which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After installing sarge on a laptop, I get the error that not all packages were
setup correctly.
Looking at it closer, the error is that the kernel is configured with devfs,
but devfs is not mounted anywhere. As a result, noflushd cannot work. There
Hello,
I'm running a sid/unstable system with devfs+devfsd and kernel 2.6.3.
I've got both kudzu and discover running, with basically their default
configurations.
I recently switched back to devfs+devfsd from a non-devfs configuration
(I had some issues with the non-devfs setup). I&#x
d is installed and I can see the devices via
> the full devfs path.
>
>> You are correct that you need to use the
>> /dev/ide/... device names for
>> LVM. You can use the old device names (/dev/hd??)
>> for mount. Probably
>> most all non-lvm commands. Certa
> If devfsd is a debian install ("dpkg -l devfsd" will
> tell you), it should
> be set up fine.
>
> And, if you can see your devices as /dev/ide/...
> then it is all fine.
>
Yes, devfsd is installed and I can see the devices via
the full devfs path.
> You ar
message is displayed:
>
> --
> if devfs is compiled into the kernel then it MUST be
> mounted on /dev
> Otherwise LVM will not be able to locate your Physical
> Volumes. You must
> also use the full devfs device names in LVM commands
> rather than the
> shortened dev
Thanks for the response. I will try lvm10 again (I am
avoiding lvm2 for the same reason you are). I think
the problem may that I don't quite understand what I
need to do to set up LVM. When lvm10 is installed
this message is displayed:
--
if devfs is compiled into the kernel th
On Sat, 03 Jan 2004 13:30:06 -0800, ope wrote:
I am running sarge (testing) and have been using devfs and lvm10 for
nearly 2 years with no problems, either with stock or custom-compiled
kernels. However, I don't mix distros, and your problem may be related to
that, particularly as it once w
On Sat, Jan 03, 2004 at 01:30:06PM -0800, ope <[EMAIL PROTECTED]> wrote:
> From what I can tell, it really won't matter much if I
> get rid of devfs. I wanted to check with everyone
> here to see if there were any issues with getting rid
> of devfs. Is there anything I
devfs
enabled. I would really like to have LVM working so I
am trying to figure out what my options are. One
option is to recompile the kernel without devfs
support.
>From what I can tell, it really won't matter much if I
get rid of devfs. I wanted to check with everyone
here to see if th
On Thu, Jan 01, 2004 at 10:07:17PM +0300, Andrey Borzenkov wrote:
> On Wednesday 31 December 2003 23:31, Andrew Morton wrote:
> > when i modprobe ppp_generic, i get this error in dmesg:
> > PPP generic driver version 2.4.2
> > devfs_mk_cdev: could not append to parent for ppp
> > failed
Oops! - that must have been a stupid question.
I haven't read anything about that in the Howtos - although maybe I was
looking for the wrong thing...
Can anyone point me to a howto on getting 2.6 up-and-running without DevFS.
->Or even point out some useful terms etc. to search for.
On Tue, Nov 18, 2003 at 11:06:23AM -0500, Sven Heinicke wrote:
|
| To get te the point, how ho I change an i686 3.0r1 system with
| proposed-updates and the 2.4.22-2-686-smp kernel to be devfs? I would
| be most happy with pointers to Linux general documentation on how to
| this.
Compile a
s to
> register fine, etc etc, but the mountable device no longer appears in
> my devfs /dev/. How can I debug this, what should I look for, what
> might be missing?
Do you still have the required scsi-drivers in kernel? I once forgot to add
scsi-disk-support to my kernel resulting in
till seems to
> register fine, etc etc, but the mountable device no longer appears in
> my devfs /dev/. How can I debug this, what should I look for, what
> might be missing?
>
> Thanks,
> Hugo
>
Kernel modules? usb-storage and related (discussed on this list recently)
If not g
To get te the point, how ho I change an i686 3.0r1 system with
proposed-updates and the 2.4.22-2-686-smp kernel to be devfs? I would
be most happy with pointers to Linux general documentation on how to
this.
The story: I was setting up an i686 system with woody that needed a
driver I was not
s to
> register fine, etc etc, but the mountable device no longer appears in
> my devfs /dev/. How can I debug this, what should I look for, what
> might be missing?
>
I don't know about the technical side, but what about calling it a
"drive" vs. a "disk"? I d
I've got a USB storage device (what should one call these things? I
hate calling it a "flash disk" since I feel it's not a disk (disc?) ;)
It worked great at one point. However, recently, it still seems to
register fine, etc etc, but the mountable device no longer appears in
> I thought devfs was going to be mostly removed from the installations.
>
> This is based on a comment I received once long ago from a Debian
> posting that devfs as a whole wasn't working out all that well and has
> been removed from the 2.6 kernel.
Yes. devfs has been de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 16 November 2003 21:22, Todd Pytel wrote:
> I agree. I only had one or two issues with devfs, and those were really
> problems with other applications not being coded to recognize it.
I had some problems with devfs in connection wi
On Sun, 16 Nov 2003 20:19:32 +0100
"John L. Fjellstad" <[EMAIL PROTECTED]> wrote:
> On Sunday 16 November 2003 12:52, Karsten M. Self wrote:
>
> > Same story I've heard. My experience with it is pretty gwadawful.
>
> My experience with devfs has been pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 16 November 2003 12:52, Karsten M. Self wrote:
> Same story I've heard. My experience with it is pretty gwadawful.
My experience with devfs has been pretty good. It's nice knowing exactly
which device is loaded just lookin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 15 November 2003 14:48, Tom Allison wrote:
> This is based on a comment I received once long ago from a Debian
> posting that devfs as a whole wasn't working out all that well and has
> been removed from the 2.6 kernel.
I
on Sat, Nov 15, 2003 at 08:48:29AM -0500, Tom Allison ([EMAIL PROTECTED]) wrote:
> I was doing an installation using whatever disks I can find (stable,
> tesitng-installer) and I ran into a problem of something that I recall
> once long ago.
>
> I thought devfs was going to be
I was doing an installation using whatever disks I can find (stable,
tesitng-installer) and I ran into a problem of something that I recall
once long ago.
I thought devfs was going to be mostly removed from the installations.
This is based on a comment I received once long ago from a Debian
> - Original Message -
> From: "Manolis Tzanidakis" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, October 30, 2003 1:49 PM
> Subject: Re: devfs and lvm
>
> [20031030] Benedict Verheyen <[EMAIL PROTECTED]> wrote:
>
&
- Original Message -
From: "Manolis Tzanidakis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 30, 2003 1:49 PM
Subject: Re: devfs and lvm
[20031030] Benedict Verheyen <[EMAIL PROTECTED]> wrote:
> Hi,
Hello
> currently my s
[20031030] Benedict Verheyen <[EMAIL PROTECTED]> wrote:
> Hi,
Hello
> currently my server (2.4.21) is running LVM. All partitions are on
> LVM except a boot partition. I would like to move to devfs.
> Any good documents or howto's out there that explain how to set
> th
Hi,
currently my server (2.4.21) is running LVM. All partitions are on
LVM except a boot partition. I would like to move to devfs.
Any good documents or howto's out there that explain how to set
this up. I understand that i will need to install devfsd and
that i might have to change the root
On Tuesday 28 October 2003 17:30, Kjetil Kjernsmo wrote:
> Yes, it's there! :-)
>
> [EMAIL PROTECTED]:~> grep devfs /proc/mounts
> none /dev devfs rw 0 0
>
> > If devfs is in /proc/filesystems,
>
> Yes, it is there too.
Just to let you all know I have solved thi
sion
> > that mount should know about it if devfs is used. It says that
> > mount | grep devfs
> > should report something, but for me it doesn't. Which is weird.
> > It does seem like devfs is not mounted.
>
> Maybe it's mounted on boot, and init somehow unmount
On Tue, Oct 28, 2003 at 11:21:50AM +0100, Kjetil Kjernsmo wrote:
> Reading
> http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/dev_files.html
> (which is basically the howto I'm following) I get the impression that
> mount should know about it if devfs is used. It says tha
Hi and thanks for the response!
On Tuesday 28 October 2003 04:23, Jerome R. Acks wrote:
> Since you have devfs mounted on /dev, you ought to be able to use
> devices in /dev/tts directly rather than compatibility symlinks to
> ttyX.
Yes. I thought so too. Anyway, you're giving m
Dan Jacobson <[EMAIL PROTECTED]> writes:
> LILO version 22.5.7.2 says
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> The kernel was compiled with DEVFS_FS, but 'devfs=mount' was omitted
> as a kern
LILO version 22.5.7.2 says
Warning: '/proc/partitions' does not match '/dev' directory structure.
The kernel was compiled with DEVFS_FS, but 'devfs=mount' was omitted
as a kernel command-line boot parameter; hence, the '/dev' direct
On Wed, Sep 10, 2003 at 04:39:03PM +0200, Harry Brueckner wrote:
> I just switched to a self compiled 2.6.0-test4 kernel with devfs
> support turned on and devfsd is running nicely. Now when I boot into
> the new 2.6 kernel it starts up but throws tons of messages like
> FATAL: Modul
Harry Brueckner wrote:
> Hello,
>
> I just switched to a self compiled 2.6.0-test4 kernel with devfs support
> turned on and devfsd is running nicely.
> On my old 2.4.20 kernel I did not use devfs.
>
> Now when I boot into the new 2.6 kernel it starts up but throws to
On Wednesday 10 Sep 2003 15:43, Tom Badran wrote:
> On Wednesday 10 Sep 2003 15:39, Harry Brueckner wrote:
> > Hello,
> >
> > I just switched to a self compiled 2.6.0-test4 kernel with devfs support
> > turned on and devfsd is running nicely.
> > On my old
On Wednesday 10 Sep 2003 15:39, Harry Brueckner wrote:
> Hello,
>
> I just switched to a self compiled 2.6.0-test4 kernel with devfs support
> turned on and devfsd is running nicely.
> On my old 2.4.20 kernel I did not use devfs.
> Any ideas what might be wrong?
Prehaps you
Hello,
I just switched to a self compiled 2.6.0-test4 kernel with devfs support
turned on and devfsd is running nicely.
On my old 2.4.20 kernel I did not use devfs.
Now when I boot into the new 2.6 kernel it starts up but throws tons of
messages like
...
FATAL: Module /dev/ttyx0
FATAL: Module
On Sat, Sep 06, 2003 at 04:54:22PM +0200, Anders Ellenshøj Andersen wrote:
> I can't open an xterm, not even as root. As regular user there is a lot of
> disk activity and then the terminal window fails to open.
Did you build in pty support? Xterm and friends care about that.
> Please CC me as
I am testing kernel-2.6 on unstable on my Asus A1300 laptop. I have everything
up and running except konsole/xterm.
I can't open an xterm, not even as root. As regular user there is a lot of
disk activity and then the terminal window fails to open.
I am using devfs compiled into the kerne
Nick Hastings <[EMAIL PROTECTED]> writes:
> * Todd Pytel <[EMAIL PROTECTED]> [030829 16:11]:
>> On Fri, 29 Aug 2003 15:11:00 +0900
>> Nick Hastings <[EMAIL PROTECTED]> wrote:
>>
>> > Any devfs experts know how to fix this line properly?
>>
* Todd Pytel <[EMAIL PROTECTED]> [030829 16:11]:
> On Fri, 29 Aug 2003 15:11:00 +0900
> Nick Hastings <[EMAIL PROTECTED]> wrote:
>
> > The last line of
> > this file must be malformed. I simply commented it out.
> >
> > [EMAIL PROTECTED] ~ 17% cat /e
On Fri, 29 Aug 2003 15:11:00 +0900
Nick Hastings <[EMAIL PROTECTED]> wrote:
> The last line of
> this file must be malformed. I simply commented it out.
>
> [EMAIL PROTECTED] ~ 17% cat /etc/devfs/conf.d/alsa
> # device permissions for ALSA sound devices.
> REGISTE
running sid with a 2.6.0-test2 kernel with devfs. Yesterday I did a
> dist-upgrade and then shut down. The devfsd package was _not_ upgraded.
> I'm not sure if it is relevant but initrd-tools was upgraded.
>
> I rebooted today to find that none of the old style device nodes
Hi all,
firstly please excuse possible line wrap problems and lack of my usual gpg
signature. I'm sending this via squirrel mail for reasons described below.
I'm running sid with a 2.6.0-test2 kernel with devfs. Yesterday I did a
dist-upgrade and then shut down. The devfsd package
Hi Andreas,
you wrote :
> The problem I see, as far as I could get, is that
> the card is initialized OK, but the /dev/ttySxx -link is not created.
how do you know that ?
what does dmesg say about it ?
if it is as you think, then it is a bug in card driver,
if that driver is in Debian,
What's the contents of /proc/usb/*?
ap
--
Andrew J Perrin - http://www.unc.edu/~aperrin
Assistant Professor of Sociology, U of North Carolina, Chapel Hill
[EMAIL PROTECTED] * andrew_perrin (at) unc.edu
On Fri, 8 Aug 2003, Darry
--- Andrew Perrin <[EMAIL PROTECTED]> escribió:
>
> On Fri, 8 Aug 2003, Darryl Barlow wrote:
>
> > I am running Debian Unstable with a 2.4.21 kernel, and am trying
> unsuccesfully
> > to connect my sony cypershot DSC P7 via usb storage.
> >
> > I won't post logs at this stage. However, syslog
I am running Debian Unstable with a 2.4.21 kernel, and am trying unsuccesfully
to connect my sony cypershot DSC P7 via usb storage.
I won't post logs at this stage. However, syslog and messages show that the
camera is detected and fully recognised. Also, host1 is being created under
/dev/scsi
I have found a workable solution, though I think
Hotplug in Debian Unstable will need a little work before it makes it to
testing. It appears that Hotplug loads sr_mod instead of sd_mod for this
device. A simple modprobe sd_mod is sufficient to get it working.
Thanks to everyone who replied f
Hi,
I'm trying to use a new Xircom Ethernet/Modem PC-Card with my
Debian/unstable notebook. The problem I see, as far as I could get, is
that the card is initialized OK, but the /dev/ttySxx -link is not
created. I tryed the card booting the KNOPPIX-liveCD which recognized it
all fine, and afte
NOT WORK
> without properly recompiled kernel. Not only that, it does not give
> any clue what exactly is wrong.
>
...
>
> Not necesarilly. Sometimes people need other software that just
> happens to need devfs.
Just to make a subtle distinction here, I'll point out that the fun
> > apt-get devfs
Oops, my mistake. Please read
apt-get devfs
as
apt-get devfsd
also all referentces to package devfs should read devfsd. I guess
this made my original post a bit unclear. Sorry.
...
> > I was thinking that in an ideal world the configuration of
> > a
Vesselin Kostadinov <[EMAIL PROTECTED]> writes:
> I had to mess around with few packages, one of them being devfs. It
> looked easy:
>
> apt-get devfs
>
> So apt downloaded and configured it. I thought I was done with it
> and I can concentrate on the other (more impor
On Monday July 07, 2003 at 03:30
Vesselin Kostadinov <[EMAIL PROTECTED]> wrote:
> apt-get devfs
>
> So apt downloaded and configured it. I thought I was done with
> it and I can concentrate on the other (more important to me) packages.
> Not so. After "become-an-expe
Hi,
I had to mess around with few packages, one of them being devfs.
It looked easy:
apt-get devfs
So apt downloaded and configured it. I thought I was done with
it and I can concentrate on the other (more important to me) packages. Not
so. After "become-an-expert-in-devfs" e
> On Sun, Jan 26, 2003 at 04:05:52PM +0100, Nicos Gollan wrote:
> > On Sunday 26 January 2003 15:32, Dave W wrote:
> > > What I _did_ try was
> > >
> > > mount /dev/scd0 /cdrom
> > >
> > > and that still fails. I still have scsi emulation and the
> like setup so
> > > I guess perhaps at least THA
On Sun, Jan 26, 2003 at 04:05:52PM +0100, Nicos Gollan wrote:
> On Sunday 26 January 2003 15:32, Dave W wrote:
> > What I _did_ try was
> >
> > mount /dev/scd0 /cdrom
> >
> > and that still fails. I still have scsi emulation and the like setup so
> > I guess perhaps at least THAT little bit has cha
On Sunday 26 January 2003 15:32, Dave W wrote:
> What I _did_ try was
>
> mount /dev/scd0 /cdrom
>
> and that still fails. I still have scsi emulation and the like setup so
> I guess perhaps at least THAT little bit has changed. Perhaps it's
> using sr or sg or one of the other scsi alphabet soup
On Sun, 2003-01-26 at 00:09, Jerome Acks Jr wrote:
> devfsd creates symlinks from old device names to devfs device names.
> /dev/hda1 will be a symlink to ide/host0/bus0/target0/lun0/part1. Your
> /dev/cdrom will be a symlink to /dev/cdroms/cdrom0.
>
> So "mount /dev/fd0
On Sat, Jan 25, 2003 at 10:44:14PM -0500, Dave W wrote:
> I've been messing around with devfs in sid, trying to learn my way
> around, since this may be the way of the future ... and although
> /dev/scsi/host0/bus0/target2/lun0/cd makes good SENSE and is pretty easy
> to figure
I've been messing around with devfs in sid, trying to learn my way
around, since this may be the way of the future ... and although
/dev/scsi/host0/bus0/target2/lun0/cd makes good SENSE and is pretty easy
to figure out, it's not so quick to type when mounting by hand. I'm
used
"Jameson C. Burt" <[EMAIL PROTECTED]> writes:
> For "Device File System", Debian "devfsd" package,
> how might I test that "devfsd" properly creates files in /dev?
Does your kernel actually have devfs support? I believe the standard
Debian
Hello
> For "Device File System", Debian "devfsd" package,
> how might I test that "devfsd" properly creates files in /dev?
Try hotplug and use usbview to see usb devices.
I had same problem, after several tryes it worked (never understand why :-)
David Dumortier
--
To UNSUBSCRIBE, email to
package,
> so I added to devfsd's configuration file,
>/etc/devfs/devfsd.conf
> the line,
>REGISTER ^v4l/video0$ CFUNCTION GLOBAL symlink v4l/video0 video0
> When starting "camserv", I get the not so specific error message,
>(V4L) video_open: No such
For "Device File System", Debian "devfsd" package,
how might I test that "devfsd" properly creates files in /dev?
As a particular example, I work with the Debian "camserv" package,
so I added to devfsd's configuration file,
/etc/devfs/devfsd.conf
t
On Thu, Jan 09, 2003 at 09:27:07AM +0100, Nicos Gollan wrote:
> Have a look at /etc/devfs/perms
OK, that got permissions set right, now how do I get xsane to realise
it's existance?
--
.''`. Baloo <[EMAIL PROTECTED]>
: :' :proud Debian admin and user
`
> between boots?
Have a look at /etc/devfs/perms
- --
Embedded Linux -- True multitasking!
TWO TOASTS AT THE SAME TIME!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE+HTJfeOF0+zcVdv8RAivYAKCOvEwzik+Y+FX3Mr3S3H9VpLwhVwCdE3f7
5oOehWyWjZtALFOltYJdqtM=
=sxWW
-END P
How would I go about making a scanner attached to
/dev/scsi/host0/bus0/target0/lun0/generic world-readable and
world-writable so any user can access it, and preserve permissions
between boots?
--
.''`. Baloo <[EMAIL PROTECTED]>
: :' :proud Debian admin and user
`. `'`
`- Debian - whe
1 - 100 of 253 matches
Mail list logo
