• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 ... 8 9 [10]
136  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 18, 2009, 06:41:06 AM
While trying to add the former Windows domain groups as spelled before

  root@Share:~# groupadd "Domain Users"
  groupadd: Domain Users is not a valid group name

re the above error message I ran into the following hint http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/groupmapping.html

So I added a mapping

  root@Share:/var/lib# net groupmap add ntgroup="Domain Admins" unixgroup="Domain_Admins" rid=512 type=d
  Successfully added group Domain Admins to the mapping db as a domain group
  root@Share:/var/lib# net groupmap add ntgroup="Domain Users" unixgroup="Domain_Users" rid=513 type=d
  Successfully added group Domain Users to the mapping db as a domain group
  root@Share:/var/lib# net groupmap add ntgroup="Domain Guests" unixgroup="Domain_Guests" rid=514 type=d
  Successfully added group Domain Guests to the mapping db as a domain group
  root@Share:/var/lib# net groupmap add ntgroup="Domain Computers" unixgroup="Domain_Computers" rid=515 type=d
  Successfully added group Domain Computers to the mapping db as a domain group

  root@Share:/var/lib# net groupmap list
  Domain Users (S-1-5-352321536-2717123682-1120367698-xxxx-513) -> Domain_Users
  Domain Guests (S-1-5-352321536-2717123682-1120367698-xxxx-514) -> Domain_Guests
  Domain Computers (S-1-5-352321536-2717123682-1120367698-xxxx-515) -> Domain_Computers
  Domain Admins (S-1-5-352321536-2717123682-1120367698-xxxx-512) -> Domain_Admins

At least the info shows now

  root@Share:/var/lib# net rpc info
  Enter root's password:
  Domain Name: MYDOMAIN
  Domain SID: S-1-5-21-1644491937-1383384898-xxxx
  Sequence number: 125xxxxx
  Num users: 10
  Num domain groups: 9
  Num local groups: 3

I think a step into the right direction, but error

 "Das servergespeicherte Benutzerprofil wurde nicht geladen. Sie werden mit einem lokalen Benutzerprofil angemeldet. nderungen an dem Profil werden nach der Abmeldung nicht auf den Server kopiert. Das Profil wurde nicht geladen, weil eine bereits vorhandene Serverkopie des Profilordners nicht die richtigen Sicherheitseinstellungen besitzt. Entweder muss der aktuelle Benutzer oder die Administratorengruppe Besitzer dieses Ordners sein. Wenden Sie sich an den Netzwerkadministrator."

persists. Also confused, why the Domain SID differs from the one in my previous post, though all files have just been copied from the NSLU to the Plug?
137  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 14, 2009, 08:52:01 AM
PS: BTW I also got the following error message:

root@Share:~# net rpc info
Domain Name: MYDOMAIN
Domain SID: S-1-5-352321536-2717123682-xxxx
Sequence number: 125xxxxx
Num users: 10
Num domain groups: 0
Num local groups: 0

root@Share:~# net rpc user
Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME)

??

I wasn't aware that it's such a hassle to migrate a PDC to another device and nearly considering giving up and starting from scratch meaning:

  returning to my pre migration attempts SD-card image (luckily I made one)

  leaving the existing domain with all PCs
  deleting all (roaming) profiles on all PCs

  just putting the adapted smb.conf in place on the plug
  attaching the usb-drive to the plug

  firing up samba on the plug
  joing all PCs to the domain again
  recreating the user accounts again

  hope that the users' profile/config still stored on the usb-drive (/mnt/sda1/<user>/profile will still work when the users login the first time ...
 
138  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 14, 2009, 08:39:28 AM
No I didn't.

Though I had been trapped by the /var/run vs /var/lib path issue I went ahead with another try and overcame the missing users issue, however got stuck with a logon issue.

But here's the story step by step.

After realizing that no *.tbd files should go into path /var/run/samba on the Plug I updated my smb.conf (/etc/smb.com) as follows:

Code:
cat /etc/samba/smb.conf.new
[global]
        workgroup = MYDOMAIN
        netbios name = %h
#       server string = Linksys NSLU2.0
        server string = SheevaPlug
#       interfaces = 127.0.0.1/24, ixp0, lo
        interfaces = eth0, lo
        bind interfaces only = Yes
        map to guest = Bad User
        null passwords = Yes
#       smb passwd file = /opt/etc/samba/passdb.tdb
#       smb passwd file = /etc/samba/passdb.tdb
        passdb backend = tdbsam
        guest account = guest
        username map = no
        log level = 1
        max log size = 10
        name resolve order = wins bcast
        socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
        load printers = No
#       add user script = /opt/bin/adduser -H '%u'
#       delete user script = /opt/bin/deluser '%u'
#       add group script = /opt/bin/addgroup '%g'
#       delete group script = /opt/bin/delgroup '%g'
#       add user to group script = /opt/bin/addgroup '%g' '%u'
#       add machine script = /opt/bin/adduser -s /bin/false -h /dev/null '%u'
        add user script = /usr/sbin/useradd --create-home '%u'
        delete user script = /usr/sbin/userdel '%u'
        add group script = /usr/sbin/groupadd '%g'
        delete group script = /usr/sbin/groupdel '%g'
        add user to group script = /usr/sbin/useradd --gid '%g' '%u'
        add machine script = /usr/sbin/useradd --home /dev/null --shell /bin/false '%u'
# http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
# http://www.comptechdoc.org/os/linux/manual4/smbconf.html
        domain logons = Yes
        os level = 33
        preferred master = Yes
        domain master = Yes
        dns proxy = No
        wins support = Yes
#       config file = /opt/etc/samba/smb.conf
#       config file = /etc/samba/smb.conf
        create mask = 0775
        force create mode = 0660
        force directory mode = 0775
        guest ok = Yes
        hosts allow = 127.0.0.1, 192.168.
        hosts deny = 0.0.0.0/0
        default case = upper
        case sensitive = No
        map system = Yes
# new from here as not defined in the previous SLUGs config
        obey pam restrictions = Yes
        pam password change = Yes
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        panic action = /usr/share/samba/panic-action %d
#       lock directory = /etc/samba/locks

#[ADMIN 1]
[Admin1]
        comment = access restricted
#       path = /share/hdd/data/
        path = /
        valid users = @administrators
        write list = @administrators

#[DISK 1]
#       comment = access restricted
#       path = /share/hdd/data/public/
#       valid users = @administrators
#       write list = @administrators

#[ADMIN 2]
[Admin2]
        comment = access restricted
#       path = /share/flash/data/
        path = /mnt/sda1/
        valid users = @administrators
        write list = @administrators

[Video]
        comment = public RO
#       path = /share/flash/data/video/
        path = /mnt/sda1/video/
        valid users = @administrators, @everyone
        write list = @administrators

[Music]
        comment = public RO
#       path = /share/flash/data/music/
        path = /mnt/sda1/music/
        valid users = @administrators, @everyone
        write list = @administrators

[Pictures]
        comment = public RO
#       path = /share/flash/data/pictures/
        path = /mnt/sda1/pictures/
        valid users = @administrators, @everyone
        write list = @administrators

#[DISK 2]
[Public]
        comment = public RW
#       path = /share/flash/data/public/
        path = /mnt/sda1/public/
        valid users = @administrators, @everyone
        write list = @administrators, @everyone

[Software]
        comment = public RO
#       path = /share/flash/data/software/
        path = /mnt/sda1/software/
        valid users = @administrators, @everyone
        write list = @administrators

[bd]
        comment = User bd
#       path = /share/flash/data/bd/
        path = /mnt/sda1/bd/
        valid users = @administrators, @bd
        write list = @administrators, @bd

[hw]
        comment = User hw
#       path = /share/flash/data/hw/
        path = /mnt/sda1/hw/
        valid users = @administrators, @hw, @wedo
        write list = @administrators, @hw, @wedo

[md]
        comment = User md
#       path = /share/flash/data/md/
        path = /mnt/sda1/md/
        valid users = @administrators, @md
        write list = @administrators, @md

[od]
        comment = User od
#       path = /share/flash/data/od/
        path = /mnt/sda1/od/
        valid users = @administrators, @od
        write list = @administrators, @od

[so]
        comment = User so
#       path = /share/flash/data/so/
        path = /mnt/sda1/so/
        valid users = @administrators, @so
        write list = @administrators, @so

[ssd]
        comment = User ssd
#       path = /share/flash/data/ssd/
        path = /mnt/sda1/ssd/
        valid users = @administrators, @ssd
        write list = @administrators, @ssd

[td]
        comment = User td
#       path = /share/flash/data/td/
        path = /mnt/sda1/td/
        valid users = @administrators, @td
        write list = @administrators, @td
