Re: Slink release - what's left?
Steve Dunham wrote: > Steve McIntyre <[EMAIL PROTECTED]> writes: > > > Where are we up to on non-i386 boot/installation? If we're going to > > release together, which I assume is still the plan, then we need to get > > this sorted _soon_. I know someone (Eric? Stephane?) is working on the > > sparc disks and I have some support for them now. I've seen work ongoing > > on the m68k disks, too. I've not seen much for Alpha yet, but that may be > > my fault. > > Eric is working on the disks. I think he is going to patch slink_cd > for the dual boot stuff. (It's pretty simple, I can come up with the > patch after I know how he is naming the disk images. > > I'm not sure if he will have time to finish it until this weekend. He > is adding support to boot-floppies to handle 2.2.x kernels and install > the right kernel depending on the architecture of the Sparc kernel. > > The changes to slink_cd to implement the dual booting are trivial. I > believe that Eric is going to take care of this. (I can do it if he > doesn't.) resc1440.bin, drv1440.bin for 2.0.35 sparclinux resc1440-2.2.1.bin, drv1440-2.2.1.bin for alternate 2.2.1 sparclinux resc1440-2.2.1-sun4u.bin, drv1440-2.2.1-sun4u.bin for 2.2.1 ultralinux Could you fix slink_cd yourself then send back the patch to me? I don't have much time to spend on debian this weekend and my priority is to fix bugs related to 2.2 kernel support in bootdisks. BTW, I did a fresh install on a SparcClassic using a tftpboot image built with TILO & your 2.2.1 kernels. No major problems... if using a framebuffer. I just was unable to configure the device drivers (modconf exited immediately; I need to investigate...). The big problem I have is in serial console support. Since linux is using /dev/console now, I cannot detect in a trivial manner whether it is connected to a serial console or not. I need to find a way to discriminate between linux console & serial console... Thanks for your help. -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970)
Gnome 0.99.4 packages
I've built some Gnome 0.99.4 packages from the stuff in potato. There a few minor problems with it - the gnome-terminal doesn't work (it can't get a pty for some reason - this will also break gnome-apt) and the "gnomecc" program dies whenever you exit from a capplet (but the changes do take effect anyways). The version of balsa in slink is made for a different version of gtk, so I left it out. (The MDI stuff and a few other things are different.) Same story for the gnome-games (the ones in slink are ancient and won't compile against the new libgtk). The panel and gnumeric seem to work well, as does the "thin-ice" theme (try it out, gnumeric looks really nice with the thin-ice theme). The packages are at: ftp://ftp.cse.msu.edu/pub/debian/gnome There is a Packages file, so the following /etc/apt/sources.list line should work: deb ftp://ftp.cse.msu.edu/pub/debian gnome/ Steve [EMAIL PROTECTED]
another minor bug in slink
silo seems to require all of the stages and the kernel to be in the first 100MB of the HD and not the 1st GB as docs say... I am not currently subscribed to this list, please, cc me... Thanks, Paco
slink bug (sunmouse major)
slink base_2_1.tgz has wrong major number for /dev/sunmouse was: (11,6) should be: (10, 6) anyway, congratulations! great work! thanks, Paco
Re: ipx-cgsix and X
And thus spake Daniel Urbach, on Thu, Jan 21, 1999 at 07:36:46AM -0900: > Wow, > that was painful. I just finished installing SLINK onto my ipx via ftp. > ( I had to gateway through anothe linux machine with a 14.4 modem, I > wouldn't recomend it ) Things seem to be going well so far but I need a > little help. First which X server should I chose ( dont know what color > depth a cgsix will support ) and I am having trouble with MAKEDEV. I > installed the 8 bit serverand X fails to start becausse there is no > /dev/kbd. MAKEDEV fails to build /dev/kbd with the error " I dont know > how to make device "kbd". > > Also I need to make a link for /dev/mouse but I dont know what device > to link it to. This is my first real experience with the Sparc machine I > am using sun type 4 keyboard ( reported at boot up ) and the mouse ( > sun 3 button optical ) that is atached to it. > > > Thank you for any pointers you might be able to give From: http://www.debian.org/Lists-Archives/debian-sparc-9901/msg00058.html Try the following commands to create missing devices: # mknod /dev/kbd c 11 0 # mknod /dev/fb0 c 29 0 # mknod /dev/sunmouse c 10 6 This got X working for me, so I think this is all you'll need to do for that. FYI- a cgsix is an accelerated 8bit card with 1mb vram (I think :). The cgthree is unaccelerated. -- Kevin Doherty, [EMAIL PROTECTED] "Multiple exclamation marks are a sure sign of a diseased mind." -- Rincewind (from _Eric_)
Re: SPARC Server 630MP
> Would like to inquire as to whether or not your distribution will support > the SUN SPARCsystem Server 630MP. This system uses the CY605c processors > and has the dreaded VME architecture. The SparcLinux kernel supports the 6XXMP series and will do SMP as of recent 2.1/2.2 kernels. VME is not supported yet. Anton
Re: Please test: impoved sparc and alpha X patches.
> Were you going to add that XF86Config file to the xserver-mach64 > package? Err, I thought I had. Small typo on my part made it not make it in there. I'm making another one (I won't bother building the other packages this time though, since it's only the packaging of the xserver that has changed). It should be in place in a few minutes. /Anders -- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | [EMAIL PROTECTED] Physics student | Hem: +46 31 47 69 27 Chalmers University of Technology, G|teborg, Sweden | Mob: +46 707 27 86 87
Re: Please test: impoved sparc and alpha X patches.
Anders Hammarquist <[EMAIL PROTECTED]> writes: > Hi again. > > New versions of the merged X pacakges for sparc and alpha are now available. > This time with a working xfs. > http://master.debian.org/~iko/ Works fine here. (Ultra-5 using mach64 server and Sparc20 using XSun24.) I've also successfully used xfs, xdm and xterm. Were you going to add that XF86Config file to the xserver-mach64 package? Steve [EMAIL PROTECTED]
Re: How to begin? (And pointer to new UltraSparc install images)
Jake Griesbach <[EMAIL PROTECTED]> writes: > Sorry for the ignorance here. I'm interested in installing Debian on a > SparcStation 1+, but I'm not sure how to begin. It doesn't have a floppy > drive, so I will need to boot over the network or from a CD. I am very > familiar with x86 linux, and SunOS 4.1.3 which the machine currently runs. > Where can I get instructions on net booting for a network Debian > installation? > Do I need to keep SunOS on the machine? I rather not, unless it means > decreased functionality. (I have heard that the SunOS drivers are needed > to execute SunOS programs.) > I have another question unrelated to net booting: when installing SunOS > from CD, it could only be installed from a Sun CDROM drive, a generic > CDROM drive would not be recognized by the kernel. Is this true for > Debian Linux too? Yes. The block size of the CDROM has to be set correctly for the PROM to understand it. (Once the system is booted Debian should be able to handle any kind of CD.) If you do a network boot, you can read the CD from inside Debian. Brief instructions that I sent to Nils for network installs on an UltraSparc with my newer install images. (Use the disk images from sun4cdm directory if you have a non-ultra machine.) If you don't want to use my images, just grab the tftpboot.img, {resc,drv}1440.img and base2_1.tgz from the main ftp site and follow the instructions. On the sparc: Find out it's MAC address by looking at the screen: 8:0:20:x:x:x On the other Linux box: * Make sure the kernel has rarp support (if it's in a module you'll have to load it). "rarp -a" will tell you if you have support compiled in. * Enable tftpd by uncommenting the tftpd line from /etc/inetd.conf. Then send SIGHUP to the inetd process. * Fetch tftpboot.img from my ftp site: ftp://ftp.cse.msu.edu/pub/debian/install.new and place in /boot (world readable). Make a symlink from tftpboot.img to the hex IP address of the sparc, e.g. ln -s tftpboot.img /boot/C0A80101 if the IP is 192.168.1.1. Use a relative link - tftpd chroots into /boot. * Also get the rest of the stuff from the "install.new" dir and export it via NFS to the sparc. (The base2_1.tgz and the sun4cdm directory.) * Add the rarp entry on the other Linux box: rarp -s 192.168.1.1 8:0:20:1:2:3 where "192.168.1.1" is the IP of the Sparc, and "8:0:20:1:2:3" is the MAC address. * Now, you can start a tcpdump, if you want to watch, then type: "boot net" At the PROM prompt on the Sparc. It should acquire an address, then download a large tftp image, then boot into Linux. You want to do configure Network before you install the kernel or base (so you have an NFS option). Point it at the location of your copy of base2_1.tgz and the sun4cdm stuff. Steve [EMAIL PROTECTED]
SPARC Server 630MP
Greetings, Would like to inquire as to whether or not your distribution will support the SUN SPARCsystem Server 630MP. This system uses the CY605c processors and has the dreaded VME architecture. If indeed you do I would like to gather information on how to obtain the distribution. Thank you for your assistance. Lance [EMAIL PROTECTED]
Re: Slink release - what's left?
Steve McIntyre <[EMAIL PROTECTED]> writes: > Where are we up to on non-i386 boot/installation? If we're going to > release together, which I assume is still the plan, then we need to get > this sorted _soon_. I know someone (Eric? Stephane?) is working on the > sparc disks and I have some support for them now. I've seen work ongoing > on the m68k disks, too. I've not seen much for Alpha yet, but that may be > my fault. Eric is working on the disks. I think he is going to patch slink_cd for the dual boot stuff. (It's pretty simple, I can come up with the patch after I know how he is naming the disk images. I'm not sure if he will have time to finish it until this weekend. He is adding support to boot-floppies to handle 2.2.x kernels and install the right kernel depending on the architecture of the Sparc kernel. The changes to slink_cd to implement the dual booting are trivial. I believe that Eric is going to take care of this. (I can do it if he doesn't.) Once anders X patches are in Branden's hands, the remaining issues will be the install documentation and the gdb package. Steve [EMAIL PROTECTED]
Re: libc6 vulnerability
Joel Klecker <[EMAIL PROTECTED]> writes: > At 19:42 -0800 1999-02-07, Paul Vojta wrote: > >Folks: > > > >When checking the security of my system, I found that it is vulnerable > >to the following standard attack (in tcsh syntax): > > > > env RESOLV_HOST_CONF=/etc/shadow /usr/sbin/traceroute foobar > > or env RESOLV_HOST_CONF=/etc/shadow fping foobar > > > >This allows the user to read any (text) file on the system. > > I have a Debian diff including a patch for this, someone simply needs > to compile and upload it. All that needs to be done is fix the > debian/changelog (by that I mean the -- line, I give permission to > use the -2 revision to whomever uploads this) and dpkg-buildpackage. > http://www.debian.org/%7Eespy/glibc-pre2.1_2.0.105-2.dsc > http://www.debian.org/%7Eespy/glibc-pre2.1_2.0.105-2.diff.gz This has been compiled and uploaded. (As I said, I removed the hardcoded "sparc" distribution - it must have been a mistake from the last version I uploaded that you didn't catch.) Steve [EMAIL PROTECTED]