Re: Status

[Artyom Tarasenko]

On Fri, Apr 15, 2016 at 1:06 PM, John Paul Adrian Glaubitz
 wrote:
> On 04/15/2016 12:52 PM, Artyom Tarasenko wrote:
>> This misinformation made me feel obliged to fix it in the upstream.
>> So, today's QEMU git can boot FreeBSD/sparc64. Don't know though
>> whether it's really relevant for anyone at debian-sparc mailing list.
>> :-)
>
> Awesome, thanks a lot!
>
>> (15+ years ago, mentioning *BSD on a Linux mailing list or vice-versa
>> would cause a holly war, but now we are all grown up, right?)
>
> Well, for my part, I think that emacs is much better than vim! xD

Well emacs is good. Except for the missing text editor. xD

> Btw, from your above comment it sounds like you have commit
> access to qemu? Am I understanding this correctly? Because
> I have a few qemu patches for the m68k target which are still
> waiting to be merged.

I don't have commit access to qemu. I think meanwhile it's more or
less centralized and pretty much everything is committed by Peter
Maydell.

The way to get the patches  is to post them on the Mailing list CCing
the sub-system maintainer.
According to the current MAINTAINERS file (I'm not loud, the actual
file name is all caps), M68K
has "Orphan" status. Which probably mean that you gonna have to CC
Peter himself.

Perhaps you would like to be a m68k mainainer? You cope with
debian-sparc very well. :-)

Artyom

-- 
Regards,
Artyom Tarasenko

SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

Re: Status

[John Paul Adrian Glaubitz]

On 04/15/2016 12:52 PM, Artyom Tarasenko wrote:
> This misinformation made me feel obliged to fix it in the upstream.
> So, today's QEMU git can boot FreeBSD/sparc64. Don't know though
> whether it's really relevant for anyone at debian-sparc mailing list.
> :-)

Awesome, thanks a lot!

> (15+ years ago, mentioning *BSD on a Linux mailing list or vice-versa
> would cause a holly war, but now we are all grown up, right?)

Well, for my part, I think that emacs is much better than vim! xD

Btw, from your above comment it sounds like you have commit
access to qemu? Am I understanding this correctly? Because
I have a few qemu patches for the m68k target which are still
waiting to be merged.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Status

[Artyom Tarasenko]

On Thu, Apr 7, 2016 at 1:38 PM, Artyom Tarasenko  wrote:
> On Thu, Apr 7, 2016 at 11:29 AM, Michael-John Turner  
> wrote:
>> On Thu, Apr 07, 2016 at 11:12:50AM +0200, John Paul Adrian Glaubitz wrote:
>>> The document you linked is over 6 years old! sparc64 emulation is pretty
>>> usable already, I have installed the sparc64 netinst images that I built
>>> without any problems.
>>
>> Ah, I missed the date at the bottom of the page and didn't realise that!
>> I'm not sure that installing newer version of Solaris works yet though (at
>> least according to this[1] 2015 thread from Stack Exchange). Still,
>> possibly worth a try though.
>
> Not yet. There is some  progress, for instance, qemu-system-sparc64
> can boot Linux since March 2013 [1], and NetBSD since 2014 [2].
> One of the problems is that qemu-system-sparc64 emulates a workstation
> which has been never existed as a bare metal. Therefore it's not
> possible to use an existing firmware to boot Solaris and Solaris for
> 64 bit SPARC machines is very picky about the firmware.
> But Mark Cave-Ayland is working on OpenBIOS (in the mean time it can
> already boot FreeBSD)

Ops. Have just seen the mail from Mark, that not yet. Sorry for the
mis-information.
The rest is still valid. :-)

> and I work on sun4v emulation which could re-use
> Firmware from the OpenSPARC project (its Firmware is indeed
> Solaris-compatible).
> So, stay tuned.
>
>
> 1. http://tyom.blogspot.de/2013/03/debiansparc64-wheezy-under-qemu-how-to.html
> 2. http://tyom.blogspot.de/2014/08/upstream-qemu-can-run-netbsdsparc64.html
> --
> Regards,
> Artyom Tarasenko
>
> SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu



-- 
Regards,
Artyom Tarasenko

SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

Re: Status

[Artyom Tarasenko]

On Thu, Apr 7, 2016 at 11:29 AM, Michael-John Turner  wrote:
> On Thu, Apr 07, 2016 at 11:12:50AM +0200, John Paul Adrian Glaubitz wrote:
>> The document you linked is over 6 years old! sparc64 emulation is pretty
>> usable already, I have installed the sparc64 netinst images that I built
>> without any problems.
>
> Ah, I missed the date at the bottom of the page and didn't realise that!
> I'm not sure that installing newer version of Solaris works yet though (at
> least according to this[1] 2015 thread from Stack Exchange). Still,
> possibly worth a try though.

Not yet. There is some  progress, for instance, qemu-system-sparc64
can boot Linux since March 2013 [1], and NetBSD since 2014 [2].
One of the problems is that qemu-system-sparc64 emulates a workstation
which has been never existed as a bare metal. Therefore it's not
possible to use an existing firmware to boot Solaris and Solaris for
64 bit SPARC machines is very picky about the firmware.
But Mark Cave-Ayland is working on OpenBIOS (in the mean time it can
already boot FreeBSD) and I work on sun4v emulation which could re-use
Firmware from the OpenSPARC project (its Firmware is indeed
Solaris-compatible).
So, stay tuned.


1. http://tyom.blogspot.de/2013/03/debiansparc64-wheezy-under-qemu-how-to.html
2. http://tyom.blogspot.de/2014/08/upstream-qemu-can-run-netbsdsparc64.html
-- 
Regards,
Artyom Tarasenko

SPARC and PPC PReP under qemu blog: http://tyom.blogspot.com/search/label/qemu

Re: Status

[Mark Cave-Ayland]

On 07/04/16 10:29, Michael-John Turner wrote:

> On Thu, Apr 07, 2016 at 11:12:50AM +0200, John Paul Adrian Glaubitz wrote:
>> The document you linked is over 6 years old! sparc64 emulation is pretty
>> usable already, I have installed the sparc64 netinst images that I built
>> without any problems.
> 
> Ah, I missed the date at the bottom of the page and didn't realise that!
> I'm not sure that installing newer version of Solaris works yet though (at
> least according to this[1] 2015 thread from Stack Exchange). Still,
> possibly worth a try though.
> 
> [1] 
> https://unix.stackexchange.com/questions/199827/booting-solaris-10-or-11-for-sparc-in-qemu-system-sparc64

Currently FreeBSD and Solaris don't boot under qemu-system-sparc64,
although progress has been slow recently as most of my spare time went
into last year's GSoC. I'm gradually starting to find time to look at
SPARC issues again and of course more testing/bug reports are always
welcome :)


ATB,

Mark.

Re: Status

[Mark Cave-Ayland]

On 07/04/16 10:12, John Paul Adrian Glaubitz wrote:

> Hi Michael!
> 
>> On Apr 7, 2016, at 10:43 AM, Michael-John Turner  wrote:
>>
>>>
>>
>> I believe that will only work on x86 systems - KVM isn't supported on SPARC.
>> QEMU has some early emulation support for 64-bit SPARC hardware but it's
>> not really usable yet[1].
> 
> The document you linked is over 6 years old! sparc64 emulation is pretty 
> usable already, I have installed the sparc64 netinst images that I built 
> without any problems.

Wow, yes. The link you've posted below references a snapshot from the
documentation for QEMU 0.12 which is, well, old. I recently submitted an
update which can be found in the automated builds here:
http://qemu.weilnetz.de/qemu-doc.html#Sparc64-System-emulator.


