LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 09-10-2006, 06:33 AM   #1
Chroma
LQ Newbie
 
Registered: Sep 2006
Posts: 12

Rep: Reputation: 0
disabling read only


Im having several problems, the most major of which is the complete inability to navigate a shell.

I need to boot from DVD using "bare.i root=/dev/hda1 noinitrd ro"

once i do this everything goes through peachy, i login as root and try "startx"

This punts me an error concerning a X configs.
Again not an issue, ive been able to find help on this subject.

The other thread helping out however tells me to use "xorgconfig"
Not a problem i get through the configuration and BAM

Cannot write to file.

Read only mode is on due to the ro flag passed at boot, ive tried to omit this and play aronund with flags but it seems linux doesnt like to boot in anything other than read only.

Can someone give me some information on how to stop the madness?

TLDR people
I want to turn off "read only" once i boot into root, how do i achieve this?
 
Old 09-10-2006, 07:25 AM   #2
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 47
What does "navigate a shell" mean?
When you configure X, are you user "root"?
 
Old 09-11-2006, 03:54 AM   #3
Chroma
LQ Newbie
 
Registered: Sep 2006
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by uselpa
What does "navigate a shell" mean?
When you configure X, are you user "root"?
In regards to both questions... i have absoloutly no idea.
I'm entirely new to all this.

I have absoloutly no idea of the layout of the system (dir or ls seem to not want to work, i assume there's a reason for this) so im basicly typing cd [/some directory that will hopefully exist] using what faint memory i have from half hearted tinkerings a number of years ago.
I have no real idea how to do anything via bash (im not even certain thats the default shell here)

I assume im logged in as root. (im aware im making a lot of assumptions here, i guess anyone as inexperienced would logicaly do the same)

I start up, boot into the slackware dvd.
type "bare.i root=/dev/hda noinitrd ro"
and wind up eventualy at the login prompt.
I type root as the username and my password.
Wind up with a spew of MOTD and find myself at DarkStar~#

Type xorgconfig, go through the process of describing all my hardware and wind up with an error when it tries to write to xorg.conf.

/etc/xorg.conf is definately there.
I've checked but i don't know what attributes it has i have no real grasp of how to check or modify them.

like i said im entirely new to all this and highly aware of my limited grasp of the os.
 
Old 09-11-2006, 08:02 AM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Quote:
Originally Posted by Chroma
In regards to both questions... i have absoloutly no idea.
I'm entirely new to all this.

I have absoloutly no idea of the layout of the system (dir or ls seem to not want to work, i assume there's a reason for this) so im basicly typing cd [/some directory that will hopefully exist] using what faint memory i have from half hearted tinkerings a number of years ago.
I have no real idea how to do anything via bash (im not even certain thats the default shell here)

I assume im logged in as root. (im aware im making a lot of assumptions here, i guess anyone as inexperienced would logicaly do the same)

I start up, boot into the slackware dvd.
type "bare.i root=/dev/hda noinitrd ro"
and wind up eventualy at the login prompt.
I type root as the username and my password.
Wind up with a spew of MOTD and find myself at DarkStar~#

Type xorgconfig, go through the process of describing all my hardware and wind up with an error when it tries to write to xorg.conf.

/etc/xorg.conf is definately there.
I've checked but i don't know what attributes it has i have no real grasp of how to check or modify them.

like i said im entirely new to all this and highly aware of my limited grasp of the os.
Hi,

First, I would suggest that you read some good online reference to get some background. Check my sig.

Now, why are you passing parameters at boot? Did you install lilo to the MBR of your boot drive? It looks like you are still booting the install cd/dvd to boot your installation. Generally we use this method of boot for maintenance or rescue of an install.

If you failed to install lilo, you can recover by booting with the install cd/dvd and then;
Code:
#mkdir /slack_recover
#mount /dev/hda# /slack_recover   #change # to your device number
#chroot /slack_recover
#liloconfig                       #rerun liloconfig and write to mbr
Once you have written the lilo then reboot the machine. You should be able to now choose your Slackware install. I would then suggest that you login as root and then adduser. You would then be able to login as the user. Whenever you need to do root work the just 'su'.

Like I said before, read some good reference and 'man' command when in doubt.

BTW, Welcome to Slackware!

edit: A good site to look at.

Last edited by onebuck; 09-11-2006 at 08:11 AM.
 
Old 10-02-2006, 04:10 AM   #5
Chroma
LQ Newbie
 
Registered: Sep 2006
Posts: 12

Original Poster
Rep: Reputation: 0
Im booting from the DVD simply because the install machine wont get past "Verifying DMA pool..." otherwise.

I have no real idea whats causing this but im certain it cant be anything operating system related, my bios doesnt seem to want to boot up the hard drive, ive been through my bios with a fine toothed comb and found nothing to cause this, ive even went so far as to specify the hard drive geometry manualy.

I boot from the DVD and i wind up in ro mode, generaly when i boot on other machines it will mount the / partition in ro mode, check its consistency then remount it in rw mode.
Booting from DVD seems to prevent this from happening.


Not to worry however, ive installed Slack on an entirely different machine and ive learned more about linux in the past 3 weeks than ive learned in my life using other distro's

The original target machine was a lowly p166 (which is ok with me) now im using my main box and compile's take a few minuites rather than the marathon installs on the pentium

Not that any of this actualy helps my original problem, but im getting pretty comfortable using a bash shell im certain in the next couple of weeks to a month not only will i have slackware comfortably installed on the older p166 i'll have it all configured as a wireless router/storage setup too

I cant believe ive been able to use windows for so long considering just how much flexability i now have, i dont see me winding up back in win turf for quite a while.
 
Old 10-02-2006, 08:04 PM   #6
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Hi,

I just re-read your post(s).

I notice in;

Quote:
I start up, boot into the slackware dvd.
type "bare.i root=/dev/hda noinitrd ro"
and wind up eventualy at the login prompt.
I type root as the username and my password.
Wind up with a spew of MOTD and find myself at DarkStar~#
should be;

Code:
bare.i root=/dev/hda# noinitrd ro     #change the # to partition
If you have installed slackware on the machine and still have boot problems. You can boot with the install cd then;
Code:
mkdir /slack_restore
mount /dev/hda1 /slack_restore            #use your partition number
cd /slack_restore
chroot /slack_restore                     #make changes to system
                                          #REBOOT
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Mounted read-write Fat32 partition suddenly becomes read-only?? hohead Linux - General 8 04-05-2007 12:17 PM
Read-only file system after enabling/disabling root benn333 Ubuntu 2 02-25-2007 12:42 PM
mozzla problems-can not read files online, can not read attachments sarajevo Linux - Software 1 09-20-2005 06:58 PM
Example share in smb.conf doesn't work - read/write vs read only kleptophobiac Linux - Networking 0 09-01-2004 07:14 PM
kernel panic unable to mount root (yes ive read/read other posts) dmx9595 Linux - General 4 01-17-2004 05:07 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 04:02 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration