> I know - which is why I wrote a script to download these functions > on-the-fly, across the net. The thing was, there were fundamental > failings in tomsrtbt to 'try to make it behave like a normal system'.
Heh heh - I never thought it would be interpreted that way. P.S. - Email should be 80 characters wide. "normal" as in "ls -Srl" works, or ":%s/x/y/g" works. > Oh - that reminds me, why is chain.b in /etc while boot.b is on > the floppy-floppy? Because boot.b is actually used, so must be uncompressed. Chain.b is just so you can make a DOS system bootable if you have to. > This is _very_ true, took tomsrtbt on a chroot tour of my slack3.9 > partition, most (low level) network tools fail without AF_PACKET; > pretty much anything with threads fails without SYSV_IPC. > Busybox > is the only thing insulating tomsrtbt from the need for this... That is definitely not true, I only started using busybox relatively recently, it worked for a couple of few years without busybox or sysv or afpacket. Tomsrtbt is NOT intended to be a Trinux (low level networking) or LRP (routing) or MuLinux or 2DiskXWindows system. It is intended to have tools necessary for fixing broken systems. Nmap, sound, etc, all fail the test. Think about it- The point of networking is to restore a tape over the network, or to wget a file to fix something, or telnet into something. I don't include a threading library, and there should be no need for threading. This stuff is just way gravy, it is no accident that nmap and mp3 players are where you ran into this. I don't intend to suppport "applications" on it... > > at some point, but, all of this is *WAY* down the priority > list...). > What is the priority list? Fixing the man pages, freeing up space, looking at some kind of Reiser support, and support for more scsi cards and raid solutions, some kludge to make gnu tar incremental backups restorable, working on using library minimalizers to try to get libc 6 working and fitting, building an easier libc5 compilation environment, rewriting things in lua or nasm to be smaller, makeing dd + dd-lfs + dd-rescue into one small thing, a better "more", a better hex editor and disk editor and debugger (better raw disk editing is high), maybe better smbfs or ncpfs support, Not in that order. But, you get the idea- there is PLENTY of work just to make it a better rescue and recovery tool, making it better as an applications platform is somebody elses problem in some offshoot. > However, I'm just using the 2.2.20 vanilla flavour, what/from where > was the ext3 patch? I guess the modules will be fairly compatiable - > just insmod -f'd... Ext3 is a journalling filesystem, RedHat (Stephen Tweedy) maintains it. > Would you mind me creating pages for my little projects on your > wikki? Or would you like that to remain a strictly vanilla-tomsrtbt > area? Go for it. The wiki is free for all. I may re-arrange things, but this kind of thing is exactly what the wiki is for. Um, a caveat- the wiki is fine for web-page and discussion use, don't use it for file storage or distributions. It doesn't have the bandwidth to be used for anything but small chunks of static html. > > Jarvist > > P.S. Hey! The kernel has finished compiling... to > give a 600kb bzImage (!) > Pretty certain I kept to your config, > do the ext3 patches really add >200kb to the kernel?! I doubt ext3 adds that much. Compare my config, check the current one: http://toms.net/tomsrtbt-sources/part2/rb/kernel.config dd > > Boots fine, runs cdda2wav fine :^), loads sound modules fine, SCSI seems present... What am I not seeing? > -- > > Courdoroy pillows- They're making headlines! >