ATB,

Mark.

Re: Status

[Michael-John Turner]

On Thu, Apr 07, 2016 at 11:12:50AM +0200, John Paul Adrian Glaubitz wrote:
> The document you linked is over 6 years old! sparc64 emulation is pretty
> usable already, I have installed the sparc64 netinst images that I built
> without any problems.

Ah, I missed the date at the bottom of the page and didn't realise that!
I'm not sure that installing newer version of Solaris works yet though (at
least according to this[1] 2015 thread from Stack Exchange). Still,
possibly worth a try though.

[1] 
https://unix.stackexchange.com/questions/199827/booting-solaris-10-or-11-for-sparc-in-qemu-system-sparc64

Cheers, MJ
-- 
Michael-John Turner * m...@mjturner.net * http://mjturner.net/

Re: Status

[John Paul Adrian Glaubitz]

Hi Michael!

> On Apr 7, 2016, at 10:43 AM, Michael-John Turner  wrote:
> 
>> 
> 
> I believe that will only work on x86 systems - KVM isn't supported on SPARC.
> QEMU has some early emulation support for 64-bit SPARC hardware but it's
> not really usable yet[1].

The document you linked is over 6 years old! sparc64 emulation is pretty usable 
already, I have installed the sparc64 netinst images that I built without any 
problems.

Cheers,
Adrian

> If the OP has a newer system, a possible option would be to install Solaris
> in an LDOM and use that.
> 
> [1] 
> http://wiki.qemu.org/download/qemu-doc.html#QEMU-System-emulator-for-non-PC-targets
> 
> Cheers, MJ
> -- 
> Michael-John Turner * m...@mjturner.net * http://mjturner.net/

Re: Status

[Michael-John Turner]

On Mon, Apr 04, 2016 at 10:38:25AM +0200, John Paul Adrian Glaubitz wrote:
> On 04/04/2016 05:04 AM, Jerome Ibanes wrote:
> > * Does Debian/sparc64 offer any binary compatibility layer for solaris
> > 10/sparc64 binaries?
> 
> No, unfortunately not. You would have to resort to kvm to install
> an instance of Solaris in a kernel-based virtual machine.

I believe that will only work on x86 systems - KVM isn't supported on SPARC.
QEMU has some early emulation support for 64-bit SPARC hardware but it's
not really usable yet[1].

If the OP has a newer system, a possible option would be to install Solaris
in an LDOM and use that.

[1] 
http://wiki.qemu.org/download/qemu-doc.html#QEMU-System-emulator-for-non-PC-targets

Cheers, MJ
-- 
Michael-John Turner * m...@mjturner.net * http://mjturner.net/

Re: Status

[John Paul Adrian Glaubitz]

On 04/04/2016 05:04 AM, Jerome Ibanes wrote:
> A few questions related to migrating a solaris 10/sparc64 only
> application; which isn't available for other platforms.
> 
> * Does Debian/sparc64 offer any binary compatibility layer for solaris
> 10/sparc64 binaries?

No, unfortunately not. You would have to resort to kvm to install
an instance of Solaris in a kernel-based virtual machine.

> * Does Debian/sparc64 have support for X11/Xorg, and if so, which
> video cards are supported, the application aforementioned has a
> graphical requirement (which could be remotely displayed if necessary,
> but we would prefer not to).

Yes, Debian on sparc64 has full support for Xorg. Basically all display
hardware supported by the current release of Xorg should work. There
might be some issues with Sun-specific display adapters as someone
else previously reported on this list, but in such cases, you
could just install a known-working standard PC graphics card
as a work-around (PCI, AGP or PCI Express).

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: status of ruby 1.9.1 wrt porting

[Lennart Sorensen]

On Mon, Aug 29, 2011 at 11:48:34PM +0200, Lucas Nussbaum wrote:
 Ruby 1.9.3 is going to be released in september, and is a candidate for
 the default ruby version in wheezy. A snapshot is available in
 experimental. Now is an ideal time to work on porting issues and get the
 fixes integrated upstream. Ruby has a fairly large test suite, which
 makes finding problems easy, but exercises the threading library in
 interesting ways.
 
 Most of the issues are reproducible by re-building the Debian package.
 Use make  make test to get a shorter build.
 
 Here is the current complete list of issues I'm aware of. My time will
 be very limited in the coming weeks, but I will try my best to provide
 help.
 
 [armel,sparc] FTBFS due to miscompilation with -ftree-sra (inc. in -O3).
 See http://bugs.debian.org/635126.
 Currently worked-around by using -fno-tree-sra.
 Other packages might be affected.
 - FIXED from ruby1.9.1's POV, but you really want to look at this
for other packages.
 
 [armel] I've just seen that now that this one is fixed, the test suite
 segfaults.
 See
 https://buildd.debian.org/status/fetch.php?pkg=ruby1.9.1arch=armelver=1.9.3~preview1%2Bsvn33077-1stamp=1314634969
 search for 'TestFiber#test_many_fibers'.
 'make test-all' to reproduce. Failures during test-all are currently not
 fatal. The remaining ones needs more investigation, but I don't think
 that they are arch-specific. I'd like to make test-all failures fatal at
 some point.

Building on armhf seemed to go fine, and running some of the examples
looked good too.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110830140829.gl15...@caffeine.csclub.uwaterloo.ca

Re: Re: Status of (debian) linux on Sun Fire 480R

[Hermann Lauer]

  Hopefully debian kernel people will pick up a 2.6.32 kernel to
  unstable and testing in the near future.
 
 As you can see from http://packages.debian.org/linux-image-2.6.32
 it's already there :)

Great!

Tried it on a SunFire 880, hangs at boot (see below). Will try a vanilla
kernel when time permits.

 Greetings Hermann


