Re: Nothing happens after freeing kernel memory



Hello,

Personally I think rolling init into busybox is poor idea, a statically
linked init with busybox utils and shared libs is a compromise on space,
but a better way to get a system running.

I thought using BusyBox for everything possible makes it easiest for me to
create that image... of course, I can use SysVInit, but I don't need any
runlevels or suchalikes.

Yes, that's running, too. The system then had only 16 MB and I wanted to
eliminate the Ramdisk. Right now I have a 5,6 Mb image containing
loadkeys,
init and XF86_S3 which works (although without many fonts; I couldn't
afford
the memory then). DHCP Autoconfiguration is done by the kernel, which,
unfortunately, can't do this with PCMCIA nics - I wanted to make two
more
X-Terminals out of old 486-based notebooks.

dhclient instead?

That again needs work I have not done before; and it would need more
configuration. But I saw yesterday that BusyBox provides a dhcp client. The
biggest problem (and the problem that made everything useless) is the lack
of any storage inside one laptop. I'd need two floppies (kernel and root-fs)
at least, but couldn't fit the root-fs into one floppy containing
pcmcia-tools, dhcp client and X-server. A ramdisk is out of question, as 4
Mb of memory are simply not enough. This system works as a VNC client using
MS-DOS. I can even afford a two Mb ramdisk containing DOSVNC, SSHDOS and
SSH2DOS... thus far I never came with Linux, unfortunately.

[X hanging]
Yep. A 10MB lan will crawl running an X-terminal, especially with any
application that uses large amounts of image data as backgrounds (called
background pixmaps in X-speak). The problem is when an expose and redraw
event occurs the entire window contents for the top window (visible
window) and any secondary windows (more than are visible for a web
browser) are copied over the lan as raw bitmap data.

I thought that X-Terminal were used commonly on some universities over 10
MBit network connections, but I never heard that the speed was unbearable.
At home it is... do you think NX is a way to go? I like the idea of XDMCP
(connect to any server available), as this is not possible with VNC or RDP.

So a 600x900 window with 24bit graphics would send (600x900x3)/1024 =
1.58MByte of data, but if its using stacked windows or backgrounds it may
send it several times.

I only need 16 bit color depth, on the notebooks it's only 640x480x8 at
most.

In the real world the throughput of PCMCIA ethernet adapter is only about
3/4 the speed of an ISA one - and the ISA one already sucked....

Yes. The Terminal I was talking about had at least a PCI-onboard one, able
to take 100 MBit/s. But my network infrastructure here isn't able to take it
(10base2 coax cables lie in the wall and there's no way to replace them). Of
course, I could try to switch NICs and have that crossover-cable using my
RTL8139.

You could try enabling the X backing store, but a lot of code will ignore
it (see +bs option on some X servers)

I'll do later.

The best PXE boot stuff i've found is "pxes", but its gone a bit
to commercial for my personal taste.
http://pxes.sourceforge.net/

Understandable. Furthermore, the download is about 70 Mb and that won't fit
onto my CF card. I think that it should be possible to create an image of
about ... 20-30 Mb to get at least X and VNC client support. That'd be
enough if I change to Xvnc (as I've done it because of the notebooks).

Maybe a Debian boot or an LTSP client image.
http://www.ltsp.org/

That would need server-side configuration and limit the possibility to take
the thin client somewhere, hook in into the net and use it. That's why I
like XDMCP - configure xdm and boot the terminal. But if 10 MBit/s is not
enough...

You should know that I don't have a server here. I'm just experimenting with
my main computer and my Etherminal; nothing serious (yet).

Consider putting some of the older kit in the skip, trying to run an
X-term on 64MB of RAM and a fast LAN is possible, but slow LAN or less RAM
will not be viable as a general desktop.

I thought I could get the main memory down at 16 Mb again. These are the
only 32 Mb EDO modules I have (and they are not even mine), but I have about
10 unused modules of 8 Mb each.

I use a Sparc SLC with 16MB of RAM, but all it displays a single xterm
window running multitail to displays logs from a server, I would not
consider it for desktop use.

Nice to know that I'm not the only person using many computers at the same
time. My father would kill me if I had a working space like that. ;-)

Regards,
Sebastian


.



Relevant Pages

  • Re: TCP packets : end of thre-way handshake and start of data-transmission - how to dete
    ... " Several examples of connection initiation follow. ... packet because it would be necessary to assume a window size. ... client has already indicated a non-empty window). ... Server sends SYN/ACK and data ...
    (comp.arch.embedded)
  • Re: TCP packets : end of thre-way handshake and start of data-transmission - how to dete
    ... RFC 793 Section 3.4 (Establishing a connection) says in part: ... packet because it would be necessary to assume a window size. ... client has already indicated a non-empty window). ... Server sends SYN/ACK and data ...
    (comp.arch.embedded)
  • Re: Challenge: Local App to Run in TS Session??
    ... each aisle, from above, to see if this helps saturate the warehouse better. ... Microsoft MVP - Terminal Server ... Launch Navision RDP Client (preconfigured parameters auto-connects to ... to run in a non-full-screen window, because as soon as the user clicks to ...
    (microsoft.public.windows.terminal_services)
  • VPN Issue
    ... my sharepoint question. ... You can do this from the Server ... Management window. ... will be taken to the "Client Computer Management" window. ...
    (microsoft.public.windows.server.sbs)
  • Re: TCP Window Size
    ... terminal server, so window size wouldn't be the problem. ... network I/O, active clients, etc. ... Multiple parallel WAN links are being load ...
    (comp.dcom.sys.cisco)