Thanks to Fish's contribution I have made the Unix 8th Edition manuals
available at:
http://man.cat-v.org/unix_8th/
Tons of fascinating stuff there, including the jerq docs in section 9
( http://man.cat-v.org/unix_8th/9/ ) and what I think is the oldest
documentation of the /proc file system
On Fri Jul 31 23:13:51 EDT 2009, rminn...@gmail.com wrote:
On Fri, Jul 31, 2009 at 6:56 PM, J.R. Maurojrm8...@gmail.com wrote:
Doesn't ASUS burn the Linux distro into a chip, though? Maybe there
are utilities to flash it with something else.
see flashrom at coreboot.org
This is a
http://man.cat-v.org/unix_8th/
Super Bats!
- erik
On Sat, Aug 01, 2009 at 07:58:10AM -0400, erik quanstrom wrote:
why not just use normal hardware and buy a DOM for it?
none of coraid's machines, including the fileserver (!) have
spinning media. only the srs (coraid storage appliances) do.
you can get a 128mb pata dom for $13 and sata
Well, if the DOM is compatible with traditionnal IDE it could be, too,
an option for installation: an easily pluggable HD instead of floppy or
CD.
the dom is compatable with traditional ide, and with the distributed
sdata.c. before i found the doms, i used a pata - cf bridge.
- erik
On Fri, Jul 31, 2009 at 10:53 PM, Roman Shaposhnikr...@sun.com wrote:
What are your clients running?
Linux
What are their requirements as
far as POSIX is concerned?
10,000 machines, working on a single app, must have access to a common
file store with full posix semantics and it all has to
btw the sata FLASH parts are surprisingly fast. Not at all like USB
sticks, if that is what you are used to.
ron
On Sat, Aug 1, 2009 at 11:49 AM, ron minnichrminn...@gmail.com wrote:
btw the sata FLASH parts are surprisingly fast. Not at all like USB
sticks, if that is what you are used to.
ron
Ron, have you researched any long-term wear studies on these flash
drives? I've heard a lot of good things,
Harka Győző at the University of Pécs has just started a new mailing
list for the Hungarian fans of Plan 9. We discuss topics about our
favorite operating system in our native language. You can join us at:
https://omega.ttk.pte.hu/cgi-bin/mailman/listinfo/9rajong
There exist crash bugs in some of the system call handlers to do with
string validation; sometimes, only the first byte of an argument string is
validated. The following program reliably causes a kernel panic for me:
#include u.h
#include libc.h
#define SEGBASE (char*)0x4000
#define
maybe the kernel should use something like this to validate pointers
to null terminated strings?
it could just call vmemchr correctly
or vmemchr could be a touch more careful
calling vmemchr assumes that the memory isn't being changed
by some other proc mapping the same page. if you find the
NUL in one pass and then call strcpy or strlen on the pointer
later, the other proc might have pulled the NUL in the interim.
there is a function in the kernel called
On Sat, 1 Aug 2009, Russ Cox wrote:
calling vmemchr assumes that the memory isn't being changed
by some other proc mapping the same page. if you find the
NUL in one pass and then call strcpy or strlen on the pointer
later, the other proc might have pulled the NUL in the interim.
With you so
validname0 looks like it is trying to be too clever.
A better version of the first if statement would be:
if((ulong)name KZERO) {
validaddr((ulong)name, 1, 0);
if(!dup)
print(warning: validname called from %lux with user
pointer,
yes:
if((ulong)name KZERO){
validaddr((ulong)name, 1, 0);
if(!dup)
print(warning: validname called from %lux with user
pointer, pc);
p = name;
t = BY2PG-((ulong)p(BY2PG-1));
Sunday afternoon (EDT), August 2nd, we'll move the Murray Hill Plan
9 systems back into our newly-renovated machine room. Plan 9 will be
unavailable for some of this time.
diff -c /n/dump/2009/0801/sys/src/9/port/sysproc.c sysproc.c
/n/dump/2009/0801/sys/src/9/port/sysproc.c:234,247 - sysproc.c:234,248
ulong magic, text, entry, data, bss;
Tos *tos;
- validaddr(arg[0], 1, 0);
- file = (char*)arg[0];
+ file = nil;
indir =
On Sat Aug 1 21:40:18 EDT 2009, quans...@quanstro.net wrote:
diff -c /n/dump/2009/0801/sys/src/9/port/sysproc.c sysproc.c
/n/dump/2009/0801/sys/src/9/port/sysproc.c:234,247 - sysproc.c:234,248
ready. shoot. aim.
sorry. i sent the wrong patch.
i also should have mentioned that this patch is
J.R. Mauro wrote:
Doesn't ASUS burn the Linux distro into a chip, though? Maybe there
are utilities to flash it with something else.
I believe new ASUS motherboards typically boot Splashtop from hard disk,
not from flash. On my ASUS M4A78 PLUS, Splashtop can be installed into
a directory tree
On Sat, Aug 1, 2009 at 10:55 PM, John DeGoodb...@degood.org wrote:
J.R. Mauro wrote:
Doesn't ASUS burn the Linux distro into a chip, though? Maybe there
are utilities to flash it with something else.
I believe new ASUS motherboards typically boot Splashtop from hard disk,
not from flash.
http://www.ncm.com/Fathom/Comedy/RiffTrax.aspx
Russ
21 matches
Mail list logo
