Re: alpha devfs feedback
In message [EMAIL PROTECTED], Matthew Jacob writes: I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 'da' disks that were found. The only real problem is that it won't see the partitions made for 'dangerously dedicated' 'da' disks. What's the plan for addressing this? Hmm, which exact names are you missing ? Have you tried accessing them directly, for instance: ls -l /dev/da0s2e or whatever their names are ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
In message [EMAIL PROTECTED], Matthew Jacob writes: On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Matthew Jacob writes: I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 'da' disks that were found. The only real problem is that it won't see the partitions made for 'dangerously dedicated' 'da' disks. What's the plan for addressing this? Hmm, which exact names are you missing ? Have you tried accessing them directly, for instance: ls -l /dev/da0s2e or whatever their names are ? Sure. They're not there. A reboot still just has da0[c], da1[c], and da2[c] show up. Remember that there's no such thing as slices in alpha. What names do you usually access your disks by ? Just da0a etc ? You should be able to find those as well with the clone stuff... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
What names do you usually access your disks by ? Just da0a etc ?
da0{a,b,c,d} and so on..
You should be able to find those as well with the clone stuff...
Nope. Weren't there.
I booted up once. I had 3 disks- none with a FreeBSD label. The
contents of /dev for da disks was /dev/da{0,1,2}[c].
So, I did the '-Brw da0 auto' and disklabel -e trick to add
a da0a to da0. disklabel happily saw da0a after this. Nothing
in /dev. Okay- so this kind of rescan doesn't work yet.
So, I reboot. The contents of dev still are /dev/da{0,1,2}[c]. I mostly
was raising this to see if someone else has tried alpha in this regard.
If not- I can help debug this and fix it, but next week.
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
In message [EMAIL PROTECTED], Matthew
Jacob writes:
What names do you usually access your disks by ? Just da0a etc ?
da0{a,b,c,d} and so on..
You should be able to find those as well with the clone stuff...
Nope. Weren't there.
I booted up once. I had 3 disks- none with a FreeBSD label. The
contents of /dev for da disks was /dev/da{0,1,2}[c].
So, I did the '-Brw da0 auto' and disklabel -e trick to add
a da0a to da0. disklabel happily saw da0a after this. Nothing
in /dev. Okay- so this kind of rescan doesn't work yet.
So, I reboot. The contents of dev still are /dev/da{0,1,2}[c]. I mostly
was raising this to see if someone else has tried alpha in this regard.
If not- I can help debug this and fix it, but next week.
Hmm, can you send me a ls -l /dev from a !devfs alpha so I can
see what it looks like ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
On Mon, 28 Aug 2000, Matthew Jacob wrote: On Mon, 28 Aug 2000, Poul-Henning Kamp wrote: Have you tried accessing them directly, for instance: ls -l /dev/da0s2e or whatever their names are ? Sure. They're not there. A reboot still just has da0[c], da1[c], and da2[c] show up. That's more than show up on i386's :-). After booting with -s, only the whole disk devices and the root device show up. Devices for slices and partitions slices only show up when they are opened or stat'ed. This bug is normally mostly hidden by opening most partitions to mount them. Remember that there's no such thing as slices in alpha. I thought that they worked. They should work if they are configured. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
In message [EMAIL PROTECTED], Bruce Ev ans writes: Sure. They're not there. A reboot still just has da0[c], da1[c], and da2[c] show up. That's more than show up on i386's :-). After booting with -s, only the whole disk devices and the root device show up. Devices for slices and partitions slices only show up when they are opened or stat'ed. This bug is normally mostly hidden by opening most partitions to mount them. Well, this "bug" is built into the current diskslice/label code as you know (you wrote it :-) It doesn't have anything to do with DEVFS as such. My proposed solution for this can be found in the bio/buf paper I wrote. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: alpha devfs feedback
That's more than show up on i386's :-). After booting with -s, only the whole disk devices and the root device show up. Devices for slices and partitions slices only show up when they are opened or stat'ed. This bug is normally mostly hidden by opening most partitions to mount them. Hmm. Well, it turned out that after a period of time da0a showed up. Poul says I might be out of date src-wise. I'll update again and see. Remember that there's no such thing as slices in alpha. I thought that they worked. They should work if they are configured. Sorry- I meant "SRM doesnt' grok i386 labels". -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
alpha devfs feedback
I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3 'da' disks that were found. The only real problem is that it won't see the partitions made for 'dangerously dedicated' 'da' disks. What's the plan for addressing this? -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