Allocated 8 Megs of memory at 0x4000 for kernel
Uncompressing image...
Loaded kernel version 2.6.32
Loading initial ramdisk (8085481 bytes at 0xA00040 phys, 0x40C0 virt)...
-
[0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.34 2007/07/23 13:01'
[0.00] PROMLIB: Root node compatible: 
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-trunk-sparc64-smp (Debian 2.6.32-2) 
(b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Dec 17 
10:19:33 UTC 2009
[0.00] bootconsole [earlyprom0] enabled
[0.00] ARCH: SUN4U
[0.00] Ethernet address: 00:03:ba:08:d9:24
[0.00] Kernel: Using 2 locked TLB entries for main kernel image.
[0.00] Remapping the kernel... done.
[0.00] OF stdout device is: /p...@9,70/e...@1/ser...@1,40:a
[0.00] PROM: Built device tree with 102731 bytes of memory.
[0.00] Top of RAM: 0xa0ffb1a000, Total RAM: 0xffb0e000
[0.00] Memory hole size: 655360MB
[0.00] [01014000-f8a000c0] page_structs=131072 node=0 
entry=1280/0
[0.00] [01014000-f8a00100] page_structs=131072 node=0 
entry=1281/0
[0.00] [01014080-f8a00140] page_structs=131072 node=0 
entry=1282/0
[0.00] [01014080-f8a00180] page_structs=131072 node=0 
entry=1283/0
[0.00] [01014100-f8a001c0] page_structs=131072 node=0 
entry=1284/0
[0.00] [01014100-f8a00200] page_structs=131072 node=0 
entry=1285/0
[0.00] [01014180-f8a00240] page_structs=131072 node=0 
entry=1286/0
[0.00] [01014180-f8a00280] page_structs=131072 node=0 
entry=1287/0
[0.00] Zone PFN ranges:
[0.00]   Normal   0x0500 - 0x0507fd8d
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[4] active PFN ranges
[0.00] 0: 0x0500 - 0x0507f7ff
[0.00] 0: 0x0507f800 - 0x0507fd09
[0.00] 0: 0x0507fd0b - 0x0507fd7b
[0.00] 0: 0x0507fd7e - 0x0507fd8d
[0.00] Booting Linux...
[0.00] PERCPU: Embedded 7 pages/cpu @f8a002c0 s25600 r8192 
d23552 u2097152
[0.00] pcpu-alloc: s25600 r8192 d23552 u2097152 alloc=1*4194304
[0.00] pcpu-alloc: [0] 0 2 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 519563
[0.00] Kernel command line: root=/dev/sda1 ro console=ttyS0
[0.00] PID hash table entries: 4096 (order: 2, 32768 bytes)
[0.00] Dentry cache hash table entries: 524288 (order: 9, 4194304 bytes)
[0.00] Inode-cache hash table entries: 262144 (order: 8, 2097152 bytes)
[0.00] Memory: 4135384k available (3376k kernel code, 1368k data, 232k 
init) [f800,00a0ffb1a000]
[0.00] SLUB: Genslabs=14, HWalign=32, Order=0-3, MinObjects=0, CPUs=3, 
Nodes=1
[0.00] Hierarchical RCU implementation.
[0.00] NR_IRQS:255
[0.00] clocksource: mult[64] shift[16]
[0.00] clockevent: mult[28f5c28] shift[32]
[0.00] Console: colour dummy device 80x25
[   37.633793] Calibrating delay using timer specific routine.. 20.01 BogoMIPS 
(lpj=40037)
[   37.727886] Security Framework initialized
[   37.776786] SELinux:  Disabled at boot.
[   37.822624] Mount-cache hash table entries: 512
[   37.877543] Initializing cgroup subsys ns
[   37.924700] Initializing cgroup subsys cpuacct
[   37.977843] Initializing cgroup subsys devices
[   38.030940] Initializing cgroup subsys freezer
[   38.084065] Initializing cgroup subsys net_cls
[   38.139873] CPU 0: synchronized TICK with master CPU (last diff 0 cycles, 
maxerr 11 cycles)
[   38.139894] Brought up 2 CPUs
[   38.141614] regulator: core version 0.5
[   38.141869] NET: Registered protocol family 16
[   


-- 
Netzwerkadministration/Zentrale Dienste, Interdiziplinaeres 
Zentrum fuer wissenschaftliches Rechnen der Universitaet Heidelberg
IWR; INF 368; 69120 Heidelberg; Tel: (06221)54-8236 Fax: -5224
Email: hermann.la...@iwr.uni-heidelberg.de


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Status of (debian) linux on Sun Fire 480R

[Josip Rodin]

On Thu, Dec 17, 2009 at 05:19:47PM +0100, Hermann Lauer wrote:
 Big thanks to davem for fixing this and getting all into the mainstream.
 Hopefully debian kernel people will pick up a 2.6.32 kernel to
 unstable and testing in the near future.

As you can see from http://packages.debian.org/linux-image-2.6.32
it's already there :)

Now, I don't know about debian-installer images...?

-- 
 2. That which causes joy or happiness.


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Status of Debian on Sun Blade 150

[foo_bar_baz_boo-deb]

I don't think I can necessarily help with your parted issue. I just
wanted to say that I was amazed with your creativity and patience in
creating this special installation, and that I was impressed with your
diagram of the disk. Also, the black magic you described in your e-mail
to get this all to work was well thought out and very hilarious. It
reminded me of what I did at work today:

A few weeks ago, I spent half of a workday fighting with the Xerces-C++
XML processing library which we need for validating some integration
data files. I was trying to get it to compile on Solaris 2.9 in 64 bit
mode with GCC/G++ instead of the officially supported (but expensive
and not installed by default at work) Sun Forte. Their
pre-GNU-configure build script performs some disturbing mungefest on
some environment variables, inserting some secret values that
GNU-configure uses to configure the build. Of course, the secret values
that work right for Forte don't work well at all for GCC/G++. Not
surprising.

So, today, I spent half of a day reverse-engineering the secret values,
then making some educated guesses at what GCC/G++ and GNU-configure
might prefer that they be. Amazingly, it built right on the first try!
However, ironically, when I tried to redo the build with optimization,
it failed.

I believe I figured out why. Firstly, GNU-configure makes some changes
to the tree that make distclean does not fully reverse. Secondly, I
moved the directory to a different volume between compilations. I
believe that this broke some of the directory paths that GNU-configure
hardcoded into the source tree someplace. Tomorrow I'll fix it all (at
least everything always seems to work right on Fridays at my job) and
make it happy again.

One philosophical question. Does the fact that I am demented enough to
figure out how this sick and twisted build system works lead to the
need to question my own mental state? I wondered about this on the way
home this afternoon.

Anyhow, thanks for motivating me to write this funny story down.

--- Wiktor Wandachowicz [EMAIL PROTECTED] wrote:

 Jurij Smakov wrote:
 
  Everyone is working towards the same goal here, so let's not get
  too picky about the choice of words.
 
 Thanks for bringing me back to my senses. Let's focus on the topic.
 
 # fdisk -l /dev/hda
 
 Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19158
 cylinders
 Units = cylinders of 4080 * 512 bytes
 
 Device FlagStart   EndBlocks   Id  System
 /dev/hda1   258   319124440   83  Linux native
 /dev/hda2 0   2585263203  SunOS swap
 /dev/hda3 0 19158  390823205  Whole disk
 /dev/hda4 15391 19156   76806002  SunOS root
 /dev/hda5  3660  6744   6291360   83  Linux native
 /dev/hda6  6744 10574   7813200   83  Linux native
 /dev/hda7 10574 15391   9826680   83  Linux native
 /dev/hda8   319  3660   68156408  SunOS home
 
 I'd like to reiterate: I was doing tests on a live system. It came
 to life this way:
 
 1) Install Solaris 9 on a clean disk:
 
 +--+  \
 | hda2   SunOS swap 514 MB |   \
 |  ||
 +--+|
 |  ||
 |  ||
 +--+|
 | hda8   SunOS home   6 GB ||
 |UFS   / (Solaris) ||
 |  ||
 +--+|
 |  ||
 |  | \
 |  |hda3  Whole disk
 |  | /
 |  ||
 |  ||
 |  ||
 |  ||
 |  ||
 |  ||
 |  ||
 +--+|
 | hda4   SunOS root 6,5 GB ||
 |UFS   / (Solaris) ||
 |  |   /
 +--+  /
 
 Solaris installer proposed this in different way:
 (look where hda1 and hda2 were going to be!)
 
 +--+  \
 | hda2   SunOS swap 514 MB |   \
 |  ||
 +--+|
 | hda8   SunOS home ~23 GB ||
 |  ||
 |  | \
 |  |hda3  Whole disk
 |  | /
 |  ||
 +--+|
 | hda1   SunOS root   6 GB ||
 |  ||
 |

Re: Status of Debian on Sun Blade 150 (parted and the like)

[Frans Pop]

On Friday 29 April 2005 15:47, Wiktor Wandachowicz wrote:
 So, after all it looks like the problem was on my side. I'm terribly
 sorry for misinforming you, and I take back my words. Looks like Frans
 was right when he wrote about user error. I bow my head before him. He
 is the one who really knows better how to handle Debian on sparc... But
 I'm learning :-) 

:-)   /me is only a newbie regarding Sparc himself ;-)

 Probably putting swap partition in a different location could save me a
 bit of trouble. But on the side note, it was Solaris installer that put
 swap partition on cylinders 0-258 of the hard drive. So it looked to me
 that it knew what it was doing proposing such layout upon install.

