Pages

Search

gcc and glibc - Forums Linux

gcc and glibc - Forums Linux

gcc and glibc

Posted: 06 Sep 2004 09:11 PM PDT

Thanks guys! I found the rest of the rpm files on the
Fedora Core Disk 2. Now everything is working as it
should!

Much appreciated!

"Tony" <gatech.edu> wrote in message
news:chjcdr$g8r$gatech.edu... 
2 

create several partitions between hda1 and hda3

Posted: 06 Sep 2004 09:06 PM PDT

[Non-existant col.redhat removed - don't blindly trust Google]
[FollowUp-To: header set to col.misc]

ca (TCMA) writes:
 
 
 
 

You don't.
 

And that's as far as you can get. You could create exactly one more
primary partition - /dev/hda2 in this scenario. The partition table
simply doesn't allow for more than 4 primary partitions, where one of
these can be of the type "extended". Since you already _have_ an
extended partition (/dev/hda4), that slot is taken, and you can't
create more than that.

Either live with just one more partition, or change the whole layout.
Warning: Changes to the partition table may render your data
unreachable - _always_ make a backup of all valuable data of all
partitions of that disk prior to playing around with the partition
table. At the very least, printout the present partion table
(fdisk -l /dev/hda | lpr) for to have a detailed layout at hand.

Suggestion: Backup, then delete the logical volumes and the
extended partition completely. Reboot, then start Linux from
the installation medium (CDROM or DVD) of your choice, and
create a better partitioning scheme from scratch.

Michael

mounting fat32 IDE hard disk error: "does not contain valid partition table"

Posted: 06 Sep 2004 07:13 PM PDT

On 6 Sep 2004 19:13:05 -0700,
bokluk <com> wrote:
 

# mkdir -p /mnt/windows
# mount /dev/hdc1 # Will use the options specified in /etc/fstab.
 

# fdisk -l /dev/hdc
 

Generally speaking partitions don't have partition tables, disks do.

A common mistake, and hardly limited to beginners.

GL & HTH,

Michael C.
--
com http://mcsuper5.freeshell.org/

The worst sin towards our fellow creatures is not to hate them, but to
be indifferent to them; that's the essence of inhumanity. - G.B. Shaw

keyboard and mouse does not work while configuration after installion suse 9.1

Posted: 06 Sep 2004 12:46 PM PDT

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup mjt <ru> suggested: 
 
[..]
 

Perhaps the search-able hw db (www.suse.com) has more info/hints
about the mentioned notebook? In addition an external keyboard
might help to fix things.

Wouldn't suggest this "manufacturer", among the worst I've ever
seen IIRC sold by Aldi and alike.

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBPPhJAkPEju3Se5QRAr2RAKCv2qaXwh8wBMdlDxdbVE 7oHrTJQgCfRYaB
QtKE7QLJlywlRCNmzdJAyTU=
=cw4h
-----END PGP SIGNATURE-----

makeisofs question

Posted: 06 Sep 2004 05:24 AM PDT

Tim Wunder wrote:
 

Thanks for suggestion - no luck yet I'm afraid.

icewm

Posted: 06 Sep 2004 01:21 AM PDT

Gernot Frisch <net> did eloquently scribble: 

Not quite. Xwindows is a full windowing environment including such wonders
as network transparency, so you can start an X program in london and control
is/see it on your home machine in san fransisco (albeit, slowly))
:)
X will open windows if things are started in it. But there's no way to move
them, change their size, minimise, shade, etc. That's where the window
manager comes in.
 

Something that controls and manages the windows created in X. (along with
varying degrees of other functionality)
 

yes.
 

and yes, although, a file manager doesn't always need X...
mc (midnight commander) is a text-mode file manager.
 

As I said, I've never tried changing KDE's default window manager... not
even sure how. IceWM however is gnome compliant, (meaning it'll integrate
tightly with gnome).
--
__________________________________________________ ____________________________
| co.uk | "Are you pondering what I'm pondering Pinky?" |
|Andrew Halliwell BSc(hons)| |
| in | "I think so brain, but this time, you control |
| Computer Science | the Encounter suit, and I'll do the voice..." |
------------------------------------------------------------------------------

Modem dials only as root.

Posted: 06 Sep 2004 12:34 AM PDT

On Mon, 06 Sep 2004 09:34:23 -0400, Jack Frillman <net> wrote: 

<snip>
 

I like Jack Frillman's ("moo") idea: Try pppd and chat. A lot more
of us use this than wvdial.....

