This item text has been erased.

47 responses total.

This response has been erased.

In the menumore /usr/stats/DiskUsage command, what
are the numbers on the sides?  Bytes?  On !du,
I have something like 304 and on this i have something
like 504.

This response has been erased.

I didn't delete 200K of files... I don't think
there could have been an old core.. <shrug>

Hey, wait a sec, I deleted my old sent_mail 
things from pine.  That would do it.

thanks to those commands, I found a good load of stuff that simple
!ls -f -l didn't show! Now I've zipped it and stuck it in my main
directory! Thanks popcorn!

300K ? I know we have a disk crunch, but I think that's asking too much
of the users. I thought we were shooting for 1MB. Of course it is true
that nearly everyone on /home is below 1MB.

This response has been erased.

        I don't think 300K is a bad goal. I only use 56K myself, the secret
is to download mail every two weeks, not store any large text documents on
Grex, and never store bianaries for longer than the time it takes to download
them to your home machine.

Hey let's all use 1 MB!  C'mon.  Until we get more disk space this
idea of shooting for 1 MB per user is stupid.  No wonder we can't
enter responses in the bbs.  Use what you absolutely need to use.
I'll bet that most of the people using more than 300K don't absolutely
need everything that's there.  I know a lot of things are handy to
have around, but I've deleted my /bin directory and have been doing
without because I found it unconscionable to use more than most people
when our /home partition is so often starved for space.

This response has been erased.

I tend to accumulate qute a bit of mail and then download it every month
or so.  To download it any more often than that would make it hard to
check what peolple were replying to, but I don't generally need stuff
around that's more than a month old.  Last time I cleared out my mail
directory I was around 850K, which I see now would put me in the top ten,
but I see that I am now just over 200.  One important destinction for how
much disk usage is acceptable is whether somebody uses Grex as their
primary mail address.  Those who do would be expected to have more mail
files sitting around.

Re #12- This is my problem too.

The main reason my disk usage is in the 300's is that I save mail.
I subscribe to a mailing list and the info I get is important to me.
I only download at the beginning of each month, but I'm having a
little trouble for some reason getting my term to download over the
internet.  I guess I'll just have to make the ld call and get this
stuff outa here.

Browse the index here in info and see if there isn't an item
for getting file transfers to work.  Maybe you can save yourself
the ld charges.

Well I have to agree that lower limits are needed for now. I reduced my 
to 363 from somewhere in the 500's, but this is really painful.
I had no idea we were seriously trying for such small user areas.

Re #15- Right now it doesn't look like we can afford NOT to try for such
small user areas.

This response has been erased.

This Item reminds me that I would suggest that it would be useful to
include simple directory and file manipulations in the newuser information
and tutorials. I thought the most helpful thing to me, in the "early"
days, was to discover "where I was", using pwd, cd, ls, etc. 

(probably not the best place to ask, but...)

what does "pwd" do?

"Print Working Directory"

Try it. That's where you "live". Then try a     cd ..     , which
will move you "up" to the /home directory . Then, try a      ls     .
That's where everyone *else* lives. You go home with just an
isolated    cd      . It is very informative to explore one's
environment this way. 

(you have to be in a shell for the above commands to work, I believe)

This response has been erased.

"pwd" is equivilant to "cd" in DOS without any arguments.  However, "cd"
alone in Unix will return you to your home directory.

The commands in #21 work in Picospan, as stated (I made sure to try them
out before posting, to be sure I didn't miss a bang or two).

For some reason, my "pwd" is aliased to "echo $cwd".  Is this quicker then
doing a standard "pwd"?

This response has been erased.

Ya... they are the same ones that I have had since I got my first ultrix
account over at Eastern.  They are a hodge podge of things that I have seen
and liked.  Heck, my 'cd' command is aliased to five sequential commands.

I don't know if the commands save time or what, but they are what I am
used to.  But soon I will have to relearn all the 'real' unix commands. 

Used to be that one could issue     mail -f fylename   and get rid of
messages. When there was sufficient diskspace, I uncompressed a mailfile
that I have *really* wanted to edit down for a long time.
  
So I went through 131 emails, deleted most with the   d    command and
edited some with the    e   command  and spent a well over an hour iin
tis process.
 
I quite with a    q   , not an x  , ***expecting*** that the file would
shrink. Ohhhhhhhh, nOOOOOOOOOO!  "fylename" complete  came back!
  
that has never happened before! 
 
So I thought maybe there was something new in   mail  and ran the   man mail
pages across my screen looking for someting *I* had done that wasn;t kosher.
  
Found no clues. since the file is uncompressed, I'm g9nna leave it
that way until the right set of commands comes along from somewhere.
 
And I can spend another hour or so attempting to delete and edit old mail.
  
And lemme escribe why I don't feel naughty +increasing+ my filespace this
time in the face of a shortage: I have struggled to trim stuff to the
tune of over 900 blocks - even remmers sent a "thank you" note.
 
Retaking aobut 150 extra blocks until I can get  mail to do what it used
to do means I have returned 750 blocks, net, until I can release more, which
I fully intend to do.
  
Also there are some compressd files which no longer uncompress, and that
is taking up a degree of space that I think can be released, but I won't know
unitl I uncompress them and see. They might be backups of someting already
accomplished. (I +am+ anal about backups when I mess aroundwith critical
files). 
  
Seems that uncompress is now linked to gunzip and gunzip doesn;t recognize
the format. Yes, these are from the previous workhorse, Sun2, which may
help someone figure out what I should do to check/edit/download/delete 
these things.
 
But first, I'd like to know the NEW clues for   mail -f  fylename, thank you.

This response has been erased.

AS I said .... getting IN and working on fylename was NO problem with
   mail -f fylename. I spent the better part of two hours cutting/trimming/
deleting/editing/etc. 
 
Getting  OUT   with the *expectation* of a reduced filesize is the problem!
  
Of course it works going in, or I wouldn't have spent al that time messing
with it. Why was the "answer"   "fylename" complete    upon EXIT with q, not
exit with x?
 
And I did ls -ls on the fyle to make sure the space absorbed had
NOT decreased, i.e., that the "answer" was valid. To the byte, it was
the same size in bytes and blocks as two hours before.
  
Doesn't make for any encouragement that way.

I've never tried that in mail, but it always works fine in pine.

Could you edit the file down with pico, or do you want to be sure you 
can keep it compatible with the mailer? 

This response has been erased.

Yes, moving the fyle to   /tmp  is a GoodIdea (tm), one I should have
thought of before, infact (duh). Actually copying, not moving, don't
want to lose the /home space for re-write later.
 
The question is not dumb, I can goof now and then, I'm human, like you.
  
mail -f fyle   is operated on (HA!) and then returned/updated with
the same name, no changes. And when I use my alias I get a group of
files. I did the alias before and after so I could check how much
space had been returned. nada. same file name, natch.
  
Since I have performed this operation quite successfully before the
Sun3, my suspicion would be to ask "what changed?" No, I'm not
suggeting a return to the Sun2 <g>.
 
Editing the file should be independant of the editor. It works or
it doesn't work. the Edit adn Delete functions of   mail   appear
to work JustFine (tm) no matter what   fyle  I use, whether
the /spool/mail/loginid, ~/mbox, or ~/gunzipped for stripping.
  
The problem +seems+ to be in writing the smaller file back to the
disk. The newer size is NOT reflected. It's the "same as the old boss,"
apologies to the Who's "We Won't Get Fooled Again." 
  
Only this time it's Unix and not the Who singing the tune.
  

Does catting the edited file show the deleted info still there, or is it
gone? If the latter, try copying the file to a new name with either the
cp command or cat oldname >newname.  It may be a case of inserting an EOF
marker in the file but not telling the system the file is smaller. 

hmmmmmmm, haven't looked. I will in a bit.

This response has been erased.

Hmm.  I just tried this on one of my own mailfolders, and it seemed
to work fine.  I deleted some messages, and when I was done I
exited with "q", and the messages got deleted.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss