Pages

Search

in wich FAT to format a new partition - Forums Linux

in wich FAT to format a new partition - Forums Linux


in wich FAT to format a new partition

Posted: 22 Oct 2005 11:32 AM PDT

Albert <yu> wrote: 

Remove them both, I would say. That would at least get rid of windows,
no?

Care to provide some context?

Peter

Unable to access external websites

Posted: 22 Oct 2005 06:28 AM PDT

Thanks but telnet to www.google.com on port 80 times out like so:
[mat@chateau ~]$ telnet www.google.com 80
Trying 66.102.9.104...
telnet: connect to address 66.102.9.104: Connection timed out
Trying 66.102.9.147...
telnet: connect to address 66.102.9.147: Connection timed out
Trying 66.102.9.99...
telnet: connect to address 66.102.9.99: Connection timed out
telnet: Unable to connect to remote host: Connection timed out

What more information can I provide. Also what the easy way to install
lynx without using yum?

Thanks
Mat

Newbie question about static routing

Posted: 21 Oct 2005 11:48 PM PDT

Bit Twister wrote: 

We were talking about zeroconf route in route table,
not about /etc/resolv.conf. It's a different story,
as Kipling said.

If there is a static address, zeroconf must not
do anything (according to the spec), so there is
something fishy in FC implementation.

--

Tauno Voipio
tauno voipio (at) iki fi

ConfigMgmt best practice for Sys Admin (config files, etc.)

Posted: 21 Oct 2005 06:17 PM PDT


"Daniel P. Kionka" <com> wrote in message
news:supernews.com... 

Oh, goodness, I go through this all the time. I distrust CVS for this, due
to the usual method of having to create a central CVS repository, unless you
set up a CVS on each machine. I tend to use RCS locally for little config
files like /etc/fstab, /etc/exports, /etc/hosts, etc. Just make sure never
to RCS lock a file that may be edited by the system dynamically or by
another administrator behind your back. Check it in, check it back out
immediately, and you can run "rcsdiff" to track the changes.


updating SuSE 8.1 --> 10

Posted: 21 Oct 2005 10:07 AM PDT

Bob Hairgrove <com> did eloquently scribble: 

Did you try the textmode install?
never had trouble with that.

 

You can install suse 10 using the text mode install and then worry about X.
If you're so worried about not being able to configure it, save your
original XF86Config file to a floppy and try that when you've completed the
install. I can't imagine the config file format changing that much since
they branched, it might just be a matter of changing the name to xorgconfig.

If simply changing the name of the config file and using it to replace the
config file present doesn't work, try this...

Xorg is a branch of XF86, so it should work...

SaX2 isn't the only way to configure X. X can produce a config file for
itself (it needs a bit more work, when you do it this way, but X usually
auto detects the graphics and monitor settings properly, when SaX can't)

It USED to be "X -configure"
 

They did?
How? By releasing the distribution for free from the start rather than
making available after 4 months, like they used to?
Have you CHECKED if the pdfs of the manual are in the distro like they
always used to be? look in /usr/share/books
 

Simply upgrading from 8.1 to 10 would be a massive undertaking if you chose
to do it manually...
So much has changed, 2.4 and 2.6 changes have inherent problems, all the
software will be on a version of glibc far removed from the one on 8.1
meaning, if you upgrade glibc to get the new stuff working, you'd probably
break all the old stuff...

I've found before that if you upgrade, it's best to only perform the upgrade
between quite close versions, say, upgrading from 8.1 to 8.3 would be ok,
but you'd run into problems if you went far beyond that.

The best way to install if you're more than about 4 versions behind is to
reinstall, or get your hands on a previous version in between to use as a
stepping stone.
--
__________________________________________________ ____________________________
| co.uk | |
|Andrew Halliwell BSc(hons)| "The day Microsoft makes something that doesn't |
| in | suck is probably the day they start making |
| Computer science | vacuum cleaners" - Ernst Jan Plugge |
------------------------------------------------------------------------------

US Robotics modem on Fedora4

Posted: 21 Oct 2005 09:41 AM PDT

Idea - have you tried "ATDT*70,1-xxx-yyy-zzzz" for your call waiting
problem?

The *70 disables call waiting, and the comma waits a second or two
before dialing the phone number. Used this a lot during my college
days (roommates had call waiting) but my house phone doesn't (I'm too
cheap to get call waiting. Heck, I'm too cheap to get a DSL line like
the rest of my friends. :)

Madman

Help w/ GRUB, dual boot

Posted: 21 Oct 2005 06:53 AM PDT

On Fri, 21 Oct 2005 17:12:42 +0200, Bob Hairgrove
<com> wrote:

AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!

This works:
map (hd2) (hd0)
^^^
(space here)

This DOESN'T work:
map (hd2)(hd0)
^^ (no space!)

THREE F**KING HOURS WASTED looking for this !@#$%%^&& ...

AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!
AAAAAAAAARRRRRRRRRRGGGGGGGGGHHHHHHHH!!!!!!!

