Subject: Re: [parisc-linux] Win2k server boot howto - msg#00078

Previous Message by Date: click to view message preview

Re: HPPA still *ed...

On Sun, 21 Sep 2003, Colin Watson wrote: > On Sun, Sep 21, 2003 at 04:17:50PM +0200, Josip Rodin wrote: > > On Sat, Sep 20, 2003 at 10:08:41PM -0400, Nathanael Nerode wrote: > > > HPPA doesn't have updated glibc yet (still). No ETA. > > > That means that the fixed GCC 3.3 won't build on HPPA, so it can't go > > > into 'testing'. > > > > The new glibc went into testing despite hppa, so it's probably safe to > > assume that the new gcc will follow suit. Correct me if I'm wrong, but aren't essential packages from main supposed to stay forever in unstable, until they build for all architectures, at which point it is cuatiously allowed to move to testing? Why was glibc allowed to slide down to testing when hppa (assuming that hppa is the only case) didn't build? -- Martin-Éric Racine http://www.pp.fishpool.fi/~q-funk/

Next Message by Date: click to view message preview

kernel building problems: low-latency and pre-emptive patches

Greetings, Given how my HP712-60 is such a _SLOW_ machine, I thought I'd give a try to the low-latency and pre-emptive patches. They seem to apply fine, as shown below, but fail to appear in the configuration menus where I would need to enable them. Anybody can shed a light as to why that is and how would I make them appear? Btw, this was using whatever kernel is currently in the parisc-linux CVS. Thanks! X8----- <root@zarya:/usr/src/linux-2.4># make-kpkg --added-patches lowlatency,preempt --config menuconfig --revision hp712.atarifs.1 kernel_image test ! -f stamp-debian && test ! -f debian/official && \ rm -rf ./debian && mkdir ./debian test -f applied_patches && rm -f applied_patches make: [stamp-debian] Error 1 (ignored) for patch in /usr/src/kernel-patches/all//apply/lowlatency /usr/src/kernel-patches/all//apply/preempt ; do \ if test -x $patch; then \ if $patch; then \ echo "Patch $patch processed fine"; \ echo "$patch" >> applied_patches; \ else \ echo "Patch $patch failed."; \ echo "Hit return to Continue"; \ read ans; \ fi; \ fi; \ done Testing whether "Low-latency patch for the Linux kernel" patch for 2.4.22 applies (dry run): "Low-latency patch for the Linux kernel" patch for 2.4.22 succeeded Removing empty files after patching: Done. Patch /usr/src/kernel-patches/all//apply/lowlatency processed fine START applying patch "Preemptible patch for the Linux kernel" Testing whether "Preemptible patch for the Linux kernel" patch for 2.4.22 applies (dry run): "Preemptible patch for the Linux kernel" patch for 2.4.22 succeeded Removing empty files after patching: Done. END applying patch "Preemptible patch for the Linux kernel" Patch /usr/src/kernel-patches/all//apply/preempt processed fine echo done > stamp-patch X8----- -- Martin-Éric Racine http://www.pp.fishpool.fi/~q-funk/

Previous Message by Thread: click to view message preview

Win2k server boot howto

This is about using the dhcp server in win2k server to net boot a parisc box. On Sat, 30 Aug 2003, Matthew Wilcox wrote: > On Fri, Aug 29, 2003 at 04:14:04PM -0700, Jeremy Drake wrote: > > I have done it with the DHCP server that comes with win2k server. > > I think this might be useful information for the FAQ. Could you write > it up? Here is my first attempt at writing this up. Please send your criticisms/spelling fixes/flames. ------------------------------ I used Tftpd from http://tftpd32.jounin.net/ (which, in an unrelated side note, was used as part of the blaster worm, according to the site). I used the dhcp server which is a part of win2k server (Control Panel, Add/remove programs, Windows components, Networking Services, Dynamic Host Configuration Protocol (DHCP)). First, lets ask the box what its mac address is. I'm assuming you have a functional console. Power on the box, and when it says "press any key to" whatever press any key, and at the BOOT_ADMIN> prompt, type "in la" and hit enter. (For those of you who like to type, that's short for information lan). It will give you a hex number which is your workstation's mac address. Start up the DHCP admin tool (Start, Settings, Control Panel, Admin. Tools, DHCP). Expand your server in the tree, and right click on Reservations. Select "New Reservation...". For reservation name, I put my box's name. Give it an ip address that is not used in IP address, and enter the box's mac address in mac address (no delimiters, just a big hex number), and select Both for whether it should be bootp or dhcp. Then, find your new reservation at the bottom of the list under Reservations, and click it. Right click and choose "Configure Options..." It should have inherited your server's default options, so I won't cover setting router, dns, wins, and lease length. Scroll down the list of options until you get to 066, Boot Server Host Name. Check the box next to that option, and enter your tftp server's ip address (I don't trust dns to work in IPL). Also check 067, Bootfile Name, and enter the name of the lifimage (generally, lifimage is a good choice here). Say ok to that box, we're done in dhcp! Fire up tftpd32, and click the "browse" button. Browse to where you put your lifimage, and say ok. Make sure the ip address below the directory is the right one; if not, drop down the list and pick the right one. Leave this app up, the server only runs when the gui is displayed (not sure if you can run it as a service) Now we're ready to boot the box. Go back to the box, get the BOOT_ADMIN> prompt again (if you turned it off after the first time, or type "ma" for the main menu if you didn't). Type "sea" (for search), and if everything is good, you should see something like "P0 LAN.<BLAH>". If you do, congrats, if not, check all of the settings on the server (like, you recorded and typed the mac address correctly, and your dhcp server is on the same physical network segment as your workstation). If it shows a line like the above, enter "bo p0" (or whichever p number the LAN was by). Anything beyond this point belongs to an install howto more than a win2k server boot howto... -------------------------------- -- Computers make excellent and efficient servants, but I have no wish to serve under them. Captain, a starship also runs on loyalty to one man. And nothing can replace it or him. -- Spock, "The Ultimate Computer", stardate 4729.4

Next Message by Thread: click to view message preview

Re: How could HP help Debian

[moving to debian-hppa, since that seems to be the best place. doing my best to remove all traces of the original mail since that's decidedly private.] On Sun, Sep 14, 2003 at 10:30:18PM -0400, Grzegorz B. Prokopski wrote: > port "libffi" to HPPA if they want to see LGPL-ed SableVM JVM (and > probably also GCJ) working on these arches in near future [*]. Randolph Chung has libffi working quite well. He's got copyright papers sorted recently, and I believe he's just waiting for a spare couple of hours to get it all submitted. > PS: [*] And somebody tell me how to do atomic cmp&swap on HPPA - then > you have a working SableVM JVM on HPPA in 10 minutes. Seriously. You can't. hppa's only got one atomic instruction -- load-and-zero word. If you can use that as a locking primitive, ie lock read and write sides, then you're fine. If you can live with atomic assignment, you're also fine. But if you rely on something like cmpxchg() as a locking primitive, you're in trouble. > PSS: I would happily get in touch with people > interested in using SableVM more seriously. A few things is going down > the pipe, like integration with current GNU Classpath and an easily > portable/retargettable JIT engine (I don't see much of a problem to make > it work on HPPA if there were somebody interested). FWIW, it's "PPS" (Post-Post-Script). -- "It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject?" -- Robert Fisk -- To UNSUBSCRIBE, email to debian-hppa-request@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx