Date: Tue, 28 Jan 1997 13:46:23 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: Shimon@i-Connect.Net (Simon Shapiro) Cc: hackers@freebsd.org Subject: Re: 2.2-BETA Questions Message-ID: <199701280316.NAA06348@genesis.atrad.adelaide.edu.au> In-Reply-To: <XFMail.970124202122.Shimon@i-Connect.Net> from Simon Shapiro at "Jan 24, 97 07:18:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Simon Shapiro stands accused of saying:
> Some questions about 2.2-BETA
>
> 1. Does anyone care? Coming from (too much) Linux, and seeing 2.1.6,
> 2.2-BETa, 3.0... it is not a stupid question.
Er, yes. Lots of people care. 2.2-BETA is the leadup to 2.2-RELEASE,
the next production-level version. 3.0 is the current 'development'
version, which will lead to a release probably sometime late this
year. Exposing the devlopment process like this means that everyone
can see where things are going.
> 2. Assunming #1 is true, listen to this (Network Failure System; AKA NFS)
> scenario:
>
> * Linux NFS server, Debian 1.2, Kernel 2.0.27, etc. (nomis) with this
> in /etc/exports:
>
> /usr/src/FreeBSD sendero.i-connect.net(rw,no_root_squash)
>
> * FreeBSD 2.2-BETA client doing:
>
> # mkdir /NewStuff
> # mount -t nfs -o ro nomis;/usr/src/FreeBSD /NewStuff
> # ls -al /NewStuff
> ls: /NewStuff: Permission denied
What are the permissions on "NewStuff" on the server? Try "ls" without
any other flags first.
> Dunno about you but smells like a bug to me...
It looks to me like the server is being _very_ weird. Someone else
(Doug R.?) might have a better idea about that.
> 3. Made a kernel with sound, etc... Worked fine until some days ago.
> Now, all of the sudden, without me doing anything (really :-):
>
> # xmcd -debug
> ....
> Lock file: /tmp/.cdaudio/lock.f02
> Cannot open /dev/rcd0c: errno=6
Is there a CD in the drive? 6 is "not configured", which xmcd should be
telling you. A list of the boot-time probe messages (output of 'dmesg')
would be handy here, as I suspect that your CD wasn't found.
> 4. Shutdown questions:
>
> a. When init goes to single user, prompts, asking for a shell.
> You press ENTER and it sits on ``(.???msg - Cannot exactly
> remember) not found''
> ^C will get you a prompt, most of the time. Sometimes you get
> a fast roll talking about some malloc() failure. Sometimes a
> ^C will stop it, sometimes it will not.
Er "init goes to single user"? How are you shutting down?
> b. umount -a will leave things not in /etc/fstab mounted.
> It always leaves root mounted RW, only to fsck it at boot.
> Seems lie an unnecessary risk.
You're _definitely_ not shutting down correctly. 'man shutdown'.
> 5. More CD fun. Once a music CD is played, you cannot mount a data
> cd because ``device is busy''. Reboot cures.
Try exiting the CD-playing program first, if you aren't already.
> 8. Education Question: What is the logic in assigning slice ID's?
> I understand c to be the entire disk
> (why `c'? Why not?)
> Why does sysinstall assign 'e', 'f',
> but (almost) never 'd'?
You mean partition names. Tradition, mostly. 'a' is traditionally
used for a root filesystem, 'b' for swap, 'c' for the whole disk, and
d-h for 'other' partitions. For a while, 'd' was used by various
386 BSD's to deal with the disparity between "the whole disk" and
"the whole part of the disk that BSD uses"; this is obsoleted by
the 'slice' paradigm.
> 9. Some safety checks in disklabel and newfs and/or kernel slice-
> partition handling could be nice. If you create an 'a' partition
> which is exactly an overlap of a 'c' in a slice that dominates
> the disk, newfs will FREEZE the system.
Novel. I've never seen that, and I've done it many times.
> 10. Kernel Question: On an i386 PC, how does one make sure that
> another driver does not use the same ISA ports as you do?
> You are trying to be nice and NOT use something someone else is
> already using. There is a Linux thing to do that...
ISA resource allocation is a particularly noisome can of worms.
Currently, if your driver is configured with a base address in a
region previously claimed by another driver, your probe routine won't
be called. That can obviously cause problems if you plan to probe
several possible port ranges in a single probe routine.
If you have any particular ideas or requests here, please raise them,
as we're always open to suggestions on cleaning this up.
> 11. Another Kernel question: A device driver for a controller that
> is available in ISA, EISA and PCI. How do you split the code?
> We put the PCI part in pci, the ISA/EISA parts in i386/{isa,eisa}?
> But the code is NOT i386 dependant. We are putting it in dev/dpt.
> Is that a good choice?
Perhaps:
- have three seperate drivers (bad idea).
- look at the 'ahc' and 'bt' drivers; the former is pci/eisa, the latter
is pci/isa. The 'ahc' driver also has code in dev/.
> Simon
--
]] Mike Smith, Software Engineer msmith@gsoft.com.au [[
]] Genesis Software genesis@gsoft.com.au [[
]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[
]] realtime instrument control. (ph) +61-8-8267-3493 [[
]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701280316.NAA06348>