It probably does for Solaris.
I think that Solaris may format/use the swap partition in a different way 
than linux (and thus Debian) does.

So, the problem is that the installer blindly re-uses (and also formats 
by default) a swap partition that starts in sector 0.
There already is some code and dialogs in silo-installer that hooks into 
partman to warn about this, but that code appears to be unfinished and is 
currently not used.

Cheers,
FJP


pgpNkeMTxbmkT.pgp
Description: PGP signature

Re: Status of Debian on Sun Blade 150 (parted and the like)

[Wiktor Wandachowicz]

Frans Pop wrote:

Wiktor Wandachowicz wrote:

Probably putting swap partition in a different location could save me a
bit of trouble. But on the side note, it was Solaris installer that put
swap partition on cylinders 0-258 of the hard drive. So it looked to me
that it knew what it was doing proposing such layout upon install.


It probably does for Solaris.
I think that Solaris may format/use the swap partition in a different way 
than linux (and thus Debian) does.

When we'll be able to see the sources of OpenSolaris, it may as well become
quite obvious. But I'd like to repeat: on running Debian system I've put
a script which recreates swap every time Linux boots (btw. Solaris
initializes swap itself, without any action needed).

The sript I've made is in /etc/init.d/regenswap.sh, and is symlinked to
/etc/rcS.d/S09regenswap.sh. This script essentially calls mkswap for every
swap partition listed in /etc/fstab, BEFORE any swapon is called.
This way the swap partition is shared between Linux and Solaris and there
is no need to create an additional partition for linux-style swap only.

So, the problem is that the installer blindly re-uses (and also formats 
by default) a swap partition that starts in sector 0.
There already is some code and dialogs in silo-installer that hooks into 
partman to warn about this, but that code appears to be unfinished and is 
currently not used.

I don't know if it could stop me, though. I'm quite determined sometimes :-)

Friendly,
Wiktor Wandachowicz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of Debian on Sun Blade 150

[Wiktor Wandachowicz]

Jurij Smakov wrote:
Everyone is working towards the same goal here, so let's not get
too picky about the choice of words.
Thanks for bringing me back to my senses. Let's focus on the topic.
# fdisk -l /dev/hda
Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19158 cylinders
Units = cylinders of 4080 * 512 bytes
   Device FlagStart   EndBlocks   Id  System
