Ah, so that's why the page with the Origin 350 specs was taken down. What are you gonna do with the Origin 350s then, neko?
The collected works of ritchan - Page 2
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Hey, has anybody upgraded the CPU on their SunPCi II? I know Sun supports upgrades on the III. Do Tualatins work? Does the SunPCi II support a 100MHz FSB, i.e. will it play well with Coppermine Pentium IIIs?
Code:
configure: WARNING:
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
How does one build the C libraries? Is neko-ncurses built with UTF-8 support? Is the current neko-nano built with UTF-8 support? The config.log looks like it's actually barfing on a previous compile fail instead... attached, naturally.
I have an opportunity to buy a dual R10K/225 with 1MB of cache for around 20EURs. I think that's cheap.
make -j2 would be faster, I suppose, and mplayer might be faster now that colourspace conversion is on a different CPU, but it's not like I use both often. Plus I'm worried about exactly how much single thread performance loss I would incur.
I'm leaning towards overclocking my 300MHz, but I'm not sure how to do it. Is the multiplier changeable or do I have to desolder the oscillator?
make -j2 would be faster, I suppose, and mplayer might be faster now that colourspace conversion is on a different CPU, but it's not like I use both often. Plus I'm worried about exactly how much single thread performance loss I would incur.
I'm leaning towards overclocking my 300MHz, but I'm not sure how to do it. Is the multiplier changeable or do I have to desolder the oscillator?
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I figured it would be nice to have an updated library, even if I don't know what it does. So I tried my hand at it. This one is compiled with -ltermlib, as dexter1 proposed here:
viewtopic.php?f=15&t=1781
I have no idea if it's compiled or not, because I have no idea about libraries in general. It generated a .a file, which I suppose is a static library, but it doesn't give me a libreadline.so.6 file, unlike nekoware readline-4 which has a libreadline.so.4 and a libreadline.a.
Then again, all MIPSPro reported was warnings relating to -ltermlib. This is my export:
And here's some of the output:
viewtopic.php?f=15&t=1781
I have no idea if it's compiled or not, because I have no idea about libraries in general. It generated a .a file, which I suppose is a static library, but it doesn't give me a libreadline.so.6 file, unlike nekoware readline-4 which has a libreadline.so.4 and a libreadline.a.
Then again, all MIPSPro reported was warnings relating to -ltermlib. This is my export:
Code:
declare -x CC="c99"
declare -x CFLAGS="-O3 -mips4 -I/usr/nekoware/include"
declare -x CLASSPATH="."
declare -x COLORTERM="1"
declare -x CPPFLAGS="-I/usr/nekoware/include -I/usr/include"
declare -x CXX="CC"
declare -x CXXFLAGS="-O3 -mips4 -I/usr/nekoware/include"
declare -x DISPLAY=":0"
declare -x F77="f77"
declare -x GNOME2_DIR="/usr/nekoware"
declare -x GNULD="/usr/nekoware/bin/gld"
declare -x GNUMAKE="/usr/nekoware/bin/make"
declare -x HOME="/usr/people/shinichi"
declare -x JAVA_HOME="/usr/java2"
declare -x KDEDIRS="/usr/nekoware/kde"
declare -x LANG="de"
declare -x LC_ALL="de"
declare -x LDFLAGS="-L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib"
declare -x LD_LIBRARY64_PATH="/usr/nekoware/lib64"
declare -x LD_LIBRARYN32_PATH="/usr/nekoware/lib"
declare -x LD_LIBRARY_PATH="/usr/nekoware/lib"
declare -x LOGNAME="shinichi"
declare -x MAIL="/usr/mail//shinichi"
declare -x MANFMTCMD="groff -Tascii -man"
declare -x MANPATH="/usr/share/catman:/usr/share/man:/usr/catman:/usr/man:/usr/nekoware/man:/usr/nekoware/mysql5/man:/usr/nekoware/php5/man"
declare -x MP_SET_NUMTHREAD="1"
declare -x MSGVERB="text:action"
declare -x NOMSGLABEL="1"
declare -x NOMSGSEVERITY="1"
declare -x OLDPWD="/usr/people/shinichi/source/readline-6.1"
declare -x PATH="/sbin:/usr/sbin:/usr/bsd:/usr/bin:/etc:/usr/sysadm/privbin:/usr/etc:/usr/bin/X11:/usr/gfx:/usr/nekoware/mysql5/bin:/usr/nekoware/bin:/usr/nekoware/sbin:/usr/nekoware/kde/bin::/usr/java2/bin"
declare -x PERL="/usr/nekoware/bin/perl"
declare -x PKG_CONFIG="/usr/nekoware/bin/pkg-config"
declare -x PKG_CONFIG_LIBDIR="/usr/nekoware/lib"
declare -x PKG_CONFIG_PATH="/usr/nekoware/lib/pkgconfig"
declare -x PS1="[\\h,\\u]:\\w \$ "
declare -x PS2="> "
declare -x PWD="/usr/people/shinichi/source"
declare -x PYTHONHOME="/usr/nekoware"
declare -x PYTHONPATH="/usr/nekoware/lib/python2.4"
declare -x QTDIR="/usr/nekoware/qt4"
declare -x SGML_CATALOG_FILES="/usr/nekoware/share/sgml/docbook/dsssl/modular/catalog:/usr/nekoware/share/sgml/docbook/4.1/catalog:/usr/nekoware/share/sgml/docbook/4.0/catalog:/usr/nekoware/share/sgml/docbook/3.1/catalog:/usr/nekoware/share/sgml/docbook/3.0/catalog:/usr/nekoware/share/sgml/iso8879/catalog:/usr/nekoware/share/sgml/jade/catalog"
declare -x SHELL="/usr/nekoware/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="192.168.1.10 52174 22"
declare -x SSH_CONNECTION="192.168.1.10 52174 192.168.1.13 22"
declare -x SSH_TTY="/dev/ttyq0"
declare -x TERM="xterm"
declare -x TZ="CET-1CEST-2,M3.5.0/2,M10.5.0/3"
declare -x USER="shinichi"
declare -x CFLAGS="-O3 -mips4 -I/usr/nekoware/include"
declare -x CLASSPATH="."
declare -x COLORTERM="1"
declare -x CPPFLAGS="-I/usr/nekoware/include -I/usr/include"
declare -x CXX="CC"
declare -x CXXFLAGS="-O3 -mips4 -I/usr/nekoware/include"
declare -x DISPLAY=":0"
declare -x F77="f77"
declare -x GNOME2_DIR="/usr/nekoware"
declare -x GNULD="/usr/nekoware/bin/gld"
declare -x GNUMAKE="/usr/nekoware/bin/make"
declare -x HOME="/usr/people/shinichi"
declare -x JAVA_HOME="/usr/java2"
declare -x KDEDIRS="/usr/nekoware/kde"
declare -x LANG="de"
declare -x LC_ALL="de"
declare -x LDFLAGS="-L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib"
declare -x LD_LIBRARY64_PATH="/usr/nekoware/lib64"
declare -x LD_LIBRARYN32_PATH="/usr/nekoware/lib"
declare -x LD_LIBRARY_PATH="/usr/nekoware/lib"
declare -x LOGNAME="shinichi"
declare -x MAIL="/usr/mail//shinichi"
declare -x MANFMTCMD="groff -Tascii -man"
declare -x MANPATH="/usr/share/catman:/usr/share/man:/usr/catman:/usr/man:/usr/nekoware/man:/usr/nekoware/mysql5/man:/usr/nekoware/php5/man"
declare -x MP_SET_NUMTHREAD="1"
declare -x MSGVERB="text:action"
declare -x NOMSGLABEL="1"
declare -x NOMSGSEVERITY="1"
declare -x OLDPWD="/usr/people/shinichi/source/readline-6.1"
declare -x PATH="/sbin:/usr/sbin:/usr/bsd:/usr/bin:/etc:/usr/sysadm/privbin:/usr/etc:/usr/bin/X11:/usr/gfx:/usr/nekoware/mysql5/bin:/usr/nekoware/bin:/usr/nekoware/sbin:/usr/nekoware/kde/bin::/usr/java2/bin"
declare -x PERL="/usr/nekoware/bin/perl"
declare -x PKG_CONFIG="/usr/nekoware/bin/pkg-config"
declare -x PKG_CONFIG_LIBDIR="/usr/nekoware/lib"
declare -x PKG_CONFIG_PATH="/usr/nekoware/lib/pkgconfig"
declare -x PS1="[\\h,\\u]:\\w \$ "
declare -x PS2="> "
declare -x PWD="/usr/people/shinichi/source"
declare -x PYTHONHOME="/usr/nekoware"
declare -x PYTHONPATH="/usr/nekoware/lib/python2.4"
declare -x QTDIR="/usr/nekoware/qt4"
declare -x SGML_CATALOG_FILES="/usr/nekoware/share/sgml/docbook/dsssl/modular/catalog:/usr/nekoware/share/sgml/docbook/4.1/catalog:/usr/nekoware/share/sgml/docbook/4.0/catalog:/usr/nekoware/share/sgml/docbook/3.1/catalog:/usr/nekoware/share/sgml/docbook/3.0/catalog:/usr/nekoware/share/sgml/iso8879/catalog:/usr/nekoware/share/sgml/jade/catalog"
declare -x SHELL="/usr/nekoware/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="192.168.1.10 52174 22"
declare -x SSH_CONNECTION="192.168.1.10 52174 192.168.1.13 22"
declare -x SSH_TTY="/dev/ttyq0"
declare -x TERM="xterm"
declare -x TZ="CET-1CEST-2,M3.5.0/2,M10.5.0/3"
declare -x USER="shinichi"
And here's some of the output:
Code:
c99 -c -DHAVE_CONFIG_H -I/usr/nekoware/include -I/usr/include -I. -I.. -I.. -DRL_LIBRARY_VERSION='"6.1"' -O3 -mips4 -I/usr/nekoware/include -K PIC -o mbutil.o ../mbutil.c
cc-1552 c99: WARNING File = ../mbutil.c, Line = 151
The variable "non_zero_prev" is set but never used.
int prev, non_zero_prev, point, length;
^
mv mbutil.o mbutil.so
rm -f tilde.so
c99 -c -DHAVE_CONFIG_H -I/usr/nekoware/include -I/usr/include -I. -I.. -I.. -DRL_LIBRARY_VERSION='"6.1"' -O3 -mips4 -I/usr/nekoware/include -K PIC -DREADLINE_LIBRARY -c -o tilde.o ../tilde.c
mv tilde.o tilde.so
rm -f compat.so
c99 -c -DHAVE_CONFIG_H -I/usr/nekoware/include -I/usr/include -I. -I.. -I.. -DRL_LIBRARY_VERSION='"6.1"' -O3 -mips4 -I/usr/nekoware/include -K PIC -o compat.o ../compat.c
mv compat.o compat.so
rm -f libreadline.so.6
ld -shared -no_unresolved -soname libreadline.so.6 -L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib -rpath /usr/nekoware/lib -o libreadline.so.6 readline.so vi_mode.so funmap.so keymaps.so parens.so search.so rltty.so complete.so bind.so isearch.so display.so signals.so util.so kill.so undo.so macro.so input.so callback.so terminal.so text.so nls.so misc.so xmalloc.so history.so histexpand.so histfile.so histsearch.so shell.so mbutil.so tilde.so compat.so
(null): WARNING 1 : Unknown option: Wl,-rpath (ignored).
(null): WARNING 1 : Unknown option: Wl,/usr/nekoware/lib (ignored).
ld32: WARNING 84 : /usr/lib32/libtermlib.so is not used for resolving any symbol.
ld32: WARNING 157: Unresolved text symbol "free" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strlen" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcpy" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fprintf" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fflush" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sigsetjmp" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "tolower" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__libc_attr" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__iob" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strchr" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncpy" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "toupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "iswupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "towlower" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "iswlower" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "towupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "qsort" -- 1st referenced by funmap.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "select" -- 1st referenced by parens.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcmp" -- 1st referenced by search.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__new_tcgetattr" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__new_tcsetattr" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "ioctl" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "errno" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "stat" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "lstat" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "access" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strrchr" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__semputc" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__flsbuf" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strpbrk" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "endpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "setpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "opendir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "wcwidth" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__us_rsthread_stdio" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fwrite" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncmp" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "readdir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncasecmp" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "closedir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "open" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "read" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "close" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcasecmp" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "atoi" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sprintf" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: Giving up after printing 50 warnings. Use -wall to print all warnings.
rm -f libhistory.so.6
ld -shared -no_unresolved -soname libhistory.so.6 -L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib -rpath /usr/nekoware/lib -o libhistory.so.6 history.so histexpand.so histfile.so histsearch.so shell.so mbutil.so xmalloc.so
(null): WARNING 1 : Unknown option: Wl,-rpath (ignored).
(null): WARNING 1 : Unknown option: Wl,/usr/nekoware/lib (ignored).
ld32: WARNING 84 : /usr/lib32/libtermlib.so is not used for resolving any symbol.
ld32: WARNING 157: Unresolved text symbol "strlen" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcpy" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "atol" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "time" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "snprintf" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "free" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncpy" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__libc_attr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strchr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strrchr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncmp" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "memmove" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "open" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fstat" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "malloc" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "close" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "read" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "write" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "errno" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getenv" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getuid" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getpwuid" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sprintf" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "putenv" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fcntl" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "wcwidth" -- 1st referenced by mbutil.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fprintf" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "exit" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "realloc" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__iob" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
gmake[1]: Leaving directory `/usr/people/shinichi/source/readline-6.1/shlib'
cc-1552 c99: WARNING File = ../mbutil.c, Line = 151
The variable "non_zero_prev" is set but never used.
int prev, non_zero_prev, point, length;
^
mv mbutil.o mbutil.so
rm -f tilde.so
c99 -c -DHAVE_CONFIG_H -I/usr/nekoware/include -I/usr/include -I. -I.. -I.. -DRL_LIBRARY_VERSION='"6.1"' -O3 -mips4 -I/usr/nekoware/include -K PIC -DREADLINE_LIBRARY -c -o tilde.o ../tilde.c
mv tilde.o tilde.so
rm -f compat.so
c99 -c -DHAVE_CONFIG_H -I/usr/nekoware/include -I/usr/include -I. -I.. -I.. -DRL_LIBRARY_VERSION='"6.1"' -O3 -mips4 -I/usr/nekoware/include -K PIC -o compat.o ../compat.c
mv compat.o compat.so
rm -f libreadline.so.6
ld -shared -no_unresolved -soname libreadline.so.6 -L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib -rpath /usr/nekoware/lib -o libreadline.so.6 readline.so vi_mode.so funmap.so keymaps.so parens.so search.so rltty.so complete.so bind.so isearch.so display.so signals.so util.so kill.so undo.so macro.so input.so callback.so terminal.so text.so nls.so misc.so xmalloc.so history.so histexpand.so histfile.so histsearch.so shell.so mbutil.so tilde.so compat.so
(null): WARNING 1 : Unknown option: Wl,-rpath (ignored).
(null): WARNING 1 : Unknown option: Wl,/usr/nekoware/lib (ignored).
ld32: WARNING 84 : /usr/lib32/libtermlib.so is not used for resolving any symbol.
ld32: WARNING 157: Unresolved text symbol "free" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strlen" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcpy" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fprintf" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fflush" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sigsetjmp" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "tolower" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__libc_attr" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__iob" -- 1st referenced by readline.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strchr" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncpy" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "toupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "iswupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "towlower" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "iswlower" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "towupper" -- 1st referenced by vi_mode.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "qsort" -- 1st referenced by funmap.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "select" -- 1st referenced by parens.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcmp" -- 1st referenced by search.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__new_tcgetattr" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__new_tcsetattr" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "ioctl" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "errno" -- 1st referenced by rltty.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "stat" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "lstat" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "access" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strrchr" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__semputc" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "__flsbuf" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strpbrk" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "endpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "setpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "opendir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "wcwidth" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__us_rsthread_stdio" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fwrite" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncmp" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getpwent" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "readdir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncasecmp" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "closedir" -- 1st referenced by complete.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "open" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "read" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "close" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcasecmp" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "atoi" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sprintf" -- 1st referenced by bind.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: Giving up after printing 50 warnings. Use -wall to print all warnings.
rm -f libhistory.so.6
ld -shared -no_unresolved -soname libhistory.so.6 -L/usr/nekoware/lib -Wl,-rpath -Wl,/usr/nekoware/lib -ltermlib -rpath /usr/nekoware/lib -o libhistory.so.6 history.so histexpand.so histfile.so histsearch.so shell.so mbutil.so xmalloc.so
(null): WARNING 1 : Unknown option: Wl,-rpath (ignored).
(null): WARNING 1 : Unknown option: Wl,/usr/nekoware/lib (ignored).
ld32: WARNING 84 : /usr/lib32/libtermlib.so is not used for resolving any symbol.
ld32: WARNING 157: Unresolved text symbol "strlen" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strcpy" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "atol" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "time" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "snprintf" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "free" -- 1st referenced by history.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncpy" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__libc_attr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strchr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strrchr" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "strncmp" -- 1st referenced by histexpand.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "memmove" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "open" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fstat" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "malloc" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "close" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "read" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "write" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "errno" -- 1st referenced by histfile.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getenv" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getuid" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "getpwuid" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "sprintf" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "putenv" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fcntl" -- 1st referenced by shell.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "wcwidth" -- 1st referenced by mbutil.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "fprintf" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "exit" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved text symbol "realloc" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
ld32: WARNING 157: Unresolved data symbol "__iob" -- 1st referenced by xmalloc.so.
Use linker option -v to see when and which objects, archives and dsos are loaded.
gmake[1]: Leaving directory `/usr/people/shinichi/source/readline-6.1/shlib'
How is that done? Why isn't it automatically done?
I just figured this out while taking another Intellistation apart - IBM says you can only put 4 HDDs in the POWER 275, but in this photo you can clearly see that there's a filler panel at the bottom. Well guess what, there's actually another connector down there. Take out the black filler thing in the front and put in a real SCSI backplane, and voila you can have 8 SCSI hard drives in that thing. Haven't tried it, never found a need for 8 small noisy SCSI drives yet.
EDIT:
http://publib.boulder.ibm.com/infocente ... /pa520.htm
It seems to share some parts with the Intellistation POWER 275, so I suppose if you wanna buy parts directly from IBM (quite expensive really) then the part numbers here would work instead, because the ones in the Service Guide seem to have been changed to these.
EDIT:
http://publib.boulder.ibm.com/infocente ... /pa520.htm
It seems to share some parts with the Intellistation POWER 275, so I suppose if you wanna buy parts directly from IBM (quite expensive really) then the part numbers here would work instead, because the ones in the Service Guide seem to have been changed to these.
eMGee wrote:
ritchan wrote:
I just figured this out while taking another Intellistation apart - IBM says you can only put 4 HDDs in the POWER 275, but in this photo you can clearly see that there's a filler panel at the bottom. Well guess what, there's actually another connector down there. Take out the black filler thing in the front and put in a real SCSI backplane, and voila you can have 8 SCSI hard drives in that thing. Haven't tried it, never found a need for 8 small noisy SCSI drives yet.
I know it is possible, it's just a bit expensive (more of those expensive, zany, custom trays/brackets). I've wasted enough money on my system already, in all the spares I've been ordering as of late. The system itself was a steal, very cheap, but then it had to break down on me. With IBM refusing to even help me a tiny bit. Whatever offerings they gave me were wrong, riddled with spelling errors (truly incredible) and totally not to the point. Even if I had the money, I'd not want to rely on their shoddy ‘technical support’ (or whatever would have to pass for it). SGI , even since the takeover, is vastly superior in this regard. I saw you wrote that IRIX is ‘dead’ (or something like that) on your blog/site, but SGI treats IRIX users a whole lot better!
Quote:
[..] I suppose if you wanna buy parts directly from IBM (quite expensive really) [..]
No kidding, for example, they charge € 856,62 (excl. VAT) for a replacement “CD/W HDWR” drive for example. (Not that I need one, it was incorrectly quoted to me; IBM doesn't even have its part numbers right, or refuses to look up part numbers/parts from a catalog).
Yup, I emailed and called IBM support asking to buy some spare parts for the 9114-275 - the woman on the telephone said 63 EURs for a plastic door, while the email guy came back with "I'm sorry, it's too old - we don't sell spare parts for that anymore." Interestingly, he also forwarded a note from his higher-ups, who noted that I was most likely a private individual. Maybe that's why the guy who replied didn't bother to check if they still sold parts for the 9114-275.
I stuck a XVR-100 into my 9114-275 and it didn't even show up under a CRUX PPC boot CD, not under lspci -v, nor under dmesg. I guess I really need a true Mac Edition Radeon 7000... according to this random guy,
http://web.cecs.pdx.edu/~idr/graphics/cards_i_have.html
the Mac Edition Radeon 9200 PCI has a firmware problem that makes it not work with anything other than a Mac. I have no idea how to write a device driver that does 3D for it. I downloaded the ATi FireGL drivers for Linux, but I couldn't figure out if the 3D part was open source.
http://support.amd.com/us/gpudownload/P ... linux.aspx
Ugh, really don't wanna run AIX again.
http://web.cecs.pdx.edu/~idr/graphics/cards_i_have.html
the Mac Edition Radeon 9200 PCI has a firmware problem that makes it not work with anything other than a Mac. I have no idea how to write a device driver that does 3D for it. I downloaded the ATi FireGL drivers for Linux, but I couldn't figure out if the 3D part was open source.
http://support.amd.com/us/gpudownload/P ... linux.aspx
Ugh, really don't wanna run AIX again.
I hope neko doesn't mind, but I spent a lot of time writing that post up and I do want a lot of people to see it, especially people who compute "on the edge", i.e. Nekochanners. There's no Flash on IRIX, so I was hoping that as soon as Firefox 3 gets compiled and working, we might be able to all watch OGG video together - it doesn't seem to take more CPU cycles than Xvid.
http://www.andychiw.com/2010/computers/ ... e-colours/
http://www.andychiw.com/2010/computers/ ... e-colours/
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
After spending quite some money buying an SGI Octane, a Sun Blade 100, a rather powerful and at the same time useless IBM 9114-275, and lastly a PowerMac G5, I've come to the conclusion that x86 can't be beat for desktop use.
In retrospect, that might seem like a really dumb and obvious statement. But I think it's finally gotten me over this "halo" that computers with RISCky ISAs will work wonders for me. They don't. Actually, they just sit around looking cool, and the SGI Octane in particular is a great conversation piece, although it seems like it's losing out to the PoweMac G5. One thing's for sure - they're very reliable considering their age.
First there's the price/performance ratio. Well, actually the price performance ratio doesn't matter to me that much since I do have a soft spot for these babies still. But I'll just note that I've spent enough on all this hardware that I could buy myself a new x64 computer that would run circles around any one of these. That's true for any old computer - the only exception to this is a used Mac Pro, but I'll get to that in a moment.
My typical use for the machines goes like this - I run Firefox, a terminal, sshd, play music in at least several different formats (SPC/PSF, WavPack, FLAC, APE, Musepack, Vorbis, MP3, AAC, SHN, TTA and I even have the occasional MP2 file), play anime HDTV rips, uTorrent, and I generally keep all these open at the same time. I generally go out of my way to find something for the computer to do. In the case of the Octane, Blender was an excuse to do something cool with it - Maya was just scary. It looked like C4D, but was nowhere as intuitive. Occasionally I even manage to compile code with MIPSPro, getting something useful out of it. Bottom line, I'm still looking for some use for it.
In the case of the Blade 100, it was supposed to be an unobtrusive file server. That fell through because I'd have to buy a SATA card for it and run Linux, defeating the purpose of getting a SPARC, and I'd need a gigabit ethernet card. No file server supports 137GB maximum on a hard drive. Plus the fan that came with it was rather loud, and on top of that it crashed every now and then. I searched online and found that the error, which only gets sent out via the serial port, was some general umbrella term for god knows what's actually happening. I don't have the time and patience to troubleshoot that, plus my Octane's sitting on top of it.
The 9114-275 had enough power to be a desktop machine, but it just didn't have the software to do so. That was really unfortunate, and I think that's why I was really disappointed with it. To use it as a desktop, you need Linux. Take it from me, AIX as a desktop sucks. You should think of AIX's X11 as something that exists solely to let CATIA run on it. But you need to use this machine with '95 era graphics cards if you want good support. Everything faster than a Radeon 7000 is a hack. And it was terribly loud, and the sound card is of the lowest quality possible. As a person who keeps his music playing whenever he's awake, that's a definite no. I think it'd do well as a server, since it's powerful and has plenty of RAM and integrated gigabit, plus LPARs and WPARs are cool. I don't know much about what IBM's customers use their POWER CPUs for, but it's probably not LAMP.
The PowerMac G5 has quickly supplanted my laptop as my desktop. It can never be the main machine, since it can't run foobar2000, but it's quiet, takes large hard drives (I'll definitely set this up as some file server once I get the $ for HDDs), is still RISCky, and as a bonus, runs OS X and has all the perks of a desktop OS. I think I've come to ask a lot of it, much more than what I expected out of the Octane/9114-275, and so far it's done all that admirably, except for foobar2000's incredible tag management - I have to use my Windows 7 laptop for converting the codepage within music tags, for instance, and keeping the filenames in a certain scheme. It plays 720p well, barely manages to keep up with 1080p with a custom compiled mplayer+ffmpeg-mt, but that's not a big problem. The big problem is that it can play 1080p, but barely manages to do so. I can't stand that - I want it to play smoothly, or not play it at all! A dual 2.3-2.7GHz G5 would probably be able to play 1080p smoothly.
That was when I thought to myself: if I had a thousand bucks, I'd get a used Mac Pro, use OS X for everything, and WINE foobar2000. And then it hit me - I had spent the equivalent of a new computer touring around the world of RISC, only to come back to square one of x86. I felt a bit of regret, but then I was happy that I had taken this path. It really is a sinkhole for money, although not as much as being an Apple fanboy. I know a lot more about computers in general, and have a lot more experience with UNIX, which will hopefully this Wednesday get me a job.
In retrospect, that might seem like a really dumb and obvious statement. But I think it's finally gotten me over this "halo" that computers with RISCky ISAs will work wonders for me. They don't. Actually, they just sit around looking cool, and the SGI Octane in particular is a great conversation piece, although it seems like it's losing out to the PoweMac G5. One thing's for sure - they're very reliable considering their age.
First there's the price/performance ratio. Well, actually the price performance ratio doesn't matter to me that much since I do have a soft spot for these babies still. But I'll just note that I've spent enough on all this hardware that I could buy myself a new x64 computer that would run circles around any one of these. That's true for any old computer - the only exception to this is a used Mac Pro, but I'll get to that in a moment.
My typical use for the machines goes like this - I run Firefox, a terminal, sshd, play music in at least several different formats (SPC/PSF, WavPack, FLAC, APE, Musepack, Vorbis, MP3, AAC, SHN, TTA and I even have the occasional MP2 file), play anime HDTV rips, uTorrent, and I generally keep all these open at the same time. I generally go out of my way to find something for the computer to do. In the case of the Octane, Blender was an excuse to do something cool with it - Maya was just scary. It looked like C4D, but was nowhere as intuitive. Occasionally I even manage to compile code with MIPSPro, getting something useful out of it. Bottom line, I'm still looking for some use for it.
In the case of the Blade 100, it was supposed to be an unobtrusive file server. That fell through because I'd have to buy a SATA card for it and run Linux, defeating the purpose of getting a SPARC, and I'd need a gigabit ethernet card. No file server supports 137GB maximum on a hard drive. Plus the fan that came with it was rather loud, and on top of that it crashed every now and then. I searched online and found that the error, which only gets sent out via the serial port, was some general umbrella term for god knows what's actually happening. I don't have the time and patience to troubleshoot that, plus my Octane's sitting on top of it.
The 9114-275 had enough power to be a desktop machine, but it just didn't have the software to do so. That was really unfortunate, and I think that's why I was really disappointed with it. To use it as a desktop, you need Linux. Take it from me, AIX as a desktop sucks. You should think of AIX's X11 as something that exists solely to let CATIA run on it. But you need to use this machine with '95 era graphics cards if you want good support. Everything faster than a Radeon 7000 is a hack. And it was terribly loud, and the sound card is of the lowest quality possible. As a person who keeps his music playing whenever he's awake, that's a definite no. I think it'd do well as a server, since it's powerful and has plenty of RAM and integrated gigabit, plus LPARs and WPARs are cool. I don't know much about what IBM's customers use their POWER CPUs for, but it's probably not LAMP.
The PowerMac G5 has quickly supplanted my laptop as my desktop. It can never be the main machine, since it can't run foobar2000, but it's quiet, takes large hard drives (I'll definitely set this up as some file server once I get the $ for HDDs), is still RISCky, and as a bonus, runs OS X and has all the perks of a desktop OS. I think I've come to ask a lot of it, much more than what I expected out of the Octane/9114-275, and so far it's done all that admirably, except for foobar2000's incredible tag management - I have to use my Windows 7 laptop for converting the codepage within music tags, for instance, and keeping the filenames in a certain scheme. It plays 720p well, barely manages to keep up with 1080p with a custom compiled mplayer+ffmpeg-mt, but that's not a big problem. The big problem is that it can play 1080p, but barely manages to do so. I can't stand that - I want it to play smoothly, or not play it at all! A dual 2.3-2.7GHz G5 would probably be able to play 1080p smoothly.
That was when I thought to myself: if I had a thousand bucks, I'd get a used Mac Pro, use OS X for everything, and WINE foobar2000. And then it hit me - I had spent the equivalent of a new computer touring around the world of RISC, only to come back to square one of x86. I felt a bit of regret, but then I was happy that I had taken this path. It really is a sinkhole for money, although not as much as being an Apple fanboy. I know a lot more about computers in general, and have a lot more experience with UNIX, which will hopefully this Wednesday get me a job.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I think I would have gotten to the same conclusion without spending a cent if only I wasn't so good at convincing myself
It's surprising to hear the SH is in Nikon cameras. Great, now I have to have a Nikon camera too.
It's surprising to hear the SH is in Nikon cameras. Great, now I have to have a Nikon camera too.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Yup, MPlayer OS X Extended came with some official binaries that couldn't play 1080p by default, but I compiled the backend myself and stuck it in there and it seems to be smoother. In any case, still not enough for butter smooth 1080p. The aggravating thing about the SVN ffmpeg-mt binary that came with MPlayer OS X Extended was that the 1080p video was clearly lagging, yet top/htop showed that both CPUs were only stressed ~80-90%. Might have something to do with the fact that the binary was for a G4, and the G5 has the 5 instruction per group scheme that it inherited from the POWER4. Although if that's the case I'm not sure how top/htop would find out.
Apple fanboyism is when you see Apple's pricing and you start to think that's a pretty good deal, without considering normal market prices for the components. And then you start to spew shit about how Mac hardware is obviously better than everyone else's, clearly not having a clue of what you're talking about, like the idiot who asserted that a G5 is basically a souped up G4, while you slowly and surely get locked into their applications... then you get an iPod, you need iTunes for that too - oh look an iPad, dunno what it uses to sync with a PC/Mac but it can't be any better.
Apple fanboyism is when you see Apple's pricing and you start to think that's a pretty good deal, without considering normal market prices for the components. And then you start to spew shit about how Mac hardware is obviously better than everyone else's, clearly not having a clue of what you're talking about, like the idiot who asserted that a G5 is basically a souped up G4, while you slowly and surely get locked into their applications... then you get an iPod, you need iTunes for that too - oh look an iPad, dunno what it uses to sync with a PC/Mac but it can't be any better.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I haven't actually found a place for my 9114-275 yet, but it's definitely not gonna be in the middle of my dorm room stubbing my toe whenever it feels like it. I want to put it to some use, maybe even get some cash selling a shell account. It'll be running AIX 6.1 TL3SP1, with the usual things that might make a shell server useful to some people. I don't know how many people would be interested though. Would you?
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Well of course, seeing as I can't really see any use for a shell server other than to compile stuff on a weird and exotic platform. In fact I don't really get the draw of shell servers at all, that's why I want to set one up.
I'm also interested in finding a cheap copy of XLC.
I'm also interested in finding a cheap copy of XLC.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Would you guys know enough about this to do it for yourselves? And shouldn't it be reinstall XLC, not reinstall AIX?
http://hardwarebug.org/2009/08/10/drm-the-big-blue-way/
http://hardwarebug.org/2009/08/10/drm-the-big-blue-way/
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
It looks like he's talking about XLC 10.1, which is readily available from IBM at the moment. You're using XLC 9, eh? I don't know about ELF/COFF nor assembly, but what I do know is that I have had no luck getting the date out of 4a 0c 65 c8. IIRC, big endian means 8c 56 c0 a4, but when I told Windows calculator that it was a Dword, and typed it in both ways, I still got some kind of huge number.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
[saya,shinichi]:~/source/Work $ CC time.cpp
[saya,shinichi]:~/source/Work $ ./a.out
Thu May 14 20:41:12 2009
After a lot of time spent at cplusplus.com I figured it out! Unfortunately it seems time_t won't accept hex values for a value, it only holds decimal. Well, that's what Windows calculator is for!
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
You'll have an uphill battle making me believe that they care. But you're right - posting a howto is quite different from posting a crack. Which means it's even harder to find a case against him, don't you think?
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
sybrfreq wrote: Right, I've never heard about that website before but "the license was easy to crack and therefore the software is crap" means I won't bother with it again.
Huh? Do you realize you're doing the same thing as he did?
Anyway, I guess two pages of posts means it should be worth the hassle to set up an AIX 6.1 shell server. I think I'll try the post's method to get XLC 10.1 or 11.1 on it.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
sybrfreq wrote:Yes I realize I am saying the same thing as bri3d. You might say I am agreeing with him.ritchan wrote:sybrfreq wrote: Right, I've never heard about that website before but "the license was easy to crack and therefore the software is crap" means I won't bother with it again.
Huh? Do you realize you're doing the same thing as he did?
No, you just exemplified what he was talking about here:
I wonder why the author remarks that because IBM's DRM is bad, their compiler must be bad as well though - it's a foolish generalization and discards most real-world facts about software licensing.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
1. Pentium II 300MHz, 64MB RAM: too n00b back then to know anything about hostnames, quickly replaced with the second computer.
2. cruelty, Celeron 433MHz, 64MB RAM: named after I got my third PC. Still works. The Asus P2B-F is a sturdy motherboard.
3. chobit-1, Athlon XP 1800/2500, 1.5GB RAM: A Chobit is something that is way ahead of its time. Watch Chobits. My parents got it for me - and it really was the cream of the crop at the time. Still works.
4. ayanami, PowerBook G3 Lombard. Died.
5. athena-asamiya, VIA C3 933MHz, 256MB RAM: a really ugly laptop that got the chicks talking because the Tux penguin I glued onto the top was "cute" (I cut out its belly to make way for the logo holder)
6. ayanami-ii, Core 2 Duo T5500, 2GB RAM: The most powerful PC I own. An unbranded Compal GL31.
7. alpha-chobit, PAL PS3 60GB. Not really ahead of its time in all respects, but that's what the "alpha" is for.
8. saya, SGI Octane R12K 300MHz, 1GB RAM: When it first arrived it was called hulda. Wikipedia says it's a goddess of some sort, but I thought it sounded like an old woman, so I named it after Saya, because she has green hair.
9. motoko, PowerMac G5 dual 1.8GHz, 1GB RAM: Although it's powerful, chobits are special, so I simply named this one. Might change it later.
10. totoro, Sun Blade 100, 500MHz, 2GB RAM: the front plastic makes it look chubby and grey like Totoro. Plus it's pretty slow, which is the impression you get from Totoro.
11. monolith, 9114-275, 2x1.45GHz, 4GB RAM: If you don't break the plastic parts around it, it does a good job as an imposing noisy monolith.
12. unnamed, SGI Indy R5K 180MHz, 256MB RAM: haven't installed IRIX yet.
2. cruelty, Celeron 433MHz, 64MB RAM: named after I got my third PC. Still works. The Asus P2B-F is a sturdy motherboard.
3. chobit-1, Athlon XP 1800/2500, 1.5GB RAM: A Chobit is something that is way ahead of its time. Watch Chobits. My parents got it for me - and it really was the cream of the crop at the time. Still works.
4. ayanami, PowerBook G3 Lombard. Died.
5. athena-asamiya, VIA C3 933MHz, 256MB RAM: a really ugly laptop that got the chicks talking because the Tux penguin I glued onto the top was "cute" (I cut out its belly to make way for the logo holder)
6. ayanami-ii, Core 2 Duo T5500, 2GB RAM: The most powerful PC I own. An unbranded Compal GL31.
7. alpha-chobit, PAL PS3 60GB. Not really ahead of its time in all respects, but that's what the "alpha" is for.
8. saya, SGI Octane R12K 300MHz, 1GB RAM: When it first arrived it was called hulda. Wikipedia says it's a goddess of some sort, but I thought it sounded like an old woman, so I named it after Saya, because she has green hair.
9. motoko, PowerMac G5 dual 1.8GHz, 1GB RAM: Although it's powerful, chobits are special, so I simply named this one. Might change it later.
10. totoro, Sun Blade 100, 500MHz, 2GB RAM: the front plastic makes it look chubby and grey like Totoro. Plus it's pretty slow, which is the impression you get from Totoro.
11. monolith, 9114-275, 2x1.45GHz, 4GB RAM: If you don't break the plastic parts around it, it does a good job as an imposing noisy monolith.
12. unnamed, SGI Indy R5K 180MHz, 256MB RAM: haven't installed IRIX yet.
What's really surprising here is that the OP got an Intellistation POWER 285 for what, 35 bucks? WTF? Did he sell his body or something?
What types of things do you really need Classic support for? I'm running 10.5.8 on my PowerMac G5 and I'm already wishing that foobar2000 was available for PPC OS X...
Have you watched Evangelion? Then you may click on my blog link under the avatar... I hate K-ON and all the moeblob anime that came out after it. Pedos have taken over anime.
Yeah, you're really lucky! I wonder how much difference a POWER5 makes.
Yeah, you're really lucky! I wonder how much difference a POWER5 makes.
9114-275 with KDE 3.4, running ONScripter-EN
viewtopic.php?f=19&t=16721503
http://forums.novelnews.net/showthread.php?t=35673
viewtopic.php?f=19&t=16721503
http://forums.novelnews.net/showthread.php?t=35673
I had two in the first place. Now that I'm all over the RISC craze (and even if I wasn't, the PowerMac G5 does well enough and puts out even more heat than the POWER4+), I decided to give it one more chance, objectively, as a server. It's not that I fell in love with it again, it's just that I'm not trying to force it to be a workstation/desktop this time
The shell serving has to wait until I register the MAC address with somebody at the university. And as for the audio, you must have heard all those bad remarks from me. Don't believe me? The card's just 20 bucks on ebay.
The shell serving has to wait until I register the MAC address with somebody at the university. And as for the audio, you must have heard all those bad remarks from me. Don't believe me? The card's just 20 bucks on ebay.
http://www.abcg.com/TAGITT/abcgTagitt2006021407.pdf
The Sun Blade 2500/1500, HP c8000 and IBM Intellistation POWER 185, 275 and 285 are compared. The 285 comes out with a very long lead, and the high frequency POWER 185 trailing just slightly behind. The 275 is left far behind (sob, my poor 9114-275), whereas the c8000 with its dual core PA-8800 at 1GHz can't even beat the 275's single POWER4+ at 1.45GHz in multithreaded code, which is a rarity in CATIA V4. The FireGL X3 certainly does wonders against the FireGL 4/GXT6500P, although it seems that even 3-4 years after its introduction, the GXT6500P has still performance to spare and is very much CPU limited (probably on purpose so that IBM could gain major performance increases by just pouring money into the CPU, I wonder how much of the 3D pipeline is done by the CPU).
Meanwhile, the Sun machines are incredibly far behind. Why? Is the USIII really in order? If so how did they expect to compete?
The Sun Blade 2500/1500, HP c8000 and IBM Intellistation POWER 185, 275 and 285 are compared. The 285 comes out with a very long lead, and the high frequency POWER 185 trailing just slightly behind. The 275 is left far behind (sob, my poor 9114-275), whereas the c8000 with its dual core PA-8800 at 1GHz can't even beat the 275's single POWER4+ at 1.45GHz in multithreaded code, which is a rarity in CATIA V4. The FireGL X3 certainly does wonders against the FireGL 4/GXT6500P, although it seems that even 3-4 years after its introduction, the GXT6500P has still performance to spare and is very much CPU limited (probably on purpose so that IBM could gain major performance increases by just pouring money into the CPU, I wonder how much of the 3D pipeline is done by the CPU).
Meanwhile, the Sun machines are incredibly far behind. Why? Is the USIII really in order? If so how did they expect to compete?
http://www.engadget.com/2010/09/18/inte ... already-d/
Would've thought you guys would have a thread about this up and going already, what do you guys think?
Would've thought you guys would have a thread about this up and going already, what do you guys think?
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I heard some VAXes had a microcode upgrade that simply removed no-ops that you had to pay for. Is that true?
And skywriter, I have no clue what you're talking about. Slot 1 to Socket 370 converters?
And skywriter, I have no clue what you're talking about. Slot 1 to Socket 370 converters?
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
It's common knowledge that irix isn't exactly the most secure OS on the planet, but when nekonoko was running nekochan.net on his O350s, were there any breakin attempts? Just for curiosity's sake.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
So, what have you been using that monster for?
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
What, it's not like US CPUs had a totally different architecture. They still had a FSB, no point to point topology, a northbridge and a southbridge, so there's nothing particularly special about the system architecture.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
xSeries? If that's the trays for the x86 based IBM servers, no, they're not compatible.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I just downloaded AIX 7 TL1SP1. I don't really see the restriction...
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Most of these are probably due to sheer ignorance, but I still hate AIX's out of box experience. RIght off the bat, there is no SSH included, and you need to get the AIX Linux Toolbox for that (which is a whole new exercise in itself). They include every shell out there except bash and the default shell is ksh. According to online documentation on ksh, ksh supports completion via ESC-ESC. Tried that, didn't work. Doesn't even have a command history, and the command prompt is just a single $ or #, which is incredibly helpful.
I can't shift-tab upwards to check output. There is no less, only more which sucks more. Network connectivity is limited to plain old ftp, which AFAIK does not support auto file transfer type. Since there's no working web browser, if you want to download updates for AIX, you have to use a different computer to get to IBM's website, and then type in all the ftp commands on the AIX box. smitty is not smart enough to phone home for updates. The default partition/filesystem sizes are tiny and ridiculous, with no option to change this in the installer, and each upgrade necessitates at least several partition resizes, which at least AIX handles nicely since partitions don't have to be contiguous. But isn't that in itself inefficient? I found myself intentionally wasting some free space on the drive just so one of the many filesystems would still have space to expand into in the future. Hell if I know which.
dtsession panics and refuses to start the fugly window manager when you so much as change your hostname. The graphical AIX introductory assistant asks you to insert the disc and press Enter to continue, but fails to register the ENTER keypress when you finally hit it, because it's just a graphical shell around something that's better handled by smitty anyway. You need to install the AIX Linux Toolbox to get any modicum of general functionality, and there is of course NO dependency resolution.
Last but not least, the OS takes ages to boot. The only saving grace this OS has is that df has a -m and -g option, which lets you specify exactly whether you want volume sizes to be listed in megabytes or gigabytes, instead of the -h option on Linux which does a great enough job that I don't really care anyway.
If there's something I listed here that's annoying simply because I don't know how it works in AIX, please tell me. I certainly had a lot of patience the last time I got this working. I must've forgotten all the hard work to get all my favourite things up and running like the AIX Linux Toolbox, and eventually KDE3.
I can't shift-tab upwards to check output. There is no less, only more which sucks more. Network connectivity is limited to plain old ftp, which AFAIK does not support auto file transfer type. Since there's no working web browser, if you want to download updates for AIX, you have to use a different computer to get to IBM's website, and then type in all the ftp commands on the AIX box. smitty is not smart enough to phone home for updates. The default partition/filesystem sizes are tiny and ridiculous, with no option to change this in the installer, and each upgrade necessitates at least several partition resizes, which at least AIX handles nicely since partitions don't have to be contiguous. But isn't that in itself inefficient? I found myself intentionally wasting some free space on the drive just so one of the many filesystems would still have space to expand into in the future. Hell if I know which.
dtsession panics and refuses to start the fugly window manager when you so much as change your hostname. The graphical AIX introductory assistant asks you to insert the disc and press Enter to continue, but fails to register the ENTER keypress when you finally hit it, because it's just a graphical shell around something that's better handled by smitty anyway. You need to install the AIX Linux Toolbox to get any modicum of general functionality, and there is of course NO dependency resolution.
Last but not least, the OS takes ages to boot. The only saving grace this OS has is that df has a -m and -g option, which lets you specify exactly whether you want volume sizes to be listed in megabytes or gigabytes, instead of the -h option on Linux which does a great enough job that I don't really care anyway.
If there's something I listed here that's annoying simply because I don't know how it works in AIX, please tell me. I certainly had a lot of patience the last time I got this working. I must've forgotten all the hard work to get all my favourite things up and running like the AIX Linux Toolbox, and eventually KDE3.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
My first thought was: greaat, now I can relive the horror on my Linux installations.
My second thought was: there's probably a thread about this on Nekochan already.
My second thought was: there's probably a thread about this on Nekochan already.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.
I personally love it. it's new and different, and really, that's enough to make me want it. It's also totally crazy and reminds me of the Tezro, or the Octane, except that those were really just metal rectangles dressed up in amorphous plastic bits, whereas this thing really is a triangle in a cylinder! That's just mind blowing.
_________________
Originally Posted by Tommie
Please delete your post. It is an insult to all the hard work society has put into making you an intelligent being.
Like somebody at AMD said about a decade ago: Benchmarking is like sex. Everybody brags about it, everybody loves doing it and nobody can agree on performance.