C:\Documents and Settings\phb>ftp releases.mozilla.org Connected to releases.geo.mozilla.com. 220 Welcome to the Mozilla releases FTP server User (releases.geo.mozilla.com:(none)): anonymous 331 Please specify the password. Password: 230 Login successful. ftp> cd pub 250 Directory successfully changed. ftp> cd mozilla.org/firefox/releases 250 Directory successfully changed. ftp> cd latest-3.0 250 Directory successfully changed. ftp> cd win32/en-US 250 Directory successfully changed. ftp> ls 200 PORT command successful. Consider using PASV. 150 Here comes the directory listing. Firefox Setup 3.0.5.exe Firefox Setup 3.0.5.exe.asc 226 Directory send OK. ftp: 54 bytes received in 0.02Seconds 3.38Kbytes/sec. ftp> bye 221 Goodbye.
Sure, when XP stops getting patches Vista/Win7 instantly become more desirable. Lack of support finally pushed me to migrate from W2K to XP a couple of years ago, I can't think of any must-have XP features.
Easy user switching is handy, but I accomplished the same thing with a desktop shortcut for a CMD session RUNAS Administrator.
The problem is, W2K and XP are pretty close to "good enough". They're a pretty decent compromise between performance, stability, features, backwards compatibility, and driver support.
As long as the latest Firefox still runs on XP, as long as my games still work on XP, there's little incentive to upgrade to Vista/Win7.
because someone's patented the judicial system, and only those rich enough to afford it can actually access it...
Everyone in law school right now has student loans out the wazoo, you could join them easily enough.
not to count that defending criminals is not my style (although I do believe in justice - in principle), so I'll leave that to those who keep benefiting from it...
There's lots of boring law that you don't see on TV, corporate law, tax law, family law...
This disk would be fantastic in a dedicated compiler box.
Compiling is usually I/O bound, and the intermediate files and compiled programs are ephemeral. Who cares if the power goes down and you lose everything, just recompile and you're back in business.
I did some digging, what we're talking about apparently already exists - w3m includes a manpage browser called w3mman. Works well on OpenBSD, seems to do everything we discussed.
1) The man pages are self-contained on your filesystem right now, so if they were converted to HTML there's no reason to change that.
2) The people doing this hypothetical documentation would be the people who are responsible for today's great documentation. Presumably they wouldn't do egregiously stupid things to make the new docs less functional then the old docs. I'm sure 99% of todays manpages were built from a standardized template or editing an old manpage, if there are correct examples and templates people will do the right thing, and if not people will complain and documents will be fixed.
3) Yeah, man, apropos etc would probably become wrapper scripts around links or w3m or whatever.
As far as HTML versions, I wouldn't care as long as it works, whatever the documentation guys are using today I suppose.
disclaimer - I personally love the complete, well organized documentation inside the manpages, but I'm not married to/usr/bin/man.
Re:Man pages are not a quality control technique!
on
FreeBSD 7.1 Released
·
· Score: 1
Man pages are a solved problem. It works, and it works well.
Yeah, that's why no-one has done the work to HTML-ize them.
No change needed nor wanted.
Come on now, nothing is perfect. Suppose I'm reading fstab(5), at the bottom under SEE ALSO wouldn't it be nice if I could just tab over to mount(8) and read that manpage? Once I'm in the mount(8) manpage wouldn't it be nice to be able to tab to mount_nfs(8) or mount_cd9660(8) or whatever?
Someone once had a bunch of scripts that trawled the FreeBSD man pages and built an HTML index like I describe, but it appears to be dead now:(
Re:Man pages are not a quality control technique!
on
FreeBSD 7.1 Released
·
· Score: 1
It's not such a bad idea, you could add links or w3m to the base install and design the documentation so it is legible in either graphical browsers or the preferred text browser.
The real question should be: do the benefits of HTML documentation make it worth the time/effort to redo/reformat all the %PROJECT% documentation?
People have been suggesting this for probably 10 years, and no-one has done the metric buttload of work required to make it happen. 10 years from now, people will still be suggesting it.
I mean, I'm freaked out that my church (where I'm the network admin) doesn't have a proper backup solution yet (cost being the issue; any suggestions welcome).
Rsync snapshots to a USB drive. Maybe a couple of USB drives, one that you take home every week while the other stays plugged in, swap every Sunday after the service.
If your server is *nix I like rsnapshot, a wrapper script for hourly/daily/weekly/monthly snapshots - dead simple and painless.
If your server is Win32 I'm told rsync works on cygwin, never tried it myself.
Someone should build a netbook with the IBM-style nipple mouse instead of a damn touchpad. Gotta be cheaper then touchscreens, and it works with today's UI.
80s mainframe tech is NEW and EXCITING to a depressing number of tech people, look at how excited everyone got when someone remembered and re-implemented virtualization.
"eating your own dog food" is an old tech industry expression, it means the company uses their own products internally, as a testbed and to build up expertise.
The grandparent didn't bite, so I guess I'll have to reply to you:)
My dad keeps a big garden, and I'm sure he doesn't grow anywhere near 50% of the family's vegetable/grain intake, never mind fruit/dairy/eggs/meat.
I'd love to know how every citizen can have enough acreage to grow 50% of their food while living close enough to bike to work.
As you say, The EarthBox looks like a great way to supplement your diet. If every household had a couple of those we'd be healthier, and make a dent in the energy required by professional farmers.
I think the only realistic hope is for each of us to make several little steps like EarthBoxes, making little nibbles in our energy requirements that collectively add up to big savings.
Slashdot Mirror
C:\Documents and Settings\phb>ftp releases.mozilla.org
Connected to releases.geo.mozilla.com.
220 Welcome to the Mozilla releases FTP server
User (releases.geo.mozilla.com:(none)): anonymous
331 Please specify the password.
Password:
230 Login successful.
ftp> cd pub
250 Directory successfully changed.
ftp> cd mozilla.org/firefox/releases
250 Directory successfully changed.
ftp> cd latest-3.0
250 Directory successfully changed.
ftp> cd win32/en-US
250 Directory successfully changed.
ftp> ls
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
Firefox Setup 3.0.5.exe
Firefox Setup 3.0.5.exe.asc
226 Directory send OK.
ftp: 54 bytes received in 0.02Seconds 3.38Kbytes/sec.
ftp> bye
221 Goodbye.
Hell no, but it doesn't matter because regular users also don't want a version with absolutely no browser installed.
Sure, when XP stops getting patches Vista/Win7 instantly become more desirable. Lack of support finally pushed me to migrate from W2K to XP a couple of years ago, I can't think of any must-have XP features.
Easy user switching is handy, but I accomplished the same thing with a desktop shortcut for a CMD session RUNAS Administrator.
The problem is, W2K and XP are pretty close to "good enough". They're a pretty decent compromise between performance, stability, features, backwards compatibility, and driver support.
As long as the latest Firefox still runs on XP, as long as my games still work on XP, there's little incentive to upgrade to Vista/Win7.
Did they get rid of ftp.exe in Vista? I know it's still in XP.
because someone's patented the judicial system, and only those rich enough to afford it can actually access it...
Everyone in law school right now has student loans out the wazoo, you could join them easily enough.
not to count that defending criminals is not my style (although I do believe in justice - in principle), so I'll leave that to those who keep benefiting from it...
There's lots of boring law that you don't see on TV, corporate law, tax law, family law...
to me a lawyer is just like someone in marketing, but that's another story
If it's so easy, why don't you go to law school and make the big bucks?
I thought the whole point of aircan instead of vacuum is to avoid static electricity zapping the computer?
This disk would be fantastic in a dedicated compiler box.
Compiling is usually I/O bound, and the intermediate files and compiled programs are ephemeral. Who cares if the power goes down and you lose everything, just recompile and you're back in business.
Gentoo here I come!
But it makes Apache better too.
Sometimes it is possible for everyone to win.
In really big shops the bottleneck is usually testing patches against a zillion weird|old|crazy applications that someone, somewhere absolutely needs.
I did some digging, what we're talking about apparently already exists - w3m includes a manpage browser called w3mman. Works well on OpenBSD at least.
I did some digging, what we're talking about apparently already exists - w3m includes a manpage browser called w3mman. Works well on OpenBSD, seems to do everything we discussed.
http://www.obsoletecomputermuseum.org/compaq/
Looks like the screen is about the same size...
Are those hyperlinked man pages in the base install? I haven't used FreeBSD since 4.something.
1) The man pages are self-contained on your filesystem right now, so if they were converted to HTML there's no reason to change that.
2) The people doing this hypothetical documentation would be the people who are responsible for today's great documentation. Presumably they wouldn't do egregiously stupid things to make the new docs less functional then the old docs. I'm sure 99% of todays manpages were built from a standardized template or editing an old manpage, if there are correct examples and templates people will do the right thing, and if not people will complain and documents will be fixed.
3) Yeah, man, apropos etc would probably become wrapper scripts around links or w3m or whatever.
As far as HTML versions, I wouldn't care as long as it works, whatever the documentation guys are using today I suppose.
disclaimer - I personally love the complete, well organized documentation inside the manpages, but I'm not married to /usr/bin/man.
Man pages are a solved problem. It works, and it works well.
Yeah, that's why no-one has done the work to HTML-ize them.
No change needed nor wanted.
Come on now, nothing is perfect. Suppose I'm reading fstab(5), at the bottom under SEE ALSO wouldn't it be nice if I could just tab over to mount(8) and read that manpage? Once I'm in the mount(8) manpage wouldn't it be nice to be able to tab to mount_nfs(8) or mount_cd9660(8) or whatever?
Someone once had a bunch of scripts that trawled the FreeBSD man pages and built an HTML index like I describe, but it appears to be dead now :(
It's not such a bad idea, you could add links or w3m to the base install and design the documentation so it is legible in either graphical browsers or the preferred text browser.
The real question should be: do the benefits of HTML documentation make it worth the time/effort to redo/reformat all the %PROJECT% documentation?
People have been suggesting this for probably 10 years, and no-one has done the metric buttload of work required to make it happen. 10 years from now, people will still be suggesting it.
I mean, I'm freaked out that my church (where I'm the network admin) doesn't have a proper backup solution yet (cost being the issue; any suggestions welcome).
Rsync snapshots to a USB drive. Maybe a couple of USB drives, one that you take home every week while the other stays plugged in, swap every Sunday after the service.
If your server is *nix I like rsnapshot, a wrapper script for hourly/daily/weekly/monthly snapshots - dead simple and painless.
If your server is Win32 I'm told rsync works on cygwin, never tried it myself.
I'd like to see a nice post-mortem in a mainstream IT magazine once the company actually goes broke.
A clipping from Infoworld or CIOwhatever magazine might allow even beancounters to understand the risks of Scrooging on backup and DR infrastructure.
Someone should build a netbook with the IBM-style nipple mouse instead of a damn touchpad. Gotta be cheaper then touchscreens, and it works with today's UI.
80s mainframe tech is NEW and EXCITING to a depressing number of tech people, look at how excited everyone got when someone remembered and re-implemented virtualization.
"eating your own dog food" is an old tech industry expression, it means the company uses their own products internally, as a testbed and to build up expertise.
http://en.wikipedia.org/wiki/Eat_one's_own_dog_food
The grandparent didn't bite, so I guess I'll have to reply to you :)
My dad keeps a big garden, and I'm sure he doesn't grow anywhere near 50% of the family's vegetable/grain intake, never mind fruit/dairy/eggs/meat.
I'd love to know how every citizen can have enough acreage to grow 50% of their food while living close enough to bike to work.
As you say, The EarthBox looks like a great way to supplement your diet. If every household had a couple of those we'd be healthier, and make a dent in the energy required by professional farmers.
I think the only realistic hope is for each of us to make several little steps like EarthBoxes, making little nibbles in our energy requirements that collectively add up to big savings.
How big a garden do you need to grow 50% of your own food?