If we can get it running with pppd, then the problem is wvdial, not
something systemic.

AC

Grub with multiple hard disks

Posted: 05 Sep 2004 06:40 AM PDT

7 <ecu.pwp.blueyonder.co.uk> wrote in message news:<ob__c.157197$news.blueyonder.co.uk>... 
[snip] 

That was the point of my first two items -- the MBR code of hd0 is the
only one read, so with MBR on both disks loaded with grub ...
 

requires root priviledges -- see below ...
 

By this time Linux is already up and running so unless OP wants a
particular version of the kernel to run this is moot.

The issue at this point is whether /etc/fstab has run and successfully
mounted all partitions -- a reboot should not be necessary _if_ fstab
can be configured correctly. If it can't be configured to run all
_needed_ partitions by this stage (which would require duplicate
partitions on the hdds to be "foolproof") then the OP is left to
decide _which_ partitions to leave mounted/unmounted based on which
hdd the OS booted from (which is normally going to be hda in any case
-- how to figure out if hda is an "old" hdd or a "new" one).

If the disks could be treated independently (ie., run from one, forget
the other) then simply having grub in MBR of both disks would suffice.
Fear that is no what OP has in mind.

Running scripts at this stage would also require suid scripts --
something to be avoided on servers at all costs! It might be made to
work, but personally I would prefer to take my medicine up front
rather than a phone call/ass chewing at 3 a.m. ;-)

It would be nice if some things like this were possible _and_ secure,
but that is what ssh or serial terminal connections are for. Gather
from what the OP did not say that serial terminal boards are not in
place, so ...

Still, it's a good sign that you were thinking through the problem.
When you get more familiar with Linux you'll catch your thought
glitches yourself -- I do it 5-10 times a day ;-)

regards,
prg
email above disabled

Firewall, PortSentry, and ports

Posted: 04 Sep 2004 03:00 PM PDT

com (Jonathan Hayward) wrote in message news:<google.com>... 

"and making a hole in the firewall" -- does that answer your question
about how good an idea this is, ie., to detect _if_ the bad guys are
scanning us, gee, let's open the firewall ...
 

the traffic is already in before portsentry detects it (if it detects
it) -- "quick, doris, lock the door, burglars just got into the
house!"
 

"should I poke holes in the firewall" -- do you leave your doors
unlocked at night then sit up guarding them so you can catch thieves
after they enter your abode?
 

Firewall rules should always follow the simple rules:
-- policy -> drop
-- don't offer any services, and if you must only the ones that you
must
-- only let in traffic that you must
-- block outgoing traffic that is not needed
-- use connection tracking to monitor stream state, ie., monitor which
packets are related to who/what

O.G. offered up some very good advice re: auto-blocking of ports,
spoofing, etc.

If you're really interested in IDS, check into snort:
http://www.snort.org/about.html

Get a copy of nmap (you already have one most likely, but get the new
version) and scan yourself and learn "how it's done".

Play with ethereal and get familiar with packet structure -- a little
bit of familiarity here will go a long way to interpreting what you
see in logs/alerts.

Psionic was bought by Cisco and despite claims of releasing v2.0 of
portsentry, nothing has come of it -- not sure that Cisco even plans
to do anything with portsentry. Seems dead, afaict (no tears here,
though).

The "typical" ports are mostly MS related -- you can log them if you
wish _without_ letting them in. This is considered a more secure
means of detecting some things -- but you have to monitor your logs or
use software that analyses it for you. Look at your own /etc/services
file to get your bearings and try logging some of the more common
ports like ftp, smtp, ssh, telnet, dns, and netbios with iptables.

Most people (at home) play with logging for a while then turn it off.
The "dangerous" activity (scans and other things) can take many shapes
-- thus the suggestion that you look at snort.

So long as you remember KISS, don't confuse yourself with too many
automated toys meant for larger (much larger) networks, and keep an
eye on your system with a few logs, you should be OK. Most crackers
don't actually "break in", usually somone has overcomplicated things
and in the confusion, left a door wide open.

hth,
prg
email above disabled

Ddebian: gcc5 HOW2

Posted: 04 Sep 2004 05:52 AM PDT

On 2004-09-06, Miro <com> wrote: 

On Debian, start by installing the following packages:

