[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] meta-verify -f messed up GUI
- Subject: Re: [cobalt-users] meta-verify -f messed up GUI
- From: "Julius" <lists@xxxxxxxx>
- Date: Mon Jun 3 17:04:02 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
> You do. It's the way linux/unix works.
Sounds like no good reason, similar to "Just because".
The past, my past, has proven that I don't need to know
group-ID's or anything related to creating new users for linux.
Unix is not linux, btw. Also; Unix manuals are written
by guys who know how to do that, and have examples in it.
I still don't know why, but BSD man pages are always better.
Sun Cobalt RaQs should have based their servers on FreeBSD.
>> It's a man page writer freaking out on his/her own product,
>> not thinking about the possible confusion it might invoke
>> on the reader who doesn't give a rats ass and who doesn't
>> have time to read badly written manuals without ONE example
>> commandline in it. These man pages are truly a pain,
>> written by anti-socials, not with much care IMO.
>
> Tens of thousands of linux/unix users are wrong then and you're
> right.
Well yes. Tens of thousands of people smoke
and drink too much alcohol, I don't.
Need I mention more examples?
> Says you, who responds to every attempt to help with "that won't
> help".
You have proven to not be able to help, you
can't even give me an example commandline,
even though you think they must be easy to create.
> Linux is written by volunteer help. You may volunteer to do
> anything you think needs to be done differently.
Here's what's strange in Cobalt RaQ's case; The
man adduser is NOT the manual that Jeff B has written,
that would be this one:
./adduser -d www.foo.com -f "Mr Bar" -u bar -p "foiledagain" -q 400 -t
./adduser -u foo
./adduser -h
usage: ./adduser [-d fqdn] [-f full name] [-u user name] [-p password]
[-q quota] [-t] [-a] [-x] [-o]
-d fully quilified domain name ie. www.domain.com
(default: base hostname + base domain name)
-f user's Full name
-u user name
-p users passwd (default: $dflPasswd)
-q quota in MB
-t shell(telnet) enabled
-a user is a site administrator
-x frontpage enabled
-o apop enabled
Now there's a manual that explains things.
>> Why do you want it to be so black and white all the time?
>> Sun Cobalt should have thought of creating a nice commandline
>> backup-shell, which could perfectly function in place of
>> all the web-admin pages.
>
> They did.
I would not be writing here if they did.
I'm writing about an entire backup shell, which
would be graphic, menu-driven, like Midnight Commander,
and not a bunch of commandline switches where
one needs to type behind a prompt.
> Did you study the RaQ, to see if it had such a shell, before you
> bought it?
Read the manual, it clearly says what you never need to
be doing. It would void warranty to do things as root, yet
I have voided warranty to get a decent form of restorable
backups for the RaQs I need to administer.
> Thousands of people successfully administrate RaQs.
I have too, thus far. Only to find that certain
configurations cannot be done by use of the GUI alone.
Try creating a www.domain on a RaQ4i, create 200 users
for it, install some webmail package (and void warranty
by doing so), then change the domain name to
mail.someotherdomainname, et voila: trouble! The
(pretty old) version of sendmail f*cks up its virtusertable.
--
J