Recently, I wanted to buy an el-cheapo mp3-cd-player for my rather new (2 years) Toyota Corolla. I had to find out that none of the models available in standard size would fit in there, and that my only option would be go buy what Toyota offers. Too bad they don't have _any_ mp3 devices available. And if so, they would not be as cheap as the ones in stores here.
count me in for long-time tcsh users. It's not that I'm die-hard fanatic over it, but when I started using Unix there was only tcsh as a comfort shell, no bash. And why switch when tcsh works well.
so where's the source code so I can compile this on NetBSD/sparc? and NetBSD/sgimips? Or maybe only NetBSD/i386? Not all the world is Linux/i386, and the latter is becoming more and more of a closed, commercial system.
Speaking as someone who worked a lot on NetBSD's 3rd party software system, pkgsrc, which today has ~4.000 pkgs:
It's less important for software to come "pre-packages" properly, but that both the code and the build infrastructure are written with portability in mind in the first stop.
* Make sure your software compiles on non-i386 non-Linux (don't #include , don't assume/proc is the same on all Systems, don't use clone(2), etc).
* Make sure it can be relocated (configure --prefix=/foo working properly if you have to use GNU autoconf).
* Don't assume everyone uses GNU make
* Don't assume/bin/sh == Bash
* Don't depend on obscure non-easy to install software components (that again may not be present on non-i386 non-Linux - think Java!).
If that is done, your software can be added to any 3rd party package systems easily.
I think I start spamming each Linux-related post now with lengthy rubbish about it being crap and everything. Makes me wonder how immature some people are. *sigh*
During the Munich IETF 1997(?) I used rdist (part of Irix) to copy files from one machine to 40 others, as someone thought NFS was not an option.
When I had a set of (permanently running...) Unix workstations last, I used sh for-loops and ssh to run commands.
During another cluster project I was happy to use NFS to share files, and used rsh over ssh as it was ways faster.
Oh, and if you ever need to render mpegs from jpegs, check out the UCB's excellent "mpeg_encode", which does all the load balancing on a set of machines all by itself. Yumm!
IIRC the growisofs tool that's the core of the dvd+rw-tools is really just a frontend to dd(1), and you don't really need it, *IF* you have a decent driver that allows dd(1)ing a ISO image to it. Tried it some time ago under SuSE 8.something, worked.
The amd64 platform is a true 64 bit platform (hence the name:). As such, it uses 64bit entities for longs and pointers internally, which is just not compatible with the legacy PC software.
To still run legacy software, an emulation layer had to be added that maps all 32bit entities (longs, pointers,...) that applications pass on system calls into their 64bit in-kernel equivalents, and back.
That emulation layer was already necessary for the NetBSD/sparc64 port, to run NetBSD/sparc (and 32bit Solaris, etc.) binaries on 64bit platforms. It was not necessary for the NetBSD/alpha port, as there are no 32bit binaries, and it can operate in 64bit without taking care of backward compatibility.
Would be interesting to hear how other operating systems deal with the situation btw - FreeBSD, Linux, Windows anyone?
Let's hope they don't support only Linux (probably via some binary module, as nVidia does), but really open up their drivers. Preferably in a way that can be used on non-PC, non-Linux too.
Why do you think VPN "solution" providers make big money these days? Because they work exactly around that thinking and the broken network design resulting from it. With some real (non-private) address space you'd just open up the firewall to whomever you want to get access to your systems and be done with it. With private address space, you have to jump through all sort of hoops to allow your business partners access your systems.
I think it would be nice to have a group working on filesystems for all BSD systems (Free, Net, Open,...), just like what KAME does for IPv6 on BSD. That way, every BSD project would benefit from the efforts.
Yesterday I had to learn that a small utility I make (www.feyrer.de/g4u) is used (among others) by a company who is involved with the production of weapons of mass destruction of a very trigger-happy nation.:-(
SMP means running processes on more than one CPU in parallel. (With some care-taking from the kernel that both CPUs don't step on each other WRT writing to kernel data structures etc.).
Threading means splitting up a process into several (well:) threads, and let them run on either one or more than one CPU. This is basically an application-layer thing, in contrast to SMP which happens inside the kernel. Of course having SMP available helps for performance in threads systems as you can run threads in parallel on several CPUs, but SMP is not strictly necessary for a threaded system.
Many applications today use a threaded software architecture (over the classical Unix "fork"ed processes), and so having some efficient threads implementation is very important.
With the Scheduler Activations based work that Jason and Nathan made, this is a very efficient implementation as you can map N userland threads to M kernel threads, and you don't have one kernel thread for each userland thread, like some other systems (used to?) have, and which kills performance if you have many threads.
Slashdot Mirror
Recently, I wanted to buy an el-cheapo mp3-cd-player for my rather new (2 years) Toyota Corolla. I had to find out that none of the models available in standard size would fit in there, and that my only option would be go buy what Toyota offers. Too bad they don't have _any_ mp3 devices available. And if so, they would not be as cheap as the ones in stores here.
:(
Needless to say, I'm pretty annoyed by that.
- Hubert
Some data about stability:
raqim% uname -rsm
NetBSD 1.5.1 cobalt
raqim% uptime
11:40PM up 25 days, 21:35, 11 users, load averages: 0.46, 0.30, 0.23
- Hubert
(well, never was alive, for me :)
- Hubert
count me in for long-time tcsh users.
It's not that I'm die-hard fanatic over it, but when I started using Unix there was only tcsh as a comfort shell, no bash. And why switch when tcsh works well.
- Hubert
I always found xdu nice to see where the disk space is burned, but I understand this doesn't scale too well for large filesystems.
:-)
Maybe the quota subsystem can be used for something...
- Hubert
so where's the source code so I can compile this on NetBSD/sparc? and NetBSD/sgimips? Or maybe only NetBSD/i386? Not all the world is Linux/i386, and the latter is becoming more and more of a closed, commercial system.
- Hubert
Speaking as someone who worked a lot on NetBSD's 3rd party software system, pkgsrc, which today has ~4.000 pkgs:
/proc is the same on all Systems, don't use clone(2), etc). /bin/sh == Bash
It's less important for software to come "pre-packages" properly, but that both the code and the build infrastructure are written with portability in mind in the first stop.
* Make sure your software compiles on non-i386 non-Linux (don't #include , don't assume
* Make sure it can be relocated (configure --prefix=/foo working properly if you have to use GNU autoconf).
* Don't assume everyone uses GNU make
* Don't assume
* Don't depend on obscure non-easy to install software components (that again may not be present on non-i386 non-Linux - think Java!).
If that is done, your software can be added to any 3rd party package systems easily.
- Hubert
... like another hole in the head.
:(
Oh well, it's probably about hurt egos again.
- Hubert
I think I start spamming each Linux-related post now with lengthy rubbish about it being crap and everything. Makes me wonder how immature some people are. *sigh*
- Hubert
Um, we're talking operating systems here, not hardware. pkgsrc works on Irix, no need to install NetBSD. :-)
- Hubert
During the Munich IETF 1997(?) I used rdist (part of Irix) to copy files from one machine to 40 others, as someone thought NFS was not an option.
When I had a set of (permanently running...) Unix workstations last, I used sh for-loops and ssh to run commands.
During another cluster project I was happy to use NFS to share files, and used rsh over ssh as it was ways faster.
Oh, and if you ever need to render mpegs from jpegs, check out the UCB's excellent "mpeg_encode", which does all the load balancing on a set of machines all by itself. Yumm!
- Hubert
yes, nice... and what does it do if it is done with running mkisofs or if you hand it a ready-made iso image?
- Hubert
IIRC the growisofs tool that's the core of the dvd+rw-tools is really just a frontend to dd(1), and you don't really need it, *IF* you have a decent driver that allows dd(1)ing a ISO image to it.
Tried it some time ago under SuSE 8.something, worked.
- Hubert
The amd64 platform is a true 64 bit platform (hence the name :). As such, it uses 64bit entities for longs and pointers internally, which is just not compatible with the legacy PC software.
...) that applications pass on system calls into their 64bit in-kernel equivalents, and back.
To still run legacy software, an emulation layer had to be added that maps all 32bit entities (longs, pointers,
That emulation layer was already necessary for the NetBSD/sparc64 port, to run NetBSD/sparc (and 32bit Solaris, etc.) binaries on 64bit platforms. It was not necessary for the NetBSD/alpha port, as there are no 32bit binaries, and it can operate in 64bit without taking care of backward compatibility.
Would be interesting to hear how other operating systems deal with the situation btw - FreeBSD, Linux, Windows anyone?
- Hubert
The NetBSD Advocacy page has some posters available for print-it-yourself.
- Hubert
Let's hope they don't support only Linux (probably via some binary module, as nVidia does), but really open up their drivers. Preferably in a way that can be used on non-PC, non-Linux too.
:)
- Hubert (not speaking for The NetBSD Project
So where can I get a NetBSD (or Linux :)
version of FrameMaker?
- Hubert
You wish.
Why do you think VPN "solution" providers make big money these days? Because they work exactly around that thinking and the broken network design resulting from it. With some real (non-private) address space you'd just open up the firewall to whomever you want to get access to your systems and be done with it. With private address space, you have to jump through all sort of hoops to allow your business partners access your systems.
- Hubert
So does it do IPv6?
Or are they going to kludge some VPN "solution" into the stack, to make this thing work in a large scale environment?
- Hubert
I think it would be nice to have a group working on filesystems for all BSD systems (Free, Net, Open, ...), just like what KAME does for IPv6 on BSD.
That way, every BSD project would benefit from the efforts.
- Hubert
Yesterday I had to learn that a small utility I make (www.feyrer.de/g4u) is used (among others) by a company who is involved with the production of weapons of mass destruction of a very trigger-happy nation. :-(
- Hubert
SMP means running processes on more than one CPU in parallel. (With some care-taking from the kernel that both CPUs don't step on each other WRT writing to kernel data structures etc.).
:) threads, and let them run on either one or more than one CPU. This is basically an application-layer thing, in contrast to SMP which happens inside the kernel. Of course having SMP available helps for performance in threads systems as you can run threads in parallel on several CPUs, but SMP is not strictly necessary for a threaded system.
Threading means splitting up a process into several (well
Many applications today use a threaded software architecture (over the classical Unix "fork"ed processes), and so having some efficient threads implementation is very important.
With the Scheduler Activations based work that Jason and Nathan made, this is a very efficient implementation as you can map N userland threads to M kernel threads, and you don't have one kernel thread for each userland thread, like some other systems (used to?) have, and which kills performance if you have many threads.
- Hubert
source for that would be nice, to port it to NetBSD eventually. Not all the world is Linux!
- Hubert
see my report.
check out the report on our NetBSD cluster which would easily scale to many nodes.
It's just a question of proper application software, and OS doesn't really matter - I can't understand all this fuzz about Linux. *shrug*