$ apt-cache show altgcc libc5-altdev
Package: altgcc
Priority: extra
Section: oldlibs
Installed-Size: 3248
Maintainer: Debian GCC maintainers <debian.org>
Architecture: i386
Version: 1:2.7.2.3-2
Provides: c-compiler
Depends: libc6 (>= 2.2.2-2), binutils (>= 2.7-1)
Recommends: libc5-altdev
Suggests: gcc272-docs
Filename: pool/main/a/altgcc/altgcc_2.7.2.3-2_i386.deb
Size: 1399660
MD5sum: 26e7d1fef351335dd7223f004f7d2219
Description: Alternate gcc package for the libc5 environment.
This special gcc package works with the libc5-altdev package to build
binaries for the old libc5/ld-linux.so.1 environment. It can coexist with
the standard libc6 development packages.

Package: libc5-altdev
Priority: extra
Section: oldlibs
Installed-Size: 4748
Maintainer: Francesco Paolo Lovergine <org>
Architecture: i386
Source: libc
Version: 5.4.46-15
Depends: libc5 (= 5.4.46-15)
Filename: pool/main/libc/libc/libc5-altdev_5.4.46-15_i386.deb
Size: 890880
MD5sum: ecd1ce0340ee02fccab0e77760a7acf5
Description: The Linux C library version 5 (alternative dev files).
Includes libc headers, kernel headers (v2.0.29) and static
libraries. This package can be used to build libc5-base binaries
even when the libc6-dev package is installed.

GRUB does not boot windows XP

Posted: 03 Sep 2004 02:47 AM PDT

es (amanita) wrote in message news:<google.com>... 

Assume you mean there are no error messages and that you don't see a
quickly flashing grub> prompt ...
 

I've read the other threads, but this one provides the essentials.
Did not see anything obviously out of place, except ...

Did notice that you have a gross duplication of Linux stanzas in
grub.conf -- assume this is from multiple attempts to get things
working and that you've tried grub-install several times. You don't
need the extras so plan to get rid of them later.

Unless you've inadvertantly tried "grub-install /dev/hda1" (instead of
"grub-install /dev/hda"), the reason you're being "returned" to the
grub menu is because of an unfound bug with NTLDR code -- ie., no code
is executing from the _partition_ boot sector of hda1. Even MS has
not been able to run this down though they are aware of it. This
affects all dual-boot loaders, afaik.

The only other possibility is that you're chainloading to a copy of
grub that has been placed in hda1 -- most, very most, unlikely.

If you were getting error messages from NTLDR it would most likely be
another/related bug in NTLDR code that is meant to protect against a
"corrupted/virus infected" MBR. I believe you have to "stumble"
across the right sequence of "correcting" the MBR for this one to crop
up -- relates to the registry values anf file timestamps concerning
NTLDR and the MBR.

Opinions vary, but I always try (very hard) to get people to use NTLDR
instead of grub -- mainly because you're much more likely to
re-install Win and overwrite the MBR than you are with Linux (which
allows you to leave the MBR untouched). Sounds like weird advise
after the bugs I listed, but they are pretty rare and cannot be
reproduced faithfully -- seem to be random gremlins (of which there
are quite a few in Win OSes). Besides, XP and utilities are just too
ignorant/buggy around other OSes.

At the moment, you're just interested in getting XP back. Rescue
disk? Can you get to the recovery console? Are you comfortable with
restoring NTLDR to MBR? Thought of making a Linux boot floppy? Fact
is there are a number of ways to go -- none of them all that pleasant
;-(

With backups of course, you might try items below.

You may be able to fix the boot sector code like this (fixboot):
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314058
or recover just the ntldr MBR code with fixmbr.

Try here to recover ntldr (only if you have a good means of gettin
into Linux):
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/windows/xp/all/reskit/en-us/prmb_tol_fngj.asp
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmb_tol_zldj.asp
http://www.google.com/search?num=50&hl=en&lr=lang_en&ie=UTF-8&q=winxp+restore+ntldr&btnG=Search

If this works OK and everything seems "normal" you now have a choice
-- boot with ntldr in the MBR or use grub in the MBR.

To stay with ntldr, try these instructions:
http://www.geocities.com/epark/linux/grub-w2k-HOWTO.html
This will give you an ntldr menu from which you will go to a grub menu
(which will placed in the _partition_ boot sector rather than the
MBR). This and the extra setup steps is why most people just use grub
-- but if you reload XP ...

If you want to try grub in the MBR, use the "native" install
instructions at the grub> prompt instead of running grub-install from
Linux. See info grub for the details -- they are pretty simple ;-) I
would clean up grub.conf before doing this -- you only need 3 entries.

hth,
prg
email above disabled