/dev/hda1   258   319124440   83  Linux native
/dev/hda2 0   2585263203  SunOS swap
/dev/hda3 0 19158  390823205  Whole disk
/dev/hda4 15391 19156   76806002  SunOS root
/dev/hda5  3660  6744   6291360   83  Linux native
/dev/hda6  6744 10574   7813200   83  Linux native
/dev/hda7 10574 15391   9826680   83  Linux native
/dev/hda8   319  3660   68156408  SunOS home
I'd like to reiterate: I was doing tests on a live system. It came
to life this way:
1) Install Solaris 9 on a clean disk:
+--+  \
| hda2   SunOS swap 514 MB |   \
|  ||
+--+|
|  ||
|  ||
+--+|
| hda8   SunOS home   6 GB ||
|UFS   / (Solaris) ||
|  ||
+--+|
|  ||
|  | \
|  |hda3  Whole disk
|  | /
|  ||
|  ||
|  ||
|  ||
|  ||
|  ||
|  ||
+--+|
| hda4   SunOS root 6,5 GB ||
|UFS   / (Solaris) ||
|  |   /
+--+  /
Solaris installer proposed this in different way:
(look where hda1 and hda2 were going to be!)
+--+  \
| hda2   SunOS swap 514 MB |   \
|  ||
+--+|
| hda8   SunOS home ~23 GB ||
|  ||
|  | \
|  |hda3  Whole disk
|  | /
|  ||
+--+|
| hda1   SunOS root   6 GB ||
|  ||
|  |   /
+--+  /
... but I persuaded it to the previous layout.
2) Use a mixture of Debian/sparc64 and Gentoo/sparc64
install CDs to create additional partitions and ext2/ext3
filesystems:
+--+  \
| hda2   SunOS swap 514 MB |   \
|  ||
+--+|
| hda1   Linux native   126 MB ||
|ext2  /boot  (separate)   ||
+--+|
| hda8   SunOS home   6 GB ||
|UFS   /  (Solaris)||
|  ||
+--+|
| hda5   Linux native 6 GB ||
|ext3  /  (Debian) | \
|  |hda3  Whole disk
+--+ /
| hda6   Linux native 6 GB ||
|ext3  /home  (separate)   ||
|  ||
+--+|
| hda7   Linux native   ~10 GB ||
|ext3  empty  (spare)  ||
|  ||
|  ||
+--+|
| hda4   SunOS root 6,5 GB ||
|UFS   /home  (Solaris)||
|  |   /
+--+  /
3) Install Debian sarge around February 14th 2005.
I didn't let parted format any partitions apart from maybe
hda5 and hda6 (I can't remember really). Instead, I ordered
it to use existing partitions without deleting contents,
because they were empty. And it worked.
At that point it was a real achievement, b/c current d-i was
unusable on Sun Blade 150 at the time. So I used an old version,
dated 20040511, with kernel 2.4.26. It was a long process, but
eventually I've finished that with only minor problems.
After that I've had a working multiboot machine. Debian sarge
became the default, whereas specifying 'other=4' in silo.conf
let the Solaris start. A one-liner into boot scripts let the
Debian reuse Solaris swap (an mkswap before swapon, 

Re: Status of Debian on Sun Blade 150

[Wiktor Wandachowicz]

On Tue, 26 Apr 2005, Jurij Smakov wrote:
Hi Wiktor,
[snip]
According to the logs the base-installer (it's postinst script, actually) 
exited with error cannot_install. According to the source, this error can 
only occur (given that the CD is properly mounted under /cdrom) if it fails to 
read the contents of the /cdrom/.disk/base_components file (which is present 
on CD). I tend to think that it was just some random cd-rom glitch (I didn't 
encounter any problems during my testing). Could you please try reproducing 
it, and if the problem persists, return to main menu, start a shell and check 
that the mentioned file indeed exists and contains the string 'main' (without 
quotes)?

Now I didn't really expect this, but after booting a machine with the
netboot image you provided and switching to the 2nd console I got:
# ls -a /cdrom/.disk
.   ..  base_components base_installableinfoudeb_include
# cat /cdrom/.disk/base_components
cat: Read error: Input/output error
You are pure genius! I'll try another burning session soon.
And maybe another disk. At least I know what to look for.
BTW. I've found a similar behaviour on another testing machine.
It concerns the partitioner. I let it to format partitions, but
later I can't get it to display properly the contents of the drive.
I prefer doing the manual partitioning, but partitions don't show up.
Weird. It happened twice on two different machines, but not once on
the third one. Do you think it may be related to te same CD problem?
Thanks anyway!
Wiktor Wandachowicz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of Debian on Sun Blade 150

[Wiktor Wandachowicz]

Frans Pop wrote:

Hi Wiktor,

On Wednesday 27 April 2005 19:39, Wiktor Wandachowicz wrote:

And the problem I described with the parted is consistent on the same
machine. I can't get it to display partitions after I select manual
partitioning from its menu.


I'm afraid this is user error.
You've put swap as the first partition (starting on cylinder 0). This 
overwrites the sun-disklabel that is written in that location!
The result is that parted no longer recognizes the disk during the 
second installation.

With sun-disklabel you are not allowed to put swap or RAID or LVM at the 
start of the disk. ext2/ext3 are OK.

See also:
http://d-i.alioth.debian.org/manual/en.sparc/apbs05.html#id2538449


I didn't do it. Solaris 9 installer did it! It is the one who put
swap space at clusters 0-258:

# fdisk -l /dev/hda

Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19156 cylinders
Units = cylinders of 4080 * 512 bytes

   Device FlagStart   EndBlocks   Id  System
   /dev/hda1   258   319124440   83  Linux native  /boot
   /dev/hda2  u  0   2585263203  SunOS swap
   /dev/hda3 0 19156  390782405  Whole disk
   /dev/hda4 15391 19156   76806002  SunOS root
   /dev/hda5  3660  6744   6291360   83  Linux native  /
(sarge1)
   /dev/hda6  6744 10574   7813200   83  Linux native  /home
   /dev/hda7 10574 15391   9826680   83  Linux native  /
(sarge2)
   /dev/hda8   319  3660   68156408  SunOS home


BTW, that machine ALREADY WORKED before trying netboot. It had Solaris
installed first (hda{2,4,8}), with manually specified partition sizes,
then Debian has been installed side-by-side with Solaris (hda{1,5,6}).
All partitions have been visible before trying netboot, and they are still
visible after installing second Debian on spare (hda7) partition. And
fdisk still works too, just as it worked before testing the installation.
The machine still boots, too, both into sarge1 as well as sarge2.
(I can't put silo.conf here, because all machines are turned off ATM)

User error. That's impolite. 'Cause I've spent LOTS of time crafting
that multiboot configuration. The best proof is that installer DID
everything correctly first time (when all partitions were right), then
after formatting swap (hda2) it turned out that it was unable to display
partitions list anymore. From my POV it is the one to blame.

If it is indeed user error (I mean: the Solaris installer's and my error),
then I'm terribly sorry. But in that case please elaborate more how it
should be done The Right Way. Keep in mind that multiboot with a spare
partition is a must.

P.S. If you want fdisk, just switch to VT2, wget the fdisk udeb from a 
mirror [1] and 'udpkg -i' it.

[1] http://ftp.debian.org/debian/pool/main/u/util-linux/

Wow, I didn't know that. Thank you very much!

With best regards,
Wiktor Wandachowicz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of Debian on Sun Blade 150

[Jurij Smakov]

On Thu, 28 Apr 2005, Wiktor Wandachowicz wrote:
Frans Pop wrote:
With sun-disklabel you are not allowed to put swap or RAID or LVM at the
start of the disk. ext2/ext3 are OK.
Frans, if you are referring to #283303, I thought that we've fixed it. 
At least the bug is marked 'fixed' when version 62 of partman has been 
uploaded, and I remember testing it and confirming that the bug is gone.
Version in RC3 is 63, so it should be fixed there too.

I didn't do it. Solaris 9 installer did it! It is the one who put
swap space at clusters 0-258:
# fdisk -l /dev/hda
Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19156 cylinders
Units = cylinders of 4080 * 512 bytes
  Device FlagStart   EndBlocks   Id  System
  /dev/hda1   258   319124440   83  Linux native  /boot
  /dev/hda2  u  0   2585263203  SunOS swap
  /dev/hda3 0 19156  390782405  Whole disk
  /dev/hda4 15391 19156   76806002  SunOS root
  /dev/hda5  3660  6744   6291360   83  Linux native  /
(sarge1)
  /dev/hda6  6744 10574   7813200   83  Linux native  /home
  /dev/hda7 10574 15391   9826680   83  Linux native  /
(sarge2)
  /dev/hda8   319  3660   68156408  SunOS home
Wow, this is one complicated partition configuration. I would not be too 
surprised that partman chokes on it. I was trying to suggest to create a 
clean disklabel before partitioning, but as I understand it is out of the 
question =).

User error. That's impolite. 'Cause I've spent LOTS of time crafting
that multiboot configuration. The best proof is that installer DID
everything correctly first time (when all partitions were right), then
after formatting swap (hda2) it turned out that it was unable to display
partitions list anymore. From my POV it is the one to blame.
If it is indeed user error (I mean: the Solaris installer's and my error),
then I'm terribly sorry. But in that case please elaborate more how it
should be done The Right Way. Keep in mind that multiboot with a spare
partition is a must.
Everyone is working towards the same goal here, so let's not get too picky 
about the choice of words. Please try partitioning with fdisk, as Frans 
suggested. If it will work as expected, we can be pretty confident that 
the problem lies with partman. Also, it would be interesting to see 
whether parted and fdisk recognize the partition sizes and types correctly 
on a runnning system.

Thanks and best regards,
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of Debian on Sun Blade 150

[Jurij Smakov]

Hi Wiktor,
On Tue, 26 Apr 2005, Wiktor Wandachowicz wrote:
- The installer progreses up to the point where it wants to install
a base system, but it is unable to do so. The error diplayed is:
[!!] Install the base system
Cannot install Debian
The installer cannot figure out how to install Debian. No installable CD-ROM 
was found and no valid mirror was configured.
Go Back  Continue

I attach a gzipped archive of whole /var/log directory of the
debian installer (from its ramdisk). On the target machine the
installer created only some less important files.
According to the logs the base-installer (it's postinst script, 
actually) exited with error cannot_install. According to the source, 
this error can only occur (given that the CD is properly mounted under 
/cdrom) if it fails to read the contents of the 
/cdrom/.disk/base_components file (which is present on CD). I tend to 
think that it was just some random cd-rom glitch (I didn't encounter any 
problems during my testing). Could you please try reproducing it, and if 
the problem persists, return to main menu, start a shell and check that 
the mentioned file indeed exists and contains the string 'main' (without 
quotes)?

Thanks for testing,
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

installation-reports (Vince.McIntyre fwd) [was: Re: Status of Debian on Sun Blade 150]

[Wiktor Wandachowicz]

As Vince asked, I just forward this message to the lists.
Maybe next time he'll just send it himself :-)
Friendly,
Wiktor Wandachowicz
-- Forwarded message --
Date: Sun, 24 Apr 2005 17:28:01 +1000 (EST)
From: Vincent McIntyre [EMAIL PROTECTED]
To: Wiktor Wandachowicz [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Status of Debian on Sun Blade 150
Hi Wiktor, Juirij
Andreas has made some progress! See logs attached.
I could not make a full install, as the box is still needs to run solaris.
Please could you forward this report to -sparc and maybe -boot.
I'm not subscribed to either, I simply can't afford the distraction at the
moment.
Cheers
Vince

Package: installation-reports
INSTALL REPORT
Debian-installer-version:
  netinst from http://www.acm.cs.rpi.edu/~dilinger/iso.img
  MD5 sum: 03f1445c82c80e51254b55616eb99479
  'file' output:
   Sun disk label 'CD-ROM Disc with Sun sparc boot created by mkisofs' 768
alts/cyl, 768 data cyls, -2135424256 blocks, boot block present
uname -a: 2.4.27
Date: 2005 04 24
Method: see comments section
Machine: Sun SunBlade 100
Processor: Ultrasparc-IIe  (ie sun4u, or sparc64 arch)
Memory: 384Mb
Root Device: ide
Root Size/partition table:
Output of lspci and lspci -n:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[E/O]  (see below)
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]
Comments/Problems:
The command sequence was:
 solaris# halt
 ok setenv auto-boot? false
 ok reset-all
 [reboots]
 ok boot cdrom
 SILO 1.4.9
 boot: ret
 starts booting, panics when trying to mount root fs  locks up solid.
 [power down]
 count to ten..
 [power up]
 ok boot cdrom
 SILO 1.4.9
 boot: ret
  [installer comes up with choose language screen]
  Choose Language: English
  Country: Australia
  Choose keyboard layout: Go Back
(it offered a bunch of sun type5 mappings)
  Main menu: Choose keyboard layout
   Choose keyboard type: USB
   Choose keyboard layout: American English
   [red screen - select keyboard layout failed]
 (choose_keymap selects mac-usb-us, even though the keyboard was
  detected as a NON-apple keyboard. Tsk.
  It looks like the process (#459) calling kbd-chooser (process #461)
  segfaults. The logs say kbd-chooser failed with error code 139.
 )
  Main menu: Choose keyboard layout
   Choose keyboard type: None
  Main Menu: detect and mount cdrom
   [ displays a ton of modules, all turned on ]
   Continue
  [ installer detects cdrom and loads the installer components ]
  Main Menu: configure network
   [ installer tries to configure with dhcp, this fails ]
   configure network manually
  Partition Hard disk: exit

PS:
Using netcat to transfer installation logs from 'a' to 'b'
The port number is arbitrary, but do check it isn't used first.
 b% script var-log-messages
 Script started on Sun Apr 24 16:52:30 2005
 b% nc -l -p 10002 a
 On a, where the installer is running, get into the console (caf2)
 # nc -p 10002 b  /var/log/messages
 On b,
 b% exit
 Script done on Sun Apr 24 16:54:30 2005
 (for dmesg output: # dmesg 21 | nc -p 10002 b )

sb100-andreas.tar.gz
Description: Binary data

Re: Status of Debian on Sun Blade 150

[Wiktor Wandachowicz]

Jurij Smakov wrote:

 Hi Wiktor,

 Thanks to Andres Salomon ([EMAIL PROTECTED]) we now have an unofficial
 netinst CD image, which should (hopefully) work on SunBlade. I would
 appreciate if people would test it. If testing works out, we'll try to
 propagate the required changes into the first post-release Sarge
 revision. Note that the kernel on the unofficial image is
 binary-incompatible with the kernel modules which are currently in the
 archive. It can be downloaded from

 http://www.acm.cs.rpi.edu/~dilinger/iso.img

 IMPORTANT: This is an unofficial image created for testing purposes
 only, so please do *NOT* report any problems with this image to the
 Debian's BTS or to the debian-installer team.

Great, I'll try this image soon and share my experience.

 Given that the sparc installation manual has not been updated for
 Sarge :-(, this is not surprising. Perhaps you would like to volunteer
 for updating it? As I understand, it is too late already to get all
 the translations in sync, but having at least the English version
 up-to-date would be an achievement. If you are up to it, you should
 probably discuss the details with Frans Pop.

I don't know if I am good enough to actually update the whole docs. Of
course, I can try to propose an update of how to run RARP and TFTP
servers under Debian and Solaris 9 (which I have access to). IIRC this
was the way we attempted (with success!) to install Debian woody on
Blade 150 by the very first time. I hope that if Frans has some time,
maybe he can guide me a little. I can always provide a pure text for
someone to import it into more useful format.

 It is a very useful and detailed write-up, a job well done. I have
 created a wiki page SparcInstallation notes
 (wiki.debian.net/?SparcInstallationNotes)
 and included a link to your installation report there.

Why, thanks! And what is that bunch of links hg-fix(dot)com and
hgfix(dot)org doing on the page you mention? Looks like an ad or
something...

Friendly,
Wiktor Wandachowicz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of Debian on Sun Blade 150

[Jurij Smakov]

Hi Wiktor,
On Thu, 21 Apr 2005, Wiktor Wandachowicz wrote:
Hello good Debian people!
Recently I tested the installation of Debian sarge on Sun Blade 150
and I got some success. Trying netinst / businesscard CD proved to be 
useless. So I tried the netboot image with 2.6.8 kernel and it worked!
Big thanks to Uwe Wuerdinger for pointing me in that direction.
Thanks to Andres Salomon ([EMAIL PROTECTED]) we now have an unofficial netinst 
CD image, which should (hopefully) work on SunBlade. I would appreciate if 
people would test it. If testing works out, we'll try to propagate the 
required changes into the first post-release Sarge revision. Note that the 
kernel on the unofficial image is binary-incompatible with the kernel 
modules which are currently in the archive. It can be downloaded from

http://www.acm.cs.rpi.edu/~dilinger/iso.img
IMPORTANT: This is an unofficial image created for testing purposes only, 
so please do *NOT* report any problems with this image to the Debian's BTS 
or to the debian-installer team.

Information in the sarge manual
(http://d-i.alioth.debian.org/manual/en.sparc/ch04s04.html)
(http://d-i.alioth.debian.org/manual/en.sparc/ch05s01.html#boot-tftp)
seemed a bit confusing to me, so I did some experimentation on my own
with rarpd  tftpd servers. I think I've found an easier way than
suggested in manual.
Given that the sparc installation manual has not been updated for Sarge 
:-(, this is not surprising. Perhaps you would like to volunteer for updating 
it? As I understand, it is too late already to get all the translations in 
sync, but having at least the English version up-to-date would be an 
achievement. If you are up to it, you should probably discuss the details 
with Frans Pop.

I described everything in great detail and posted my results here:
http://lists.debian.org/debian-boot/2005/04/msg00651.html
So, what do you think about my results? Do you think it may be of some
use? Tell me I did a good thing, and you'll make my day happy ;-)
It is a very useful and detailed write-up, a job well done. I have created 
a wiki page SparcInstallation notes (wiki.debian.net/?SparcInstallationNotes)
and included a link to your installation report there.

Friendly,
Wiktor Wandachowicz
Best regards,
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of 2.4 kernel with sparc 4m SMP

[Jan-Benedict Glaw]

On Thu, 2004-03-25 14:46:07 -0700, Dave Lee [EMAIL PROTECTED]
wrote in message [EMAIL PROTECTED]:
 Dear 4m / SMP users, (and maybe Ben Collins)
 
 Can anybody update me WRT the status of 2.4.x running on 4m/SMP hardware ?

Should work. Don't expect 2.6.x to yet work SMP on sun4m

Please also keep an eye on sparclinux@vger.kernel.org

MfG, JBG

-- 
   Jan-Benedict Glaw   [EMAIL PROTECTED]. +49-172-7608481
   Eine Freie Meinung in  einem Freien Kopf| Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH)  ~(NEW_COPYRIGHT_LAW | DRM | TCPA));


signature.asc
Description: Digital signature

Re: Status of Debian sparc64 kernels

[Mauricio]

At 15:04 -0500 1/27/04, Ben Collins wrote:

Most people know by now that the Debian sparc64 kernel packages are way
out of date. I've been fighting with kernel sizes for awhile, and even
the current 2.4.21-smp image is too big too boot.

That's going to change over the next week. I just finished up some
changes to SILO and the kernel so that we can boot images as large as
8Megs (instead of the current 3.5Megs).

I need to finish a lot of testing first.


If you need testing, I want to put debian in a ultra 1 =)

Re: Status of Debian sparc64 kernels

[Min Xu(Hsu)]

On Tue, 27 Jan 2004 Ben Collins wrote :
 Most people know by now that the Debian sparc64 kernel packages are way
 out of date. I've been fighting with kernel sizes for awhile, and even
 the current 2.4.21-smp image is too big too boot.
 
 That's going to change over the next week. I just finished up some
 changes to SILO and the kernel so that we can boot images as large as
 8Megs (instead of the current 3.5Megs).
 
 I need to finish a lot of testing first.

That's great! I am looking forward to it.

 
 -- 
 Debian - http://www.debian.org/
 Linux 1394 - http://www.linux1394.org/
 Subversion - http://subversion.tigris.org/
 WatchGuard - http://www.watchguard.com/
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 

Re: Status of Debian sparc64 kernels

[Nate Campi]

On Tue, Jan 27, 2004 at 03:04:14PM -0500, Ben Collins wrote:
 Most people know by now that the Debian sparc64 kernel packages are way
 out of date. I've been fighting with kernel sizes for awhile, and even
 the current 2.4.21-smp image is too big too boot.
 
 That's going to change over the next week. I just finished up some
 changes to SILO and the kernel so that we can boot images as large as
 8Megs (instead of the current 3.5Megs).
 
 I need to finish a lot of testing first.

Let us know if you need testers.
-- 
Nate

It's not that I'm so smart , it's just that I stay with problems longer. 
  - Albert Einstein

Re: Status of KDE 3.1 in 'unstable'

[Ben Collins]

On Sun, Jul 13, 2003 at 12:06:28AM -0500, Daniel 'Doc' Sewell wrote:
 Hello, all...
 
   I thought by moving to 'unstable', I could get KDE 3.1.  But when I 
 tried to update, I got this message below.  I assume this means it's 
 not ready for public consumption?  Or, I'll need to point at a 
 different site in my sources.list to get it?  The KDE site says it's in 
 'unstable'.
 
   Does someone know where/how I can get it for Debian/Sparc64?

Looks like some packages are not yet built for sparc. Just means you'll
have to wait. It is unstable :)

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo   - http://www.deqo.com/

Re: Status of KDE 3.1 in 'unstable'

[Pieter-Paul Spiertz]

Hi,

On Sun, 13 Jul 2003, Ben Collins wrote:

  I thought by moving to 'unstable', I could get KDE 3.1.  But when I
  tried to update, I got this message below.

 Looks like some packages are not yet built for sparc. Just means you'll
 have to wait. It is unstable :)

These packages are krita and kuickshow. And the packages koffice and
kdegraphics that they're part of, are actually meta-packages. You can
safely install all subpackages in it, omitting krita and kuickshow,
and you'll have a working kde3.

On one machine, I had to symlink /usr/local/share/applnk to
/usr/share/applnk before it would correctly display koffice icons,
and before QT3 Designer would work, I had to follow #182189.

Apart from that, I think it works fine.


Regards,
Pieter-Paul

Re: Status of KDE 3.1 in 'unstable'

[Daniel 'Doc' Sewell]

That did the trick!  I have almost all of KDE 3.1 installed and 
running!  It looks great!



Doc Sewell

On Sunday, Jul 13, 2003, at 04:34 US/Central, Pieter-Paul Spiertz wrote:


Hi,

On Sun, 13 Jul 2003, Ben Collins wrote:


I thought by moving to 'unstable', I could get KDE 3.1.  But when I
tried to update, I got this message below.


Looks like some packages are not yet built for sparc. Just means 
you'll

have to wait. It is unstable :)


These packages are krita and kuickshow. And the packages koffice and
kdegraphics that they're part of, are actually meta-packages. You can
safely install all subpackages in it, omitting krita and kuickshow,
and you'll have a working kde3.

On one machine, I had to symlink /usr/local/share/applnk to
/usr/share/applnk before it would correctly display koffice icons,
and before QT3 Designer would work, I had to follow #182189.

Apart from that, I think it works fine.


Regards,
Pieter-Paul


---
Daniel 'Doc' Sewell
debian underscore sparc at thezealot dot net

Re: Status of boot-floppies for Debian 3.0r2

[Steffan Baron]

On Thu, Jan 23, 2003, Adam DiCarlo wrote:

Eduard Bloch [EMAIL PROTECTED] writes:

  - help Ben Collins [EMAIL PROTECTED] to test the Sparc
  boot-floppies

Hmmm, no SPARC build eh?

Are there any sparc developers on this list who have access to a SPARC
box running stable and can help us out by building this?  Please
follow-up to debian-boot.

Well, I'm not a 'sparc developer' but I'm running stable and could
build them. What do I have to do, i.e., where do I get the source
package?

Gruss
Steffan


---
I am the ILOVEGNU signature virus. Just copy me to your signature.
This email was infected under the terms of the GNU General Public License.

Re: Status of boot-floppies for Debian 3.0r2

[Eduard Bloch]

#include hallo.h
* dann frazier [Fri, Jan 24 2003, 01:20:29AM]:
 done.
 http://people.debian.org/~dannf/boot-floppies/sparc/
 let me know if i missed anything.

Fine. BenC claimed to be the one how knows what is needed to build, but
I cannot count on his promises and response times.

Now, I would like to see at least one installation report with Dann's
build - especially when they are problems.

TOFU kept.

   I have a sparcstation 4 running straight woody that i'd be willing to 
   build
   stuff on - i'm afraid i missed some context though - is this 
   for a boot-floppies update for woody?
  
  Yes, we're trying to get boot-floppies 3.0.24 for Debian 3.0r2.  See 
  http://people.debian.org/~blade/bf3024/ .
  
  -- 
  ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/
  
 
-- 
Letzte Worte des Elektrikers:
  Alles klar, kannst einschalten.

Re: Status of boot-floppies for Debian 3.0r2

[Adam DiCarlo]

Eduard Bloch [EMAIL PROTECTED] writes:

  - help Ben Collins [EMAIL PROTECTED] to test the Sparc
  boot-floppies

Hmmm, no SPARC build eh?

Are there any sparc developers on this list who have access to a SPARC
box running stable and can help us out by building this?  Please
follow-up to debian-boot.

-- 
...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/

Re: Status of Netra X1?

[Ben Collins]

On Sat, Jul 07, 2001 at 07:20:13AM -0400, mdxi wrote:
 I've been following with some interest the recent thread(s) about the 
 porting efforts on the Netra X1.
 
 Over the past week it has become apparent that I'll be getting at least 
 one of these boxes in the near future, so I was wondering if someone could 
 whip up a very brief summary of the state of Debian on these machines.

AFAIK, everything pretty much works, except for the network card. I'm
not sure what work is being done on that ATM.

 Lastly: I've been reading the serial-console HOWTO, but it seems very PC 
 oriented. Is there anything special/different about Suns that I should 
 know?

For Sun's, just hook up the serial cables, and start up your terminal
program on the remote side. The Debian installer handles setting up the
rest (and the Sun OBP handles the hardware side).

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'

Re: Status of Sid/Slink/Potato/whatever it is for me

[Christian Meder]

On Fri, Nov 27, 1998 at 12:39:36PM -0500, J. S. Connell wrote:
 1) Running the 2.0.33 on the boot disks (as of a week or two ago) with
 libc6 (2.0.100-2.1), my syslog fills up quickly with:
 
 Unimplemented SPARC system call 102 
 PSR: 40800085 PC: 500ae110 NPC: 500ae114 Y: 0090 
 g0:  g1: 0066 g2: ea94 g3: 50098cf3 
 g4:  g5:  g6:  g7:  
 o0: 0002 o1: ea40 o2: e9b0 o3: 500acef4 
 o4: 0008 o5: 5002bf50 sp: e950 ret_pc: 500acdb8 
 l0: 500acef4 l1: 0002 l2: 0002 l3: 0001 
 l4: 0002 l5:  l6:  l7: 5018f4a8 
 i0: 0002 i1: ebe8 i2: eb58 i3: 50195a44 
 i4: 0001 i5: 00036148 i6: eaf8 i7: 500acc8c 
 
 (I've also seen 103, 109, and 119.)

Use the kernel-image-2.0.35 package which should fix your problems.

 
 2) Running 2.1.128 (I think - I had to reinstall because I toasted silo
 trying to remove Solaris) and libc6 2.0.95-something, signal handling was
 very weird.  Due to some messages I got from ld.so (something about a
 signal-related structure changing size), these may go away.  I've been busy
 with work and haven't had a chance to finish building .129 yet (I ran into
 problems with the audio stuff - it was trying to include a nonexistent
 linux/hisax/foreign.h and failing), and .130 has been released, so I'll
 get back to you on this.

2.1.x and 2.0.9x don't play well together. If you want to run 2.1.x you 
should use 2.0.100.

 I'm currently updating all the packages in my system to the latest
 versions.  Are y'all aware that sid/main/binary-sparc/x11/xfonts* are
 symlinks to invalid files (once you chase the five levels of symlinks
 back)?

It wasn't broken a couple of days ago. Perhaps we should notify ftpmaster.

Greetings,


Christian

-- 
Christian Meder, email: [EMAIL PROTECTED]
 
What's the railroad to me ?
I never go to see
Where it ends.
It fills a few hollows,
And makes banks for the swallows, 
It sets the sand a-blowing,
And the blackberries a-growing.
  (Henry David Thoreau)
 

Re: status: pass 1 complete

[Joey Hess]

Johnie Ingram wrote:
 w-bassmannproc/whattime.h: No such file or directory

Install libproc-dev.

-- 
see shy jo, stuck on a trian somewhere in Texas


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: status: at libs/publib and still compiling

[Bdale Garbee]

In article [EMAIL PROTECTED] you wrote:

: gforthError: -37 make[1]: *** [primitives.TAGS] Error 37

As maintainer of the gforth package, I had to switch to egcs to get it to 
build on i386... something clashes between the current gcc and the gforth
sources, and I couldn't figure it out.

Hope that helps.

Bdale


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: status: pass 1 complete

[Johnie Ingram]

Mark == Mark W Eichin [EMAIL PROTECTED] writes:

Mark Yeah, avoid compiling emacs itself, but the emacs19 sources
Mark should already have the sparc fixes.

H...

  Loading buff-menu...
  Loading float-sup...
  make[2]: *** [emacs] Floating point exception
  make[2]: Leaving directory
  `/u2/ftp/hamm/hamm/source/editors/emacs19-19.34/src'

Guess I need that new kernel with floating point emulation, or
something.

-  PGP  E4 70 6E 59 80 6A F5 78  63 32 BC FB 7A 08 53 4C
 
   __ _Debian GNU Johnie Ingram [EMAIL PROTECTED]  mm   mm
  / /(_)_ __  _   ___  __netgod irc.debian.org  mm mm
 / / | | '_ \| | | \ \/ / m m m
/ /__| | | | | |_| |Those who do not understand UNIX   mm   mm
\/_|_| |_|\__,_/_/\_\ are doomed to repeat it, poorly.   GO BLUE






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Status of the new glibc

[Johnie Ingram]

Juan == Juan Cespedes [EMAIL PROTECTED] writes:

Juan   However: almost *all* of our binaries will have to be
Juan recompiled.

Is it safe to base a distribution on this version of glibc, if the
authors feel free to break binary compatibility at any moment?  From
what I can tell from sparc development, this glibc has worked the same
for about a year -- now everything is changing.

This has overturned a couple of formerly unconscious assumptions I've
been making:

1.  Debian packages of 1999 will be drop-in compatible
with this release, since libc6 will probaby still be used.
2.  Debian and Redhat 5.0/SPARC, if and when they release it,
will be binary-compatible.

Either theres a bug in compatibility code, or this glibc 2.1 is so
unstable and different that it is more rightly considered libc7.

The glibc 2.1 FAQ however, in section 2.15, holds out a little hope
that this is a bug in either glibc or the program (which shouldn't
reference low-level data structures at all).

Whatever is decided here, the binary compatibility of libc6 must not
change again until Debian 2.1 is released, if then.


-  PGP  E4 70 6E 59 80 6A F5 78  63 32 BC FB 7A 08 53 4C
 
   __ _Debian GNU Johnie Ingram [EMAIL PROTECTED]  mm   mm
  / /(_)_ __  _   ___  __netgod irc.debian.org  mm mm
 / / | | '_ \| | | \ \/ / m m m
/ /__| | | | | |_| |Those who do not understand UNIX   mm   mm
\/_|_| |_|\__,_/_/\_\ are doomed to repeat it, poorly.   GO BLUE


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Status of the new glibc

[Mark W. Eichin]

Is there any reason not to change the soname, if it's that
incompatible?  it's going to be *hard* to upgrade if we have to
basically redo the last month worth of bootstrapping from scratch.  If
we can use a new soname, I can deal with moving forward with this
release... but if we can't do that, or the equivalent, I'd have to
recommand *not* using this libc release until it does change enough
(and stabilize) that an soname change gets made.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Status of the new glibc

[Juan Cespedes]

On 19 Jan 1998, Mark W. Eichin wrote:

 Is there any reason not to change the soname, if it's that
 incompatible?

It's not incompatible with glibc-2.0; it is with older pre-2.1
libraries.

  it's going to be *hard* to upgrade if we have to
 basically redo the last month worth of bootstrapping from scratch.  If
 we can use a new soname, I can deal with moving forward with this
 release... but if we can't do that, or the equivalent, I'd have to
 recommand *not* using this libc release until it does change enough
 (and stabilize) that an soname change gets made.

H.J. Lu says it won't change that way again... I hope he'll
be right.

Note:  I think all the programs will still work.  They will
only display 2 warnings when executing them.  If you want, that
warnings can be avoided...

-- 
Juan Cespedes


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Status of the new glibc

[Mark W. Eichin]

 It's not incompatible with glibc-2.0; it is with older pre-2.1

Oh, I see, and 2.0.90 is really 2.1-- rather than 2.0++.

   Note:  I think all the programs will still work.  They will
 only display 2 warnings when executing them.  If you want, that

I guess I misinterpreted -- I thought you were saying the new libc
made older programs things dump core?  The warnings I can live with
(as long as they go to stderr, and even then, a way to turn them off
(temporary environment variable?) will probably make some autoconf-based
tests happier.)


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Status of the new glibc

[Juan Cespedes]

On Mon, Jan 19, 1998 at 11:17:13AM -0500, Mark W. Eichin wrote:
  It's not incompatible with glibc-2.0; it is with older pre-2.1
 
 Oh, I see, and 2.0.90 is really 2.1-- rather than 2.0++.
 
  Note:  I think all the programs will still work.  They will
  only display 2 warnings when executing them.  If you want, that
 
 I guess I misinterpreted -- I thought you were saying the new libc
 made older programs things dump core?  The warnings I can live with
 (as long as they go to stderr, and even then, a way to turn them off
 (temporary environment variable?) will probably make some autoconf-based
 tests happier.)

I'll upload it without displaying anything.  I still think
that all the programs will work, but be careful: I may be wrong.

Anyway, binaries compiled with *this* library will probably
*not* work with previous releases (I'm adding a propper `shlibs'
file).

-- 
Juan Cespedes


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .