Hitno pomoc… [sređeno]

[diablo_]

Izvinite sto sam ovako nazvao temu jel ne znam kako drugacije.

Skinuo sam neke drajvere za modem i u neki fajl bi trebalo da dodam par linija koda ali kada pokusam da snimim fajl kaze da nemam dovoljno prava za tu komandu.Evo sta bi trebalo da ukucam ali ja ne znam gde i kako.

4. Open the file /etc/fstab in any text editor.

5. On a new line at the bottom of the file, add the line
/dev/Y /mnt/X vfat users,owner,ro,umask=000 0 0
where Y is the partition number of the Fat32 partition and X is the name of the directory you created in step 2. Note that this will allow ALL users READ ONLY access to the disk. To allow Read and Write access to ALL users, change the ro to rw. If you want only root to have Read and Write access (while other users have READ ONLY access), change the ro to rw and umask=000 to umask=022.

To mi je kada stavljam hard novi ali isti mi princip treba i za modem samo ne znam kako da promenim taj RO u RW???

[Dex]

loguj se kao root korisnik

[diablo_]

logujem se kao root ali nista

[ak-87]

Pa jesi li skontao to za X i Y?
Ako jesi kopiraj sadzaj fstab-a ovde na forumu,pa cemo zajedno to da odradimo.

[diablo_]

Ma nije u tome problem!problem je u tome sto ja odradim sve u tom fajlu,sve dodam ali ne mogu da ga snimim jel nemam administraciona prava!!!Logujem se kao root ali opet nece da mi da da ga snimim.Jel mogu da editujem nekako textualni fajl preko konsloe???

[Panta]

A da nisi, slučajno, te fajlove koje ne možeš da edituješ iskopirao sa CD ROM-a ili nekog drugog RO medijuma?

[Off-Topic]

Probaj mc ili echo “/dev/hdx /mnt/hdx FS OPTIONS” >> /etc/fstab koje su ti predvidjene za taj fajl, a sigurno postoji i vi kombinacija sa zamenom konkretnog reda.

[IgorPetrovic]

Koji je distro u pitanju? Koji editor koristiš? Daj nam malo više podataka.

Ako se uloguješ kao root, snimanje izmena mora da prođe. Opiši tačno šta radiš. Pričaš o modemu a šalješ nam fstab. Budi precizan.

[diablo_]

README for 2.6 kernel series port
of Lucent/Agere linmodem driver.

1. Requirements

– Linux kernel 2.6.x (up to 2.6.10 tested at the moment of writing)
– Configured kernel headers or source (read section 6 on this)
– serial_core enabled in kernel configuration
(Device Drivers/Character Devices/Serial Drivers/”8250/16550…”
in menuconfig to “Yes” or “Module”)
(most vendor supplied kernels enable this)
– See chapter 4 for state of SMP support

2. HOWTO build

You may need to create /dev/ttyLTM0 if you haven’t used 2.4 version
of driver or if you don’t use udev. Just do:
a. mknod –mode=0660 /dev/ttyLTM0 c 62 64
b. Change owner and group owner to match /dev/ttyS0
(Debian users: set group to dialout)
c. Create symlink /dev/modem to it (‘ln -s /dev/ttyLTM0 /dev/modem’)
If you use udev, than read docs/udev-setup and skip this step.

NOTE: previous versions of this driver used device name /dev/ttyLT0. If you upgrade
from previous version, than you may leave old name. But if you plan to switch to udev,
than new name may be more preferable.

Edit KERNEL_DIR variable in Makefile to reflect your 2.6 kernel dir or leave Makefile intact.
In later case driver will be compiled (or miscompiled) against
currently running kernel. Then just run make.
You will get ltmodem.ko & ltserial.ko.
Copy them to /lib/modules/`uname -r`/other/ dir and
run depmod -a.

NOTE: installing to /lib/modules/`uname -r`/other is somewhat bad practice,
’cause if you recompile your kernel with different options ltmodem modules
placed to …/other will remain there, but will likely conflict
with new kernel configuration. If that happens you must recompile (make clean; make)
and reinstall driver. Please, be aware of that. For more safety you
may install modules to more apropriate place e.g. /lib/modules/`uname -r`/kernel/serial/.
In that case new kernel modules installation will erase old ltmodem modules,
and you will easily notice it.
I actually prefer …/other approach, because often new config will be compatible with
previous.

Edit your modprobe.conf to load ltserial (not lt_serial)
for /dev/ttyLTM0.

My modprobe.conf contains following lines:
alias /dev/modem ltserial
alias char-major-62 ltserial
alias /dev/tts/LT0 ltserial

NOTE: there were reports that devfs (which is deprecated) creates /dev/ttyLT0, not /dev/tts/LT0.
If this is true and you still use devfs, than you will need to change last line to
alias /dev/ttyLT0 ltserial.

3. Report any problems to [email protected]

4. State of SMP support

8.31 core which is supposed to support SMP does not work on my system,
so default core is old one (I dont remember what).
I have also included 8.31 core which seems to work on some (probably many)
systems. Old core also contains some fixes for SMP, I dont remember
if I did them (on top of 8.26 for example) or it is 8.30 core which
should contain that fixes.

Some code to support SMP is there since revision 6,
but because largest part of driver is closed-source
it is very hard to ensure that SMP support is correct. I believe that
driver should work fine on SMP systems with both cores.

Please, report SMP success/fail reports to me ([email protected]).

5. How to use 8.31 core

Just change ltmdmobj.o symlink to point to ltmdmobj-8.31.
E.g.:
ln -sf ltmdmobj.o-8.31 ltmdmobj.o
Be carefull to actually rebuild driver with new ltmdmobj.o.
‘make clean’ followed by ‘make’ should suffice.

6. Typical build problems

Many novice users report build problems.
All of them were about building kernel modules against precompiled kernels. Which is
sometimes tricky process (depending on your distro).

This is what FUSE project recomments
(taken from http://fuse.sourceforge.net/):

Building the kernel module needs a configured kernel source tree matching the running kernel.
If you build your own kernel this is no problem.
On the other hand if a precompiled kernel is used, the kernel headers used by the FUSE build process
must first be prepared. There are two possibilities:

1. A package containing the kernel headers for the kernel binary is available in the distribution
(e.g. on Debian it’s the kernel-headers-X.Y.Z package for kernel-image-X.Y.Z)
2. The kernel source must be prepared:

o Extract the kernel source to some directory
o Copy the running kernel’s config (usually found in /boot/config-X.Y.Z)
to .config at the top of the source tree
o Run make menuconfig, then make dep at the top of the source tree (only needed on 2.4 kernels)

If using the 2.6 kernel, then write access is needed to some files in the kernel source tree.
Usually it is enough if you make .tmp_versions and .__modpost.cmd writable.

Also see docs/Example.txt section KERNEL SOURCE PREPARATION.

[diablo_]

To vam je kompletan reame faljl ali ove linije pod alias ne mogu da dodam jer nece da snimi fajl posle editovanja.

Koristim mandrake(madriva)10.2 LE 2005 Linux pod 2.6.11-6 kernelom.Ne razumem pianje koje editore koristim.

[Аутор]

Чланци