daveh@xtenk.sgi.com (David A Higgen) (09/30/89)
> #/debug (or, in RISC/os, /proc) is *NOT* your swap space. It's a special > #type of virtual filesystem which presents a view of your running processes > #accessible through the file namespace. If it's not mounted, you just can't > #use programs (like some debuggers and other tools) that access processes by > #opening them like files. This has *nothing* to do with your swap space. > #ROGER B.A. KLORESE MIPS Computer Systems, Inc. > But the burning question is... > If your disk is partitioned so that /debug gets, say, 53meg, does that mean > that you only have 53meg of swap space, maximum? > || Tom Stockfisch, UCSD Chemistry tps@chem.ucsd.edu Tom, didn't you READ the article you were appending to? Repeat After Me, 500 times: "/debug is NOT my swap space". /debug is simply an informational window to processes' virtual space, used by debuggers (eg dbx). IT NEITHER CONSUMES NOR PROVIDES PHYSICAL RESOURCES. /debug is not "on" a disk partition. Your swap space IS on one or more disk partitions reserved for the purpose, normally partition 1 on the root disk. Other partitions can be added to the swap space; try 'man swap' for details. Incidentally, is anyone from Tech Pubs here reading this group? I would guess that the continuing confusion on the /debug issue is a strong suggestion that documentation on the point needs to be improved... Dave Higgen
ciemo@bananapc.wpd.sgi.com (Dave Ciemiewicz) (09/30/89)
In article <42340@sgi.sgi.com>, daveh@xtenk.sgi.com (David A Higgen) writes: > > But the burning question is... > > If your disk is partitioned so that /debug gets, say, 53meg, does that mean > > that you only have 53meg of swap space, maximum? > > > || Tom Stockfisch, UCSD Chemistry tps@chem.ucsd.edu > > Tom, didn't you READ the article you were appending to? > Repeat After Me, 500 times: "/debug is NOT my swap space". > > /debug is simply an informational window to processes' virtual space, used > by debuggers (eg dbx). IT NEITHER CONSUMES NOR PROVIDES PHYSICAL RESOURCES. > > /debug is not "on" a disk partition. Your swap space IS on one or more > disk partitions reserved for the purpose, normally partition 1 on the > root disk. Other partitions can be added to the swap space; try > 'man swap' for details. > > Incidentally, is anyone from Tech Pubs here reading this group? I would > guess that the continuing confusion on the /debug issue is a strong > suggestion that documentation on the point needs to be improved... > > > Dave Higgen > /debug is an file interface to system processes. Unmounting /debug to not unmount the swap space; unmounting only removes access to the interface which SGI's dbx can access and debug processes. However, playing out /debug's affectation of a real file system, many of the standard IRIX(TM) file and filesystem commands present information about the /debug interface and the swap partion AS THOUGH they were real live IRIX(TM) file systems though they are not. As part of of this, df of /debug reveals the size of your swap partion. Thus yes, if "df -k /debug" says /debug imitation file system has 51048 kbytes, your swap partion has been partioned for approximately 51MB of swap space (virtual memory). It is wise to take heed from Mr. Higgen and remember that /debug is not a real file system but is a file system abstraction of the processes executing under IRIX(TM). --- Dave Ciemiewicz -- ------------------------------------------------------------------------------- Cosmo Ciemo, Silicon Valley Dude I was traipsing through the fields of my mind when I stepped in something that smelled rather ripe. -------------------------------------------------------------------------------
ciemo@bananapc.wpd.sgi.com (Dave Ciemiewicz) (09/30/89)
In article <42352@sgi.sgi.com>, ciemo@bananapc.wpd.sgi.com (Dave Ciemiewicz) writes: > In article <42340@sgi.sgi.com>, daveh@xtenk.sgi.com (David A Higgen) writes: > > > > But the burning question is... > > > If your disk is partitioned so that /debug gets, say, 53meg, does that mean > > > that you only have 53meg of swap space, maximum? > > > > > || Tom Stockfisch, UCSD Chemistry tps@chem.ucsd.edu > > > > Tom, didn't you READ the article you were appending to? > > Repeat After Me, 500 times: "/debug is NOT my swap space". > > > > /debug is simply an informational window to processes' virtual space, used > > by debuggers (eg dbx). IT NEITHER CONSUMES NOR PROVIDES PHYSICAL RESOURCES. > > > > /debug is not "on" a disk partition. Your swap space IS on one or more > > disk partitions reserved for the purpose, normally partition 1 on the > > root disk. Other partitions can be added to the swap space; try > > 'man swap' for details. > > > > Incidentally, is anyone from Tech Pubs here reading this group? I would > > guess that the continuing confusion on the /debug issue is a strong > > suggestion that documentation on the point needs to be improved... > > > > > > Dave Higgen > > > > /debug is an file interface to system processes. Unmounting /debug to > not unmount the swap space; unmounting only removes access to the interface > which SGI's dbx can access and debug processes. > > However, playing out /debug's affectation of a real file system, many > of the standard IRIX(TM) file and filesystem commands present information > about the /debug interface and the swap partion AS THOUGH they were real > live IRIX(TM) file systems though they are not. > > As part of of this, df of /debug reveals the size of your swap partion. > Thus yes, if "df -k /debug" says /debug imitation file system has > 51048 kbytes, your swap partion has been partioned for approximately > 51MB of swap space (virtual memory). It turns out I was wrong on this point. "df -k /debug" reveals the size of your virtual memory which is the size of the swap partition plus the size of physical memory. If you really want to find out the size of your swap partion, do as root: prtvtoc /dev/rvh This will print the volume header of your first disk. If your disk is of standard configuration, your root partion will be on partition 0, swap on partition 1, and /usr on partition 6. I did this on my machine and found out that my swap partion was 72,100 sectors or 36,050 kbytes in size. My physical memory is 16 MB or 16,384 kbytes. Add the two together and you get 52,434 KB or approximately what "df -k /debug" had reported above for my virtual memory size. (I can't account for the discrepancy.) > > It is wise to take heed from Mr. Higgen and remember that /debug is not > a real file system but is a file system abstraction of the processes > executing under IRIX(TM). > Advice I really should have taken myself. Thanks to Chris Dunlap for pointing out the error of my ways. -- ------------------------------------------------------------------------------- Cosmo Ciemo, Silicon Valley Dude I was traipsing through the fields of my mind when I stepped in something that smelled rather ripe. -------------------------------------------------------------------------------
mjz@texhrc.UUCP (Michael Zeitlin) (07/03/90)
Thanks to everyone for responding to my /debug problem...
rebooting was engough!!
(i had to mkdir /debug...of coarse)
thanks...mkibler@eecs.wsu.edu (Michael K. Kibler) (02/09/91)
I have just upgraded to 3.3.2 and /debug file system is missing. Any ideas on how to make this file system? Thanks in advance, -- ---- Mike ( ~~ Radiosity is more than just heat! ) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Michael K. Kibler INTERNET: mkibler@eecs.wsu.edu Elect/Compt. Engr. Dept. UUCP : ...uunet!eecs.wsu.edu!mkibler
olson@anchor.esd.sgi.com (Dave Olson) (02/10/91)
In <1991Feb09.090111.19265@eecs.wsu.edu> mkibler@eecs.wsu.edu (Michael K. Kibler) writes: | I have just upgraded to 3.3.2 and /debug file system is missing. | Any ideas on how to make this file system? Strange, unless you had an installation problem. In any case, this should do it: mkdir /debug mount -t dbg /debug /debug /etc/rc2.d/S01MOUNTFSYS will automatically mount it during boot if /debug exists and is a directory. -- Dave Olson Life would be so much easier if we could just look at the source code.
eugholz@UZI.MIT.EDU (Eugene Gholz) (03/20/91)
I'm a little confused about what the directory /debug is for -- or, more to the point, how it is used. Various big files seem to constantly appear in the /debug directory -- and constantly to be updated since ls -l reports new dates for the last file update quite regularly. These files, however, never seem to vanish entirely -- they are just a permanent (?) fixture of my file system. Furthermore, they are not readable or writeable, even by root, even though their permissions indicate that they are both. The service guy that SGI sent out here to fix an unrelated problem (as far as both he and I could tell, unrelated, that is) didn't have much of a clue what was going on in this directory at all. In fact, he was surprised that there even was a /debug directory that I could cd into. Any ideas what's going on? The only reason that I even noticed this directory was that when doing a full system backup with bru -Z, the last tape starts trying to back-up files /debug/00001, etc., and gets read errors, "can't compress" errors, and "warning - file truncated" messages. The conclusion of the SGI support staff that I was in touch with was that the only way to get a system backup without errors was to exclude filenames beginning with /debug from my bru command... This seems really odd to me. Any information will be much appreciated. I'm really curious. Thanks, Eugene Gholz (eugholz@athena.mit.edu)
" ratcliffe) (03/21/91)
In article <9103192219.AA00700@uzi.mit.edu> eugholz@UZI.MIT.EDU (Eugene Gholz) writes: >I'm a little confused about what the directory /debug is for -- or, more >to the point, how it is used. think of "/debug" as a "ghost" "filesystem". it is NOT a filesystem according to that word's techincal definition. refer to the DBG(4) to get the bottom-line low-down on this. /debug is used, among other things to provide handles to the process id's currently running that the debuggers can lock onto. DESCRIPTION The debug file system, normally mounted under /debug, provides an interface to running processes that may be used by debuggers such as dbx... think of it as a representation of the swap space. -- daveus rattus yer friendly neighborhood ratman KOYAANISQATSI ko.yan.nis.qatsi (from the Hopi Language) n. 1. crazy life. 2. life in turmoil. 3. life out of balance. 4. life disintegrating. 5. a state of life that calls for another way of living.
hilchey@ucs.ubc.ca (Paul Hilchey) (03/21/91)
In article <9103192219.AA00700@uzi.mit.edu>, eugholz@UZI.MIT.EDU (Eugene Gholz) writes: |> I'm a little confused about what the directory /debug is for |> . . . |> The conclusion of the SGI |> support staff that I was in touch with was that the only way to get a system |> backup without errors was to exclude filenames beginning with /debug from my |> bru command... The "files" in /debug are actually processes, and if you read or write to them you will be reading or writing to the processes virtual memory. To avoid trying to save them on your backup tapes you should use Bru with the -m option (don't cross mount points), and specify the filesystems that you do want to save (typically: / /usr). ____ Paul Hilchey Computing Services The University of British Columbia