Re: How to boot FreeBSD and linux from FreeBSD MBR?
Hi Yuri, I've been through this too. The short answer is to install LILO everywhere, once for each time you install a version of Linux. I discovered this from System Rescue CD, which is an obvious piece of kit for this situation. Currently I have the FreeBSD Boot Selector in my MBR, installed from PC-BSD. This means I can boot my four Primary Partitions using F1, F2, F3, F4. F1 actually boots my dedicated Data Partition #1, which is formatted Ext2 so other systems can access it. I installed GRUB here when I installed Debian, and it works. Other times, Debian says this is dangerous, but not when first installing. From here, GRUB can boot Linux versions on other partitions. F2 boots PC-BSD as usual, on Primary Partition #2. F3 boots Debian on Primary Partition #3, using LILO, which I installed on Partition #3 with that Debian release. LILO makes Linux start much like BSD. F4 boots another Debian on Logical Partition #6, using LILO installed on Primary Partition #4. This works even though Partition #4 is an Extended DOS Partition acting as a container. I installed LILO on Logical Partition #6 too, because System Rescue CD suggests this. Logical Partition #5 is my Linux Swap. Using F1 I can boot everything from GRUB too, which would have been essential if I'd had alot of Linuxes in my Extended DOS Partition. Debian's GRUB install seems to detect other Linuxes okay, but it doesn't see BSDs. Though GRUB will boot PC-BSD too: In GRUB, press 'c' to get the GRUB Command Line. ls -lh gives information on all my Partitions. chainloader (hd0,msdos2)+1 accesses PC-BSD on Primary Partition #2. boot boots my PC-BSD. BUT: I discovered there was a problem when I had two BSD releases in two Primary Partitions. When I wanted the second BSD, GRUB always booted the first one. This looks like a bug in GRUB. Also I'm sure this whole scheme falls apart if you start moving or resizing your partitions. Yours truly: Frank Mitchell On Saturday 27 October 2012 06:14:05 Yuri wrote: When I installed ubuntu on another partition, it overwrote BSD MBR with grub one. Now grub boots ubuntu without even asking what to boot. When I tried to restore BSD MBR, BSD boots but linux doesn't. This is because there is no bootable PBR in linux partition. When I tried to install grub into PBR on its own partition, like someone online suggested, it refused with the message that this is dangerous, etc. So is there a way to boot both linux and BSD from BSD MBR (by pressing F2 or whatever)? Are there quick instructions anywhere? I just don't want grub to take over the boot process. Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Upcoming release schedule - 8.4 ?
Hey, I'm a Desktop User and I wish FreeBSD v8.3 worked for me. I can't get a Dialup Internet Connection without setting up a complicated script. And my Porn Videos crash halfway through. Yours frustratedly: Frank Mitchell On Wednesday 13 June 2012 00:08:08 Jerry McAllister wrote: Well, 8.3 is working fine for me. It is being well maintained. You sound like the people who can't decide to get something because a new version is going to come out sometime before they die. jerry ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Ways to promote FreeBSD?
Just ensure that FreeBSD is the ideal distro for downloading and watching videos. All sorts of videos... And some standard User-Software like Gnumeric and Open Office would be welcome too. Faictz Ce Que Vouldras: Frank Mitchell ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Death By NetBSD
Hi: Recently I installed NetBSD, then found FreeBSD wouldn't start. I had this problem before and believed it was due to a bug in the NetBSD Boot Selector, which I avoided installing. But this time it looked as if my FreeBSD Partition got wiped completely. Re-trying, it looked like NetBSD spotted the FreeBSD FFSv2 Partition and decided to assign it a Mount Point of /. This is listed if you look closely under NetBSD Disklabel Partitions... last chance to change. I edited that Mount Point away and afterwards my (reinstalled) FreeBSD was still present. Hey, I'm glad I keep my Data on a separate Partition. Am I the only guy who didn't know about this? Yours Truly: Frank Mitchell ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Ext2fs DVD+RW
Improved Ext2fs: What a great idea. I like trying different Unix flavours, and Ext2fs is the only filesystem they all understand. I put all my data on a separate Partition formatted Ext2, and every so often I'm glad: Like the recent occasion when the NetBSD Boot Selector altered something and prevented FreeBSD from starting, leaving me with no alternative but to reinstall. Also, under Linux, you can use Ext2fs on DVD+RW. Plain DVD-RW is unsuitable because it uses Superblocks of 16*2048 bytes, but CD-RW should be okay. Currently you can't do this under FreeBSD, probably because CD and DVD use 2048-byte Sectors, and FreeBSD wants 512-byte. Somebody said you can put UFS on DVD+RW, but I couldn't get that to work. So possibly Ext2fs would be a viable alternative to UDF, though I don't know enough about Filesystems myself to tell whether this idea has some enormous drawback. Yours truly: Frank Mitchell From: Aditya Sarawgi sarawgi.adi...@gmail.com I'm Aditya Sarawgi from India. I will be working on FreeBSD's ext2fs as a part of this year's summer of code program. I will be improving the current implementation and I will also rewrite parts of ext2fs under GPL. My mentor is Ulf Lilleengen. For more details you can visit http://wiki.freebsd.org/SOC2009AdityaSarawgi Cheers, Aditya Sarawgi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
cd9660 Lowercasing
I've developed a CD/DVD Backup Utility using the Enhanced Volume Descriptor
specified in ISO9660:1999. It doesn't have Rock Ridge yet, so the first thing
you notice on mounting is the automatic Lowercase, which interferes with
Backup Verification using diff -qr. There's a simple solution using
the gens mount option, which has Case Preservation as a side-effect, but
it's still annoying.
There must be some reason behind it, because NetBSD and Linux have a similar
feature, with options to disable it like: nomaplcase and map=off. But
their manpages make it look like a throwback to MS-DOS, and a time when all
filenames were accessed from the Primary Volume Descriptor. By default you
can't have filenames in ASCII using the Supplementary or Enhanced Volume
Descriptors either.
I think I tracked this feature down to cd9660_util.c, in Function isofntrans,
around Line 200:
for (; infn != infnend; ) {
infn += isochar(infn, infnend, joliet_level, c, clen, flags, handle);
if (!original !joliet_level c = 'A' c = 'Z')
c += ('a' - 'A');
else if (!original c == ';') {
outp -= (d == '.');
break;
}
d = c;
while(clen--)
*outp++ = c (clen 3);
}
This only alters ASCII characters. Accented uppercase letters from the top
half of ISO8859-1 are unaffected. And it doesn't apply to Joliet either. I
don't see the point. Why not just zap it away?
Yours Truly: Frank Mitchell
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Memory Locking On 64-Bit Release 6.3
My machine is an Economy Model, with 512 Meg RAM, including 64 Meg which is taken by Shared Video Memory, leaving 448 Meg usable. But my program requirements are modest too. I'm developing 2 Root-Privileged Console Executables, each around 100 KB, using a total of 11 Shared Memory buffers, each 256 KB. Faictz Ce Que Vouldras: Frank Mitchell On Sun, 9 Mar 2008 14:41:30 + Frank Mitchell wrote: MEMORY LOCKING: Recompiling my root-privileged program, I get a System Call failure for: mlockall(MCL_CURRENT); errno says: Resource temporarily unavailable how much memory is installed? But mlock(); works. ... and how many bytes/pages do you lock in this operation? note that currently the 64-bit ELF ld wastes space by allocating larger memory blocks than its 32-bit counterpart. this has been discussed before, but i don't remember any solution to the problem. regards, clemens ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Bugs On 64-Bit Version 6.3
MOUNTING EXT2FS: I dual-boot with OpenSUSE, sharing data on an Ext2 Partition. The machine is an AMD Sempron with SATA Hard Disk. After installing FreeBSD 64-bit for AMD, I suddenly got problems with mount_ext2fs. Thus: mount_ext2fs /dev/ad4s2 /mnt , with various options can yield: Operation not permitted kldload: unsupported file type I haven't noticed a pattern yet, but I discovered a simple solution: umount /mnt Which can work without complaining when I didn't know anything was mounted, like immediately after reboot. MEMORY LOCKING: Recompiling my root-privileged program, I get a System Call failure for: mlockall(MCL_CURRENT); errno says: Resource temporarily unavailable But mlock(); works. BIOS TIME SETTING: System Time keeps getting set back, typically by 5 minutes plus. I can't see another explanation yet except my new FreeBSD Installation. Faictz Ce Que Vouldras: Frank Mitchell. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Diff Symlinks
Diff with Symlinks happens to be very convenient for me. The implementation is probably a consequence of how some standard Unix Systems Command works. But obviously it would be an idea to switch it off by default, while leaving the user with the existing option. Another issue would be getting Recursive diff to work for Non-Root users without being needlessly obstructed by Permissions. Faictz Ce Que Vouldras: Frank Mitchell Jin Guojun [EMAIL PROTECTED] wrote: I do not know what is the historical reason for program diff to follow a symbolic link during the recursive diff (-r), but it seems not to be a proper implementation. So, we need to either disable recursive diff to follow the symlink, or we need a switch (option) to enable following symlink feature in recursive comparison of diff when a user real needs it. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 18/08/2006 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Coding question: finding the size of a block device
Let's assume your Block Device is an ATA Hard Disk and you're using FreeBSD 6.0 like me. Take a look at sys/ata.h and you'll see a large fully-commented structure, struct ata_params, which is used to return the information from the ATA IDENTIFY DEVICE command using something like: ioctl(DevFil,IOCATAGPARM,Parms); This probably tells you everything you need. Plus IOCATAGPARM also returns CD/DVD Drive information using the related IDENTIFY PACKET DEVICE command. For further details consult the T13 Website. For ATA/ATAPI you might start with: T13 1153D Revision 18 Information Technology - AT Attachment with Packet Interface Extension (ATA/ATAPI-4). Though there are later versions: T13 1321D (ATA/ATAPI-5) and T13 1410D (ATA/ATAPI-6). Whatever device you have there's probably some Hardware Command which gives you all the technical details. Faictz Ce Que Vouldras: Frank Mitchell -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.3/374 - Release Date: 23/06/2006 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
