ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Trick LTIB into using custom Kernel


From: Stuart Hughes
Subject: Re: [Ltib] Trick LTIB into using custom Kernel
Date: Tue, 13 Apr 2010 08:36:11 +0100
User-agent: Thunderbird 2.0.0.16 (X11/20080707)

As Kevin said user/user works.

root/root should work unless it's been changed.  These accounts get
setup as defaults by the skell package.

check that rootfs/etc/{passwd,shadow} has these permissions:

-rw-r--r-- 1 root root 1743 2009-11-20 19:08 rootfs/etc/passwd
-rw-r--r-- 1 root root 1131 2009-11-20 19:08 rootfs/etc/shadow

Also look in rootfs/etc/passwd, the root account should look like this:

$ cat rootfs/etc/passwd | grep ^root
root:x:0:0:root:/root:/bin/sh

and rootfs/etc/shadow should look like this:
$ cat rootfs/etc/shadow | grep ^root
root:$1$$oCLuEVgI1iAqOA8pwkzAg1:11851:0:99999:7:::

address@hidden wrote:
> My problem was that I just replaced these files with my old custom
> files.  I merged the files and now it works.
>  ltib
> |-- config
> |   |-- platform
> |   |   `-- mpc5200
> |       |-- busybox.config
> |       |-- defconfig
> |   |       |-- linux-2.6.26-m9000.config
> |   |       `-- main.lkc
> |   `-- userspace
> |       `-- packages.lkc
> 
> Linux boots up on my target.  I used to be able to telnet into my target
> with username: root, password root.  Now, apparently, the password isn't
> root.  Do you know how the root password gets set?
> 
> Thanks!
> 
> 
> ----- Original Message -----
> From: "Stuart Hughes" <address@hidden>
> To: address@hidden
> Cc: address@hidden
> Sent: Monday, April 12, 2010 10:06:26 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [Ltib] Trick LTIB into using custom Kernel
> 
> The lzo spec file is here: dist/lfs-5.1/lzo/lzo.spec
> 
> How did you do the cvs update? maybe you had pending changes of your own
>  blocking the update of packages.lkc?
> 
> You need to make sure you have the latest from Savannah merged in. Check
> your status with:
> 
> $ cvs -nq up
> 
> Anything marked with an M means you have local changes
> Anything marked with a C is a conflict.
> 
> The likely candidate for not showing up in the configuration screen in
> config/userspace/package.lkc
> 
> If you find you have a local changes, then move yours aside (mv x x.sav)
> then do a cvs up and the do a diff to find out whether there are local
> changes in your .sav that you want to keep.
> 
> Regards, Stuart
> 
> address@hidden wrote:
>> I did install the latest from Savannah.
>>
>> If I do: ./ltib --configure/ Package list --->
>> lzo is not in the list.
>> [ ] lkc
>> [ ] ltp : Linux Test Project
>> [ ] lmbench
>> [ ] lrzsz
>> [ ] m4
>> [ ] madplay
>> [ ] make
>>
>> But if I do: ./ltib -m listpkgs
>> lzo is listed
>> lzo-2.03-0               lzo                         n    GPL        
>> LZO is a portable lossless data compression libr
>>
>>
>>
>> ----- Original Message -----
>> From: "Stuart Hughes" <address@hidden>
>> To: address@hidden
>> Cc: address@hidden
>> Sent: Monday, April 12, 2010 9:38:07 AM GMT -05:00 US/Canada Eastern
>> Subject: Re: [Ltib] Trick LTIB into using custom Kernel
>>
>> I thought you updated to the latest from Savannah? this has lzo wired
>> in.  Your easiest path to success is to update to the latest Savannah
>> copy of CVS.  It's not enough just to grab the spec file, you also need
>> the entries in pkg_map and packages.lkc
>>
>> address@hidden wrote:
>>> Hi Stuart,
>>> I very much appreciate the help!
>>>
>>> The host side is all fine. The problem is with the target compilation
>>> of mtd-utils.
>>>
>>> zlib looks like this: --- zlib
>>> But lzo is not in the list anywhere.  It is also not in the list in my
>>> original installation.  Maybe something has changed since it was first
>> done.
>>>
>>> I suppose I need to put an lzo.spec file in: ltib/dist/lfs-5.1/
>>>
>>> How should I find the right spec file?  (I don't know how all the spec
>>> files got there in the first place.)
>>>
>>> Thanks!
>>>
>>>
>>> ----- Original Message -----
>>> From: "Stuart Hughes" <address@hidden>
>>> To: address@hidden
>>> Cc: address@hidden
>>> Sent: Sunday, April 11, 2010 6:40:45 AM GMT -05:00 US/Canada Eastern
>>> Subject: Re: [Ltib] Trick LTIB into using custom Kernel
>>>
>>> That header comes from lzo, it should only be needed when building for
>>> the target, for the host it should use an older version of mtd-utils
>>> that does not require this.
>>>
>>> Is this a failure building the host support packages or has it got past
>>> that stage?  (e.g. come out of the redirecting to host_config.log)
>>>
>>> If the failure is building the host support packages, then check that
>>> the package that is being built is mtd-utils-20060302 (look in the
>>> host_config.log for "Processing: mtd-utils-20060302"
>>>
>>> If this is not set, make sure you have the file
>>> config/platform/host/pkg_map which contains:
>>> PKG_MTD_UTILS = mtd-utils-20060302
>>>
>>> If this is a target package build failure, then make sure that lzo is
>>> selected.  It should be automatically if you have run ./ltib -m config
>>> (or --configure).  Also make sure zlib is selected.  To make sure run:
>>> ./ltib -m config and make sure lzo and zlib are selected:
>>>
>>>        [ ] lrzsz
>>>        --- lzo
>>>        [ ] m4
>>> ....
>>>        [ ] zaptel
>>>        --- zlib
>>>
>>> Note the --- indicates it's been selected by another package.  If this
>>> is not set, manually select with the space bar.
>>>
>>> Regards, Stuart
>>>
>>>
>>> address@hidden wrote:
>>>> Beautiful!
>>>>
>>>> A lot is going well but now mtd-utils is failing because it can't find a
>>>> header file.  Anybody know what to do?
>>>>
>>>> gcc -I./include -DWITHOUT_XATTR -O2 -g -Wall -c -o compr_lzo.o
>>>> compr_lzo.c -g -Wp,-MD,./.compr_lzo.c.dep
>>>> compr_lzo.c:29:23: *error: lzo/lzo1x.h: No such file or directory*
>>>> compr_lzo.c: In function 'jffs2_lzo_cmpr':
>>>>
>>>> Failed building mtd-utils
>>>>
>>>> (running on Ubuntu 9.10, latest LTIB from Savannah)
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Kevin Wells" <address@hidden>
>>>> To: address@hidden, address@hidden
>>>> Sent: Friday, April 9, 2010 2:32:16 PM GMT -05:00 US/Canada Eastern
>>>> Subject: RE: [Ltib] Trick LTIB into using custom Kernel
>>>>
>>>>  
>>>>
>>>> You can copy your custom files into the Local package pool and it
>>>>
>>>> won't attempt to download the files. The LPP is usually at:
>>>>
>>>> /opt/ltib/pkgs. It looks like you'll need to start by downloading
>>>>
>>>> the 2.6.26.3 Linux tarball from kernels.org and place it in you LPP.
>>>>
>>>> Also verify all your patches are in the LPP.
>>>>
>>>>  
>>>>
>>>> thanks,
>>>>
>>>> Kevin
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>> *From:* address@hidden
>>>> [mailto:address@hidden *On Behalf Of
>>>> address@hidden
>>>> *Sent:* Friday, April 09, 2010 11:25 AM
>>>> *To:* address@hidden
>>>> *Subject:* [Ltib] Trick LTIB into using custom Kernel
>>>>
>>>>  
>>>>
>>>> I think I have found all the 'custom' LTIB files for my target.
>>>>
>>>>  
>>>>
>>>> The latest LTIB from Savannah configures with no errors. Host-side
>>>> config is good.
>>>>
>>>>  
>>>>
>>>> When LTIB runs, u-boot gets downloaded, patched, compiled OK.  When it
>>>> gets to the kernel, it tries to download a tar file from the GPP.
>>>>
>>>>  
>>>>
>>>> The problem is that the guy who set this all up got the kernel from
>>>> Pengutronix.  Which file in LTIB is directing the tool to download the
>>>> kernel tar file?  How can I trick LTIB into using a custom kernel?
>>>>
>>>>  
>>>>
>>>> Thanks!
>>>> .
>>>>
>>>> ERROR
>>>>
>>>> Processing: kernel-2.6.26-m9000
>>>>
>>>> =================================
>>>>
>>>> Build path taken because: no prebuilt rpm,
>>>>
>>>> Testing network connectivity for gpp
>>>>
>>>> OK GPP: is available
>>>>
>>>> Try linux-2.6.26.3.tar.bz2.md5 from the GPP
>>>>
>>>> http://bitshrine.org/gpp/linux-2.6.26.3.tar.bz2.md5:
>>>>
>>>> 13:55:49 ERROR 404: Not Found.
>>>>
>>>> Try linux-2.6.26.3.tar.bz2 from the GPP
>>>>
>>>> http://bitshrine.org/gpp/linux-2.6.26.3.tar.bz2:
>>>>
>>>> 13:55:50 ERROR 404: Not Found.
>>>>
>>>> Can't get: linux-2.6.26.3.tar.bz2 at ./ltib line 802.
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>> These seem to be the 'custom' files for my target
>>>>
>>>> patches
>>>>
>>>> |-- ltib
>>>>
>>>> |   |-- config
>>>>
>>>> |   |   |-- platform
>>>>
>>>> |   |   |   `-- mpc5200
>>>>
>>>> |   |   |       |-- busybox.config
>>>>
>>>> |   |   |       |-- defconfig
>>>>
>>>> |   |   |       |-- linux-2.6.26-m9000.config
>>>>
>>>> |   |   |       `-- main.lkc
>>>>
>>>> |   |   `-- userspace
>>>>
>>>> |   |       `-- packages.lkc  
>>>>
>>>> |   |-- dist
>>>>
>>>> |   |   `-- lfs-5.1
>>>>
>>>> |   |       |-- common
>>>>
>>>> |   |       |   `-- pkg_map
>>>>
>>>> |   |       |-- kernel
>>>>
>>>> |   |       |   |-- kernel-2.6.26-m9000.spec.in
>>>>
>>>> |   |       |   `-- kernel-common.tmpl
>>>>
>>>> |   |       |-- poco
>>>>
>>>> |   |       |   `-- poco.spec
>>>>
>>>> |   |       `-- u-boot
>>>>
>>>> |   |           `-- u-boot-1.3.3-m9000.spec
>>>>
>>>> |   `-- rootfs
>>>>
>>>> |       `-- sbin
>>>>
>>>> |           `-- hotplug
>>>>
>>>> `-- opt
>>>>
>>>>     `-- ltib
>>>>
>>>>         `-- pkgs
>>>>
>>>>             |-- drivers-i2c-chips-eeprom-add_write_support.patch
>>>>
>>>>             |-- kernel-2.6.26-m9000.patch
>>>>
>>>>             |-- mpc5200-add-ATA-DMA.patch
>>>>
>>>>             |-- mpc5200-add-pscuart-mctrl.patch
>>>>
>>>>             |-- mpc5200-dont_touch_xlb_pipelining.patch
>>>>
>>>>             |-- poco-1.3.3-dynamicanyholder.patch
>>>>
>>>>             |-- poco-1.3.3_datetimeformatter.patch
>>>>
>>>>             `-- u-boot-1.3.3-m9000.patch
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> LTIB home page: http://ltib.org
>>>>
>>>> Ltib mailing list
>>>> address@hidden
>>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> LTIB home page: http://ltib.org
>>>
>>> Ltib mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> LTIB home page: http://ltib.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib




reply via email to

[Prev in Thread] Current Thread [Next in Thread]