|
Grex > Micros > #199: FreeBSD, Linux, or other PC Unixes? |  |
|
| Author |
Message |
| 25 new of 257 responses total. |
pfv
|
|
response 50 of 257:
| 
Feb 11 16:47 UTC 1999 |
Crap... That is Not A Good Thing (tm)
You realize, of course, that I did NOT want to hear this...
as I am currently trying to decide twixt FreeBsd, RH 5.2, Debian
and TL as my ONLY Operating System..
Goddamnit... This Bodes Not Well at all.. *sigh*
Well, maybe if I use FIPS and shrink down the DOS partition to the
minimal for Dos 6.0... crapdoodle.. I wanna' be m$ free.
I would point out, to those that ain't experienced it, that trying
to get any sorta' older DOS installed from any of the win9x crap
is a total wash.. And, for the love of Bog - make sure you have a
bootdisk with that old DOS that WORKS before suffering m$ any
further..
|
toking
|
|
response 51 of 257:
|
Feb 11 17:44 UTC 1999 |
resp:50
try
http://www.FreeDOS.org
|
pfv
|
|
response 52 of 257:
|
Feb 11 17:46 UTC 1999 |
Yeah, I recall seeing it long ago and hearing of it..
I have no clue how it is doing, let alone how it "plays well with
others". Certainly win95/98 does NOT play well.
|
toking
|
|
response 53 of 257:
|
Feb 11 18:00 UTC 1999 |
it's probably worth a shot for a minimal DOS, and it's not M$
|
drew
|
|
response 54 of 257:
|
Feb 11 20:45 UTC 1999 |
Is this Win 95/98 specifically that trashes the MBR? I ended up re-installing
the main Windows NT 4.0 partition (attempt to do an XCOPY from CD while in
the auxiliary NT system resulted in BSODs and an invisible system); but the
LILO in the MBR is *still* intact.
|
mwg
|
|
response 55 of 257:
|
Feb 11 21:48 UTC 1999 |
Re: Superblock - One of the Unix types can probably give a much more
detailed answer, but from what I can tell, the superblock of a Unix-type
file system contains some vital bits of information, like fs type, some
inode information, and a few other things I haven't a clear picture of
yet. In the Linux superblock, it is possible to store a copy of LILO, the
Linux Loader, such that if the computer attempts to boot the Linux
partition, LILO gets run. LILO can be told to do several things based on
stored settings and optional interruption and input. It is possible (I do
this) to set the Linux partition as the active bootable partition, and
still boot to DOS by default if you don't interrupt the boot process.
By keeping LILO out of the MBR, I can avoid the problem of an OS trashing
my ability to boot, although I still keep two backup boot disks, just in
case.
|
dang
|
|
response 56 of 257:
|
Feb 12 03:24 UTC 1999 |
The superblock is just the first block of a partition. If there is
nothing in the MBR, such as if you've just gotten a new hard drive or
just installed windows, then the BIOS runs the program in the first
block (read superblock) the the partition marked active. It has the
same kind of space restrictions as the MBR, almost. If the BIOS is
running it, it needs to be withing BIOS addressable space, which is 1024
if you have a brain-dead BIOS. (If so, upgradeing your BIOS will almost
certainly cure it.)
Re: FreeBSD screw-up: I run FreeBSD as the only OS on my computer at
work, and I've installed any number of times, with no problem. From
what you've said, it sounds like no partition was marked as active,
and/or you didn't install the FreeBSD Bootloader. That's optional.
|
mdw
|
|
response 57 of 257:
|
Feb 12 03:47 UTC 1999 |
The superblock is a block near the start of the filesystem that
describes the organization of that filesystem. It includes a magic
number (to say it's a so-so type of filesystem), and various parameters
that the filesystem uses to locate the other data structures on that
filesystem, such as the inode table, free block bitmaps, etc. The
superblock is usually *not* block 0, because block 0 is reserved for the
boot logic. In edition 7 Unix (ca. 1979 technology), the boot block was
512 bytes, and the superblock started in block 1 (blocks then being 512
bytes). In the berkeley filesystem (ca. 1984), multiple copies of the
superblock are written to disk, scattered onto different cylinders of
the disk. This makes it slightly easier to recover from certain kinds
of disk catastrophes (like something that trashes the "real" superblock
at the start of the disk.) 512 bytes is plenty of space for a really
dumb optimized boot strap module in pdp-11 assembler, that is just smart
enough to load "/boot" from the same disk and filesystem. In the
berkeley fast filesystem (variants of which are used in SunOS 4 and
386bsd), 8192 bytes of space at the start of the filesystem are reserved
for boot logic. 8192 bytes makes it easier to port this logic to new
systems, and makes it possible to write the logic in C on many systems.
This logic is "in addition" to the logic in the MBR on 386 systems;
generally, the MBR would invoke the boot block which would load /boot
which would load /vmunix (or /bsd or whatever the kernel is called on
your system). In SunOS, the boot block has the locations of /boot
written into it; a program named "installboot" must be run in order to
write the locations of /boot into the boot block logic.
|
pfv
|
|
response 58 of 257:
|
Feb 12 05:40 UTC 1999 |
Somehow, I think we're talking the same thing w/ different
nomenclature..
yeah, the MBR is supposed to vector the bios to the /boot
partition and it's loading whatever the heck lilo creates from all
the assorted kernels you save as well as other OS's you care to
run.. I'd bet it's a chunk of lilo and either the actual kernel
or a chunk of what HAD been used to load DOS or Doze..
Near as I can tell now, the old slackware system that got
codwalloped was entirely due to my being a total neophyte to
building kernels and writing a zdisk/bootdiskette.. Because I
hadn't prepared said floppy, 95 got away with hammering me and I
had no idea how to get access to either /boot or / - thus ended
a brief flirtation with slackware..
Additionally, having been fried by 95 before, I am not at all
anxious to tempt the fates ever again.. There isn't anything for
Doze I can't live without or substitute something related.
|
toking
|
|
response 59 of 257:
|
Feb 12 17:45 UTC 1999 |
resp:56 well, when I was trying to install freebsd as a second OS I kept
selecting to have the boot manager thing installed, but I'd assumed that
with it being the only system on the HD I could get away with the second
option (standard boot record)
|
mwg
|
|
response 60 of 257:
|
Feb 13 20:13 UTC 1999 |
Re#57: If all else fails, you can boot with your original slackware setup
disks, mount your Linux partitions on the RamDisk file system, then re-run
lilo at the bash prompt, which should regenerate your LILO MBR. (Unless
something has trashed /etc/lilo.conf.) Then issue a shutdown command and
see what happens.
|
mwg
|
|
response 61 of 257:
|
Feb 13 20:14 UTC 1999 |
Frack! I meant #58.
|
dang
|
|
response 62 of 257:
|
Feb 13 22:30 UTC 1999 |
resp:59 No, that won't work. That only works if you have another
intelligent boot loader (such as NT or OS2) already running that you a)
don't want to trash and b) can configure to run FreeBSD. If FreeBSD is
alone, you have to install the bootloader from it, or nothing will boot.
|
jshafer
|
|
response 63 of 257:
|
Feb 14 06:09 UTC 1999 |
Re: my floppy difficulties, back there somewhere, I got around
the problem by rebooting to Win95 (Actually whatever DOS comes
with Win95) and copying the files to the hard disk, then rebooting
in FreeBSD and mounting the DOS partition.
I just got a new external modem, and am now grexing from FreeBSD.
As soon as I figure out how to configure my X-windows display
stuff so I can get a display bigger than 320x200, and figure out
which of the ports I installed was the POP3 client, I may be ready
to do away w/ M$ in general...
|
pfv
|
|
response 64 of 257:
|
Feb 14 16:45 UTC 1999 |
XF86Config is a LOT of fun.. Just remember to always leave the
^alt+[backspace] enabled ;-)
|
jshafer
|
|
response 65 of 257:
|
Feb 14 19:33 UTC 1999 |
Thanks, Pete!
|
dang
|
|
response 66 of 257:
|
Feb 17 05:16 UTC 1999 |
And keep a backup copy of one that works... :)
Actually, I've found that xf86config (the program, not the file) works
pretty well. If you want high color depth, tho, you're pretty much
stuck with a -bpp 32 somewhere on some command line.
|
pfv
|
|
response 67 of 257:
|
Feb 17 06:22 UTC 1999 |
Gods yes...
Switching X versions needed a new config - it said.. Thankfully,
I'd saved the old one - in paranoid fashion.. the OLD one worked
all the time.. the new one was an abomination!
|
gull
|
|
response 68 of 257:
|
Feb 17 22:11 UTC 1999 |
Re #66: Or do what I did. Edit startx (it's just a shell script) to make
-bpp 32 the default.
|
toking
|
|
response 69 of 257:
|
Feb 18 16:55 UTC 1999 |
O.K. I finally got X working, but I'm stuck with some pretty crappy
color (just what does a color depth of 8 = in terms of number of
colors?) and suggestions on how to make that a little better? (I know
that in Windows I can set it to 16 bit
Ohh yeah....once you have FreeBSD installed is there some way to
reinstall the bootloader thing? (i'm stuck booting from floppy right
now...)
|
pfv
|
|
response 70 of 257:
|
Feb 18 17:17 UTC 1999 |
Use "XF86config" - 8 bit is.. 256 colors (guys?)
Yeah, 16 or 24 bit make life tolerable..
|
toking
|
|
response 71 of 257:
|
Feb 18 17:38 UTC 1999 |
I'm under the direct assumption that somewhere on my system there is a
program that I can run called XF86config, if so, where is it? do I run
it from inside X? ^---C?
ohh yeah...I've tried searching the web to no avail...anyone know where
I can find something about getting the MWave modem thats built into an
IBM ThinkPad 755CDV working under freebsd?
|
dang
|
|
response 72 of 257:
|
Feb 19 00:19 UTC 1999 |
No, the program is xf86config, all lowercase. The config file itself is
capitalized like this: XF86Config. 8 bit color is indeed 256 colors.
You can actually use more than 256 colors, but only 256 at one time. If
you have 8 bit color, you usually get bizarre color changes when you
select programs like netscape, because they load thier own colormap. If
you are using startx to start X, then you can do this:
startx -- -bpp n
where n is one of 8, 16, 24, or 32. That coresponds to 256 colors, High
Color, and True Color (both the last two) on Windows. Its 256, 65,536,
16 million, and 4e9 colors. If you use xdm to start X, you will need
to edit it's config files and add a "-bpp n" to the line that has the X
server listed.
I know of no way to install the bootloader in FreeBSD other than by
installing. There probably is such a way, but I've never needed it.
Try http://www.freebsd.org which is a pretty good web site.
|
eprom
|
|
response 73 of 257:
|
Feb 19 02:06 UTC 1999 |
hmm..the bootloader thingy? try /stand/sysinstall as root
then go to the post-config menu..then to fdisk then type "q" to quit
that should get you to the bootload thingy option...then go back to fdisk
and type "w" for write changes....theres probillly a more simple way
but i dunno know how....
|
pfv
|
|
response 74 of 257:
|
Feb 19 17:28 UTC 1999 |
Hmm.. I find:
/usr/X11R6/bin/XF86Setup
No "xf[86config]" of any type.. We're heading into system
differences, I suspect. Sorry about misleading about, I'd have
SWORN I ran that..
|