1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<META NAME="generator" CONTENT="lgazmail v1.1F.i">
<TITLE>The Answer Guy 36: No STREAMS Error while Installing Netware for Linux</TITLE>
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
LINK="#3366FF" VLINK="#A000A0">
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<H4>"The Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<center>
<H1><A NAME="answer">
<img src="../../gx/dennis/qbubble.gif" alt="(?)" border="0" align="middle">
<font color="#B03060">The Answer Guy</font>
<img src="../../gx/dennis/bbubble.gif" alt="(!)" border="0" align="middle">
</A></H1>
<BR>
<H4>By James T. Dennis,
<a href="mailto:answerguy@ssc.com">answerguy@ssc.com</a><BR>
Starshine Technical Services,
<A HREF="http://www.starshine.org/">http://www.starshine.org/</A>
</H4>
</center>
<p><hr><p>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<H3 align="left"><img src="../../gx/dennis/qbubble.gif" height="50" width="60"
alt="(?) " border="0">No STREAMS Error while Installing Netware for Linux</H3>
<p><strong>From Sean McMurray on Tue, 17 Nov 1998
</strong></p>
<!-- begin 35.20 -->
<P><STRONG>
I'm trying to install <A HREF="http://www.caldera.com/">Caldera</A> Netware for Linux on Redhat 5.1.
Following the instructions from
<A HREF="ftp://ftp.caldea.com/pub/netware/INSTALL.redhat">ftp://ftp.caldea.com/pub/netware/INSTALL.redhat</A>,
I get to Step 5 under "Downloading the Files."
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Well, I haven't played with this yet, since I don't
have any Netware client systems around here. (Maybe
one of these days I'll fire up one of my old XT's to
use for clients).
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
When I type in rpm -i kernel-2_0_35-1nw_i386.rpm, I get the
following error:
</STRONG></P>
<P><STRONG>
ln: boot/vmlinuz-2.0.35-1nw-streams: No such file or directory
</STRONG></P>
<P><STRONG>
Can you tell me why? More importantly, can you tell me how to fix it?
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Well, the Netware for Linux requires a kernel with
STREAMS and IPX patches built into it.
</BLOCKQUOTE>
<BLOCKQUOTE>
STREAMS is an alternative to BSD sockets. It's a
programming model for communications within a Unix or
other kernel --- between the applications interfaces
and the devices. The Linux kernel core team has soundly
reject suggestions that Linux adopt a STREAMS networking
model for its native internal interfaces and we won't
go into their reasoning here. (I'm inclined to agree with
them on this issue in any event.)
</BLOCKQUOTE>
<BLOCKQUOTE>
So, this error suggests that the 'ln' command (creates
hard and symbolic links) can't find the '<TT>/boot/vmlinuz...</TT>'
files to which it refers.
</BLOCKQUOTE>
<BLOCKQUOTE>
One trick to try is to view the contents of the rpm
file using 'mc' (Midnight Commander). Just bring up
'mc', select the RPM file with your cursor keys and
highlight bar, and hit [Enter]. That will treat the
RPM file as a "virtual directory" and allow you to
view and manually extract the contents. Look in
RPM:/boot for the kernel file --- also look for the
README files.
</BLOCKQUOTE>
<BLOCKQUOTE>
I've occasionally manually extracted the files from
an RPM and just put them in place myself. Then I read
through any scripts that and docs contained therein
to see what <EM>should have been done</EM> by the rpm system.
(Usually this sort of dodge is only necessary when
doing piecemeal upgrades to the rpm package itself).
</BLOCKQUOTE>
<BLOCKQUOTE>
There are other times when I have to resort to
'rpm -i --force --nodeps ...' to get things to work.
</BLOCKQUOTE>
<BLOCKQUOTE>
Note that this kernel may not support you hardware
configuration (that's one reason why many Linux users
build custom kernels). So you may have to find and
install the kernel source patches and build your own
--- or at least build a set of modules that match
that version.
</BLOCKQUOTE>
<BLOCKQUOTE>
Probably your best bet would be to subscribe to the
caldera-netware mailing list. Look to Liszt to
help find specific mailing lists and newsgroups:
</BLOCKQUOTE>
<blockquote><pre> Liszt: caldera-netware
http://www.liszt.com/cgi-bin\
/start.lcgi?list=caldera-netware&server=majordomo@rim.caldera.com
</pre></blockquote>
<!-- end 35.20 -->
<hr width="40%" align="center">
<H3 align="left"><img src="../../gx/dennis/qbubble.gif" height="50" width="60"
alt="(?) " border="0">No STREAMS Error while Installing Netware for Linux</H3>
<p><strong>From Sean McMurray on Wed, 18 Nov 1998
</strong></p>
<!-- begin 35.25 -->
<P><STRONG>
Jim Dennis wrote:
</STRONG></P>
<P><STRONG><FONT COLOR="#000099"><EM>
<BR>>When I type in rpm -i kernel-2_0_35-1nw_i386.rpm, I get the
<BR>>following error:
<BR>>ln: boot/vmlinuz-2.0.35-1nw-streams: No such file or directory
<BR>>Can you tell me why? More importantly, can you tell me how to fix it?
</EM></FONT></STRONG></P>
<P><STRONG><FONT COLOR="#000066"><EM>
Well, the Netware for Linux requires a kernel with
STREAMS and IPX patches built into it.
</EM></FONT></STRONG></P>
<P><STRONG>
Shouldn't it be included in <A HREF="http://www.caldera.com/">Caldera</A>'s RPMs then. It seems that the first they
their install does is try to build a new kernel.Also, does the fact that
ncpfs is built in indicate that the STREAMS and IPX patches already exist -
the IPX patches, anyway?<clipped>
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
It is. That's what that kernel is saying.
However it seems that the <TT>/boot</TT> directory isn't there
(my to 'mkdir' that) and, for some reason, your 'rpm'
command isn't or can't make it. (If you do have a
<TT>/boot</TT> directory --- maybe you've used 'chattr +i' to
make it immutable. Maybe you have a file named <TT>/boot</TT>
so that a directory can't be made by that name. Who
knows?).
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Midnight Commander won't open the RPMs on my system, but I
executed rpm -qpl kernel-2_0_35-1nw_i386.rpm > dump.txt
to get a listing. The <TT>/boot</TT> files are:
/boot/WHATSIN-2.0.35-1nw
/boot/vmlinuz-2.0.35-1nw
</STRONG></P>
<P><STRONG>
The only files with the word stream in the title is
/lib/modules/2.0.35-1nw/misc/streams.o
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
... that would be the STREAMS loadable kernel module.
The other support and IPX patches are compiled into that
kernel, and the FAQ tells you how to build a kernel to match
the shipping one (close enough to load the requisite modules
and route/utilize the IPX protocols anyway).
</BLOCKQUOTE>
<P><STRONG><FONT COLOR="#000066"><EM><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
There are other times when I have to resort to
'rpm -i --force --nodeps ...' to get things to work.
</EM></FONT></STRONG></P>
<P><STRONG>
I tried to rpm -e kernel-2_0_35-1nw_i386.rpm, but rpm says that it
isn't installed.
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
That tries to "erase" (uninstall) that package --- except
that you have to use the package's name not the package
*file's* name. kernel-2.0.35-1nw is probably the package
name. The filename is independent of that, though it
is conventionally similar.
</BLOCKQUOTE>
<BLOCKQUOTE>
You can use the 'rpm -qpi' command to extract information
about the RPM file including the package name.
</BLOCKQUOTE>
<BLOCKQUOTE>
In general the -i and -p options to 'rpm' refer to
<EM>file</EM> while others refer to "packages."
</BLOCKQUOTE>
<BLOCKQUOTE>
If you issued the command 'rpm -ql foo-1.2.3-bang'
RPM would list all of the files that are "owned by" the
foo-1.2.3-bang package. If you issue the command
'rpm -qpl foo-1.2.3-bang.i386.rpm' then the command would
list all of the file in that package <EM>file</EM>. If (by some
chance) you had a different implementation of the same
package these two lists might differ.
</BLOCKQUOTE>
<BLOCKQUOTE>
(That's a minor problem with the RPM system --- there's no
central naming authority on package naming and versioning so
you can have differences between, for example, the
<A HREF="http://www.suse.com/">S.u.S.E.</A> and <A HREF="http://www.redhat.com/">Red Hat</A> packages, with some differences in
dependencies --- etc. Actually it's a rather major pain in
the patootie when you're a S.u.S.E. user and you keep
getting packages that are contributed to the Red Hat site.
However, it's still usually easier than building them from
tarballs and the "right" answer for me is probably for me to
learn enough about <EM>building</EM> my own RPM's that I can grap
the source RPM packages and modify them to fit. The "right"
answer for Red Hat and S.u.S.E. and Caldera is to make their
packages as compatable with one another as possible ---
particularly with regards to dependences and provision
identification).
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
So I tried to rpm -e kernel-2_0_35-1nw_i386.rpm again, but rpm says it's
already installed
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
That sounds wrong. Are you sure you typed exactly that?
</BLOCKQUOTE>
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
I don't know rpm (or Linux) well enough to trust not hosing my
kernel. I guess it's not that big of deal. I can just re-install
RH5.1 from scratch.
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
After awhile building and installing new kernels will seem
as routine and editing an old DOS CONFIG.SYS file (though
you probably won't do anywhere near as often.
</BLOCKQUOTE>
<P><STRONG><FONT COLOR="#000066"><EM><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
Probably your best bet would be to subscribe to the
caldera-netware mailing list.
</EM></FONT></STRONG></P>
<P><STRONG>
I'm subscribed, but impatient.
Thank you for your help.
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
HEIGHT="28" WIDTH="50" BORDER="0"
>
I'd manually extract the kernel file from that RPM
file, put it in the <TT>/boot/</TT> directory, edit your
<TT>/etc/lilo.conf</TT> file, run the <TT>/sbin/lilo</TT> command and
try to reboot. Search through the old back issues
of LG to read many messages about how LILO works --
or just read the HOWTO at:
</BLOCKQUOTE>
<BLOCKQUOTE>
<A HREF="http://www.ssc.com/linux/LDP/HOWTO/mini/LILO.html">http://www.ssc.com/linux/LDP/HOWTO/mini/LILO.html</A>
</BLOCKQUOTE>
<BLOCKQUOTE>
(... and other LDP mirrors all over).
</BLOCKQUOTE>
<BLOCKQUOTE>
Naturally you'll want to leave an entry for your existing
(working) kernel so that you can reboot into that if this
Caldera supplied kernel is inappropriate for your system.
You'll also want to prepare a boot/root (rescue) diskette.
Although one (image) comes with each Red Hat distribution
I personally prefer Tom Oehser's "rtbt" (a full mini
distribution on a single floppy --- with a suite of Unix
tools sufficient to do most networking and rescue
operations). You can find that at:
</BLOCKQUOTE>
<BLOCKQUOTE>
<A HREF="http://www.toms.net/rb">http://www.toms.net/rb</A>
</BLOCKQUOTE>
<!-- end 35.25 -->
<!--startcut ======================================================= -->
<P> <hr> <P>
<H5 align="center"><a href="http://www.linuxgazette.com/ssc.copying.html"
>Copyright ©</a> 1999, James T. Dennis
<BR>Published in <I>The Linux Gazette</I> Issue 36 January 1999</H5>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<P align="center">
<table width="98%"><tr valign="center" align="center">
<td rowspan="3" colspan="6"><A HREF="../lg_answer36.html"><IMG
SRC="../../gx/dennis/answernew.gif"
ALT="[ Answer Guy Index ]"></A></td>
<TD><A HREF="./a.html">a</A></TD>
<TD><A HREF="./b.html">b</A></TD>
<TD><A HREF="./c.html">c</A></TD>
<TD><A HREF="./1.html">1</A></TD>
<TD><A HREF="./2.html">2</A></TD>
<TD><A HREF="./3.html">3</A></TD>
<TD><A HREF="./4.html">4</A></TD>
<TD><A HREF="./5.html">5</A></TD>
<TD><A HREF="./6.html">6</A></TD>
<TD><A HREF="./7.html">7</A></TD>
<TD><A HREF="./9.html">9</A></TD>
<TD><A HREF="./10.html">10</A></TD>
<TD><A HREF="./11.html">11</A></TD>
<TD><A HREF="./12.html">12</A></TD>
</tr><tr valign="center" align="center">
<TD><A HREF="./15.html">15</A></TD>
<TD><A HREF="./16.html">16</A></TD>
<TD><A HREF="./18.html">18</A></TD>
<TD><A HREF="./19.html">19</A></TD>
<TD><A HREF="./20.html">20</A></TD>
<TD><A HREF="./21.html">21</A></TD>
<TD><A HREF="./22.html">22</A></TD>
<TD><A HREF="./23.html">23</A></TD>
<TD><A HREF="./24.html">24</A></TD>
<TD><A HREF="./25.html">25</A></TD>
<TD><A HREF="./26.html">26</A></TD>
<TD><A HREF="./27.html">27</A></TD>
<TD><A HREF="./28.html">28</A></TD>
</tr><tr valign="center" align="center">
<TD><A HREF="./29.html">29</A></TD>
<TD><A HREF="./31.html">31</A></TD>
<TD><A HREF="./32.html">32</A></TD>
<TD><A HREF="./33.html">33</A></TD>
<TD><A HREF="./34.html">34</A></TD>
<TD><A HREF="./35.html">35</A></TD>
<TD><A HREF="./36.html">36</A></TD>
<TD><A HREF="./37.html">37</A></TD>
<TD><A HREF="./38.html">38</A></TD>
<TD><A HREF="./39.html">39</A></TD>
<TD><A HREF="./40.html">40</A></TD>
<TD><A HREF="./41.html">41</A></TD>
<TD><A HREF="./42.html">42</A></TD>
<TD><A HREF="./44.html">44</A></TD>
</tr><tr valign="center" align="center">
<TD><A HREF="./45.html">45</A></TD>
<TD><A HREF="./46.html">46</A></TD>
<TD><A HREF="./47.html">47</A></TD>
<TD><A HREF="./48.html">48</A></TD>
<TD><A HREF="./49.html">49</A></TD>
<TD><A HREF="./50.html">50</A></TD>
<TD><A HREF="./51.html">51</A></TD>
<TD><A HREF="./52.html">52</A></TD>
<TD><A HREF="./53.html">53</A></TD>
<TD><A HREF="./54.html">54</A></TD>
<TD><A HREF="./55.html">55</A></TD>
<TD><A HREF="./56.html">56</A></TD>
<TD><A HREF="./57.html">57</A></TD>
<TD><A HREF="./60.html">60</A></TD>
<TD><A HREF="./61.html">61</A></TD>
<TD><A HREF="./62.html">62</A></TD>
<TD><A HREF="./63.html">63</A></TD>
<TD><A HREF="./64.html">64</A></TD>
<TD><A HREF="./65.html">65</A></TD>
<TD><A HREF="./66.html">66</A></TD>
</tr><tr valign="center" align="center">
<TD><A HREF="./67.html">67</A></TD>
<TD><A HREF="./69.html">69</A></TD>
<TD><A HREF="./72.html">72</A></TD>
<TD><A HREF="./76.html">76</A></TD>
<TD><A HREF="./77.html">77</A></TD>
<TD><A HREF="./78.html">78</A></TD>
<TD><A HREF="./79.html">79</A></TD>
<TD><A HREF="./80.html">80</A></TD>
<TD><A HREF="./81.html">81</A></TD>
<TD><A HREF="./82.html">82</A></TD>
<TD><A HREF="./84.html">84</A></TD>
<TD><A HREF="./85.html">85</A></TD>
<TD><A HREF="./86.html">86</A></TD>
<TD><A HREF="./87.html">87</A></TD>
<TD><A HREF="./91.html">91</A></TD>
<TD><A HREF="./94.html">94</A></TD>
<TD><A HREF="./95.html">95</A></TD>
<TD><A HREF="./96.html">96</A></TD>
<TD><A HREF="./97.html">97</A></TD>
<TD><A HREF="./98.html">98</A></TD>
</tr></table>
</P>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<A HREF="../lg_toc36.html"
><IMG SRC="../../gx/indexnew.gif" ALT="[ Table Of Contents ]"></A>
<A HREF="../../index.html"
><IMG SRC="../../gx/homenew.gif" ALT="[ Front Page ]"></A>
<A HREF="../lg_bytes36.html"
><IMG SRC="../../gx/back2.gif" ALT="[ Previous Section ]"></A>
<A HREF="../larriera.html"
><IMG SRC="../../gx/fwd.gif" ALT="[ Next Section ]"></A>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
</BODY></HTML>
<!--endcut ========================================================= -->
|