Thus I shut down samba on the NLSU and copied the files to the Plug

  scp share:/opt/etc/samba/*.tdb /var/lib/samba/.
  scp share:/opt/var/samba/*.tdb /var/lib/samba/.

Replaced the smb.conf on the Plug

  cp /etc/samba/smb.conf.new /etc/samba/smb.conf

Shut down the NSLU and attached the external USB-HDD to the Plug

  mount /dev/sda1 /mnt/sda1

and started nmbd and smbd on the Plug.

Hurrah! Me as user od (also in group administrators) can access all Shares as expected.

Woke up my daughter's PC from hibernation (she was logged-in already) and yes. Her drive Z: mapped to \\share\md is still there and accessable.

She can also see all other shares, but as expected she can only access the ones defined as such
 
Now the sad part starts: logged her off, but when rebooted and trying to logon again I got a message that some permissions may be wrong and that I should contact the admin (but the h**l, I'm the bloody admin and I have no clue ;-))

Nevertheless the logon continues and Z: is mapped as it should be, but as something isn't working as it should be I had to revert to the old setup and fire off the NSLU again ...
139  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 13, 2009, 04:49:27 AM
OK, set
  lock directory = /etc/samba/locks
in smb.conf.

However still struggling and curious why pdbedit -Lv just returns the info about the user nobody.

Created a new user to find out if i) he gets inserted and ii) which files are going to change.

Hence, the file sits in /var/lib/samba/passdb.tdb

though the follwoing pathes are specified

  smb passwd file = /etc/samba/passdb.tdb
  config file = /etc/samba/smb.conf

and "smbd -b | grep -i dir" says:

   SRCDIR:      /build/buildd/samba-3.3.2/source
   BUILDDIR:    /build/buildd/samba-3.3.2/source
   SBINDIR: /usr/sbin
   BINDIR: /usr/bin
   SWATDIR: /usr/share/samba/swat
   LIBDIR: /usr/lib/samba
   MODULESDIR: /usr/lib/samba
   LOCKDIR: /var/run/samba
   PIDDIR: /var/run/samba
   PRIVATE_DIR: /etc/samba

Lost! Am I using a wrong/outdated doc? (http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#tdbdocs) or are pathes returned by smbd wrong?
140  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 12, 2009, 08:17:33 AM
Ups, though I think this didn't caused the issue as I didn't reboot after copying over the files, yet

But I noticed that re fstab /var/run is tmpfs_

varrun /var/run tmpfs rw,nosuid,mode=0755 0 0

Shouldn't I either

i) mount /var/run to the SD card
 or
ii) change the default LOCKDIR /var/run/samba compiled into the default Ubuntu Samba to another path on the SD
?!?
141  Linux Stuff / General Linux questions / Re: Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 12, 2009, 07:30:47 AM
I tried to move from the NSLU to the Plug yesterday but without success.

I manually recreated all - except some empty "Shema Admin" etc. groups and users with adduser / addgroup on the Plug (same uid/gids).

Further I stopped samba on the slug and copied the files from PRIVATE_DIR: /opt/etc/samba and LOCKDIR: /opt/var/samba to the plug PRIVATE_DIR: /etc/samba and LOCKDIR: /var/run/samba
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#tdbdocs

Thou I could access the public shares I couldn't access e.g. my users share even for read.

And I noticed that rather seeing all user accounts I just find root@Share:~# pdbedit -Lv
---------------
Unix username:        nobody
[...]

still struggling ...
142  Linux Stuff / Linux distributions / Re: Question Kernel Update on: October 12, 2009, 07:15:38 AM
just as a follow up - I further changed the bootargs parameter slightly back to

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw

as though booting from SD I need some delay for my usb-drive to be recognised and to show up as device /dev/sda1 (for mounting it via fstab)

and though "nand_mtd" boots the "orion_nand" works as well and as don't know what difference it makes I'll stick with the recommended version ;-)
143  Linux Stuff / General Linux questions / Re: What's the best way to backup my current setup. on: October 11, 2009, 01:12:16 AM
Quote
I'm sure someone has this figured out.

no, not really, thou I'm following another concept. My intention is to have everything running from an SD card, thus the NAND config just to be a fall-back. IMO this at least has two advantages:

i) you could still use your approach for a backup, as it doesn't make difference if the it's coming from NAND or SD!?
ii) it's esier to make regular images from an SD card
iii) you can have several SD cards with builds going into different directs which can be scratched easily to start over again.
144  Linux Stuff / General Linux questions / Proper way to migrate samba pdc from unslung NSLU to Sheeva? on: October 10, 2009, 05:59:52 AM
Hi folks,

so far I use a unslung Linksys NSLU2.0 with a pen drive for the rootfs and an external HDD for my smb/cifs shares.

It acts as a file sharing device and as the primary domain controller to my hand full of Windows XP Prof systems and my family and a few others (<10) roaming accounts.

I now want to replace the NSLU (unslung 6.3, samba 3.2.15) by the Sheeva Plug (kernel 2.6.31.3, samba 3.3.2), but the more I read at the samba site or other forums the more I get confused how to plan a proper migration.

Hopefully you can give me some suggestions. I'll try to give a brief insight into the current setup and my thought which make me struggle.

i) while I have to migrate anyway would it wise to move from PDC to AD (e.g. Vista W7)?
  (or should I have this done in two steps (PDC_nslu -> PDC_sheeva -> AD_sheeva)
ii) the Ubuntu uses shadow files (which the NSLU doesn't - how do I migrate my users (' pwds)?
iii) how should the "adduser" etc. scripts be adjusted
  (should I add the former gids and uids manually to the plug)
iv) can I work with "net rpc vampire"?
  (will it set the actual user pwds?)
v) should I expand the new smb.conf with the "pam" related stuff?
...

Here's how my actual global section looks like
Code:
[global]
workgroup = MyDomain
server string = Linksys NSLU2.0
#new config should be: server string = SheevaPLug
interfaces = 127.0.0.1/24, a.b.c.d/24, ixp0, lo
#new config should be?: interfaces = eth0, lo
bind interfaces only = Yes
map to guest = Bad User
null passwords = Yes
smb passwd file = /opt/etc/samba/passdb.tdb
#new config should be: smb passwd file = /etc/samba/passdb.tdb
passdb backend = tdbsam
guest account = guest
username map = no
log level = 1
max log size = 10
name resolve order = wins bcast
socket options = TCP_NODELAY SO_KEEPALIVE SO_SNDBUF=16384 SO_RCVBUF=16384
load printers = No
add user script = /opt/bin/adduser -H '%u'
#new config should be?: add user script = /usr/sbin/adduser '%u'
delete user script = /opt/bin/deluser '%u'
#new config should be?: delete user script = /usr/sbin/deluser '%u'
add group script = /opt/bin/addgroup '%g'
#new config should be?: add group script = /usr/sbin/addgroup '%g'
delete group script = /opt/bin/delgroup '%g'
#new config should be?: delete group script = /usr/sbin/delgroup '%g'
add user to group script = /opt/bin/addgroup '%g' '%u'
#new config should be?: add user to group script = /usr/sbin/addgroup '%g' '%u'
add machine script = /opt/bin/adduser -s /bin/false -h /dev/null '%u'
#new config should be?: add machine script = /usr/sbin/adduser -s /bin/false -h /dev/null '%u'
domain logons = Yes
os level = 33
preferred master = Yes
domain master = Yes
dns proxy = No
wins support = Yes
config file = /opt/etc/samba/smb.conf
#new config should be: config file = /etc/samba/smb.conf
create mask = 0775
force create mode = 0660
force directory mode = 0775
guest ok = Yes
hosts allow = 127.0.0.1, 192.168.
hosts deny = 0.0.0.0/0
default case = upper
case sensitive = No
map system = Yes
#should this below be added to the new smb.conf on the plug?
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
panic action = /usr/share/samba/panic-action %d

I noticed that my users' accounts are all in the same group gid 501 on the Slug, but that every machine has it's own uid = gid!?
145  Linux Stuff / Linux distributions / Re: Question Kernel Update on: October 03, 2009, 01:33:50 PM
hmm, tweaking a bit it works now, though I don't know what made the trick :-(

as far as I can tell I used the guideline http://plugcomputer.org/plugwiki/index.php/Install_Prebuilt_Kernels_From_sheeva.with-linux.com to update the kernel in my two plugs' NAND to 2.6.31.1.

though I made no [1] changes to the bootargs_sd parameter
Code:
bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000
bootcmd=run bootcmd_sd; run bootcmd_nand

[1]: (removed rootdelay=10 thou it work before already; and /uImage is symlink to /sheeva-2.6.31-uImage on the first small ext2 partition)

it now also boots the kernel and rootfs from the SD card :-)

Code:
debian login: root
Password:
Last login: Sat Oct  3 22:13:56 CEST 2009 on ttyS0
Linux debian 2.6.31.1 #2 PREEMPT Wed Sep 30 18:47:19 MDT 2009 armv5tel
[...]
root@debian:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p2          964532    462796    452740  51% /
tmpfs                   256692         0    256692   0% /lib/init/rw
varrun                  256692       260    256432   1% /var/run
varlock                 256692         0    256692   0% /var/lock
udev                    256692       116    256576   1% /dev
tmpfs                   256692         0    256692   0% /dev/shm
/dev/mmcblk0p1            7745      2763      4582  38% /boot
tmpfs                   256692         0    256692   0% /var/cache/apt
root@debian:~# ls -al /
total 81
drwxr-xr-x 21 root root  4096 Oct  1 02:56 .
drwxr-xr-x 21 root root  4096 Oct  1 02:56 ..
-rw-r--r--  1 root root     0 Sep 13 17:40 This.is.SD
drwxr-xr-x  2 root root  4096 Sep 11 23:24 bin
drwxr-xr-x  3 root root  1024 Oct  3 22:04 boot
drwxr-xr-x 12 root root  3800 Oct  3 22:28 dev
drwxr-xr-x 60 root root  4096 Oct  3 22:28 etc
drwxr-xr-x  2 root root  4096 Dec 23  2008 home
drwxr-xr-x 12 root root  4096 Oct  1 02:56 lib
drwx------  2 root root 16384 Sep 13 16:00 lost+found
drwxr-xr-x  2 root root  4096 Jan 19  2009 media
drwxr-xr-x  3 root root  4096 Sep 13 18:58 mnt
drwxr-xr-x  2 root root  4096 Jan 19  2009 opt
dr-xr-xr-x 63 root root     0 Jan  1  1970 proc
drwxr-xr-x  5 root root  4096 Oct  3 22:03 root
drwxr-xr-x  2 root root  4096 Sep 13 19:29 sbin
drwxr-xr-x  2 root root  4096 Nov 13  2008 selinux
drwxr-xr-x  2 root root  4096 Jan 19  2009 srv
drwxr-xr-x 12 root root     0 Jan  1  1970 sys
drwxr-xr-x  5 root root  4096 Sep 12 18:36 tmp
drwxr-xr-x 15 root root  4096 Nov 13  2008 usr
drwxr-xr-x 13 root root  4096 Dec 23  2008 var
146  Hardware and U-Boot firmware / Hardware / Difference in how formating an SD Card? on: October 02, 2009, 08:06:54 AM
All,

I want to have the (kernel and) filesystem running from an SD card. Beside keeping the logging volume low I was wondering if I have to care about e.g. the FS type and block size to maximise lifetime and IO performance.

So far I used ext2 for the kernel partition and ext3 for the FS, but didn't bother about fdisk chosing a block size matching the cards physics?

Lifetime is maybe not such important as (1GB) SDs are cheap anyway (having regular snapshops).
147  Linux Stuff / Linux distributions / Re: Question Kernel Update on: September 26, 2009, 01:21:49 PM
Ah sorry, when I wrote "I tried to follow the instruction in the readme" I ment that I set the parameters as instructed

# setenv mainlineLinux yes
# setenv arcNumber 2097

I also changed

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw

to

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw

What I didn't do was adding "rootfstype=jffs2" as I use the root fs as ext3 on the SD card!?
And I didn't saved the parameters (saveenv) as I didn't wanted to make the changes permanent, yet.

I just hit "boot" after I made the (temporary) changes. Or should I have used "bootm 0x8000000" instaed?

148  Linux Stuff / Linux distributions / Re: Question Kernel Update on: September 26, 2009, 05:00:34 AM
may I jump onto this train also, please.

Once sb has answered Bluesbird's question may I also ask for an answer to my related issue:

Re information provided in various threads/forums (thx!) I have successfully upgraded u-boot

Code:
U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19

and I was able to get the original kernel booting from an 1GB SD card (ext2 /dev/mmcblk0p1: /uImage.sheeva.040309; ext3 /dev/mmcblk0p2: root-fs).

Nevertheless I struggle to get the 2.6.31 kernel to run. I tried to follow the instruction in the readme and i think I adapted them from the use in NAND to my setup using an SD.
But when booting I only get a message saying something

Code:
Uncompressing Linux... done, booting the kernel.

but nothing further happens.

Below are my boot parameters which work with the 2.6.22.18 kernel. Maybe sb can give a hint how to modify those working with the 2..31.6 version, please.

Marvell>> printenv
Code:
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
serverip=10.10.0.2
ipaddr=10.10.0.1
cesvcid=ULULULULULULPPULULULULULDA
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:D8:11
run_diag=no
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
bootargs_nand=console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
bootcmd_nand_orig=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage.sheeva.040309; bootm 0x8000000
bootcmd=run bootcmd_sd; run bootcmd_nand
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0x100000@0(uboot)ro,0x0@0x100000(uImage),0x1ff00000@0x100000(rootfs)rw
bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
Pages: 1 ... 8 9 [10]