> ... a special arrangement that allows me to skip
> the course work part of grad school ...
[shudder]
I hope that "special arrangement" includes passing the final exams,
or otherwise demonstrating that you already know the content, of at
least the minimum course work that would ordinarily be req
> Forgot to mention this project vary well turn into my PhD thesis
That's a rather different context than "personal hobby reasons".
I was going to suggest this anyway, but for a dissertation project
I would _very strongly_ suggest that you thoroughly research Linus
Torvalds' experiences in implem
[trimmed some of the lists]
Chris Rees wrote:
> ... git doesn't work with our workflow.
I'm sure the workflow itself is documented somewhere, but is
there a good writeup of _how_ git doesn't work with it, e.g. what
capabilit{y,ies} is/are missing? Seems this might be of interest
to the git deve
Can someone point me to a fairly detailed description of
how softdep handles "rm", in particular how it determines
whether a particular inode (e.g. a symlink) contains text
instead of a list of block numbers?
___
freebsd-hackers@freebsd.org mailing li
> > Is the inclusion of VLNK here correct? I would think that
> > only the target of the symlink should matter: if it happens
> > to point onto a writable FS, the fact that the symlink itself
> > is on a ROFS should not matter.
>
> yes, it is correct.
> short symbolic links are stored in the inod
I've just noticed this, in ufs/ufs/ufs_vnops.c:ufs_access()
/*
* Disallow write attempts on read-only filesystems;
* unless the file is a socket, fifo, or a block or
* character device resident on the filesystem.
*/
if (mode & VWRITE) {
switch (vp->v_type) {
There seems to be a recurrent problem, at least in 6.1, of sysinstall
not installing the kernel:
http://lists.freebsd.org/pipermail/freebsd-questions/2006-May/122261.html
http://lists.freebsd.org/pipermail/freebsd-questions/2006-June/124096.html
http://lists.freebsd.org/pipermail/freebsd-que
7 matches
Mail list logo
