Linux-Misc Digest #751, Volume #27 Mon, 30 Apr 01 10:13:01 EDT
Contents:
Re: dd if=/dev/zero of=/dev/hda (Villy Kruse)
Re: Problem linking ("Jay")
Re: What recent distributions for an old 486? (SammyTheSnake)
Re: dd if=/dev/zero of=/dev/hda (SammyTheSnake)
Re: wu-ftpd login delay, telnet okay. ("Peter T. Breuer")
linuxconf 7.1 ("MrEye")
Re: wu-ftpd login delay, telnet okay. ("Peter T. Breuer")
Re: SV: Expanding full partitions (Dave Brown)
Re: Linux vs Microsoft ("bowman")
Re: linuxconf 7.1 (Guy Forssman)
Re: linuxconf 7.1 (Guy Forssman)
Re: dd if=/dev/zero of=/dev/hda (Dances With Crows)
Re: dd if=/dev/zero of=/dev/hda ("Peter T. Breuer")
Re: How Do Modules Work? (Dave Brown)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: dd if=/dev/zero of=/dev/hda
Date: 30 Apr 2001 13:18:35 GMT
On Mon, 30 Apr 2001 07:15:40 GMT, David <[EMAIL PROTECTED]> wrote:
>Neil Zanella wrote:
>>
>> Hello,
>>
>> I am trying to zero my entire hard drive including the master boot record.
>> I have issued the command dd if=/dev/zero of=/dev/hda and several variants
>> of it with bs and count options but each time I do this it takes forever.
>> The hard drive is not even 10GB and the system is only two years old or
>> so but after two hours dd was still running.
>>
>> Any ideas of how I can speed up the process? The worst thing about dd is
>> that it displays no output as it runs. For instance it would be nice
>> if it could display a message for each MB it copied or for each 10MB
>> it copied or something like that.
>>
>> Thanks,
>>
>> Neil
>
>
>!!!!WARNING!!!!
>THIS WILL DELETE ALL PARTITIONS AND
>WIPE THE DRIVE CLEAN!!!!
>
>!!!!YOU HAVE BEEN WARNED!!!!
>
>To remove all partitions and wipe the drive clean.
>
>cat /dev/zero >/dev/hdX
>
That would take for ever as well. It just takes that long to write 10
gigabyte to a disk.
Villy
------------------------------
From: "Jay" <[EMAIL PROTECTED]>
Subject: Re: Problem linking
Date: Mon, 30 Apr 2001 13:24:43 GMT
Get a reply? Looks to me like you're missing some source and object from
the Libraries. Try to locate a few of the failed .so or .o components.
Download and install the latest X11 and Glibc libraries.
"Jose Antonio Cortijo Solera" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi everybody,
> trying to compile a program written en C, I receive this message and I
> don't know what the hell I can do, please, HELP!
> Don't worry, is like this because of I put the linker verbose to try to
> find something wrong ;)
> If someone want I can send him the source code and he can try to compile
> it by himself, it's around 800 Kb.
> Thank you very much.
> //Jose
>
> P.S: I am using Mandrake 8.0
>
> GNU ld version 2.10.91 (with BFD 2.10.1.0.2)
> Supported emulations:
> elf_i386
> i386linux
> using internal linker script:
> ==================================================
> OUTPUT_FORMAT("elf32-i386", "elf32-i386",
> "elf32-i386")
> OUTPUT_ARCH(i386)
> ENTRY(_start)
> SEARCH_DIR(/lib); SEARCH_DIR(/usr/lib); SEARCH_DIR(/usr/local/lib);
> SEARCH_DIR(/usr/i586-mandrake-linux/lib);
> /* Do we need any of these for elf?
> __DYNAMIC = 0; */
> SECTIONS
> {
> /* Read-only sections, merged into text segment: */
> . = 0x08048000 + SIZEOF_HEADERS;
> .interp : { *(.interp) }
> .hash : { *(.hash) }
> .dynsym : { *(.dynsym) }
> .dynstr : { *(.dynstr) }
> .gnu.version : { *(.gnu.version) }
> .gnu.version_d : { *(.gnu.version_d) }
> .gnu.version_r : { *(.gnu.version_r) }
> .rel.init : { *(.rel.init) }
> .rela.init : { *(.rela.init) }
> .rel.text :
> {
> *(.rel.text)
> *(.rel.text.*)
> *(.rel.gnu.linkonce.t.*)
> }
> .rela.text :
> {
> *(.rela.text)
> *(.rela.text.*)
> *(.rela.gnu.linkonce.t.*)
> }
> .rel.fini : { *(.rel.fini) }
> .rela.fini : { *(.rela.fini) }
> .rel.rodata :
> {
> *(.rel.rodata)
> *(.rel.rodata.*)
> *(.rel.gnu.linkonce.r.*)
> }
> .rela.rodata :
> {
> *(.rela.rodata)
> *(.rela.rodata.*)
> *(.rela.gnu.linkonce.r.*)
> }
> .rel.data :
> {
> *(.rel.data)
> *(.rel.data.*)
> *(.rel.gnu.linkonce.d.*)
> }
> .rela.data :
> {
> *(.rela.data)
> *(.rela.data.*)
> *(.rela.gnu.linkonce.d.*)
> }
> .rel.ctors : { *(.rel.ctors) }
> .rela.ctors : { *(.rela.ctors) }
> .rel.dtors : { *(.rel.dtors) }
> .rela.dtors : { *(.rela.dtors) }
> .rel.got : { *(.rel.got) }
> .rela.got : { *(.rela.got) }
> .rel.sdata :
> {
> *(.rel.sdata)
> *(.rel.sdata.*)
> *(.rel.gnu.linkonce.s.*)
> }
> .rela.sdata :
> {
> *(.rela.sdata)
> *(.rela.sdata.*)
> *(.rela.gnu.linkonce.s.*)
> }
> .rel.sbss :
> {
> *(.rel.sbss)
> *(.rel.sbss.*)
> *(.rel.gnu.linkonce.sb.*)
> }
> .rela.sbss :
> {
> *(.rela.sbss)
> *(.rela.sbss.*)
> *(.rel.gnu.linkonce.sb.*)
> }
> .rel.sdata2 :
> {
> *(.rel.sdata2)
> *(.rel.sdata2.*)
> *(.rel.gnu.linkonce.s2.*)
> }
> .rela.sdata2 :
> {
> *(.rela.sdata2)
> *(.rela.sdata2.*)
> *(.rela.gnu.linkonce.s2.*)
> }
> .rel.sbss2 :
> {
> *(.rel.sbss2)
> *(.rel.sbss2.*)
> *(.rel.gnu.linkonce.sb2.*)
> }
> .rela.sbss2 :
> {
> *(.rela.sbss2)
> *(.rela.sbss2.*)
> *(.rela.gnu.linkonce.sb2.*)
> }
> .rel.bss :
> {
> *(.rel.bss)
> *(.rel.bss.*)
> *(.rel.gnu.linkonce.b.*)
> }
> .rela.bss :
> {
> *(.rela.bss)
> *(.rela.bss.*)
> *(.rela.gnu.linkonce.b.*)
> }
> .rel.plt : { *(.rel.plt) }
> .rela.plt : { *(.rela.plt) }
> .init :
> {
> KEEP (*(.init))
> } =0x9090
> .plt : { *(.plt) }
> .text :
> {
> *(.text)
> *(.text.*)
> *(.stub)
> /* .gnu.warning sections are handled specially by elf32.em. */
> *(.gnu.warning)
> *(.gnu.linkonce.t.*)
> } =0x9090
> .fini :
> {
> KEEP (*(.fini))
> } =0x9090
> PROVIDE (__etext = .);
> PROVIDE (_etext = .);
> PROVIDE (etext = .);
> .rodata : { *(.rodata) *(.rodata.*) *(.gnu.linkonce.r.*) }
> .rodata1 : { *(.rodata1) }
> .sdata2 : { *(.sdata2) *(.sdata2.*) *(.gnu.linkonce.s2.*) }
> .sbss2 : { *(.sbss2) *(.sbss2.*) *(.gnu.linkonce.sb2.*) }
> /* Adjust the address for the data segment. We want to adjust up to
> the same address within the page on the next page up. */
> . = ALIGN(0x1000) + (. & (0x1000 - 1));
> .data :
> {
> *(.data)
> *(.data.*)
> *(.gnu.linkonce.d.*)
> SORT(CONSTRUCTORS)
> }
> .data1 : { *(.data1) }
> .eh_frame : { KEEP (*(.eh_frame)) }
> .gcc_except_table : { *(.gcc_except_table) }
> .ctors :
> {
> /* gcc uses crtbegin.o to find the start of
> the constructors, so we make sure it is
> first. Because this is a wildcard, it
> doesn't matter if the user does not
> actually link against crtbegin.o; the
> linker won't look for a file to match a
> wildcard. The wildcard also means that it
> doesn't matter which directory crtbegin.o
> is in. */
> KEEP (*crtbegin.o(.ctors))
> /* We don't want to include the .ctor section from
> from the crtend.o file until after the sorted ctors.
> The .ctor section from the crtend file contains the
> end of ctors marker and it must be last */
> KEEP (*(EXCLUDE_FILE (*crtend.o ) .ctors))
> KEEP (*(SORT(.ctors.*)))
> KEEP (*(.ctors))
> }
> .dtors :
> {
> KEEP (*crtbegin.o(.dtors))
> KEEP (*(EXCLUDE_FILE (*crtend.o ) .dtors))
> KEEP (*(SORT(.dtors.*)))
> KEEP (*(.dtors))
> }
> .got : { *(.got.plt) *(.got) }
> .dynamic : { *(.dynamic) }
> /* We want the small data sections together, so single-instruction
> offsets
> can access them all, and initialized data all before uninitialized,
> so
> we can shorten the on-disk segment size. */
> .sdata :
> {
> *(.sdata)
> *(.sdata.*)
> *(.gnu.linkonce.s.*)
> }
> _edata = .;
> PROVIDE (edata = .);
> __bss_start = .;
> .sbss :
> {
> PROVIDE (__sbss_start = .);
> PROVIDE (___sbss_start = .);
> *(.dynsbss)
> *(.sbss)
> *(.sbss.*)
> *(.gnu.linkonce.sb.*)
> *(.scommon)
> PROVIDE (__sbss_end = .);
> PROVIDE (___sbss_end = .);
> }
> .bss :
> {
> *(.dynbss)
> *(.bss)
> *(.bss.*)
> *(.gnu.linkonce.b.*)
> *(COMMON)
> /* Align here to ensure that the .bss section occupies space up to
> _end. Align after .bss to ensure correct alignment even if the
> .bss section disappears because there are no input sections. */
> . = ALIGN(32 / 8);
> }
> . = ALIGN(32 / 8);
> _end = .;
> PROVIDE (end = .);
> /* Stabs debugging sections. */
> .stab 0 : { *(.stab) }
> .stabstr 0 : { *(.stabstr) }
> .stab.excl 0 : { *(.stab.excl) }
> .stab.exclstr 0 : { *(.stab.exclstr) }
> .stab.index 0 : { *(.stab.index) }
> .stab.indexstr 0 : { *(.stab.indexstr) }
> .comment 0 : { *(.comment) }
> /* DWARF debug sections.
> Symbols in the DWARF debugging sections are relative to the
> beginning
> of the section so we begin them at 0. */
> /* DWARF 1 */
> .debug 0 : { *(.debug) }
> .line 0 : { *(.line) }
> /* GNU DWARF 1 extensions */
> .debug_srcinfo 0 : { *(.debug_srcinfo) }
> .debug_sfnames 0 : { *(.debug_sfnames) }
> /* DWARF 1.1 and DWARF 2 */
> .debug_aranges 0 : { *(.debug_aranges) }
> .debug_pubnames 0 : { *(.debug_pubnames) }
> /* DWARF 2 */
> .debug_info 0 : { *(.debug_info) *(.gnu.linkonce.wi.*) }
> .debug_abbrev 0 : { *(.debug_abbrev) }
> .debug_line 0 : { *(.debug_line) }
> .debug_frame 0 : { *(.debug_frame) }
> .debug_str 0 : { *(.debug_str) }
> .debug_loc 0 : { *(.debug_loc) }
> .debug_macinfo 0 : { *(.debug_macinfo) }
> /* SGI/MIPS DWARF 2 extensions */
> .debug_weaknames 0 : { *(.debug_weaknames) }
> .debug_funcnames 0 : { *(.debug_funcnames) }
> .debug_typenames 0 : { *(.debug_typenames) }
> .debug_varnames 0 : { *(.debug_varnames) }
> /* These must appear regardless of . */
> }
>
>
> ==================================================
> attempt to open
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crt1.o succeeded
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crt1.o
> attempt to open
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crti.o succeeded
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crti.o
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/crtbegin.o
> succeeded
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/crtbegin.o
> attempt to open csim.o succeeded
> csim.o
> attempt to open gui.o succeeded
> gui.o
> attempt to open /usr/lib/libgtk.so succeeded
> -lgtk (/usr/lib/libgtk.so)
> attempt to open /usr/lib/libgdk.so succeeded
> -lgdk (/usr/lib/libgdk.so)
> attempt to open /usr/lib/libgmodule.so succeeded
> -lgmodule (/usr/lib/libgmodule.so)
> attempt to open /usr/lib/libglib.so succeeded
> -lglib (/usr/lib/libglib.so)
> attempt to open /usr/lib/libdl.so succeeded
> -ldl (/usr/lib/libdl.so)
> attempt to open /usr/lib/libXi.so failed
> attempt to open /usr/lib/libXi.a failed
> attempt to open ./trivialgfx/lib/libXi.so failed
> attempt to open ./trivialgfx/lib/libXi.a failed
> attempt to open ./lib/libXi.so failed
> attempt to open ./lib/libXi.a failed
> attempt to open /usr/lib/libXi.so failed
> attempt to open /usr/lib/libXi.a failed
> attempt to open /usr/X11R6/lib/libXi.so succeeded
> -lXi (/usr/X11R6/lib/libXi.so)
> attempt to open /usr/lib/libXext.so failed
> attempt to open /usr/lib/libXext.a failed
> attempt to open ./trivialgfx/lib/libXext.so failed
> attempt to open ./trivialgfx/lib/libXext.a failed
> attempt to open ./lib/libXext.so failed
> attempt to open ./lib/libXext.a failed
> attempt to open /usr/lib/libXext.so failed
> attempt to open /usr/lib/libXext.a failed
> attempt to open /usr/X11R6/lib/libXext.so succeeded
> -lXext (/usr/X11R6/lib/libXext.so)
> attempt to open /usr/lib/libX11.so failed
> attempt to open /usr/lib/libX11.a failed
> attempt to open ./trivialgfx/lib/libX11.so failed
> attempt to open ./trivialgfx/lib/libX11.a failed
> attempt to open ./lib/libX11.so failed
> attempt to open ./lib/libX11.a failed
> attempt to open /usr/lib/libX11.so failed
> attempt to open /usr/lib/libX11.a failed
> attempt to open /usr/X11R6/lib/libX11.so succeeded
> -lX11 (/usr/X11R6/lib/libX11.so)
> attempt to open /usr/lib/libX11.so failed
> attempt to open /usr/lib/libX11.a failed
> attempt to open ./trivialgfx/lib/libX11.so failed
> attempt to open ./trivialgfx/lib/libX11.a failed
> attempt to open ./lib/libX11.so failed
> attempt to open ./lib/libX11.a failed
> attempt to open /usr/lib/libX11.so failed
> attempt to open /usr/lib/libX11.a failed
> attempt to open /usr/X11R6/lib/libX11.so succeeded
> -lX11 (/usr/X11R6/lib/libX11.so)
> attempt to open /usr/lib/libtgi.so failed
> attempt to open /usr/lib/libtgi.a failed
> attempt to open ./trivialgfx/lib/libtgi.so failed
> attempt to open ./trivialgfx/lib/libtgi.a succeeded
> (./trivialgfx/lib/libtgi.a)tgiCreate.o
> (./trivialgfx/lib/libtgi.a)tgiSetCurrent.o
> (./trivialgfx/lib/libtgi.a)tgiSetColour.o
> (./trivialgfx/lib/libtgi.a)tgiPrimitives.o
> (./trivialgfx/lib/libtgi.a)tgiDelete.o
> (./trivialgfx/lib/libtgi.a)tgiShow.o
> attempt to open /usr/lib/libsimg.so failed
> attempt to open /usr/lib/libsimg.a failed
> attempt to open ./trivialgfx/lib/libsimg.so failed
> attempt to open ./trivialgfx/lib/libsimg.a failed
> attempt to open ./lib/libsimg.so failed
> attempt to open ./lib/libsimg.a succeeded
> (./lib/libsimg.a)environg.o
> (./lib/libsimg.a)robotg.o
> (./lib/libsimg.a)geom.o
> (./lib/libsimg.a)param.o
> (./lib/libsimg.a)light.o
> (./lib/libsimg.a)wall.o
> (./lib/libsimg.a)sobst.o
> (./lib/libsimg.a)obst.o
> (./lib/libsimg.a)motor.o
> (./lib/libsimg.a)zone.o
> (./lib/libsimg.a)gripperrobot.o
> (./lib/libsimg.a)aravq.o
> (./lib/libsimg.a)vectorlist.o
> (./lib/libsimg.a)vector.o
> attempt to open /usr/lib/libpthread.so succeeded
> -lpthread (/usr/lib/libpthread.so)
> attempt to open /usr/lib/libdl.so succeeded
> -ldl (/usr/lib/libdl.so)
> attempt to open /usr/lib/libstdc++.so failed
> attempt to open /usr/lib/libstdc++.a failed
> attempt to open ./trivialgfx/lib/libstdc++.so failed
> attempt to open ./trivialgfx/lib/libstdc++.a failed
> attempt to open ./lib/libstdc++.so failed
> attempt to open ./lib/libstdc++.a failed
> attempt to open /usr/lib/libstdc++.so failed
> attempt to open /usr/lib/libstdc++.a failed
> attempt to open /usr/X11R6/lib/libstdc++.so failed
> attempt to open /usr/X11R6/lib/libstdc++.a failed
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/libstdc++.so
> succeeded
> -lstdc++ (/usr/lib/gcc-lib/i586-mandrake-linux/2.96/libstdc++.so)
> attempt to open /usr/lib/libm.so succeeded
> -lm (/usr/lib/libm.so)
> attempt to open /usr/lib/libgcc.so failed
> attempt to open /usr/lib/libgcc.a failed
> attempt to open ./trivialgfx/lib/libgcc.so failed
> attempt to open ./trivialgfx/lib/libgcc.a failed
> attempt to open ./lib/libgcc.so failed
> attempt to open ./lib/libgcc.a failed
> attempt to open /usr/lib/libgcc.so failed
> attempt to open /usr/lib/libgcc.a failed
> attempt to open /usr/X11R6/lib/libgcc.so failed
> attempt to open /usr/X11R6/lib/libgcc.a failed
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/libgcc.so
> failed
> attempt to open /usr/l/usr/bin/ld: final link failed: Bad value
> ib/gcc-lib/i586-mandrake-linux/2.96/libgcc.a succeeded
> attempt to open /usr/lib/libc.so succeeded
> opened script file /usr/lib/libc.so
> attempt to open /lib/libc.so.6 succeeded
> /lib/libc.so.6
> attempt to open /usr/lib/libc_nonshared.a succeeded
> attempt to open /usr/lib/libgcc.so failed
> attempt to open /usr/lib/libgcc.a failed
> attempt to open ./trivialgfx/lib/libgcc.so failed
> attempt to open ./trivialgfx/lib/libgcc.a failed
> attempt to open ./lib/libgcc.so failed
> attempt to open ./lib/libgcc.a failed
> attempt to open /usr/lib/libgcc.so failed
> attempt to open /usr/lib/libgcc.a failed
> attempt to open /usr/X11R6/lib/libgcc.so failed
> attempt to open /usr/X11R6/lib/libgcc.a failed
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/libgcc.so
> failed
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/libgcc.a
> succeeded
> attempt to open /usr/lib/gcc-lib/i586-mandrake-linux/2.96/crtend.o
> succeeded
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/crtend.o
> attempt to open
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crtn.o succeeded
> /usr/lib/gcc-lib/i586-mandrake-linux/2.96/../../../crtn.o
> ld-linux.so.2 needed by /lib/libc.so.6
> found ld-linux.so.2 at /lib/ld-linux.so.2
> collect2: ld returned 1 exit status
> make: *** [csim] Error 1
------------------------------
From: [EMAIL PROTECTED] (SammyTheSnake)
Subject: Re: What recent distributions for an old 486?
Date: Mon, 30 Apr 2001 14:20:35 +0100
In article <9cgjd5$krl$[EMAIL PROTECTED]>, Fabrizio wrote:
>What recent distributions for an old 486 ?
>I want to revamp the old stuff still around...
I echo what one poster said about debian. I've used it on _really_
underpowered systems w/o problems. for example, I had a 386/25 laptop with a
112MB HDD which worked admirably (though a _little_ tight!) until the
hardware died :(
HTH
Cheers & God bless
SammyTheSnake
--
Sam.Penny @ Ntlworld.com | Looking for a computer related
Linux, Hardware & Juggling specialist :-) | job, if you can help, e-mail me :)
Wheels: bike, 'ickle bike, and unicycle. | /o \/ Working on 5 ball 1/2 shower
Boxen: K6-266@300, dual Celery500 & Nx486 | \__/\ & some 6 / 7 ball exercises
------------------------------
From: [EMAIL PROTECTED] (SammyTheSnake)
Subject: Re: dd if=/dev/zero of=/dev/hda
Date: Mon, 30 Apr 2001 14:18:23 +0100
In article <[EMAIL PROTECTED]>, David wrote:
>Neil Zanella wrote:
>>
>> Hello,
>>
>> I am trying to zero my entire hard drive including the master boot record.
>> I have issued the command dd if=/dev/zero of=/dev/hda and several variants
>> of it with bs and count options but each time I do this it takes forever.
>> The hard drive is not even 10GB and the system is only two years old or
>> so but after two hours dd was still running.
>>
>> Any ideas of how I can speed up the process? The worst thing about dd is
>> that it displays no output as it runs. For instance it would be nice
>> if it could display a message for each MB it copied or for each 10MB
>> it copied or something like that.
>>
>> Thanks,
>>
>> Neil
>
>
>!!!!WARNING!!!!
>THIS WILL DELETE ALL PARTITIONS AND
>WIPE THE DRIVE CLEAN!!!!
>
>!!!!YOU HAVE BEEN WARNED!!!!
>
>To remove all partitions and wipe the drive clean.
>
>cat /dev/zero >/dev/hdX
you may want to do something like
dd if=/dev/zero of=/dev/hda bs=1M
so that the system can do burst=mode transfers and stuff to the HDD.
incidentally, why do you want to do this? there might be a more efficient
way to do that...
Cheers & God bless
SammyTheSnake
--
Sam.Penny @ Ntlworld.com | Looking for a computer related
Linux, Hardware & Juggling specialist :-) | job, if you can help, e-mail me :)
Wheels: bike, 'ickle bike, and unicycle. | /o \/ Working on 5 ball 1/2 shower
Boxen: K6-266@300, dual Celery500 & Nx486 | \__/\ & some 6 / 7 ball exercises
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: wu-ftpd login delay, telnet okay.
Date: Mon, 30 Apr 2001 15:19:44 +0200
[EMAIL PROTECTED] wrote:
> When I ftp into my Redhat 7.0 box, running wu-ftpd 2.6.1, I experience a
> 30 second delay before seeing the login prompt. I have read numerous
> posts in the various comp.os.linux newsgroups, and it seems this problem
> is often caused by reverse DNS lookup failures. I beleive this is NOT
> the case on my machine.
Well, tell us the IP and we'll check! All we have to do is an nslookup
of your IP on your dns server (and you should do the same).
Peter
------------------------------
From: "MrEye" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,linux.redhat.misc
Subject: linuxconf 7.1
Date: Mon, 30 Apr 2001 09:21:03 -0400
I just installed rh7.1. the last rh distribution I used was rh6.2. What
happened to 'linuxconf'. I need it to modify the users. Does rh7.1 have a
different configuration tool?
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: wu-ftpd login delay, telnet okay.
Date: Mon, 30 Apr 2001 13:29:19 GMT
eric <[EMAIL PROTECTED]> wrote:
> I'd dump wu-ftpd and go with something else like proftpd or sftp (from
> openssh) (not that this would change the issue your having, but it would
> probably increase the security of your box)
I'm not convinced by this argument. Not that I'm saying that it's not
correct! Just that it's not absolutely convincing. I personally prefer
wu-ftp because at least I know it has no known bugs - it has all the
beta testers in the world testing it. But that's not enough! And
a better illustration of why testing is inadequate as a software
quality assessment procedure I never have seen.
Peter
------------------------------
From: [EMAIL PROTECTED] (Dave Brown)
Subject: Re: SV: Expanding full partitions
Reply-To: [EMAIL PROTECTED]
Date: 30 Apr 2001 08:52:39 -0500
In article <9c9ck1$8ht$[EMAIL PROTECTED]>,
Mikael \"Elvis\" Ahlgren wrote:
>I was thinking it would be possible to expand var on the current disk. I am
>not used to Linux but I have been using AIX a bit and there it's possible to
>expand partitions as long as there is space left on the disk. Maybe this is
>different on Linux? This partition must somehow get bigger. Any suggestions
>how I achieve this without buying another disk? The current disk is big
>enough but the partitions was not set properly during installation and now I
>have to fix this....
>
>Mikael Ahlgren
Yes, Linux is different from AIX. AIX has Logical Volume Manager which
allows a Logical Volume (analogous to "partition") to reside on non-
contiguous cylinders of a disk. There's one or more implementations
of an LVM available or being worked on, but I'm not sure they're ready for
prime time.
Your best bet might be to create a new partition, mkfs it, and mount it
at /var/xxx (whatever directory is accumulating the unexpected file space).
(You'll have to backup the current contents of /var/xxx prior to the mount
in order to reclaim the disk space).
Probably the easiest way to reorganize a disk is with Partition Magic, as
it can not only resize, but relocate the partition on the disk.
--
Dave Brown Austin, TX
------------------------------
From: "bowman" <[EMAIL PROTECTED]>
Subject: Re: Linux vs Microsoft
Date: Mon, 30 Apr 2001 07:36:13 -0600
"Allen Ashley" <[EMAIL PROTECTED]> wrote in message
news:9cjbhs$[EMAIL PROTECTED]...
>
> I got a floppy with the tulip driver for linux with my LinkSys card. As I
> recall you can get the drivers from www.scynld.com. LinkSys provides more
> support for linux than some other vendors.
my floppy was unreadable. I did find the link to the drivers on the LinkSys
site, downloaded, compiled, and installed them. Works for me, but I do this
for a living. Tell Mom she needs to get some driver source, compile it, copy
it to /lib/modules/xxxxx, do an insmod on pci-scan and tulip, and set up her
init files so they'll load in the future, and she'll be booting back into
Win98.
Compare that to a manual with separate sections for each Win falvor, plus
quick start sheets.
Still, it is better than a certain UPS manufacturer who suggested that, in
the spirit of open source, I might want to give them the source for my
driver, after I wrote and debugged it. Yeah right. Send money. (or a free
UPS)
------------------------------
From: Guy Forssman <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,linux.redhat.misc
Subject: Re: linuxconf 7.1
Date: Mon, 30 Apr 2001 15:26:31 +0200
Reply-To: [EMAIL PROTECTED]
MrEye wrote:
> I just installed rh7.1. the last rh distribution I used was rh6.2. What
> happened to 'linuxconf'. I need it to modify the users. Does rh7.1 have a
> different configuration tool?
>
>
>
Hi there check if you installed it? I have installed 7.1 and found it under
kdestart gnomeprograms system or on the desktop there should be a icon
called kontrol-panel where you will find linuxconf.
otherwise do a rpm -ivh from your cdrom
Guy Forssman
------------------------------
From: Guy Forssman <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,linux.redhat.misc
Subject: Re: linuxconf 7.1
Date: Mon, 30 Apr 2001 15:29:04 +0200
Reply-To: [EMAIL PROTECTED]
MrEye wrote:
> I just installed rh7.1. the last rh distribution I used was rh6.2. What
> happened to 'linuxconf'. I need it to modify the users. Does rh7.1 have a
> different configuration tool?
>
>
>
Hi me again
there is also a icon called user when you start the kontrol-panel on the
desktop.
Guy Forssman
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: dd if=/dev/zero of=/dev/hda
Reply-To: [EMAIL PROTECTED]
Date: 30 Apr 2001 13:43:09 GMT
On Mon, 30 Apr 2001 03:38:06 -0230, Neil Zanella staggered into the
Black Sun and said:
>I am trying to zero my entire hard drive including the master boot record.
You don't need to zero the entire drive unless you have super-secret
data on there that you don't want anyone to see, and in that case, you
should get a large sledgehammer and/or some thermite.
>I have issued the command dd if=/dev/zero of=/dev/hda and several variants
>of it with bs and count options but each time I do this it takes forever.
Well, yes. At a transfer rate of 15M/s (pretty good for an older IDE
system especially if you don't have DMA and multi-sector R/W on) then
it'd take about 820 seconds to zero an 8G drive. If the drive is
failing mechanically, it could take even longer than that.
>The hard drive is not even 10GB and the system is only two years old or
>so but after two hours dd was still running. Any ideas of how I can
>speed up the process?
dd if=/dev/zero of=/dev/hda bs=512 count=1
This will blow away the MBR and the partition table, making it very
difficult to restore any data that was on the disk. It will take about
1/10 of a second to execute. Doze will assume there's nothing on the
disk, Unix fdisk will say that there's no partition table and it will be
impossible to mount any filesystems that used to reside on the disk.
This is all you need to do to make the disk "like new" in 99% of all
cases, and after doing it you can reinstall whichever OS you want and it
will think the disk has never been used.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: dd if=/dev/zero of=/dev/hda
Date: Mon, 30 Apr 2001 15:33:33 +0200
Villy Kruse <[EMAIL PROTECTED]> wrote:
> That would take for ever as well. It just takes that long to write 10
> gigabyte to a disk.
mmm .. at 5MB/s (streaming), it should take 2000 seconds, or 35 mins
(whichever is longer :-).
I would suggest a session with hdparm first. hdparm -d 1 /dev/hda ?
And up the blocksize in dd:
n=0
while true; do
dd if=/dev/zero of=/dev/hda bs=1024k seek=$n
echo -n .
n=$[ $n + 1 ]
done
You can get fancier. Spinning ascii wheels?
Peter
------------------------------
From: [EMAIL PROTECTED] (Dave Brown)
Subject: Re: How Do Modules Work?
Reply-To: [EMAIL PROTECTED]
Date: 30 Apr 2001 09:05:03 -0500
In article <TkLF6.384$[EMAIL PROTECTED]>, Scott Brady Drummonds wrote:
>Hello, all,
>
>I'm writing a paragraph or two in a related paper on kernel features that do
>not require kernel recompilation. Specifically, I wanted to mention Linux
>modules but I have no idea how they work!
>
>Could anyone give me the run-down on how the kernel would make use of a
>library without knowing if it was present in memory or, if present, where it
>was located? Or, better yet, are there any on-line resources that might
>help me research this for myself?
Depends on how deep you want to go. If you have the time and the $$, the
O'Reilly book "Understanding the Linux Kernel" is good.
When I explain modules (very broad-brush), I say that they are "kernel
extensions", comparable to what users used to put in their DOS config.sys
file as "device=c:\dos\ansi.sys", which attached ansi terminal support to
the DOS kernel. But how much this helps the current bunch of Windows
users that don't know much more about operating systems than clicking on
the "Start" button, I can't say.
There's also a mini-HOWTO on Modules, although IIRC it's more data-oriented.
--
Dave Brown Austin, TX
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.misc.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
