This bootable ISO image contains NetBSD 3.99.7 and allows you to boot NetBSD/i386 -current without having to install to a hard disk. The LiveCD was initially intended to be a rescue cdrom, but is now capable of much more. KDE-3.4.2 and all kde3-i18n packages were included.
Much more what? The link is equally cryptic on what this can do.
ftp://ftp.netbsd.org/pub/NetBSD/misc/xtraeme/README.LIVECD
Have you tried viewing the README associated with the .iso file?
I’ve downloaded and booted from the CD. I get a command prompt. Anyone know what to do next? Can’t find any docs on root password, etc.
Read the README file at the linked site. That command line prompt *IS* your starting point! While the CD has KDE preinstalled on it, it is still meant to be a rescue CD and not a KDE demo system. Hence the command line prompt.
Hint. The README file is at ftp://ftp.netbsd.org/pub/NetBSD/misc/xtraeme/README.LIVECD, and the instructions you are looking for are near the end.
password for root and user: NetBSD
How come there is a NetBSD 3.99.7? When was 3.0 released?
Nope it was not released, this should help
http://www.netbsd.org/Releases/release-map.html
I’m right typing from 2.0, can’t wait 3.0 🙂
That has to be the worst numbering scheme ever thought up.
I know it’s really a minor thing, but I expected better from these folks…
“That has to be the worst numbering scheme ever thought up.”
I thought it weird too, using 3.99.x numbering when 3.0 isn’t even out. But that release map a previous poster points to, clears things up:
For development that is going to be 3.0, a 2.99.x numbering is (or rather, was) used. <3, but newer than other 2.x releases. Then a branch is forked, and *that* branch is feature-frozen, and further stabilized/bugfixed into 3.0 release candidates.
At that point, numbering is bumped from 2.99.x to 3.99.x, and development continues on features that are to ‘disruptive’ to even make it into not-yet-released 3.x. So that’s development aimed at some future 4.x release.
Confusing at first, but makes a lot of sense if you aim for quality releases, and simultaneously work on bleeding-edge stuff. So I’d say these NetBSD folks DO know what they’re doing.
For contrast, compare with Linux: *really* experimental stuff essentially on hold, since no 2.7 development branch. Ofcourse people can do very experimental stuff, but only in their own backyard. And some less experimental, but not widely tested stuff is thrown into 2.6.x releases, leaving it up to users that compile their own kernels, to discover what breakage occurs, and how stable each new ‘stable’ release really is. IIRC this policy was changed recently, but we still have to see how that works out.
My point was, I guess that is if something needs to be explained, it’s not intuitive. This numbering system falls easilly into this category.
I love this error… any GRUB cheat codes to select my display params so I can actually try this release?
So..I guess there’s no installer on the cd, judging by the readme. In case I like what I see and want to skip on downloading another iso and such, like with most live-distros.
I realize this is being targeted as a rescue CD, but honestly, if every frickin’ Linux distro that has KDE or Gnome can detect the video at startup, why can’t this one boot into a graphical startup (or offer it as an option in GRUB)?
From their docs:
o How to start KDE?
You should configure XFree86 and the .xinitrc before trying to start it:
$ xf86config [as root]
$ echo “exec startkde” > ~/.xinitrc [as user]
$ xinit
Yeah, because when I’ve got a trashed PC to rescue, I’m completely aware of the monitor’s sync rate, the video card’s brand and onboard RAM, AND I always have time to reconfigure these things every time I reboot.
If you were a good little sys admin, you’d have a hard copy of your hardware components or know them by heart.
If I were working with my own equipment, yes. If I’m fixing my frantic friend’s box, no.
What the hell would you wan’t KDE for when resqueing a system. I don’t get it.
Yeah, because when I’ve got a trashed PC to rescue, I’m completely aware of the monitor’s sync rate, the video card’s brand and onboard RAM, AND I always have time to reconfigure these things every time I reboot.
When you’re a syadm on a rescue mission you use CLI tools to repair the system.
I should try this for fun, since Knoppix 3.9 is unstable (UNION FS module fatally dies under load).
cannot find …
cannot read …
cannot start ….
but hey its runs on a toaster …
Try downloading NetBSD 2.0 and install it Then decide.
Its true, if YOU cannont read, NetBSD cannont start.