[Gbootroot-devel] gdkbirdaao, spin button, device=size
Brought to you by:
freesource
Menu
▾
▴
[Gbootroot-devel] gdkbirdaao, spin button, device=size
|
From: Jonathan R. <mtt...@ac...> - 2000-08-28 17:10:20
|
On Sun, 27 Aug 2000, Cristian Ionescu-Idbohrn wrote: > On Sun, 27 Aug 2000, Jonathan Rosenbaum wrote: > > > Yes, I mean guess_default_kernel_image_and_root_device. Test it out > > really well, first. If you just want to set-up a demo cvs version so the > > variable results go to STDIN, that will be o.k., too. > > I attach that sub as a test case to this message. This is fine. It's actually a better way to test your functions. Gdkbirdaao is nice, I'll be linking it to the GUI. Append options will be put in the Advanced Section. > > I just got the new stripping section working, and I was able to test it in > > Debian because ld-2.1.2.so is not stripped. This means I can close bug > > 112073. I am wondering what will happen if I do a --strip-all rather than > > --strip-debug with libraries? If this works I may add this as an option, > > too. Yes, --strip-all works for initrd, so I'll add an option for libraries for people who like to live on the edge. > There's some more. I was playing around with gBootRoot and noticed some > inconsistances: > 1. if you role the floppy density counter down to 0 and then try go back > up twards 1440 and 1722, you get very funny figures This is because of the way Gtk works. This is something to put in the FAQ. There are two adjustments, step and page increments. When you press your first mouse button the step has been set to 282 so that a person can easily switch between 1440 & 1722. When you use your second mouse button the page is set at 360. You can go down to zero by pressing your third mouse button on the down arrow. Now page up with the second button to 1440 and step with the first button to 1722. Pretty cool, eh? > 2. the floppy device name _must_ be syncronized with the counter; > modifying one of then, should change the other This is an interesting function for you to write. I will be looking forward to it. 1722 has been set to fd0 by default, and I think it is a cool default value. (My own blurb about devices). Some problems I see with the present set-up of gBootRoot relate to the reopening of bug 11215. Most people will probably make disks on the same floppy used to boot, but if they use /dev/fd1, the disks won't work, so I'll add another field to the advanced section to avoid this problem. This leads to an interesting issue. Do you know if there are any ways to figure out all boot devices supported by a systems's BIOS? If we know this we could just list those devices in the beginners section, which would be a really cool thing to do. I hope you can figure out how to do this. Even is we can't read the BIOS, lots of the devices you list in 3 are unecessary. We could also just generalize and create a list of know boot devices. > 3. I know there are 2 different name schemes; Debian, the distro I use, > has support for these floppy devices: > > brw-rw---- 1 root floppy 2, 0 Apr 4 23:21 /dev/fd0 > brw-rw---- 1 root floppy 2, 84 Apr 4 23:21 /dev/fd0u1040 > brw-rw---- 1 root floppy 2, 88 Apr 4 23:21 /dev/fd0u1120 > brw-rw---- 1 root floppy 2, 28 Apr 4 23:21 /dev/fd0u1440 > brw-rw---- 1 root floppy 2, 124 Apr 4 23:21 /dev/fd0u1600 > brw-rw---- 1 root floppy 2, 44 Apr 4 23:21 /dev/fd0u1680 > brw-rw---- 1 root floppy 2, 60 Apr 4 23:21 /dev/fd0u1722 > brw-rw---- 1 root floppy 2, 76 Apr 4 23:21 /dev/fd0u1743 > brw-rw---- 1 root floppy 2, 96 Apr 4 23:21 /dev/fd0u1760 > brw-rw---- 1 root floppy 2, 116 Apr 4 23:21 /dev/fd0u1840 > brw-rw---- 1 root floppy 2, 100 Apr 4 23:21 /dev/fd0u1920 > brw-rw---- 1 root floppy 2, 12 Apr 4 23:21 /dev/fd0u360 > brw-rw---- 1 root floppy 2, 16 Apr 4 23:21 /dev/fd0u720 > brw-rw---- 1 root floppy 2, 120 Apr 4 23:21 /dev/fd0u800 > brw-rw---- 1 root floppy 2, 52 Apr 4 23:21 /dev/fd0u820 > brw-rw---- 1 root floppy 2, 68 Apr 4 23:21 /dev/fd0u830 > brw-rw---- 1 root floppy 2, 1 Oct 20 1999 /dev/fd1 > brw-rw---- 1 root floppy 2, 37 Oct 20 1999 /dev/fd1CompaQ > brw-rw---- 1 root floppy 2, 5 Oct 20 1999 /dev/fd1d360 > brw-rw---- 1 root floppy 2, 9 Oct 20 1999 /dev/fd1h1200 > brw-rw---- 1 root floppy 2, 41 Oct 20 1999 /dev/fd1h1440 > brw-rw---- 1 root floppy 2, 57 Oct 20 1999 /dev/fd1h1476 > brw-rw---- 1 root floppy 2, 73 Oct 20 1999 /dev/fd1h1494 > brw-rw---- 1 root floppy 2, 93 Oct 20 1999 /dev/fd1h1600 > brw-rw---- 1 root floppy 2, 21 Oct 20 1999 /dev/fd1h360 > brw-rw---- 1 root floppy 2, 49 Oct 20 1999 /dev/fd1h410 > brw-rw---- 1 root floppy 2, 65 Oct 20 1999 /dev/fd1h420 > brw-rw---- 1 root floppy 2, 25 Oct 20 1999 /dev/fd1h720 > brw-rw---- 1 root floppy 2, 81 Oct 20 1999 /dev/fd1h880 > brw-rw---- 1 root floppy 2, 85 Oct 20 1999 /dev/fd1u1040 > brw-rw---- 1 root floppy 2, 89 Oct 20 1999 /dev/fd1u1120 > brw-rw---- 1 root floppy 2, 29 Oct 20 1999 /dev/fd1u1440 > brw-rw---- 1 root floppy 2, 125 Oct 20 1999 /dev/fd1u1600 > brw-rw---- 1 root floppy 2, 45 Oct 20 1999 /dev/fd1u1680 > brw-rw---- 1 root floppy 2, 61 Oct 20 1999 /dev/fd1u1722 > brw-rw---- 1 root floppy 2, 77 Oct 20 1999 /dev/fd1u1743 > brw-rw---- 1 root floppy 2, 97 Oct 20 1999 /dev/fd1u1760 > brw-rw---- 1 root floppy 2, 117 Oct 20 1999 /dev/fd1u1840 > brw-rw---- 1 root floppy 2, 101 Oct 20 1999 /dev/fd1u1920 > brw-rw---- 1 root floppy 2, 33 Oct 20 1999 /dev/fd1u2880 > brw-rw---- 1 root floppy 2, 105 Oct 20 1999 /dev/fd1u3200 > brw-rw---- 1 root floppy 2, 109 Oct 20 1999 /dev/fd1u3520 > brw-rw---- 1 root floppy 2, 13 Oct 20 1999 /dev/fd1u360 > brw-rw---- 1 root floppy 2, 113 Oct 20 1999 /dev/fd1u3840 > brw-rw---- 1 root floppy 2, 17 Oct 20 1999 /dev/fd1u720 > brw-rw---- 1 root floppy 2, 121 Oct 20 1999 /dev/fd1u800 > brw-rw---- 1 root floppy 2, 53 Oct 20 1999 /dev/fd1u820 > brw-rw---- 1 root floppy 2, 69 Oct 20 1999 /dev/fd1u830 > > I think the redhatish distros have anothe scheme. Don't know anything > about the others. > > Do you want me to add this stuff to the bug list? Always feel free to add Bug Reports. The stuff in this letter would be Category: program Group: enhancement Prioritize based on how important you feel these features will be to the next public release. If it can be put on hold it is less important, if it keeps the program from working properly it is very important. Mention 'cretzu' as the reporter. Email goes out to whoever is the reporter and whoever the bug is assigned to. Keep up the great work, Lead Developer! |
