hey,
i was wondering if anyone had a convincing reason why there's a
addrspacestruct addrspace *vmspace;
in the thread structure, and if there's a good reason it couldn't be moved
into the process structure, if kernel threads are all going to access memory
unmapped.
thanks,
brady
Hey there 161 posse,
I'm trying to use the full solution source from asst2 to begin asst3
work, but the build keeps breaking in the kern/test files with "too many
arguments to thread_fork()". Have I done something wrong in applying the
new solution tree, or is there a more obvious problem here? (The sources
being used for at least the test files are certainly the solution ones).
Thanks!
Ben
What have people found is the best way to test system calls/file state? Is
there any reason a kernel thread can't use a system call? Normally I know
kernel threads are not supposed to be using system calls, but seeing as we
don't have fork() yet, there's no other good way to test concurrency.
Nick
I found that the host-sh only compiles if a put in #include <sys/wait.h> and
the os161 version won't, of course, compile if that line is in. What am I
missing?
Nick~
> -----Original Message-----
> From: Ben Zotto [mailto:zotto@fas.harvard.edu]
> Sent: Wednesday, March 07, 2001 9:05 PM
> To: Nicholas C. Murphy
> Subject: Re: [cs161-list] shell compilation
>
>
> Nick,
> the Makefile for the bin directory actually compiles both automatically
> for you. If you go to the ~/cs161/src/bin directory and do a "make" that
> should do it. If it goes funny, try "make all" from the ~/cs161/src
> directory. I think that's how I got it working. The it dumps two
> executables in the directory, sh (for os161) and host-sh (for ICE/Alpha).
>
> Good luck!
>
> Ben
>
> On Wed, 7 Mar 2001, Nicholas C. Murphy wrote:
>
> > Since the header files are in different places in Unix than in
> OS161, what's
> > the best way to go about compiling the shell first on ICE and
> then for OS161
> > without having to go in and manually edit the code (or is that the best
> > way)?
> >
> > Thanks,
> > Nick
> >
> > _______________________________________________
> > cs161-list mailing list
> > cs161-list(a)fas.harvard.edu
> > http://www.fas.harvard.edu/mailman/listinfo/cs161-list
> >
>
Just to make sure, parents kill their children when they exit, that is to say,
no process can exist without a parent (except for the first one).
--arvin
*******************************************
On reflecting at dinner that he had done nothing to help anybody
all day, he uttered these memorable and praiseworthy words.
"Friends, I have lost a day."
-Suetonius
For some reason, I'm unable to run sys161 anymore. I ran config, make
depend, make, and make install. But when I go to ~/cs161/root and run
sys161 kernel, I just get Command not found. This worked fine in the
previous assignments. I do have ~cs161/usr/etc/cs161.cshrc in my .cshrc
file.
Does anyone have any ideas?
Thanks,
Fred
Hi,
I am seeing some strange behavior. Whenever I execute a userlevel program
which makes some system call, the input/output from/to the console in the
kernel becomes really slow. This is after the userprogram has returned and
the the system is waiting at 'OS/161 kernel [? for menu]:'. I can see the
prompt being displayed very slowly ...
Similar problems anyone? Ideas?
Georgi