--
Bob Hairgrove
com

Using cron as a non-root user

Posted: 21 Oct 2005 12:13 AM PDT

On 21 Oct 2005 00:13:12 -0700, banyan <com.sg> wrote:
| Folks,
|
| I wanna allow a normal user to schedule a specific task, which entails
| root permission to execute, using cron. I put a file as below in the
| "/etc/cron.d" directory, where the "myprog" requires root priviledge to
| run.
|
| -----------------------------------------
| SHELL=/bin/sh
| PATH=/usr/local/sbin
|
| # m h dom mon dow user command
| 22 17 19 10 * root myprog
| -----------------------------------------
|
| I then grant the normal user the write right to the file. However, cron
| does not schedule the "myprog", when the user adds a new task entry
| into the file. cron seems aware that it is not root that modify the
| file.
|
| Although I can crontab the file and make cron schedule the task, it is
| not run as a root. How can I achieve my objective?


Give them the root password.

You may as well do it directly, (with an accompanying talk) instead
of giving it to them indirectly by letting them run whatever they like
as root.

Alternatively, setup 'sudu' and let then run the crontab command as root.

You are still effectively giving them full access though.


--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/~paulcol
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro

PCMCIA problem with Travelmate 6500

Posted: 20 Oct 2005 06:01 PM PDT

On Fri, 21 Oct 2005 19:32:48 +0200, <com> wrote:
 

Are there any messages on the screen? What does this crash look like?
 

First I should avoid any misunderstanding that arises because it may look
like I am more knowledgeable than I am. Take what I say as suggestions from
one who is quite much scrambling in the dark.

I tried to look up in the Linux kernel code where the message about
"please try pci=biosirq" comes from, and found it in the file
arch/i386/pci/irq.c. Of course, I don't understand much of the code,
I would have to spend a couple of weeks reading it and googling to read
up on harware issues, pci and cardbus standards etc.

However, this may be a lead:

if (io_apic_assign_pci_irqs) {
... (not executed)
} else if (pci_probe & PCI_BIOS_IRQ_SCAN)
msg = ""; (not executed)
else
msg = " Please try using pci=biosirq."; (executed)

I hardly remember what is "apic", but I see in your original post that:

# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set

Did you configure and compile your own kernel, or is this a distribution kernel?

For whatever it is worth, my own kernel has

$ grep APIC /boot-copy/config-2.6.13-1.1526_FC4
CONFIG_X86_GOOD_APIC=y
# CONFIG_X86_UP_APIC is not set

I don't have any 2.4 kernel around.

The help information on these options goes:

config X86_UP_APIC
bool "Local APIC support on uniprocessors"
depends on !SMP && !(X86_VISWS || X86_VOYAGER)
help
A local APIC (Advanced Programmable Interrupt Controller) is an
integrated interrupt controller in the CPU. If you have a single-CPU
system which has a processor with a local APIC, you can say Y here to
enable and use it. If you say Y here even though your machine doesn't
have a local APIC, then the kernel will still run with no slowdown at
all. The local APIC supports CPU-generated self-interrupts (timer,
performance counters), and the NMI watchdog which detects hard
lockups.

config X86_UP_IOAPIC
bool "IO-APIC support on uniprocessors"
depends on X86_UP_APIC
help
An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
SMP-capable replacement for PC-style interrupt controllers. Most
SMP systems and many recent uniprocessor systems have one.

If you have a single-CPU system with an IO-APIC, you can say Y here
to use it. If you say Y here even though your machine doesn't have
an IO-APIC, then the kernel will still run with no slowdown at all.


Looking a little more at the code, it now seems to me that the lines I quoted
above, apply mostly to SMP systems, and that the failure in your case happens
earlier. "io_apic_assign_pci_irqs" is a macro that computes to "0" if
X86_UP_IOAPIC is not selected.


Another thing that attracts my attention is:

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
CONFIG_CARDBUS=y
CONFIG_TCIC=y
CONFIG_I82092=y
CONFIG_I82365=y

I notice that PCMCIA is included only as a module, and the rest as
compiled-in. I know very little about this, I just had a vague notion that
PCMCIA is a broader and more fundamental concept than e.g. Cardbus.

While generally the kernel configuration system is good at preventing you
from this kind of mistakes, since something now obviously is wrong, I feel
like inquiring about this: What if the other parts actually require PCMCIA?
I believe that the kernel allways runs the init functions of all compiled-
in modules before that of any loadable module. This could be the wrong order.

-Enrique

mandriva05 - hiding all boot prompt messages

Posted: 20 Oct 2005 02:47 PM PDT

"Bit Twister" <com> ha scritto nel messaggio
news:home.invalid... 

yeah, i'm sorry


Slackware and KDE

Posted: 16 Oct 2005 04:14 PM PDT

Larry Blanchard wrote: 
 

Yes. The name of the problem is kppp.
 

Why do you consider GUIs and your scripts mutually exclusive?
--
John Hasler
gt.org
Dancing Horse Hill
Elmwood, WI USA